Archie D

Just putting what I posted on the Zero 88 Users Group here in case anybody needs a solution to the same problem.

Hi Peter, I've just replied to your post on the Zero 88 Users Facebook Group. Give it a go and let me know how you get on. Archie

Fantastic to hear it is working. Please feel free to ask any more questions if you have any. Archie

Hi @CestM0i64, In ZerOS, Playback 0 is the master playback, so using OSC (e.g. /zeros/cue/go/0/20) will go to cue 20 in the Master Playback. Therefore, Playback 1 will be go/1/<cue number>, and so on. Hope this helps, feel free to ask any more questions you may have. Archie

Ever since acquiring my Frog 2, I noticed that with the Dockhouse (Capture) Demo Presentation show file for ZerOS (available from Zero 88 here), it is of course a .zos file. The change from .isf to .zos for show files was made in ZerOS 7.9.8, a version of which is after 7.8.2.39 (the last supported software version for Frog 2) meaning Frog 2 only loads show files saved with the .isf extension. This means my fellow Frog 2 users won't be able to use the Capture Demo File for learning or having a play/experiment, so I have "converted" the .zos show file to .isf in order to be compatible with Frog 2. I imagine the audience for this won't be too large anymore since I feel Frog 2 popularity has died down significantly, but I'm posting this as a public resource in case it is of use to anybody who still uses a Frog 2 or a console on a version of ZerOS before 7.9.8. When loading in the show file, you'll be told it was from a Frog 2 and that some data won't be loaded. There shouldn't be any reason that some data won't be loaded with the way I've done this, but if you are loading this file onto a Frog 2, UDF 1 (User Defined Fader) will have a stored state on it. If loading this onto a different console type without UDFs (e.g. Solution), this should be transferred onto playback/submaster 1 (theoretically). It is also worth noting that this .isf show file is only within the limitations of Frog 2 - meaning the other higher universes found on the .zos version won't be seen or usable (Universe 5 & 6). The attached show file loads with the newer ZerOS skin if on Frog 2 - other consoles have that skin by default regardless, to provide a familiar user interface appearance to the other consoles people may have used with capture in comparison to the light grey and green classic theme on Frog 2. I have tested the .isf file with the Zero 88 provided Dockhouse 2022 file designed for the .zos version and it does work correctly. Anyway.. here's the show file, hope it is of use. Z88 Capture Dockhouse v7-8-2-39.isf

Thank you for this information, it definitely sounds like ZerOS Watchdog kicked in while loading the show file. It would have displayed a list of registers and then also a stack trace. Archie

Hi Paul, Saving the setup within the show file as well theoretically shouldn't cause any problems. If you can recall - when the console crashed, was it a black screen with a load of white text (ZerOS Watchdog kicking in) or did the console just completely freeze, preserving monitor output too? Let me know how you get on later with LF48TEST1.zos, it has a few things disabled/removed to see if anything in the show file itself is crashing the LF48. One of my theories for this was that because the Leapfrog 48/96 came with 2 DMX universes as standard, with an optional upgrade card while the Solution comes with 4 universes straight from the factory, that ZerOS was trying to index a universe from the Solution (3 & 4) that didn't exist on the Leapfrog when loading in the show file (if the optional upgrade card for 2 more outputs isn't present). Hence, U3 and U4 are disabled in that show file. However, it is just a theory and could be wrong. It's all about experimentation to see what works! I look forward to hearing from you, thank you. Archie

Hi Paul, Thank you for providing your show file. Please could you see if this file loads into your Leapfrog 48? If it doesn't and the console crashes, what does the console show on the external monitor? Please don't panic that your cues/playbacks are missing by the way for this file - I'm simply juggling things to see what does what. Thank you. LF48TEST1.zos

Hi Paul, Sounds good, if you’re still experiencing difficulties tomorrow, please could you upload your showfile here if that’s okay? I can then see if I can potentially find anything on PhantomZerOS and my Solution XL (though if it loads fine onto a Solution and not the Leapfrog 48, I might be lost) When the Leapfrog 48 crashed, was it a ZerOS Watchdog message that appeared? I’m curious as to what it said, or what the crash behaviour was like.. Thank you and have a good rest of your day. Archie

Hi @Muller Light, ZerOS showfiles are cross-compatible between ZerOS-based consoles, only with some data not being loaded (for example when you load a FLX showfile into a Solution, some data from the FLX won’t be loaded in). However, this won’t happen because Leapfrog 48 and Solution are identical, you’ll only receive a warning due to the different console types, but all data will be passed over. What software version are both of your consoles running? To see this, in the Output Window click ‘Other Windows’ (top left) -> System Information -> Software Version. What format is your showfile? Is it a .isf, or .zos? Many thanks, Archie

Hi Simon, To adjust cue delay times on Solution, the best method is to use the MFKs (Multi Function Keys) instead of the encoder wheels. Navigate your cursor using the mouse or arrow keys to an 'Up' or 'Down' field, then tap ENTER to start editing the time. On the top right MFK, tap 'Delay'. It will now have the red LED lit, with the white background to show it is selected. Type in a time using the MFKs or an external keyboard, then hit ENTER again to submit this. For your instance editing the 'Down' field, the down delay has now been applied to your cue. You also have the option to do this at the same time when editing a regular up or down fade time for a cue for efficiency. When editing a fade time, simply switch between 'Delay' being selected or not, and when pressing ENTER to submit these changes, both changes for the regular fade time and the delay time will be applied in one go together. I hope this helps, feel free to ask any other questions you may have. Archie

Hi Simon, Good to hear it seems to have fixed itself. I've just popped in to leave a few comments. You may have accidentally knocked the intensity encoder wheel slightly when making changes, so when re-recording default values with RECORD -> HOME -> Default, the intensity information is also included in the defaults of the fixture. Were you using RECORD -> HOME -> Default to do this after changing the intensity to 0%? This next bit is unlikely, but did the 'Intensity' selection button have a red indicator instead of blue? If it was blue, that intensity information won't be recorded into the defaults, so when you CLEAR CLEAR, the fixture will still go back to the original intensity default value. An image is attached with 'Intensity' under 'Attributes' having a blue indicator. The reason I say this is unlikely is because when you make a change (intensity in this case), when tapping RECORD, the changed parameters (which are therefore tagged) will be automatically in red to show they are selected. Though with this being said, in the image you have provided while trying to change fixture 5's intensity back to 0, 'Intensity' has a red indicator... Correct - the yellow D in 'Sources' as opposed to 'Intensities' indicates the intensity is coming from a default value of that fixture. A red P in 'Sources' indicates a manual programmer adjustment or modification. All in all, it is sorted, but I just thought I'd provide little segments of extra information in case anybody reading this isn't sure. Have a great week Simon. Kind regards, Archie

Forgive me if I've misunderstood the original post, but following this, here's a fixture file.. With this, we're using sub-fixtures instead of regular parameters in one single fixture like other fixtures would. This allows you to separate two parts of what we want to achieve here - to use this singular fixture as having the 'Lamp' (Intensity) defined as your actual dimming light (in your case - two linked to the same channel), and then configure the 'Scroll' part separately of the fixture to be on a different address, achieving your initial wish to 'link' the scrollers to the 'Intensity' of your incandescent fixture, where both the Intensity and two scrollers (together) can be as far apart in the DMX universe as you need, but the lamp must be the lower address (meaning the scroll can only be a DMX address after the lamp). Note that if you define the Scroll part of the fixture to be on e.g. DMX 57, that will be the first scroller. The second scroller will therefore be on DMX 58, with the Intensity being anywhere you wish (e.g. DMX 3 - completely away from the scrollers), again 'linking' the scrollers to the intensity. You will need to replace the Dimmer fixture you currently have patched in for your intensity with this one, but don't worry - the lamp intensity will work exactly the same, but giving you the additional scrollers. The scrollers will then actively 'listen' to the intensity and when it is at 0, the scrollers will use Move on Dark. We can see this in action with the grey background of fixture 1 on the second screenshot - the Scroll1 and Scroll2 values were both moving on dark at that time. And remember to always back up your show file before making critical changes like this. When patching this new fixture in after loading the .ift via SETUP > Load > IFT File, a 'Part' column will be added to the Fixture Schedule. This will indicate the Lamp and Scroll parts of the fixture as described above. See pictures and fixture file (.ift) below... Lamp + 2 Scrollers.ift

Hi Simon, Fantastic to hear it’s working for you. I expect the 9-134 is a locked colour as you say, and then 240-255 is to use colour..? I think the aim of it is to use 240-255 as a sort of ‘base’ intensity adjustment with a wiggle room of only a range of 15, with the colour values themselves allowing for fine intensity adjustments (0-255 on each of RGBW). Best of luck with your panto! Kind regards Archie

Hi Simon, thank you for sharing the DMX chart for your fixture. It appears that CH1 in the 9-134 range is the fixture's intensity control itself (I think), with 0-8 having the fixture in dark at zero intensity. Using a virtual intensity channel for this is a good idea (which you have done) and will scale the values accordingly. Out of curiosity, what manufacturer and fixture is this chart for? You're correct, you won't see how to set these in the ZerOS fixture creation tool, it appears to only be available on the fixture tools application. You'll find this within the 'Details' tab of the parameter you are editing, of which you can assign names to specific value ranges which will appear and change when controlling that parameter (on the Wheels LCD and external monitor in the Output Window). I've attached a picture below of what I've made for CH1 in the picture you have provided, along with the view of how it should look on the Wheels LCD and the external monitor in the Output Window. You'll notice that on the selected field named 'Shutter Closed' (DMX value 0-8), I have 'Dark' set to 'Yes' by ticking the 'Is Dark' box. This will now ensure those values work with Move on Dark on the desk, so when the fixture goes down into these values for zero brightness, ZerOS will 'know' it is at zero intensity and is safe to move parameters ready for another cue. You may not need this 'Is Dark' feature, as you're using virtual intensity, but I'm not sure. If you use Fixture Tools for this, and then decide later on to edit that fixture profile using the on-board ZerOS fixture editor, you might find it will break these added labels per value range, just something to be aware of. If there's anything else I can potentially help with, please feel free to ask.