Jump to content
Vari-Lite Controls Support Forum


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by delicolor

  1. I sent something to Support@zero88.com on Wednesday and didn't hear anything back. Has it changed or is it a domain hiccup?
  2. Mostly good news! This will make our S24 1U backup for the FLX 2U mostly seamless and open up the possibilities for pixel mapping. (We have to forego fixtures 49+ at the moment).
  3. Last week as it was valentines day, we had our movers with red heart gobos on a slow gentle sweep chase on the dance floor. I thought I would also add another look to the scene so changed the colours and recorded it onto the same fader as an additional cue. Pressing go whilst the first cue is running does cause the colour change, but the beams scurry to a different position before resuming the same movement. Is there a way for the chases to be in synchronisation so that the beams continue their sweeps and just change colour?
  4. I've sent the file. I created a new file from factory reset Phantom 17.4.2 with one MP75, recording three cues on playbacks with primary colours & setting buttons to Go(fade). Frustratingly it is working perfectly normally! There is presumably something a bit more obscure going on and hopefully you can get to the bottom of it. Having worked in software support a long time ago I remember that actually duplicating the issue is often half the battle...
  5. Hi Edward, thanks for your fast response. I have duplicated the different behaviour on Phantom Zeros, I had 17.4 installed and the expected actions took place, I then upgraded to 17.4.2, the snap colour changes were taking place as described, as observed on the DMX output. I'll send the showfile over before doing default testing in case it is an interaction of another setting.
  6. We just noticed a change of behaviour with 17.4.2 on our FLX that impacted somewhat on a show at the weekend. We have been running the software since December but most of the shows are with passive states on the four multi-function keys so a bit of busking by the Boss at the weekend raised the issue. (I had done my usual functional regression testing of course). We don't use the stack- we busk the shows on the playbacks as our venue is an Organ heritage centre and it is rare that visiting Organists give us an accurate set list. (Or even the resident Organists for that matter!) We have a bank of ten playbacks that control four Elumen8 MP75 RGBW fresnels, used to light the console sides. Each fader has the four lanterns at 100% with various colour groupings. For historical reasons going back to Frog days the volunteers worked out that you only needed one fader up and pressing the button on any of the 9 other faders would give a smooth fade to the new colour state. It didn't matter if the state was already LTP triggered with the blue box on the monitor, you still got the smooth colour transition. It left the board in a bit of a mess LTP-wise but didn't impact the lights between simple shows. However, the Boss was surprised to see that sometimes pressing a button resulted in a snap colour change and it was unpredictable (to him) whether it would snap or fade. Yesterday I quickly realised that if a playback had already been triggered previously, selecting it again whilst still highlighted caused the colour snap. Rolling back to 17.4 showed it was the software rather than the showfile. The release notes for 17.4.1 mention ZOS-8696 which is related to playback trigger & release so that is the likely culprit. I don't know if it is a bug or an unintended consequence but would appreciate a workaround if possible. (I never worked out if the ZOS reference body text was accessible to users). I can provide a showfile on request but in the meantime I will create a simple show on Phantom to duplicate it at home.
  7. Did the battery replacement article ever get written? I’m starting to get NVRAM errors on my 5 year old FLX. I see the manual confirms what screws to remove but not the innards. Ian
  8. I’m busy for the Tagging one tomorrow (today by the time this is seen). Will there be a sanitised version available afterwords as per some previous ones? Thanks, Ian
  9. PEBCAK made me smile. When I worked in Telecommunications, I queried why my Clerk of Works was writing NFG on rejection slips. He explained it stood for “Not found good”, at least when senior management asked. He had a special one for certain switchboard Operators as well- OFI, “Operator found ignorant”.
  10. Thanks for your thoughts David. We certainly want the scenes on the UDK buttons 1-4 for occasions when the skilled people are doing other stuff elsewhere but there can be a simple showfile generally in use to achieve this and we can do more exotic things when required. The remote push idea is further down the line.
  11. I was thinking along the lines of doors open/interval, show (Concert mode), show (ballroom mode) and FUF (full up finish, an old variety term). Latching to push any of the four buttons in order to bring the state(s) up and down. For the regular weekly concerts and dances a simple state will suffice. (Well, the dance has a number of overlaid slow chases but they will run on one fader already). This is all just planning as we are still on FLX-S at the moment.
  12. I normally leave Youtube on auto. I looked again and it was running at 480p, although with stopping and starting again it gave me 720p. I have a 100 Meg pipe so top speed is normally fine. I attach a screen grab (at 480) to show why I thought the old Phantom may have been the reason, it is from May 20th 2021 so by coincidence exactly one year ago. Maybe Edward was having a bad internet day!
  13. One other thing- I watched the online UDK video on Youtube to grasp what I could do with them and it struck me how difficult it is to read the drop-down menus on the old version of Phantom. It was never a problem following along with your PC as you could turn on the monitor or screen window but it is busy enough on the Youtubes with the visualiser as well. Are there any plans to refresh the old videos using the new phantom? (Or perhaps you have and I’m looking in the wrong place).
  14. Thanks for your speedy reply. Reflecting on it, I thought that the buttons on the regular faders would only be a latching flash to full rather than a fade initiation but I’ve never explored it. I take your point about tying the UDKs up and we may want to do other things with them on occasions. I see each of the four keys has the choice of being locked to one state or having ten available following the page button. Could a macro trigger a defined page 10 UDK even though the UDK is locked to page 1? Thanks, Ian
  15. I’m planning to use the four multi function keys to provide four scene states for when we don’t need to man the desk. We are in the process of moving our technical zone at the back of the hall up into a new control room and it occurs to me that we can make up some push-button panels to connect to the remote switch inputs, for simple state selection. I haven’t entirely got my head around macros yet but wonder how easy it would be for inputs to trigger MFK pushes rather than cues on a cue stack tucked out of the way somewhere?
  16. I just mean that when I tap on a red profile entry from the fixture schedule, if not recognised it just shows as per the screen. I assumed it would have listed the attributes as per the .ist of the fixture, not just an empty black box. It isn't an issue, I just thought it would work slightly differently.
  17. I will confirm tomorrow whether the same happens on the desk.
  18. I have been trying this out on Phantom in advance of going to the venue. It seems to work fine and I get the expected results on Capture. However, I was surprised to see that all fixtures now show as orange on my latest showfile which had been saved at software level 7.10, previously I had a mixture of white ones for known lights and red ones for ones created from the .ift editor. Most of the ones that were white offer up the library one to update to (with the usual nuisance resetting of the description field) but the red ones don’t offer up anything, or even show the channel attributes. Will importing the fixture .ift file help at all at showing the attributes?
  19. I recently obtained a wing which works fine as access to the other page of faders, however on turn-on it always starts up in channel mode even though the main desk comes up in the state last used, mostly playback mode in our case. (I haven’t entirely worked out the detail although it is presumably showfile related as a desk reset puts it back to starting in channel mode). The wing sensibly always starts on page 2 presumably because the desk always starts on page 1. Can I request that consideration be given to making it match the mode of the main desk on power up initialisation? We frequently have non-technical people bringing up a static lighting state (as well as PA & video) for our routine performances and the less key presses the better. Being able to page the display in fader display mode would be useful, someone else already raised this in the product improvement thread. Looking forward to trying out the new release. Ian
  20. Interestingly, I upgraded the Leapfrog to 7.10 as well as the S24 and when I loaded up the current file from the S24 into the Leapfrog all fixtures 1-48 retained their fixture numbers rather than renumbering the non-dimmers from 101 onwards. This saves twenty minutes of fixture renumbering when keeping the backup up to date. So the original grumble seems to be resolved, much appreciated!
  21. A user called Viola. Probably just registered up and started spamming.
  22. Thanks John, that sort-of works in that the direction is respected although the finess is a bit lacking on hitting a particular level. (Although that could be me being heavy handed). It looks like the acceleration settings make it fiddly.
  • 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.