Jon Hole

What a horribly long fixture! With this one, like this one, I'd highly suggest patching it as seperate fixtures for each cell. I've added it to the main library, but put it under "showline" rather than "philips" as the manufacture

I love this thread :-) They are :-) This has already been answered - but yes, they are fine to use As long as you keep within the USB standards, you'll be fine. If you try pulling to much current, FLX will just cut off that USB port until you unplug the device. It's worth noting that this goes against the Manufacturer's recommended guidelines

Hi Johnny Have a look at the "Trigger" settings on page 55

Hi James, Kevin's explained pretty much everything. I've gone through your post and added links that will take you to more information about each thing (I've possibly gone overboard with the links...!) Jon

I've replied to your PM Matt, but probably best I publically post it here too. Hi Matthew, Sub-fixtures don't quite work like that. They work designed for fixtures where two separate DMX addresses are required - for example a lantern with a colour scroller, or a moving light like the VL1K where the tungsten lamp can be plugged into the house dimmers. For fixtures like the KAM Parbar, where realistically they are four separate fixtures connected together, I would make separate profiles that control each part individually. This makes programming much easier. So, for the Parbar, I'd either make a "control" fixture that is just channels 1 -3, and then patch four RGB Dimmers (available in the library under "standard fixtures"), or I'd create a profile with the control channels and the first RGB channels (so channels 1 - 6), and then patch three more RGB Dimmers. Does that make any sense? Jon

"Fader Controls..." is used so the physical fader controls the level of those attributes, rather than them getting triggered at the "trigger level". So, for example, by default, if I move a fader to 5%, the intensity will come on at 5%, and the Colour, Beam and Position data will get fully triggered to their positions over their fade times. If I then say "Fader Controls... Colour", only Beam and Position will get fully triggered, and Colour will only move 5% from the previous colour to the new colour. As I slowly move the fader up, Beam and Position won't change (As they've already been fully triggered) but colour will get closer and closer to it's end value. If I start moving the fader back down, colour will return back to the previous colour, whereas Beam and Position won't change (until I go below 5% when they'll release). I often use this with position, and record a fader with the position of my moving lights pointing up at the ceiling above the audience. Then, if I have all the moving lights running effects over my stage, I can use this fader to pull that effect out into the audience (around 50%) or keep going and put the effect up onto the ceiling. To filter what's being recorded into a cue in the first place, you need to use "tagging" and the record window. In the record window, under the "attributes" heading, you can choose which attributes to record. Green means all parameters within this attribute (as per position below) Red means tagged parameters within this attribute (as per intensity, colour and effect below) Off (blue) means no parameters within this attribute (as per beamshape below)

There's talk about how we can make this work. Something I really want, that's connected into all this, is for triggers / releases to be "tracked" through the stack - so if a playback is triggered in Cue 8, and released in Cue 12, if I jump to Cue 10 the playback should automatically start, or if I miss / jump over Cue 12, the playback should automatically release. It's all connected with the above requests.

Hi Leon, Thanks for these comments - we'll keep them in mind during future software updates. On FLX, individual "playbacks" that are chases have BMP buttons, so maybe this will move over to Solution eventually too!

Yes please - will make it easier for me to follow! Potentially yes - you could be playing back parameter settings from one playback (LTP) and intensity settings from another playback (HTP).

Hi Kevin, You need to "release" the stack before the settings will take affect. Easiest way to do this is hold down CLEAR and press the GO button.

Yes - that's exactly what I'd do - create one fixture for the channels that affect the whole fixture, and then patch separate fixtures for each "cell". Thanks for making these! In the library, within "Standard Fixtures", there's already an RGBA profile. When creating a profile such as RGBA, where there's no dimmer channel, you need to create a "Virtual Intensity" - which scales the RGBA values down to 0% when you change the intensity. To do this, create an extra parameter for dimmer, but choose "Virtual Intensity". Then on all the other parameters that can "create light" (so RGBA, but not things like pan, gobo etc), choose "Scale by Virtual Intensity". You should end up with something like this:

AFAIK they have arrived... If not, delivery date was first week of December but I thought they come in early. I'm not in the office today but will check tomorrow!

Don't worry - you're not! They are all great posts. We'll probably wait until the forum is populated slightly further, and then look at making some changes.

It's only possible to assign these units in the fixture profile itself, not once they are patched as separate fixtures on the console

Hi Kevin - is this on FLX? It might be that the colour information is programmed into the cue anyway. Are you in tracking or non tracking mode? Try going into Stack Setup and choosing "unblock". Does this solve it?

Thanks Kevin - we'll get these added into the library :-)

Hi Johnny Have a read through Fixture Editor User Guide PDF available on this link: http://zero88.com/support/index.php?/Knowledgebase/Article/View/49/ Specifically look at the "Parameter Details" on Page 5.

Hi pierotec, We no longer dstribute them I'm afraid. However, I'm sure there are plenty of little companies nearby you in Italy who can make you a FROG 2 flightcase - worth sending a few emails / making a few phone calls. Jon

There's no reason a USB stick shouldn't work on FLX - we've not had any problems so far. We normally use quite small USB sticks (1GB - 8GB) rather than the larger 16GB / 32GB upwards, as it takes ZerOS slightly longer to index them when you plug them in. On our other ZerOS consoles, there are some compatibility issues when installing software (For example, the Kingston Traveller range doesn't work). However, on FLX we have the new, simpler and quicker installation method where we don't have that problem.

Hi Kevin, Thank you for making the profile and sending it over. I've quickly glanced over it and it all looks good, so we'll add it to our next library release. Either is fine, but setting it to strobe definitely makes sense. The "special" option is used for two things: First, the "special" option links parameters to specific functions within ZerOS - such as a the Colour Picker and the Pan / Tilt grid. There aren't any "special functions" for strobe, so this is irrelevant in this situation. Secondly, the "special" option is used when swapping out a fixture for another type of fixture (using the "change" button in SETUP > Edit Fixtures > Patch) to match parameters between the two fixtures. All the best, Jon

Hi Steve, Thanks for the comments, I've added them onto "Gemini" (our issue tracking software). Out of interest, maybe you could expand on this comment: To me personally, a BMP button is much more useful than a fader to control speed, as it allows me to enter the speed to match any music etc that I might be keeping in time with. However, I'd like to hear more about your views? Many thanks Jon

Hi Rob, We’re soon to be releasing two new iOS apps, both free, so we’ve taken the old app offline so people don’t purchase it and waste their money. We’re testing the app through Apple’s “testflight” – I’m more than happy to add you to this if you wish, so you can try the apps before we release them. If you’d like to, just email me the email address you use on the App store and I’ll add you.

Hi Akari, I've just had a look at the fixture library - there's definitely a second Gobo Wheel in there! Are you aware that if you press "Beamshape" a second time, you'll get another three options on the three wheels? Each time you press "Beamshape" it will cycle through all the available options.

Yes, this link might give you a little more info about that: http://www.arvydas.co.uk/2013/07/cheap-usb-midi-cable-some-self-assembly-may-be-required/ It shouldn't matter which midi units you use, but as the above explains, the really cheap ones cut corners and fail to keep to spec. We've got MOTU units which work well and aren't too expensive. A lot of USB / FireWire sound cards also have MIDI outputs on them, so worth looking at those.

Hi, Thanks for that - here's the profile for you. SRL-LB50.ift All the best Jon