Bezier Shapes Pan/Tilt corrupted in cues

[blackeyed28]

hello,
i have an issue that i can't seem to figure out.

i've created sequences like this:

scanners_move -> a sequence containing all the shapes with a 6s step (with only pan/tilt turned to fade)
scanners_color -> a sequence contains all the colors in the gobos with 3s step (with only color turned to snap)
scanners_on -> a sequence that turns the lamp of the scanner on. (with only dimmer turned to snap)

i created a cue with all 3 of these, and it worked great. i followed this technique for all of my lights (colorstrips, tri-pearls, etc). i also created specific sequences like scanners_colorDark, which only contained dark colors, ..and scanners_moveSlow, which contained slow moving sweeps. the idea is that i can quickly put whatever i need into a cue window and save the cue and add it to a button. it was working well, and then the bezier shapes just stopped working (in a saved cue window with many sequences).

inside my cue window, where i have several of these sequences, i started manually hitting the play button, starting with the scanners_move, to see if one of the other sequences was overwritting my pan/tilt by accident. a couple of them were. one was just a 1 step sequence that turned my front lighting on. it did nothing but send a RGB value. i redid it, and again, it would kill the pan/tilt of my scanners (setting both values to zero). i tried everything, ..creating more steps in the front lighting sequence, ..but i just kept getting strange results... like the 1st shape of my scanners works, ..but then they stop until it rotates back around to my 1st shape again.

i'm really confused. i have some moving head's, and they were causing my scanners to stop moving also, ..so i pulled them from my cue list. i've recreated those sequences from scratch 5084590843 times to make SURE i'm not writing values in the pan/tilt of my scanners.

btw, i was testing via the actual fixtures, ...but it is also occuring in the output dmx window.

any ideas ? i tried searching threads and i found one thread, but no answer.

thanks!

[blackeyed28]

UPDATE

after playing with it for awhile, ...i found a workaround.

if you have a sequence with bezier shapes in a cue, make sure ALL other squences in that cue have the same number of steps (or more). for some reason, say if you have a squence with 6 shapes / steps, ..and another sequence (for some other fixture) in the same cue with only 2 steps, only 2 steps of the shape sequence will work. just increase it up to 6 (or whatever the shape sequence has), and it seems to work.

hope that makes sense.

[djSupport]

"and again, it would kill the pan/tilt of my scanners (setting both values to zero)."

Im not sure if I read it wrong but theres an option 'snap' 'fade' and 'off' using off will ensure that lets say you have two sequence running one runs a scanner and a RGB parcan and the other just runs your scanner if the second has all the 'off' settings enabled for the parcan the scanner will now move the way it was programmed in the second sequence but the parcan will be playing as set by the first sequence

[remco_k]

^^ yep, that must be it.

Check all your other sequences, every step of them, to see if the pan/tilt channels are 'off'.
If not, then there's your problem. Set them off, and save the sequence.
Ofcourse the sequence that runs your pan/tilt operations should not be set to off while checking this.

[Mavi]

In addition: make sure sequences are programmed in "transparant mode".

[blackeyed28]

just FYI, i did go back and make sure all my sequences were in transparent mode, ..and they were. i was unaware of transparent/static modes until i searched through this forum looking for answers.

as far as the sequences over-writing pan/tilt, ...i made sure, and re-programmed them over and over to make for absolute certain the pan/tilt was turned to OFF. i really like the fact i can program sequences to control certain aspects of the fixture independently. in fact, i designed all of my sequences this way, ..so i was VERY careful about setting only the aspects i was programming.

based on my workaround, i figured it was a bug.

[djSupport]

if you think its abug submit it by clicking the link above ^^^^^^^^^^^^^

[blackeyed28]

yes, i'll submit it.

i'll be sure and work up exact steps to reproduce it when i submit it (should help out the developer).

thanks for replying. i'm loving freestyler and i appreciate the forum support!