Page 1 of 1
Updated: Both timecode modes are broken in 3.5.2 (I'm wrong)
Posted: 18 Mar 2013, 01:27
by kittmaster
I followed the video using the real time with the clock, set the times, waited for the time to elapse....nothing happens.....
Its hard enough learning this software let alone when it isn't working.
Finally getting the moving heads almost right and now this......anyone know which version works the best? I can't stand this. I'm really getting frustrated.
Re: Both timecode modes are broken in 3.5.2
Posted: 18 Mar 2013, 02:12
by kittmaster
Ok well, maybe not, I got the real time going, I realized that it's using 24 hr time (should have realized that since no AM or PM > ....... newbie landmine).....I've yet to see the elapsed work yet.....I'll keep messing with it.......

Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 02:42
by kittmaster
Ok, I'm just having another moment......I figured it out.......but I am still having a problem.
I've attached my latest sequencing files for anyone to possibly help me out. I've got 4 cue button to show what my issue currently is. I have a green chase, blue chase and a blue/green and x-moves.....green and blue work on their own, but when I combine them into the cue, they run at the same time, and not in sequence as I want.
if i hit the x-moves, those work how they are supposed to, but you will see only one of the led par sequence color blue dominates and green never starts but runs at the same time as the blue in the cue. I can't use the "loops all sequences" because it screws up the x-moves......I need these to chase in sequence and have the movers work as they are set up......
Can someone give me an idea what I can do to fix this? Please download the file and try it.....I'm pulling my hair out over here........so close and yet so far away........
Thanks
Chris
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 10:24
by Mattotone
Your sequence file for blue, turns off all the green red and yellow par cans.
Edit your sequences you will see an orange star next to every fixture. This indicates they are included in that current sequence. If you select any fixture they are set to snap to zero.
Did you program as static? try re programming i transparent mode, this will only include the fixtures / channels that you change in the step.
#TIP in each step set the channels to the value it needs to be even if you just set it in the last step, if you don't it wont be included in that step and the sequence will not behave as expected. E.G fixture one set to red in step one, in step two you will need to set it to red again to ensure it stays red in step two.
The idea of the cueLists is to load and play all the cues in that list. so it is working as designed.
Maybe I'm biased but to complete what you want to do try GoMonkey theatre cue stack, its something else to learn but its the most flexible cue List on offer.
For the example you will need to move your cans and xmoves sequences out of there folders as goMonkey doesnt support folders
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 12:59
by kittmaster
Yes, I programmed them in static as I was having issues, I'll try transparent again and see what happens.....thanks for the feedback...... I'll let you know how it goes.
Chris
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 14:19
by kittmaster
I've tried the transparent mode originally, what I find is that when the scene switch, it leave the LAST par of the LAST sequence ON. I need it to chase the color pattern, and when it switches, turn off all the old sequence and start the new. That is why I went static, but clearly that is problematic too......I really don't want to use a third part app, I really want to get this running in freestyler alone........ I did look at your example though.....thanks for that, if I go that route, I'll use it as a baseline..........
Any thoughts to what I mentioned above?
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 16:30
by Mattotone
You need to set restore values in the cue switcher. So when you stop the sequence they all switch off. In transparent mode you need to specify what is on or off in each step.
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 16:37
by Mattotone
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 19:14
by kittmaster
Ok I'm convinced.......can go monkey be hooked into the visualizer to see how the chases and such will look when in operation mode?
How does it know to talk to my enntec pro?
I guess that is the part i don't understand......I watched the video, your taking the chb files and stacking them and ordering them, sounds like just what I want.....
Does freestyler have to be open to use it?....
Tell me about the operation, that is the way I think I want to go......
TY!
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 19:39
by Mattotone
Go Monkey is an addon to Freestyer, its main purpose is to load sequences in the right order and play them at the right time.
You still make your sequence files in Freestyler, Its still Freestyler that plays them back its just be directed by the GoMonkey. The visualiser will still work as well as all the other functions such as overrides blackout etc.
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 19:56
by kittmaster
Oh snap that is sweet......I'll give it a whirl tonight when I get home. Are there any settings to worry about getting corrupted or are you given some type of back door API access that makes it work?
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 20:37
by Mattotone
No it communicates via the Api given by the developer of Freestyler 100% legit.
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 22:01
by kittmaster
Ah ok, so no worries going forward, very nice......thanks for the responses.
Chris
Re: Updated: Both timecode modes are broken in 3.5.2 (I'm wr
Posted: 18 Mar 2013, 23:18
by kittmaster
posted in your dev thread...app crashes