Latest news

[aussiephil]

KC

Many Thanks for the update, it's good to hear something, so many people thought it had all died.... considering the amount of work that's gone into this as a re-write the silence is not surprising.

Cheers and best wishes
Phil

[KC]

Hey KC, how did the toilet fix turn out?

The flapper is clean and smooth, the seat for the flapper is clean and smooth...I am officially flummoxed. And down half a day-off for it.

Knowing KC, he'll just blame it on the hardware.

Hey, that doesn't mean it's not the hardware. Even a stopped clock is right a couple times a day. And besides, I'm a software guy; it's practically in my job description to pass the buck.

[KC]

...so many people thought it had all died....

Really? Man, I'm glad I said something. I mean, you all should know better, but when you're left with nothing being said for so long, it's not exactly a far-fetched conclusion.

[aussiephil]

Really? Man, I'm glad I said something. I mean, you all should know better, but when you're left with nothing being said for so long, it's not exactly a far-fetched conclusion.

I'm glad you said something too, though even then i've had to convince a number of people that what you have said is a very positive indication of progress. During June and July Australia will have FIVE major "mini's" Melborne, Adelaide, Perth, Brisbane and Sydney and i believe some form of Vixen3 demo has been scheduled for each, but at least one organiser is now concerned that the differences between the original beta and the new may be too great and has talked of pulling the demo.

My brief look says it is not but the now missing effects from the sequencer put a large dint in demo ability.

Whilst it will now doubt happen when you get the full setup for builds etc running, in the mean time is there any chance of a Build Number as part of the ZIP file name so we know when to download a new build?

Cheers
Phil

[KC]

...in the mean time is there any chance of a Build Number as part of the ZIP file name so we know when to download a new build?

That is the plan. Also email notifications, but the continuous integration isn't yet put together.

I know that there are three effects that we had in the previous demo that aren't there currently -- chase, spin, and twinkle. They're coming. Will their presence be enough for the jeopardized presenters to carry through with their presentations?

There are a couple of things in there that may aid them too. Fire me an email and we can hash this out offline.

[aussiephil]

That is the plan. Also email notifications, but the continuous integration isn't yet put together.

I know that there are three effects that we had in the previous demo that aren't there currently -- chase, spin, and twinkle. They're coming. Will their presence be enough for the jeopardized presenters to carry through with their presentations?

There are a couple of things in there that may aid them too. Fire me an email and we can hash this out offline.

Email sent, thanks.

cheers
Phil

[aussiephil]

Hi KC and team,

Thanks for 3.0.1.1 and the effects added back in. All the configuration screens and boxes seem to work correctly on the effects and you can add them to a sequence without issue.

Got a preview window up and running and in the absence of actual E131 output (all i really use these days) based on the preview window the chase effect may not be functioning as i expect.

Is the bug tracker up and running or should i just leave this with you to check the code out, maybe expectation is different to intent.

the RGB property seems to be missing at the moment as well.

Should we have a general feedback thread to stop the clutter.

Thanks for the hard work KC and all as always

Cheers
Phil

[KC]

I thought I had that chase working the same as it was in 3.0.0. What are you seeing that's different?

[aussiephil]

KC,
Went back and checked.
Setup:
50 Nodes grouped into a single node group.
8 second chase, set to bounce back and forward with a RGB gradient set to apply to whole effect.

in 3.0.1.1
What i see is the 50 nodes have the gradient applied over the time period but the nodes don't chase.

in 3.0.0.0
The 50 nodes would chase back and forward with the gradient applied over time.

Interpretation:
The chase effect is being applied at the group level only.

Now this is a priority/parent/child problem that the team may already in hand but for say a pixel megatree i may want a chase to occur at different group levels. IE... on a per node basis, a per string basis or across a group of items.
Taking that a logical step further, to be able to have a chase applied at the node level and a separate overlaid chase applied at the string level could be very very powerful.

Cheers
Phil

[KC]

You may have to explain this to me further. I attached a screenshot of what I think you're saying, as far as the config for the effect. Doing this, the result I see is a chase down followed by a chase up; the color of each changing from red to green over the span of the whole effect.