Archie D

Don’t apologise - life gets in the way sometimes! I hope they’ve managed to sort the intermittent fault out. My JesterML had a ribbon cable that looked like the legs of the components on the front panel had pierced part of it. On the Blue Room, I assisted someone else identifying an issue with their front panel on a Jester 24/48. Their ribbon cable was pierced too. Seems like it might be a common thing? But not sure. Possibly could be solved by carefully cutting the component leg just below the solder joint while leaving a little bit of leg left, shortening the spike. That way the ribbon cable hopefully won’t suffer.

Update time! The issue has been coming back intermittently. Rather late, but tonight I have just replaced the ribbon cable between the processor board and front panel with one which came out of my spare Juggler (has the same FC-26P connector). Will be monitoring how it does over this week and if the buggy LCD issue arises again. Will post progress on the issue.

Hi Zulu, No worries - fantastic to hear everything’s working as intended now. Best of luck with your show! Archie

Hi @Petera, The ADJ Jolt 300 is available in the ZerOS Fixture Library on the console, therefore you won't need to match the channels to another fixture in the library. Archie

Hi Brian, When a playback with values stored is raised or active while recording a cue, those values are stored into that newly recorded cue. You can circumvent this by disabling Smart Tag in the Record / Update Options window (tap RECORD or UPDATE, then tap again to exit - selection will be stored). When Smart Tag is disabled, values coming from other active playbacks will not be recorded in, preventing slip-ups. The source options at the top of the Update Options window are effectively a way of telling the console what things you want to update in a single operation. It can be added to via syntax, e.g. UPDATE (the cue I am currently in is automatically in the source options), AND 2 (adds cue 2 to the source options, to specify cues from other playbacks at the same time use Playback Number/Cue Number). This means the console will be updating both the cue I am currently in as well as cue 2 with the desired 'Remove' operation. You can tap various items in the source options area to exclude them or add them, indicated with red and blue stripes. Correct - the values would be stored inside the recorded cue within the main stack, therefore they need to be removed from the cue. To remove a fixture entirely from a cue, you can follow my listed steps in my earlier post but leaving out the un-tagging of Intensity. Go into the cue, simply home the fixture(s) to tag all parameters and then remove from the cue via Update. I hope this helps - if you have any queries or require further explanation feel free to ask. Archie

Hi Zulu, No worries, glad to hear the solution worked on Phantom ZerOS for you. To 'fix' an individual cue, repeating the steps listed would work perfectly. However, if you have a range of cues together which all have the same problem, you could attempt using Track Forwards in the tracking options along with 'Remove' within the Update Window, but be aware of potential blocked cues. If the values that cause the movement and colour change during the fadeout are tracked through to following cues, then Track Forwards will work alongside 'Remove'. You can alternatively use Cue Only in the tracking options within the Update Window and simply use syntax (UPDATE 3 THRU 7), which would apply the 'Remove' to all of those cues for tagged parameters. As the issue you're facing is rooted from information stored in cues, the cues themselves must be updated to remove that information. If you have any other questions, please feel free to ask. Archie

Hi @Zulu, It sounds as if the cue in which your fixtures fade out have position and colour information too. To let these fixtures fade out without any movement or colour changes, we need to remove that information from that cue. First, save a copy of your showfile so you can revert to it if needed (Z/Shift -> Save Show). Now select your problematic cue (the one to fade out the fixtures) and tap GO to proceed into that cue. Select your moving fixtures, then tap the Home icon (top left of the internal touchscreen). This homes & tags all parameters for the selected fixture(s). Now, we want to un-tag only the Intensity parameter so that the intensity of the fixtures still go to zero (e.g. that information is preserved), instead of previous values tracking through. To do this, tap the Z/Shift key, then tap 'Intensity' above the first encoder wheel - it should switch to have a dark background. That parameter is now un-tagged. Now tap the UPDATE key (you may have to hold it for the Update Window to appear on the internal touchscreen, this behaviour can be adjusted in SETUP -> Settings -> Record & Update), ensure 'Remove' has a red stripe (enabled) and Smart Tag has a blue stripe (disabled). Also make sure that 'Cue Only' has a red stripe so that we are only dealing with and affecting this cue. Tap your Master GO button to submit the update. You should now find that the fixtures fade out without changing position and colour. If you have any questions feel free to ask. Archie

Hi Simon, It is extremely unfortunate that Ian passed away, he is definitely missed. Regarding the wheels - there is a tiny PCB on each wheel held by four plastic clips (two latch over the PCB and two stick up through holes on the PCB). If this PCB comes out of those clips and slides out slightly, the contacts don't meet the wheel and so the wheel's movements are not read correctly. If you don't get anywhere with White Light as kgallen has suggested, and are confident with opening your Solution up (the front panel along with the palm-rest hinges up from the base to an extent) then it may be worth checking those PCBs. If all PCBs are seated correctly and the wheels still do not respond correctly, it would be worth looking into spares. Hope this helps.

Hi Edward, Apologies for the delay, things have been rather busy this end. Thank you for your advice - when things have calmed down a bit I will have a look into the BIOS instructions, thank you for the link. I'll let you know the outcome. Many thanks again, Archie

Hi Edward, Thank you for your reply, I really appreciate it. That probably explains why I can't get into it. I was looking for the Startup Tool to future-proof the desk in case I need to do a fresh software install to recover it as the desk currently isn't picking up any bootable USB sticks (have tried multiple, including the MBR method), neither is it picking up the software CD supplied with the desk. Since it was introduced for FLX S, am I correct in thinking it will only accept .exe upgrade files instead of a whole bootable USB? Many thanks, Archie

No worries, great to hear.

I'd recommend using ZerOS 8.0.1 for your next show as I believe ZOS-12594 is the bug fix for the crashing issue in ZerOS 8.0.0. ZerOS 8.0.1 also fixes the issue when referencing a non-existent palette (ZOS-12752) using syntax (e.g. COLOUR 40 ENTER where Colour Palette 40 does not exist), previously this would crash the desk. This is actually quite useful if you accidentally hit the wrong key while trying to reference a palette (therefore entering the incorrect palette number, accidentally being one that doesn't exist), and then you have to restart the whole desk to gain control again.

Hello @alg, Move on Dark can be enabled via entering your playback's settings (hold SETUP + Tap Playback's button) -> Move on Dark -> Enabled. The 'General', 'Chase', 'Raise and Lower' etc. that you see along the top are tabs to access groupings of playback settings, they aren't buttons to adjust actual settings. By default, when opening a playback's settings window, 'General' will always be the first tab selected (hence you see General every time you open the window), as they are general playback settings which aren't necessarily specific to other tabs such as 'Raise and Lower' or 'Chase'. If you're perhaps thinking of playback defaults found in SETUP -> Defaults -> Playback Defaults, these settings will only be applied to newly created playbacks and will not change existing ones. (D:3.0) in a fade time cell of a cue indicates a delay, with the time before it (0.0 in your case) indicating the actual fade time. If a cue had "5.0 (D:2.0)" in the "Up" cell, when going into that cue the console would delay executing the fade for fading up lights in that cue for two seconds, then proceed with the five second fade. This can be useful in cases for example where you don't want a moving light to come up until it has actually snapped into its position to prevent seeing it swoosh across stage during an intensity fade up or for staggering fades. Hope this helps, if you have any other questions please don't hesitate to ask. Archie

Hi all - unfortunately, I fear that this post may not get very far as most Frog 2 users have completely moved on (to my knowledge), but here goes.. On my Frog 2, I wish to access the ZerOS Startup Tool. Usually, you'd keep tapping F1 while the console is booting. If I do this on my Solution XL, it works as expected. Frog 2, nope... After the console's blue BIOS splash screen on the external monitor saying "Loading, please wait..." disappears, I keep tapping/holding F1 but the console boots straight into the main ZerOS application. The tapping/holding down of F1 is mentioned both in the online manual, and in a comment by Simon (original software developer for Frog2OS - that's ZerOS now). One theory that I've been thinking about - usually when updating the console with a bootable USB drive (old method), a screen would appear with an 'Update Software' button, I think that is using the Startup Tool application on the console's CF card (separate from the main ZerOS application). Even when I plug in a bootable USB or use the original 7.8.2.39 software CD to try and bring that update window up, still nothing. My conclusion is that the startup tool application doesn't actually exist on the desk's CF card. At some time, I plan to open the console and extract the CF card, pop it into my CF reader and see if the Startup Tool application exists on it. If it doesn't, I think I would be able to extract it from the Solution CF card (from memory the Startup Tool is from 2007 across all desks, so I think it should work fine) and put it on the Frog 2 one. Before I do that, are they any ideas anybody may have as to why this is happening? Many thanks for any assistance with this. Archie

Hi Ian, That's great news, glad to hear you got it sorted. Have a good day, Archie