kgallen

Sorry Edward, I was being a bit flippant with the historical behaviour. Actually since installing 7.9.3 the other day I haven't done much "encoder bashing" so I'll have to give it a go and see what you chaps have been up to. Previously my observations were that the "acceleration curve" wasn't very good (i.e. there wasn't one) - at the slow end there would be jumps of 3/4/5 counts per "click" (particularly noticeable on effect speed which changes a lot with a count at the low end) and then when you wanted to get a shift on, you'd be frantically winding the thing round and round. Anyway we digress onto FLX, this is a Solution thread I've seemingly hijacked!

Oh we FLXers have our own encoder sensitivity issues - although at least they don't spin on their own! Strange that one, the (same?) wheels on my Fat Frog have always been quite stiff...! There seems to be a lot of variability in them as other users reported theirs as quite free-running as you have on your Solution.

Sorry James, I wasn't having a pop - I was just confused how a software change could help if the "wheels spin by themselves when the bass is booming". No software algorithm could filter that out, more that the wheels needed to be "rotationally stiffer" and hence a "hardware" issue. Kevin

How can physically loose wheels be fixed by a software update?

Poor guy! Tell him from me he did a great job (on the videos - I've no idea how well it went in Dubai, I'll let you be the judge of that!)

Day 12 - Edward plays a blinder! Just a smidge of hesitation though as he pushes up the fader after the blind edit of the 6-bank stage right down lights. Has it worked... yes it has, hurrah! Edward breathes again...!

I want to know if Tyler has eye makeup on in Day 9 or if you had a team night out the day before

Day 10 - full marks to Edward for being able to say "with a ZerOS Show file you can load a whole show" without getting his tongue wrapped around the desk and just about getting away without saying "Zerosh"!!! I bet you all had a bash at that script and Edward was the only one who could say it and get through the whole "ZerOSh Showfile with ASHKII" without laughing his socks off!

That will mean iPad4 (2013, Lightning connector), iPhone 5 and earlier won't work and iPad Air and iPhone 5s and newer should. 10.3.3 is the last iOS release for the 32-bit platforms. Platforms after that are based on 64-bit processors.

Woohoo - Day 8 Edward, you get your first starring moment on the Calendar! ....and the boy plays a blinder! Great video! I'll have to start an in-office sweepstake on who gets Day 9 etc... Has Jon not given you a zero88 t-shirt yet?

Well if you did them fully in-house then all credit to you all - very professional! As usual I'm just being a bit picky! It's a great idea - and having an edit of outtakes for Boxing Day is genius! Actually, I loved Tyler's (scripted) line from 0:52 on Day 3: when describing the new Add Fixtures: "if you want your fixtures to start every 10, I can actually say Patch Offset of '20'' "

These are great, Jon. I’m thoroughly enjoying them and learning. Tyler is doing a great job and you’re just a natural. Edward comes across on the FLX S videos like he’s been doing it for years! Great work guys! Kevin ps sometimes sound goes a little muffled when the presenter turns towards the desk - maybe a lower lav mic placement on the shirt and a little more compression and make up gain?

This is one downside with "one" codebase, "ZerOS", needing to support many hardware platforms that have quite diverse control surfaces - Frog2, LeapFrog 48/96, SCD Server Pro, Orb, Orb XF, then FLX, now FLX S 24 and 48, and that's not including any internal hardware variations within these platforms. Checking against all of these platforms for input then conditioning the output accordingly must be quite a burden on the CPU and a real headache for the software team! And that's before we start running any lighting related tasks like cue stacks and FX engines. It seems, and frustratingly but quite rightly, the CPU effort is prioritised to generating the DMX stream. The usability though sounds just disastrous for your (ziglights) typical use cases. The tricky choice for the Zero88 team is like what just happened with Frog2 - do they continue to try to support the "older" probably "slower" hardware platforms or do they start to drop off the supported list. This is clearly tricky if the products are still current range like Solution! At some point in the future, the FLX processing power will be the "slow one" - although I'm hopeful that there is a little more headroom there with the quad-core implementation - and no LCDs (note to those users who want LCD scribble strips!). The other option is to diverge the software to be more specific to the hardware platform. But that then becomes an engineering headache supporting all of the branched streams of code development. I sympathise with both the users and the developers!

Lovin' (no 'g') them so far! (If you're not of a certain age... http://www.bbc.co.uk/programmes/p03048pd)

Hi Jon, it’s possible the answers are less ‘black and white’ than the poll allows. I use my FLX in several different configurations depending on the complexity of the show. It’s likely Solution users are similar. Maybe you need more detail like ‘always use a mouse’ or ‘happy to always require a mouse ‘? Kevin

See, he's like a genie in a bottle! One quick rub and... oh, hold on, this isn't going in the right direction at all...! It must be getting towards panto season...

I don't think that's any excuse. They get what they put (or don't put) in the spec, so they should spec the requirements better. As a company they are wanting to elevate themselves from DJ gear to the pro world so they should get a grip on their specs!

Edward - in LF48/96 does the battery retain showfile information or just time/date like Jon says for FLX? (Honest, I'll let you have some peace and quiet in a minute...!)

Cunning! Thumbs-up. Thanks Edward - I thought the ZerOS LF48/96's were blue. Is my CR2032 comment valid for this desk?

The OPs picture shows a green facia - so it looks like a Mk1 Leap Frog (FrogOS) rather than a Leap Frog 48/96 (ZerOS)... So this thread is in the wrong Forum and we need to be careful to give the correct advice for this particular console due to the ambiguous naming. Edward: Maybe you could clarify which side screws need removing as I suspect this is not all of them. For example on a Fat Frog, only the two lowest ones need to be removed to get into the system tray for e.g. replacing the coin cell. On a Leap Frog with the bigger chassis, maybe more need to be removed, but possibly not all - which would result in all metalwork coming apart in big mess! To the OP: Before you go in there, get yourself a CR2032 coin cell, and whilst you're fixing the wheel, replace the motherboard battery at the same time. See: http://support.zero88.com/Consoles/ORB-XF/975067721/Replacement-Battery-Information.htm And also maybe check the software version you're running. Your desk looks to me to be a Mk1 Leap Frog, in which case the latest FrogOS software is 10.12: http://support.zero88.com/Legacy-products/Legacy-Consoles/Frog-Series/975242041/Frog-Series-Overview-Software.htm IanK - get on this one quick! Kevin

That's a bit disappointing for Chauvet - they're not the cheapest of fixtures. I think the problem can come about from as simple an issue as not decoding the start code byte for 0x00 which denotes a normal DMX packet. An RDM packet has 0xCC in this position. When the fixture doesn't enforce the 0x00 decode it interprets any RDM packet as a normal DMX packet. I guess the reason the higher addressing works as Jon suggests it that the RDM packets are shorter than a full 512-channel DMX packet and thus the fixture, which is counting channels up to its own, finds the inter-packet BREAK first and thus the RDM packet gets ignored by that means. Flicker is listed on the Wikipedia RDM page ("Compatibility with existing DMX hardware") as a symptom of fixtures not decoding the start code as they should.

That is weird. Were the 3 flickerers(!) much earlier in the DMX addressing as Jon eludes to? Do those fixtures support RDM?

Hmmm.... Interesting. My "problem" fixture stopped flickering recently. Initially when I was playing with it out of the box I had it (probably) at address 0. More recently I moved it up to 220 to fit into the rig DMX map and it hasn't flickered since, so there is wisdom in that suggestion! I think I'll have a play with some addressing and maybe check out some of my other fixtures!

Some ‘cheap’ fixtures aren’t compatible with RDM because they aren’t truly DMX compliant. This usually manifests itself as a flicker in the fixture because the fixture incorrectly interprets the RDM data as DMX. You need to put the fixture onto a separately DMX universe or turn off RDM/RigSync on that universe and patch/configure manually. With FLX S24 there is only one universe so you can either turn off RigSync and patch the whole rig manually or remove the fixture. As it sounds like a fixed install then once it’s all configured you’re done anyway. It's also worth checking you added DMX terminators at the appropriate places. I recently bought (new) such an intolerant fixture too which is annoying... So in summary, it’s not the FLX S, it’s the fixture. Just to check - do your other fixtures support RDM? If some don’t then you’ll have to do manual patch and configure on those anyway. As you’re suggesting you’re a supplier/installer I’m going to assume you understand what RDM and DMX are and what they can/can't do for you and what the requirements on the fixtures are! Hope that helps. Kevin

Eric - I’d get some quotes for FLX. The numbers I see quoted list and on e.g. eBay are not representative. At those levels I never could have afforded my FLX. From what you’ve said I think you should look towards the ‘mother’ FLX to give you maximum flexibility and expansion scope. The FLX S range look darn good but I’m guessing FLX would be the one for you. I don’t work for Zero88!