Jump to content
Vari-Lite Controls Support Forum

kgallen

Regulars
  • Posts

    1,815
  • Joined

  • Last visited

  • Days Won

    71

Posts posted by kgallen

  1. Hi Jon,

     

    Is there a timeframe for when the dust covers are available? (As in I ordered and paid for one when I ordered my FLX, but it's not 'materialised' B) yet!).

     

    I appreciate there are other more important things to work on, but I'm just curious when the cover might arrive...!

    Thanks,

    Kevin

  2. Hi Jon,

     

    (7.8.4 production)

     

    If a UDK is setup with Release=No, I found that Clear+UDK (or Clear+Fader Func) won't release the channels on the UDK.

     

    p57 of the Draft1 manual talks about UDK release, but you could read the two paragraphs under "Release" either way.

     

    I had a situation where the UDK controlled strobes on some LED fixtures (Flash=Latch). With the setup as Release=No, there was no real way to release the strobe. I was in tracking mode running a stack on playback 0, and running cues did not clear the strobe (since the strobe attribute was not tagged in any recorded cue and was tracking through and I didn't have a blocking cue - even a DBO wasn't!). Running Cue 0 (playback 0) also did not release the strobe, which I was surprised at - in that the strobing was still there when the fixture faded up in cue 1. Clear+UDK did not release the strobe. Home the fixture did not, because this was just in the programmer and Clear-Clear "released" the home. The only way I could find to release the strobe was to know that UDK4 has triggered it and change its setup to Release=Yes, re-trigger it and re-release it.

     

    I was just experimenting with the desk, but I think Clear+UDK (and Clear+Fader Func) should always release the channels, even if UDK setup Release=No, as I understand the Clear+... operation is somewhat intended as a "get out of jail" operation?

     

    Thanks,

    Kevin

  3. Using 7.8.4 production release.

     

    Enhancement request (might already be in the pipeline):

     

    Could the Cue Settings for a Cue include an option to override the MOD time. For example usually I might set a slow (e.g. 10s) MOD time on the playback for noise reasons on e.g. scrollers. However it would be useful to be able to override this in a Cue Setting when e.g. the next cue is coming along soon, and I need the scroller to get to the next required colour frame a bit more quickly than the playback default.

     

    An observation - not sure if this is expected or even what the "right answer" is!

     

    I found (with a scroller), that if the scroller was in the middle of a MOD change, but then a cue was run that had a fast colour fade setting, the (scroller) MOD took on the time of that cue's colour fade setting, even though that fixture (associated lamp) was still dark in that new cue. This means that if the cue contained just lit LEDs that were colour changing fast, any scrollers doing a MOD potentially come much more noisy as their MOD speeds up (even though they are still @0 in that cue). So the MOD time is being overridden by the cue colour fade time. Related to my request above, if the lamp was being lit in that cue, then the speed up potentially helps get the right colour frame in place in time. However if the lamp is still dark, then there is a needless noise penalty.

     

    Regards,

    Kevin

  4. I've created a scroller fixture that includes the details of the colours versus DMX addresses (mid/endpoint). This allows me to use the colour auto-palettes for the scroller.

     

    However I don't seem to be able to associate the scroller (as a separate fixture with it's own profile) with the associated dimmer channel for the lamp, so move-on-dark can be supported.

     

    Can I associate my scroller fixture with it's associated lamp/dimmer channel, or do I need to create a custom multi-part "Lamp + Scroller-with-colour-detail" fixture?

     

    Maybe there is a "better" way to be able to exploit the auto-palettes with a gel-based scroller on FLX?

     

    For completeness, my fixture definition is attached (Chroma-Q CQ1D).

     

    Thanks,

    Kevin

    ChromaQ_CQ1D.ift

  5. ift attached for:

     

    LEDJ Performer 18 Quad 4ch/8ch

    http://prolight.co.uk/images//media/LEDJ252/LEDJ252-um0.pdf

    (There is one already in the library, but it's a bit incomplete and the 8ch mode is not there).

     

    LEDJ Slimline 7Q5 RGBW 2ch/3ch/4ch/7ch

    http://prolight.co.uk/images//media/LEDJ59/LEDJ59-um0.pdf

    (Slight update to those in the library already)

     

    LEDJ Slimline 9Q8 7ch

    http://prolight.co.uk/images//media/LEDJ53/LEDJ53-um0.pdf

    (Not in the library)

     

    ift attached for:

     

    Stairville CB-100 4ch

    https://images6.static-thomann.de/pics/atg/atgdata/document/manual/c_286432_v2_r1_en_online.pdf

    (Not in the library)

     

    Regards,

    Kevin

    LEDJ_P18Q_S7Q5_S9Q8.ift

    STAIRVILLE_CB100.ift

  6. (Sorry if this is covered elsewhere).

     

    Any guidelines for USB Memory Sticks for use with FLX?

     

    Like: compatible/incompatible brands (including physical limitations!), memory sizes, formatting requirements.

     

    USB 2.0 specified in the manual, don't see any other specs.

     

    Thanks,

    Kevin

  7. Hi Jon,

     

    I wrote a set of fixture profiles for the LEDJ Intense 9HEX10 (9 channel mode options).

     

    I referred to the LEDJ Intense 9P10 you tuned for me a while back, and hopefully I've constructed this one to your guidelines. One question/deviation, for the strobe channel, I set the Special type to Strobe rather than None as in your 9P10. Not sure if I did the right thing there.

     

    Manual is here: http://www.prolight.co.uk/images//media/LEDJ254A/LEDJ254A-um0.pdf?ProlightConcepts=ylrlcnhjmgfn

     

    Please tune if required and add to the next fixture library release.

     

    Thanks,

    Kevin

     

    ps Sorry if it's more hassle to check someone else's fixture file than creating it yourself from scratch from the manual!

    LEDJ_Intense_9HEX10.ift

  8. If I knew how to add a dancing smiley to this post I would, but I don't, so I'll just add a big-grin one instead :D

     

    Thanks for this manual Jon, I realise it's been a lot of work, but it is much appreciated by us users!

     

    I didn't find a reference to the software version this version of the manual relates to - usually in Zero88 manuals this is on the first inner page.

     

    Well that's my bedtime reading sorted for the next week!

     

    Thanks,

    Kevin

  9. I found that after touching (on the internal screen) the "Calibrate" "button" (<Setup> then System Settings), I had to press Enter on the desk to get the external touch screen to show the calibration points. Subsequently re-calibrating, I don't recall having to press Enter...

     

    I was using the recommended iiyama T1731SR touch-screen monitor. I must confess I didn't find the touch screen response particularly accurate or fast - hence the multiple attempts at recalibration, which didn't particularly improve things. This may well be the nature of these things, this is the first time I've use an external touch screen of this type.

     

    Firmware was 7.8.4.

  10. To the OP:

     

    Rob,

     

    Does Ian's (excellent) explanation help/make sense? (Excellent piece of deduction there Ian if I may say).

     

    Do you need help rebuilding your fixture profile to add a virtual intensity channel? In the first instance I'm sure Jon would help out if you can provide a pdf link to the manual for the fixture. If not, then there are a few of us on here who can put one together for you, or you could download the Fixture Editor from the Zero88 site (here: http://zero88.com/support/index.php?/Knowledgebase/Article/View/49/256/zero-88-fixture-tools---version-26) and build one yourself, it's quite straightforward.

     

    Actually if your fixtures are pretty basic R, G and B LED pars, then there is almost certainly a RGB+virtual intensity in the Zero88 fixture library already.

     

    Regards,

    Kevin

  11. ... must admit I've never tried virtual intensities as all of my LEDs have master dimmer channels. But if the latest release note says it's there (and related bugs have been fixed), it looks good to go!

     

    Ian - guessing this feature didn't make it into the Illusion 500 software then? :ph34r:B)

  12. Here's a showfile. Cue 67.5 is the one in question. What I've done for this upload, is to edit the latest showfile I'm using in the theatre, on the Phantom Frog, and to edit the Q67.5 chase to snap-fade profile (in the actual show it's snap-snap because of this issue). Since I'm at home now and edited this on Phantom Frog, I haven't tested this on the real rig to ensure the effect I'm reporting exhibits on this showfile, but hopefully it would - maybe you have a DMX sniffer to use on a real Fat Frog DMX output?

     

    Thanks,

    Kevin

     

    ps Note also this is Q67.5 because try as I might, I couldn't edit my previous scene Q67 to make it a chase type, so Q67 got deleted and Q67.5 created instead!

     

    ETA Correction: Only Fixture 2 (an LEDJ 9Q8) is used in Q67.5. It's at brightness=34%/green=255 in both steps of the chase. It's at DMX 120. Other LED fixtures in the rig are at brightness 0% in all steps of this Q.

     

    ETA I didn't see any of the other generics flicker, but I'd say the blink was too quick for tungsten to respond, but it was obvious with the LED fixture. The generics use Betapack 1's and 2's (analogue from a Demux48) and the LEDs are fed from one output of a Chauvet DMX optical splitter and the Demux48 is fed from another output, so there is a degree of isolation between the DMX feeds to the two luminaires involved in this query. The LED DMX chain is terminated in the last of 5 daisy-chained fixtures.

     

    This picture shows a bit of an oblique shot of the scene. The generic of channel 9 is that lighting Dorothy/Tinman etc behind a gauze and the LED fixture 2 is producing the green backlight on the skeleton character on main stage to the left. The bottom of the LED fixture can just be seen as the highest green bright spot to the upper centre-left in the picture.

     

    http://www.pixelsintime.co.uk/Category/The-Wizard-of-Oz/i-zTcBpbR/0/X2/The%20Wizard%20of%20Oz-232-X2.jpg

  13. It seemed to be at the transition point between the steps, so I think at the snap on point (i.e. after the fade down) and at the top of the fade (i.e. after the snap). Lights were in significantly different locations, so weren't side by side to compare exactly. The generics were front/cross light and the LED backlight, so could see one or the other in peripheral vision. The generic (just a pair of tungsten PAR16s) that was intended to be the only one changing was channel 9/DMX 9 and the LED fixture I definitely saw blink is up at DMX 120 (fixture 2). There were other LED fixtures in the rig at brightness 0; I didn't see these come on at all, just the one that was on blinked off.

    When the show is done I could probably create a showfile. Actually I could send the one for the show as now and you could edit the chase cue to change the chase fade profile if you like? I understand this desk is well out of production, so I'm not expecting you to spend on any time on this really!

    Thanks, Kevin

     

    Edited to correct which LED fixture it was (2) and DMX base address (120). There was only this LED fixture on for the Q in question, the others were at brightness 0% [and didn't blink on].

  14. Documenting for prosperity...

    Whilst programming a show the other day I set up a simple 2 step chase on a single generic channel to do a 'flicker'. I found that if I set the chase type to the snap-fade (|\) profile, it caused some LED fixtures in the rig to blink at the step change point. These fixtures weren't changed at all in the two steps. The desk was in full mode. If I set the chase profile to the snap-snap (|-|) setting I didn't get the blink. Shame really as the snap-fade setting was much better for the effect. Software is 10.12.

    Kevin

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.