Jump to content
Vari-Lite Controls Support Forum

delicolor

Regulars
  • Posts

    72
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by delicolor

  1. I have a couple of motorised zoom fixtures that are a little intrusive sound wise if zoomed at normal speed but are effectively silent if zoomed over (say) thirty seconds as the mechanism inches the lead screw drive. I mostly use them spotted down (so that is the default) but may wish to widen the beams on occasions.

    Whilst I can allow for the slow movement in a cue stack, we mostly work from submasters as busking.  If the lanterns are involved in a playback fader scene I can set the beam fade timer so that it will quietly zoom on trigger or fader move but when the fader reaches zero again afterwards they will quickly (and noisily) return to the default zero value. I can get round this by having another fader with a slow beam time returning the zoom position to default but it is a bit clumsy. Is there a better way round it or have I overlooked a default beam value? The desk is a Solution (Leapfrog) running 7.9.9.

    Thanks in anticipation (and looking forward to being allowed to let audiences back in again soon).

    Ian

  2. Hi Edward, thanks for your reply. The DMX IN feed came from the THRU of a DMX splitter, the IN of which came from desk DMX OUT 2. One of the four splitter outputs is cabled off to a pair of DMX LED drivers and 120 ohm terminated.

    So I wouldn’t have expected to see any DMX signal but I suspect interference as one of the tapes is very flickery at low levels (a second one with identical components on the other side of the hall is fine) and it is an RDM capable splitter so pickup might be possible. 

    As an aside, fixture 1 on DMX Universe 1 was flickering during the test (until I pulled the DMX IN) and it does use channels 1-7. It may have been freestyling & causing the rogue DMX, or more likely responding to pickup if in is patched to out 1:1 during test mode. 

    Anyway, I’m happy the desk is functionally fine.

    I had tried using faders 1-48 to trigger scenes on playbacks and whilst it worked, I found that the LTP level matching was a bit unpredictable unless I removed all intensity fade times and even then sometimes a playback would not follow the fader. As it seems to work fine on phantom zeros I now wonder if interference on the DMX IN might have been making it misbehave and will look back again at getting scenes onto faders as some volunteers struggle with the concept of playback paging and where light is coming from.

  3. I had a play with the test mode on my desk. I seemed to be getting continuous slow random press and release messages in between the genuine key presses but eventually noticed that there was some level movement on my DMX IN signal (I’m not certain what from though, the DMX 2 goes into an RDM splitter and on to a couple of led driver decoders with a termination. I’ll explore if there is some noise pickup offline). When I pulled out the DMX IN cable all keypress messages stopped (other than genuine ones).

    The faders and buttons seem to be well behaved, however I was puzzled as to what the four faders and six buttons at the bottom of the screen were there for? I expect it is something obvious with hindsight!

    527F1F18-6853-4D72-934E-76D89BEFEEBB.jpeg

  4. Thanks Edward. It didn’t occur to me that Preset mode would still work as I was thinking in terms of it being DMX channels 1 to 24 (or 48 in wide).

    Sad to see Solution has now been manufacture discontinued but I assume future Zeros releases will continue to recognise it.

  5. As an aside, does the test mode apply to Leapfrog/Solution? I’m not back in front of the desk until Monday.

    I have the opposite problem that a few faders creep up to 1% which now that I have fixtures 1 - 48 defined means if the lights are off they highlight red and get inhibited. I assume the resolution is the same.

  6. I was wondering if it is actually possible to install two instances of phantom ZerOS on the same PC, namely 7.9.7 and 7.9.8?
     

    I have a laptop and tablet on the go at present but it would be more convenient to use just the one as the tablet is somewhat restrictive. However I don't want to waste time trying it out to no avail or doing split boot-ups.

    Thanks in anticipation for your reply.

     

  7. Edward, I tried the presets to playbacks quickly yesterday, using five faders patched to DMX universe 2 channels set to trigger five playbacks. It sort-of worked but some behaviour was not quite as expected, mainly on playbacks with colour only attributes and fader follow set. It seemed to be fine via the actual playback faders but via the triggering they went up OK but stayed up. I cannot emulate this on Phantom ZerOs due to the inability to connect DMX OUT to IN to fire the triggers. However I will look more closely when next in the venue as it might have been something I overlooked.

    As an aside, I did find a small display bug. When creating cues with just one colour attribute to save into a playback, holding the the clear whilst jiggling the wheels deselected them Ok and the wheel background changed from white to blue, whilst the display changed from blue to black. However the white no colour attribute would deselect OK on the wheel but remain blue on the screen.Smart tag off, 7.9.7 on Leapfrog 48 and Phantom. The illustration shows the display with only blue selected at 100% but white misleadingly remains highlighted. The same seems to happen with intensity. It is immediately updated to show correctly if adding/deselecting fixtures or refreshing the outputs screen.

    E7EE045E-A7A1-447E-BBEA-8DAD2990D18F.jpeg

  8. Hi guys, I have been recreating my fixture profiles to make them a bit more streamlined and remove unwanted functionality.

    All is now working well, however I have noticed that regardless of what order I set the wheels, my Leapfrog 48 just sets them the way it wants to.

    For example, if I want red/green/blue on colour set 1 and blank/blank/white on colour set 2, it always puts white on set 1 first wheel.

    I'm running 7.9.7 with editor 2.6.

    Any ideas guys?

     

  9. 27 minutes ago, Edward- Z88 said:

    Hi Ian,

    Rather than being able to record playbacks directly onto the channel faders, you can use spare channel faders to control playbacks on other playback pages. This can be done using DMX In, by linking one of your unused DMX outputs on the back of the console to the DMX input port, on Leapfrog or Solution consoles.

    The topic below mentions this, which may be the one you saw...

    <snip>

    No, that was all new to me, but thanks for the tip, I'll see if I can think of a use for it.

  10. I thought I saw somewhere in the forum (or maybe another forum) that being able to place a playback onto channel faders 1-48 as well as the ten paged MFF playbacks was coming on software. 7.9.x for Solution (and LeapFrog) desks.

    Is this actually the case or is this just wishful thinking? I realise I can do this with a Zeros Wing but that is a four figure sum more usefully spent elsewhere.

    Thanks,

    Ian

  11. 3 minutes ago, Edward- Z88 said:

    Hello,

    Yes that is correct. As Solution XL and Leap Frog 96 consoles are different console types, ZerOS will give you a warning. However as Leapfrog 96 and Solution XL operate in the same way, you will not lose any show data.

    The Dockhouse Capture project file (Project.zip) is available to download from the article below...

    http://support.zero88.com/1004254221

    You will then be able to open this in your licensed version of Capture. On universe 1 in the demo file you will have 10 Clay Paky A.leda Wash K20 moving washes rigged above the stage, and 8 ADB ALC4 LED cyc lights.

    Edward

    I had seen that article but hadn't specifically tried the S version, thanks for the tip.

  12. I had a quick try-out with this without issue on my PC. However, I tried converting a couple of legacy fixtures and it suggested other fixtures that were similar but not identical. (Just low end washes and movers but the same physical looking fixture can have several arrangements of the attributes).

    What will the road map be on replacing the fixture editor tool, which I assume will not work with the new library?

    Thanks,

     

    Ian

  13. Eric, I can move between Leapfrog 48 and PhantomZeros in "Solution (& Leapfrog 48)" mode without issue, running current 7.9.7. It does give me a warning that the saved file I am loading was recorded on a Leapfrog (or a Solution) and some data may not be loaded, however it seems it does load ok.

    It is also possible to load the sample Capture program called Dockhouse.exe (the showfile is Dockhouse FLX CITP.jsf) that is visually almost fully controllable from the phantom although a few fixtures don't make it into Solution mode. I own a single Universe capture license but unfortunately universe 1 in the demo file is just the backcloth!

  14. On 8/23/2020 at 7:54 AM, delicolor said:

    Using Phantom ZerOS 7.9.7, I noticed this behaviour as well when playing about with Z remote and Z monitor Apps on both Android and Ipad. I will check it on our actual desk tomorrow, which is a Leapfrog 48 on 7.9.7.

    Confirmed the thumb wheel is the opposite way round to the apps on the real desk as well.

  15. On 12/5/2014 at 12:02 PM, Jon Hole said:

    Hi Ziglight,

     

    The reason for the thumb wheel working in this direction is so all your fingers and thumbs work in the "same direction" - away from your palm to increase the value, and towards your palm to decrease the value.

     

    Well spotted about the wheels screen... that does work in the other direction and should be changed, so I've added it as issue ZOS-5982

    Using Phantom ZerOS 7.9.7, I noticed this behaviour as well when playing about with Z remote and Z monitor Apps on both Android and Ipad. I will check it on our actual desk tomorrow, which is a Leapfrog 48 on 7.9.7.

  16. 4 hours ago, Edward- Z88 said:

    Hi Ian,

     Do you have a Leap Frog 48 or Leap Frog 96? If you have a Leap Frog 48, you could for example have 24 dimmer channels on the first row of channel faders, and then 24 LED fixtures or movers on the bottom row of channel faders. If you then have more than 48 fixtures in total, you can spill onto the MFKs to give you an additional 200 

    In answer to your question, it is a LeapFrog 48 and we don't have any conventional dimmers connected. The rig is mostly LED wash fixtures with a few movers (and a mirror-ball type effect). I might keep a few faders for conventionals should someone bring a rack in.

  17. Edward, thank you for your thorough reply.


    They had set the old desk up so that a handful of important fixtures had their channels patched onto the Presets in blocks of 6 (intensity, red, blue, green, white, not used). I had assumed at first that the heads were set to first address 1, 7, 13 etc. to achieve this but when I dug into the config I could see that the higher DMX numbers in the 100s were patched accordingly. Whilst it means the operator could colour mix on faders it would presumably conflict with LTP on the desk.

    Regarding intensity, can each of the 48 dimmers be patched to multiple DMX addresses in parallel or is it one DMX per dimmer/fader? That will get round multiple heads with the same start address with them running out of blocks of 6 faders.

    Whilst you are on, can I output DMX universe 1 to both desk outlets 1 & 2 simultaneously? That will sort out a short term wiring config to match the current arrangement.

    I have looked at the manual and tinkered with GhostZerOS but I haven't quite got my head round the subtleties of setup yet.

  18. We have a number of generic 8 channel RGBW leds working happily on an older Frog.

    We now have a Leapfrog on 7.9.7 and I want to simplify the functionality as much as possible moving forward so that inexperienced users don't inadvertently set off macros and such.

    (I'm sure that colour mixing is best left to the desk rather than the head, same with transition speed and we certainly don't want any disco macros firing off).

    Is there a straight-forward way of creating a null parameter associated with a fixture channel nailed to output level 0 which would lock the fixture down to RGBW plus dimmer? I rummaged in the details tab but couldn't work out an obvious answer (unless dark is tied in with it).

    Similarly, can a parameter be nailed up to 255 or constrained to a range such as 0 to 240?
     

    Thanks guys,

     

    Ian

×
×
  • 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.