no idea. you either have to share show file or video showing all settings. LTP control mainly applicable to all attributes with ranges such as Pan and Tilt, CMY, Zoom, iris etc
Hi, and thank you for the great tutorials you done! I try this way and working everything perfect by the initial shutter open in the beginning of the range I want, stored in a cue, to the final shutter range in another cue controlled by fader on ltp channels....ok work perfect.... Now I record a second cue in the same cue stack of shutter fader because I want activate a macro during a strobo all...for example... I have first Go: all strobo and second Go: all strobo that trigger a macro that activate a another cue that change withe colors for all fixture during strobo all... But at second Go fader no work nevermore till I relase and activate strobo cue stack again. I try by copy cue or record again or tracking only ltp or nobody...but same problem. Can you help me please😅... thank you!!!
Do I understand correctly that: the LTP cue you built and assigned to the fader, is setting the highest value that is desired in the range of that slider's motion? And the net effect is that the effective range of that fader is from the 005 established in the Special Cue (or head personality) up to the 114 set in the LTP cue.
Pretty much, but in general, it goes from either default or active data from active cue/playback. So if your “destination” of the movement is at front of the stage, then and active PB sets position of head Audience High, then moving fader up will be moving heads from up to down as your fader moves.
Also I noticed when I use my midi controller as a fader in the executed window, the fader will go through the range I set a few times correctly, but the more I use it the less range the fader will go through until it just does no range…
please note, PB's settings such as LTP control instead of HTP etc etc - are blocked out of Midi/OSC and other 3rd party protocols. and as Exec fader is mimicking PB and it's settings, maybe that's why it may work in the beginning and then stop working altogether. sadly I cannot test it at this moment
How come when I try this with other attributes the position of the attribute stays static when I move the fader?
no idea. you either have to share show file or video showing all settings. LTP control mainly applicable to all attributes with ranges such as Pan and Tilt, CMY, Zoom, iris etc
Hi, and thank you for the great tutorials you done! I try this way and working everything perfect by the initial shutter open in the beginning of the range I want, stored in a cue, to the final shutter range in another cue controlled by fader on ltp channels....ok work perfect....
Now I record a second cue in the same cue stack of shutter fader because I want activate a macro during a strobo all...for example... I have first Go: all strobo and second Go: all strobo that trigger a macro that activate a another cue that change withe colors for all fixture during strobo all... But at second Go fader no work nevermore till I relase and activate strobo cue stack again. I try by copy cue or record again or tracking only ltp or nobody...but same problem. Can you help me please😅... thank you!!!
Do I understand correctly that: the LTP cue you built and assigned to the fader, is setting the highest value that is desired in the range of that slider's motion? And the net effect is that the effective range of that fader is from the 005 established in the Special Cue (or head personality) up to the 114 set in the LTP cue.
Pretty much, but in general, it goes from either default or active data from active cue/playback.
So if your “destination” of the movement is at front of the stage, then and active PB sets position of head Audience High, then moving fader up will be moving heads from up to down as your fader moves.
So in that case its not from default, but active PB’s data
Also I noticed when I use my midi controller as a fader in the executed window, the fader will go through the range I set a few times correctly, but the more I use it the less range the fader will go through until it just does no range…
please note, PB's settings such as LTP control instead of HTP etc etc - are blocked out of Midi/OSC and other 3rd party protocols. and as Exec fader is mimicking PB and it's settings, maybe that's why it may work in the beginning and then stop working altogether. sadly I cannot test it at this moment