V8 color,gobo and position chase problems

[hanman]

Today I upgraded v8.0 for my titan mobile...I find out that if I record pan/tilt or color or gobo chase, I get bouncing chase wich I can not control (xfade and speed) unless it is on speed 0, then it stops...only dimmer chase works fine..
v8 its pretty much useless for me right now because of this and i cand downgrade it on v 7.5 unless i format disk and reinstall windows....I have gig in 3 days...

[niclights]

I can't reproduce this.

If I start a new show, patch some fixtures with colour controls and make a colour chase by default it plays forward and I can control speed and xfade by wheel when they autoconnect.

Can you think of anything you might be doing differently?

If you can provide detailed steps to repeat from a new show that would be very useful.

[ciuf]

Do you really need to format windows to downgrade??

[hanman]

@ ciuf: I deleted v.8.0 using windows "unistall program" in control panel...reboot and start avolites PC suite 7.5 installer, then I get a lot of "xxxxxx version already installed" mesages and v 8.0 it's back...

@nic : select group, and press red color in color palletes, press all and then select 1in 4...then press white, record chase, 2x times playback button, red again and fixture + , and then I repeat this 4 times...result : bouncy chase..
select group and press color red in color palletes, record chase 2x times playback button, white color in color palletes and the I hit playback button of my chase playback fader... result: bouncy chase...
same for positions and gobos....
but If I do exactly same procedure for dimmer chase it works fine...I remember that i notice this problem few times also in v7.0 but after restarting software it was ok...so i didn't pay any attention to this..

I'm recording my chases since v3.5 and also from pearl 2004...

[niclights]

Hi,

I've looked into this in more detail and there appears to be a specific problem with using preset palettes in chases. Thank you for highlighting this. I have raised it for further investigation.

For now the workaround is to ensure you only use user created palettes. You can make new palettes by applying the values from the preset palettes but it is important to turn off 'record nested palettes', otherwise the new palettes will just reference the originals and still break.

[hanman]

jesus christ.....

tnx for now i'll try this first thing in the morning...

[icke_siegen]

I got the same thing reported by a colleague. Seems that under certain circumstances the cue timings are recorded wrongly - the cues default to delay/fade:0, instead of 'global'. At the moment, you can rectify this by opening the chaser times window, click the Delay Time column (and later repeat this for the 'Fade Time' column), and set it to 'Use Global' from the soft buttons.

@Nic: I'll also report this to Olie, just for reference