kgallen

I'll try and find some related threads as this is asked a bit. Edward or Jon will probably answer properly when they come along. This is probably the most obvious thread: (Ignore my ramblings at the beginning).

I hoped it might have been posted last night so you had something to look at this morning... 🙃

Have you got the colour fade time at 0s (snap) on those cues that aren't intensity fading? Attach your showfile here.

Thanks Edward, better links than mine!

Hi Gabriel, Welcome to the Forum. The Martin Allure already appears to be in the library, for Jester, here: Legacy Console Library Look for "McAlPrBa.ift" and "McAlPrEx.ift" - in fact I'll attach them to this post - I think you just need to put them onto a USB stick and load them into the Jester ML. If you want to download the whole gft41 library file it can be found at this link. Otherwise, for a fixture profile, you need to follow the process here: https://zero88.com/library#support The Jester support page is here: https://zero88.com/control/jester Instructions for Jester ML libraries are here: https://zero88.com/storage/downloads/ab019f28-de03-4bc8-9cfe-39426850eb1d/Jester-MLTL-Fixture-Library-Update.pdf If this doesn't get you sorted then I'm sure Edward will help you out first thing in the morning. McAlPrBa.ift McAlPrEx.ift

We're expecting this in the next month or so. This is "multi-cell fixture" support. Keep 'em peeled for ZerOS 7.10 on this site. However unless you want to do fancy things with multi-cell effects then you will be fine patching and using as @DALX suggests. (Note: You will consume more of your 48 fixture slots on your FLX S24 if you instead want individual cell control, so the new ZerOS version will be useful for you.)

DMX - just daisy-chain in to out as you've already done, starting at the FLX S24, in and out of each fixture. Ideally you would add a DMX terminator on the end, but for getting going you should be fine without. Note you should aim to use cables that are designed for DMX, not microphone cables (although I suspect your fixtures have the official 5-pin XLR connection which would preclude you using audio cables). See also this Wikipedia article on DMX although you don't need to understand all of the nitty-gritty technical details, just the basic idea and setup. Also have a brief look at RDM as it sounds like your fixtures have some sort of implementation - however you may be better using a manual setup as Edward describes, at least until you get the hang of things. Regards your fixtures, Master will definitely be wrong. If there are no other options, then use Slave. If you are completely new to this then consider joining the Blueroom Technical Forum - this is a UK-based technical theatre forum. There is a Beginners section where you can ask basic questions without getting ridiculed.

We're equally sad. It freaked me out as after my reply the thread said it was unread and you'd edited it at *exactly* the same time. And so you had...! ...and I hadn't arrived here from an email notification, just happened to refresh the page, so it's not like we both got the email and decided to reply! Spoooky...

Wot he said ^^^^^ 🤣

A blocked value is one that stops any tracking ("purple" value) from an earlier cue. If you record a cue using SHIFT+RECORD then you will get a "snapshot" cue which records everything and thus blocks tracking and effectively restarts any tracking from that snapshot cue. The downside of snapshot (blocking) cues is they also block Move On Dark which is not usually a good thing if you have anything mechanical which needs to "prep" for a later cue. Examples are moving lights, colour scrollers, gobo rotators.

Hi @Edward Z88, thanks. Do you recall, was this the same issue with my FLX last year (when I came over to Cwmbran)? I don't remember if we recovered it prior to me leaving the console with you for service. If so do we know why this corruption occurs?

@Takuya Chinen, @Edward Z88 Is the solution shareable? It may be of interest for other users. 🙂

One other "minor" item we've spoken about before: some sort of "version control" on fixture profiles so we know which of our "identically named" fixture definitions are actually being used by the showfile. Current solution is when creating or updating definitions we have to keep putting something in the name like "v2" or "v3". This is a real pain when debugging/updating a new fixture definition as you're never sure what the desk is using!

@Ed75worth getting yourself registered as a beta tester. Whilst you may or may not have time to help here (it depends for us all) there may be discussion there that you can contribute to (that part of the forum is not general access) given your experience and also your ‘fresh eyes’. There was a bug a while back with 2-way playbacks that had similar attributes to what you report (although it was with a general playback rather than the master). I’m not sure what that status of that ZOS is (I’ll dig it out when not on a phone). Possibly it was fixed, but it came to mind with your report. Good to have you ‘on board’! Kevin

Didn't you know - everyone always wants "bigger and faster" (and better!). 🤣

I'd also like to give a slight tickle to an RDM monitor - not sure if this is "Reporting & monitoring of RDM Sensors etc". RDM documentation seems to be as bad if not worse than DMX maps versus firmware version. For debug, being able to see what RDM data is being returned by a fixture would be useful. I believe you have some debug code of this nature internally. Would be useful under a debug section under the Z key. Edward was very helpful last year debugging the RDM codes from a Chauvet fixture that did not seem to return the codes that I'd obtained from the manufacturer - in fact the codes we finally worked out were nothing like the codes given to me by Adam Hall Support.

@Sven76 you should ask Jon to put all of your 6 ticks on "Pixel Mapping"! 😝 Greetings to you!

Nice to ‘meet’ you Ed, welcome. Hope to see you around on the forum! Kevin

Thanks Jon. I've now ticked Dimmer Curves and MIDI Out (6 ticks, maybe I dropped one of my previous ones!). Would the MIDI Out be via macros? (and thus hopefully not a huge development impact - main task probably a UI update to put in settings). I ought to re-read up on MIDI...

I've voted for the entries that, based on 5-8 selections, would be of most interest for me. However there are other entries that are of interest, so I'll group these below so you know there is other "lower priority" interest in some of these ideas. Some of the ideas above I suspect are relatively quick/easy to implement. Others will take a lot of development validation. Maybe it is worth splitting this survey into say 3 categories of easy/medium/big development cost and getting us to vote on them? Each release it would only be reasonable to have one "big" feature, but a number of smaller features could bring good user benefits whilst not incurring a large development cost. For example the Rig plan/Stage sizing - would be great but the development cost is likely high and would come at the cost of several incremental features. Improved macros, intensity fanning, import/export are probably functions that build easily on existing features and don't break fundamental desk software architecture. 2nd choice Comprehensive Copy/Move 'Learn' functionality - depends if I understand right here. Sometimes I will create an auto-follow sequence that links in with an audio track. Possibly this could help here. Rig plan layout (I'm assuming this would be a lot of effort to implement, so whilst I've asked for this, I've relegated it to my "second choice" set) Stage sizing - for movers this would be excellent, but again, I suspect a big development cost since it needs the above first 3rd choice Intensity fanning Import/export - for backup and archive (rather than moving to another console automatically) Improved macros (I need to use these more - looks like you have some ideas) Custom desktop layouts As covered recently, RGBAW/I/L and Fixture Editor are pretty much at the top of the list for many (Sven will shout at me again for not putting Pixel Mapping here!). One other for me is dimmer curves (or "taming cheap LEDs"!) and "switch" (snap 0->255 at a given threshold) for controlling relays on stage practicals and triggering other outboard equipment from lighting cues. I don't believe the desk can output MIDI control, so I have to do via DMX. Regarding partial file load which I ticked as "first choice" - I would like to start building up a library of bits of setups and cues that I can load in. At the moment I have to either wipe the desk and start again or load an old show and delete lots of cues or settings. I can see Jon wants a new skin. I think many users might consider this a distraction to getting much awaited functional features 😛

Hi Takuya, Here are the instructions for creating a bootable USB stick. Hopefully this can help you recover your console: https://zero88.com/manuals/zeros/software-updates/zeros-usb-creator

I’ll certainly have the software (or at least a pretty recent one) downloaded (not that I could upload it here). What I don’t have or know off the top of my head, is how to make a bootable USB stick that the desk can use. That information was down the links that I now find are 404.

Jon/Edward, The resources we used to use to support the community are gone. Links posted by Edward to resources in the past 12-18 months no longer work let alone the knowledge we built up over the past 'n' years. We can't help out unless we can access these types of resources. This means you will have to answer every Forum support question yourselves, the community can no longer help others because you've taken away all of the knowledge that we used to use to provide answers. I just tried to help a user with a crashed S48. I couldn't give him instructions for a bootable USB stick because none of the links that I could find in previous Forum posts work and I've got no clue where I could hope to find the new location of such instructions. I'm sorry, this is not acceptable. I know Z88 have been through turmoil with business reorganisations but the data we need still exists, you've just restructured your web portal so we can no longer access this data. Come on chaps, this beautiful company is going to sh*t within 3 months of DavidC moving on. Honestly, I think you need to have a big sit down with your "new" management and decide what sort of company you want to be. Because I'm not liking the outlook. From a 25 year customer.

Can you make a bootable USB stick with the software on and see if the desk will read from that from a power cycle? I'd point you to some instructions on how to make a bootable stick but I can't - none of the links I can find in past articles with instructions on how to do this work anymore. 😡 Edward/Jon - seriously chaps this state of affairs with the website needs to be fixed ASAP. The community can't help anyone anymore without your support both directly to the question and getting this damn website sorted so that we can access the resources we need to help users with problems. I'm not talking about ancient stuff here, I'm talking about links posted by Edward within the past 12-18 months.

Hi Delphine, I'm looking at your two showfiles together. This is what I see: #1 AUTONOMIE GIEVRES I can see 25-28 "7P Hex IP" present and 33-34 are "LED - RGBW". No fixtures named PARA*. #2 PONT SAINT MARTIN3 Fixtures 25-28 deleted as you said, fixtures 33 and 34 are swapped from "LED- RGBW" to "PARLED 1820IR" (and named "PARA J" and "PARA COUR"). So the result going from #1 to #2 is: Any programming related to fixtures 25-28 is deleted (deleted from cues and palettes) Any palettes specific to "7P Hex IP" will disappear since there are no other "7P Hex IP" in the patch (Edward to confirm what is deleted!) Any programming for fixtures 33-34 that were "LED-RGBW" will be re-targetted to "PARLED 1820IR". The desk will try to match up functions between the old and new fixture type and map across programming the best it can. This assumes you did fixture swap-out for 33 and 34 (and did not delete 33-34 [which would result in all 33-34 programming lost] and then patch fresh fixtures). In fact I see you swapped out 29-34 "LED - RGBW" in #1 to "PARLED 1820IR" in #2 so the desk should have moved the programming from a "LED - RGBW" to a "PARLED 1820IR" the best it could match parameters. However I note that in the Fixture Schedule, the "LED - RGBW" are in white - so current library fixtures - whereas the "PARLED 1820IR" are in red - so are "legacy" fixtures. I wonder if this is compromising the swap-out? I don't have adequate experience of the new library to comment further. Edward to advise! The desk isn't "magically" going to swap programming for 29-30 in #1 to 33-34 in #2 so I'm not sure what you mean by "My PARAs are found in 33 and 34, whereas on the original file they are in 29 and 30". As I understand it, as long as you use fixture swap-out then the desk will use the ID to map previous fixture programming to new fixture programming. (The DMX address is not relevant).