kgallen

When you turn SmartTag off you are taking complete control of what parameters are tagged and thus recorded. In this case I’m selecting the fixture, modifying the colour attributes (which tags them - makes the background ‘blue’), then when I RECORD I turn off SmartTag which says ‘hey console I’m in charge I just want you to record the colour attributes I changed and nothing else, just do as I say and nothing more’. In the example of reprogramming defaults I agree it’s nothing to do with e.g. move on dark (this is just one example of where SmartTag usually helps the programmer), just by turning it off I’m in explicit control of what is recorded (and also In this case intensity was zero so SmartTag would have caused my colour parameters changes to be ignored). Note that the colour attribute is by default set as ‘not separate’ (changeable in Setup). This means that if you adjust one colour parameter e.g. red, all of the colour parameters are tagged as it’s assumed that you want to create a certain colour and this requires all colour emitters to be recorded to recreate that. If you really only wanted to record the red emitter you would need to manually untag the blue, green, amber, colour wheel etc parameters (to make their background ‘black’) so they weren’t recorded. When played back, only the red emitter would be controlled, the blue, green etc would stay as they were. This is very powerful but can also be very confusing for inexperienced/basic users. Note that beamshape parameters default to ‘separate’ as it’s assumed that if you were changing e.g. the zoom you didn’t also want to record e.g. the gobo. Some advanced programmers have SmartTag turned off permanently as they always want explicit control of what is recorded via tagging, especially if they are setting up a range of ‘partial looks’ on playbacks/submasters that they’ll use to busk with. If you’re programming a theatre stack then for many ‘normal’ users (myself included) SmartTag is usually on. Note also when looking at your showfile I did it in PhantomZerOS which I started in FLX mode (not FLX S mode as your actual hardware). This gives me access to some more features, like the Source screen. This allowed me to see (but we already ‘knew’) that your fixture was controlled by ‘Default’ as the fader was lowered. I selected the fixture so I could see the parameters details, then on the Source screen I saw the colour parameters change to ‘D’ (and also saw the flick of B=G=255 in the DMX window) as I lowered the fader. Aha! Default is white (as we expected) and causing that flick in colour as you first reported. Reprogramming the default to R=G=B=0 was easy after that. Happy programming - let us know how you get on and any other questions and we’ll try to help.

@Veit0r when adjusting values you want the background of the field above the encoder wheel to be blue not black. Blue means the parameter is tagged. This is the information the console uses to know what to record - it records tagged values. If you click the field to make it have a black background you untag it. The console will then not record the change. Also in the case of reprogramming the default I turn off SmartTag. This is because I wanted to reprogram the RGB default values whilst I had the intensity at zero (and not tagged). SmartTag will only record intensity (at zero) if intensity is zero, it won’t record other tagged parameters (this is related to allowing Move On Dark to work). Hope that clarifies things and you can now have more success with your programming! https://www.zero88.com/manuals/zeros/controlling-fixtures/tagging

@Veit0r can you try this showfile please. I just reprogrammed the default for that fixture to R=G=B=0 (Process: Clear-Clear, select the fixture, make R=G=B=0, tap RECORD, turn off SmartTag, tap HOME, select Default). If I play on PhantomZerOS, whereas with your showfile I see the G and B flick to 255 in the DMX window when lowering the fader, this doesn't happen with the showfile attached below. raiseandlowerplayback13mk2.zos Regards, Kevin

Created for a BlueRoom member for his Fat Frog. No action required. Posted here for other users if required. Note: There are also a couple of versions of this in the GFT41 library. 11, 6, 3 channel modes (40ch mode not coded). WashFXHex.ift

Thanks @Davidmk. I’m home very late due to needing to take a 60+ mile detour to get home (don’t ask… Highways Agency, I mean you…). I’ve read the whole of that other thread again. Wow, that was a corker, I seem to have blanked that one out! In the Reddit discussion, for me it comes down to default of white maybe with a bit of release on lower config thrown in to confuse things more. @Veit0r sorry it will be tomorrow earliest before I can take a look on my FLX (at least you have an FLX S unlike on the other thread). In the meantime if you’re able to try out some of especially @Davidmk‘s suggestions hopefully you will beat me to a solution…

Thanks @Veit0r I’ll try and take a look tonight.

(For background for other experienced users/contributors on here, I’ve tried to help out with this one on Reddit and it seems the issue still exists - any other ideas/what did I forget etc, thanks!). @Veit0r if you could save your showfile and upload it here we can try and debug on our own desks and try our best to understand what’s going on and get you a solution - as you showed on Reddit this can be seen in the output screen as DMX values actually going out to the fixture. Thanks for posting on here (and in the correct sub forum!) where we’ve a chance of reproducing the problem.

View+<master Go> or View+<button under a fader> will move you around to view each playback. https://www.zero88.com/manuals/zeros/cues-playbacks/cues-window

Press View+Master GO ?

I think your link was fine. When I tried it again it went straight to the right page. Phone browser weirdness maybe! with the manual I think you *have* to know it’s there somewhere. The Search just doesn’t work for me, it finds too much stuff and too much unrelated stuff…

When I tried David’s link it wouldn’t show the page as it thought the console was FLX S24. Posting this link just in case the above doesn’t work: https://www.zero88.com/manuals/zeros/palettes/advanced-palettes?filter=3

Loading a full showfile on the real console or into Phantom ZerOS should load everything, especially the patch!

Visualisation software is complex, it’s not easy to offer for free (unless it comes with a console that costs £20,000-plus). I’ve got a Capture Solo license. It integrates tightly with FLX consoles (bidirectional control). But the Solo license is about £300 I think. Track forward will apply the update you make to all following cues until a cue is reached where the fixture is given another instruction. e.g. - Fixture 7 is set to 50% in cue 4. Fixture 7 does not change until cue 12 where it gets set to 80%. Fixture 7 is currently tracking from cue 4 through cue 11 (cue 5 thru cue 11 will show in purple in the output window). - In cue 5 you do an update to fixture 7 to make it 60% and you track forward. The result is fixture 7 is still 50% in cue 4 but in cue 5 through cue 11 the new update value of 60% applies. In cue 12 fixture 7 goes to 80% as before. Hope that helps.

On S24/S48 many of the buttons are ‘soft’ at the top of the touch screen. To busk and avoid snaps in general, go into the Z screen and enable Programmer Time with the 5secs or whatever value you want. This video will be useful

SmartTag will record 0% intensity. That’s the one thing it definitely does. What it won’t do is record changes to other parameters at the same time. If you want to record other parameters changes (or the classic Effect Off) at the same time as the fixture goes to 0% then turn off SmartTag for that record operation - remembering to turn it back on for the next one (you can just hit record, turn it on then hit record again to clear the options box without actually recording anything).