kgallen

Requesting new fixture profiles To requests new fixtures, please email us, ensuring you supply full details of the fixture (Make, Model, Mode) and a download link to the Operating Manual. FixtureSupport@Zero88.com

If I remember correctly I think that came in 7.9.4. 🤔

Thanks for the clarification and tips Edward (as always!). Apologies to the OP for the slight thread steal but hopefully the information is relevant and useful!

Thanks Edward - is this the same a No Effect or would it HOME the fixtures C/B/P too (which is probably undesirable). Also creating the block cue would disrupt move-on-dark for other fixtures. If this understanding is right and hence there are implications, how else could this be achieved? Thanks, Kevin

I'm sure it's extremely bad practice and unnecessary if (a) I could use the desk properly (b) the desk was an incy-wincy bit better at handling this, but yes I do this too just to make sure the fixture is recorded. A common case is to ensure an Effect is removed from a fixture, by ensuring the "No Effect" is recorded into the cue - otherwise your heads keep moving about running the effect even though they are now dark. Given that some LEDs will light at 1% (which will be a DMX value of 2 or 3 typically) this doesn't always give you a "dark" fixture, so it depends on the fixture if you can get away with this fudge. I guess the proper way is to manually tag the fixtures for No Effect in the cue where the fixture is DBO (because SmartTag won't do it for you), but that is such a faff as you've already recorded the bulk of your cue with SmartTag then you have to go in again to deal with the fixtures with Effect to tag them and Update the cue. If there is more usable way then Edward or Jon will tell us in the next post... 😁

Hi. I benefit from move on dark all the time now and usually it works in the background without me even knowing or worrying. One mistake I made early days was in doing a record-all/snapshot cue which will stop MOD working, and understandably. Hopefully Jon’s instructions give you a starting point - subsequently just beware of the record-all trap! Kevin

Sorry guys I'm not sure I can reconcile these new "explanations", this is a plain bug surely. Other users have reported similar issues/confusion in other threads, that I've linked to this one to see if there is a common problem. Jon (apologies if you have followed the thread but:) - I'm recording an Effect palette. I can understand that if I was recording a Colour palette the desk would want to record just the colour attribute. Edward already confirmed early on that what I'm trying to do (which is not anything fancy) is reasonable and the desk should do as expected. Are you saying this is not the case and it's not a bug but some "unreasonable expectation" of what should happen given what the GUI is presenting as options? I select the required attributes for recording on Record Options then I press OK. It's not doing what I ask regards which attributes to record. Why have these Record Option buttons if the desk doesn't follow what options are enabled? I don't see what syntax or touch has got to do with it - the information required in the palette is there selected by buttons on the Record Options form. As stated above, I even follow your KB "Tagging" article and the desk does not behave in the way the KB article says - they KB says it in plain English "These tagging options allow you during the Record process to choose which attributes to include:", "Under Attributes, you can then go in and choose which attributes to include or ignore. ", "You can choose to include an attribute by tapping the Attribute soft button to include it and it will go red.". Is palette recording not following this same schema? Please be straight with us - if it's a bug, let's log it, fix it and move on, not dancing around some "legalese" language about "advanced" usage. If it's not a bug and expected behaviour then please clarify the KB and add it as an enhancement request so we can do it. Thanks as always, Kevin

Hi Edward. Ok thanks. What’s the difference here to what I’ve been doing - is that typing the Effect palette number rather than tapping the screen? So is this a workaround for a bug and is there a reference number? Thanks, Kevin

Hi Edward, Bump. Did you ever get through investigating this? Seems pretty fundamental functionality that isn't working as expected! Kevin

PhantomZerOS 7.9.5 MD.zip from here:

But if the sunstrip can be patched as multiple fixtures then you can apply effects across the cells as if they were individual devices. This has been asked many times on this forum so with a bit of a search you'll probably find more details. example:

Look in the FLX forum.

Here you go. This has 3 options so you can mix and match: 6ch, 12ch, 24ch versions. Each has a virtual intensity. So if you use the 24ch version then there is one virtual intensity to scale all 24 channels. You could however patch 4 fixtures each of the 6ch version then you would have a "master" intensity control for each 6ch group. Mix and match as you like. The actual dimmers are under Beamshape. The virtual dimmer (the one intensity channel) defaults to 255 so SmartTag should work ok for you. Enjoy! Kevin Tega_Dimmer6_12_24.ift

I'm not sure I understand the point of this much - can only presume you have more than 24 non-generics. What I think you need to create as a fixture definition will have 24 beamshape 'dimmer channels' plus one intensity channel as a virtual intensity to scale those 24 beam shape channels. This is because a fixture can only have one true intensity channel so you can't create one fixture with 24 intensities. I'll have a go at building one for you... one moment...

Speed override. Shift+unprogrammed playback button then select Speed Override.

Thanks Jon. That's good to hear. However as I've commented to Edward before, I'm still not clear why you want to hard-separate current and legacy products. Users don't know or care what their product fits under and your product line moves on so this implies you need to keep reshuffling the website to move stuff over - I'm not clear who gains from such partitioning? The user has to search multiple places and you have to keep moving stuff. Then as now we find the good current stuff has wandered off into the legacy section. Sure, on a product page mark it in big flashing words at the top that it's a discontinued product but why artificially separate in the support portal? More appropriate partitiioning is consoles, dimmers etc like it is on the Zero88 front page. If you must "separate" them maybe have the list like your example above but have "Consoles <current list> <blank line> <legacy list>" then the 40 odd don't crowd your current crown jewels but there is not a "separate section". Umm ok, having had a look at the Beta site, it is looking nice and much more usable. Much less fussy than what you showed me back in April... I'd be interested to see how quickly I can get to the critical support articles when I'm on a phone with a weak 3G connection. Can this be accommodated at all by loading the flash graphics last? Cheers, Kevin ps Couldn't see a link in the ZerOS Beta Forum, is it a different Beta forum? Ah it's that thread a few down rather than a new one. Got it. pps Should we not ask about the updated FLX manuals promised in May? 😋

In over 10 years of using the Fat Frog I never knew the reason for the Reset DMX option. Sure I triggered it a couple of times for the duck of it, but I never had a real reason for it! If you have inherited the desk I'd just be sure to install 10.12 software on it (the latest). This can be downloaded from this site, put onto a floppy and on power cycling the desk with this floppy in the desk should upgrade. Actually prior to doing this, replace the internal battery. 10.12: https://eaton.nanorep.co/storage/nr1/kb/2AD62C9/3879A76B/3A210339/31/FrogOS v10.12.zip Battery: (Jeez, Edward those "Download" and "Support" sections are just truly awful. Is it ever going to get sorted into an accessible resource? You can't find anything in the damn area. Casual visitors have no chance. As I've said many times before - I know what I'm looking for and I still have to hunt around - and I know there is stuff under there somewhere. Frog-wise it's just a jumble and ZerOS-wise half of the useful stuff for FLX is under the "Legacy" Orb/XF sections.)

Rigo - what have you lost? Have you lost the programming of your show? If so you can only recover it if you have previously saved to floppy disk which you can reload from. Maybe you can list exactly what you did to "reset" - tell us which menu items you used. Kevin

As Edward has confirmed for us I don't believe so on FLX. With Frog range, a flat battery caused all sorts of misbehaviour. As a result I asked about the battery in the FLX soon after I bought it, and Jon said that the battery was only there for the RTC and not related to retaining show data in RAM before it's copied to some non-volatile storage.

Cheers Olly. I hope you get the desk sorted quickly. Don't envy you having to drop back to Jester. I'd have to drop back to Fat Frog and that would be no easy move these days with so much LED and relying on move on dark so much! Kevin

Eeeekkk! Sorry I'm not closer otherwise I'd try to help out! Out of interest, how do you get in to FLX test mode? I feel I should already know this!

In a nutshell, I turned my FLX on to do some more pre-show setup - it had been fine the night before, closed down ok - no front panel LEDs, no DMX output, but buttons and internal screen working. A power cycle did not help, I had to do a factory reset. I was panicing big time...! For the info Edward is after you need to tap some other tab on that screen - not sure if it's System Information, Console or Events - something like that!

I had something similar with 7.9.4. Does my report here look like what you experienced? In my case a desk reboot didn't help - I had to do a Factory Reset. (My post is in the Beta Test Forum, not sure if you can see that post. However my comments relate to 7.9.4 production software.)

Different name is all I know. There have been a number of enhancement requests for this to be improved, including from me, as I have the same gripe.

First one is Smart Tag. You’re doing the right thing by selecting No Effect in the next cue but it’s not being recorded because it has zero intensity so Smart Tag ignores it (yes very annoying). I think if you make the No Effect change then press Update and hold briefly you will get up the options box then tap Smart Tag so it goes blue. You should see some parameter boxes have red stripes and Tagged Fixtures is red. If you ok the Update then you should have recorded the change. Not sure about your second question - mine fade as other fixtures. Worth checking your fader is an intensity channel - if it’s a traditional mover rather than an LED maybe the shutter is snapping closed due to a beamshape setting?