Veit0r

Okay, I think i'm able to do it now. To be honest, its not clear to me why I have to disable smart tag before recording the new default. Move on dark was completely ignored from me because... no stepper motors The real blocker while all the testing was: I had the "Show Record & Update Window" set to External display, but closed the external display view since the real console has no display output. So I never saw the SmartTag Setting and had to google after you mentioned it how to get it. I just made the defaults in the "real" file for all the fixtures and reenabled the SmartTag again to be able to "easily" create new cues without having to tag all the channels. I will try it on real hardware as soon as possible and let you (and reddit) know. Thanks again! PS: The SmartTag topic just unlocked some SGM Pilot3000 memories in my mind...

Hm.. okay! I just tried it in phantom, I think the one thing I didnt get was: when selecting the colors & intensity for the default value the buttons have to be black not blue. This feels very unintuitive for me. However after changing the values and "deselecting" them before recording to the default via home button my first test playback works as I expect. The bad thing is, I cant get another color playback to work.. it simply ignores my settings and does nothing. I'll play around and let you know. I swear, i tried the process at least 5 times and it worked on the last attempt when tapping the values to black background. I will start from scratch again with the file I sent to really understand it. Thanks for your help already!

Hi, thanks for your attempts and quick answers attached the showfile. On Playback fader 13 there is one cue. If you raise it, and lower it again, you can see channels 4 and 5 going to 255. raiseandlowerplayback13.zos

Hi, I already did a post on reddit but it didnt get me any further... I have the problem that my LED fixtures (in this case some ROXX eShow TW+ and SGM P5s) switch back to RGB Values 255,255,255 when the trigger release threshold is triggered. You can see it in the Video attached to the reddit post. I recreated the whole thing in PhantomZerOS and brought it down to a simple one fixture, one cue setup after a factory default but cant still fade a color cue out without a flash to white at the end. I reset the desk completely to factory defaults. one fixture, one cue with color red. cue fade times (the play/pause button) are all set to zero. global fade times and defaults are also on zero (setup->defaults->default cue times) I set the home and default values of the one fixture to color 0,0,0 (selecting the channel/fixture set the three color rotaries to 0, make sure they're highlighted blue->Update->home with bulp icon->home and then the same with default. Still, my created cue (or a new one based on the set defaults) with just the color red works and goes to 255,255,255 when it reaches the trigger/release level. I can see it in the DMX Output window by pressing Z Button. If I got it right, if those were the defaults, they would show up in yellow in the output, but they're shown blue. Where do those values come from? I also tried editing the default values via the fixture editor on the console, also without the desired effect. I just want to fade simple color cues with different faders without any flash(fast or slow) to white below trigger/release level. Setting the trigger/release to 0 doesnmt work either. Please help! I went through the documentation, videos and reddit. I spend many hours, what am I doing wrong here with such a simple cue?