alg

It had been set to flash, rather than Go(Fade). I will set back after current show is finished. We have been running the show on one of the sub-masters which works fine. Thanks for the hint.

Thanks I will get this checked.

The lighting designer on our next production has found that whilst he can programme cues into the master playback when he tries to play the stack it will not move beyond the first cue. It is possible to select another cue in the stack, take the master fader down and then up and that cue is selected. In practice not a viable way to run a production. Use of the space bar on the keyboard doesn't work either. All was fine on the last production but something has changed. We can still programme a stack on any of the other sub-masters and these seem to run as they should. Any suggestions on what could be causing this problem with the master playback?

Thanks for the offer. I seem to have managed to solve the problem as follows 1. I have taken the faulty fixture definition created when the fixture was first set up using rig sync 2. I have edited this to correct the errors in set up with the appropriate channels set be colours rather than beams, this was then saved back. 3. I then deleted the fixtures and then reconnected the two fixtures using the repaired fixture definition. After small issue that both lamps ended up with the same DMX address (not sure how this happened), this was easily corrected on the fixture itself. It is possible there is a problem with the RDM connection that sits behind this issue, for investigation on another day. 4. Finally I have deleted the faulty fixture definition from the list. This was to ensure it didn't get used in the future. I did try other ways such as creating a new fixture definition from scratch or finding an existing ETC 6 channel device with the same configuration and editing that, neither seemed to tick the box.

Hi kgallen Thanks for these thoughts. I suspect you are right about the RigSync details have been corrupted in some way. In looking at the fixture definition it looks perfectly normal, however if I click on the various channel numbers that should be colours it appears they have been identified as beam parameters. Do you know if it possible to update the fixture profile currently being used by the new ETC fixture to correct this? Or is it simply easier to start again and unpatch the existing lamps. Then either modify the existing corrupt profile or simply start again and create a profile from scratch as per the instructions. And then add the fixtures again. Would you disable RigSync and do this manually, or would rig sync now use the correct profile. It's a pity Z88 don't keep the library up to date as they used. It seems all the UK experts have left the company and everything is been run from the states.

I have today installed the above fixture on our installation controlled by a FLX S48. The units were successfully identified by Rigsync and appear in the fixture schedule as 6 channel devices which is their standard setting. However the devices are identified in Red in the fixture schedule, this appears to say that it is not in the standard fixture schedule. They can be identified using the identify feature but are not under desk control. I can see the intensity DMX signal using the monitor on the Z button. However the red/green/blue LED do not appear to be under control, nor thew strobe or fan. And the lamps do not come on. Any suggestions on what could be causing this?

Will the fixture list be updated for the new ETC Coloursource V Zoom PAR fixture?

Yes using the DMX monoitor under the Z key. Show now finished.Will monitor as we move onto a new production to see what happens. I can't see any rational explanation why the fixtures should have behaved in that way. No cabling or other changes. The only other factor that may impact is that prior to programmiong the desk we have been using the remote app whilst focussing, the app wass till connected, could that have any impact?

Following a summer break, with addition fixtures being added, I have found that the the LED fixtures would not initially respond to the desk. Randomly they would start working and respond to being faded up and down, this wake up time was random with some taking seversal minutes to respond to the desk. I would see the DMX output was under the control of the fader but the fixture was not responding. Using the identify feature the fixture could be flashed. Since programming the desk for the first production of the season the fixtures come up on cue. What could cause a fixture to behave this way, this is clearly not a hard fault as the fixtures do in the end respond. The fixtures are ETC Coloursource Fresnels and Junior spots. This doesn't seem to make sense, any suggestions?

Thanks Edward with your help sorting out sundry teething challenges with setting up a our FLX S48, some I think were unique but with your patience we achieved a working system. Best wishes for the future.

Thanks for this feedback. One or two points on clarification. Re the saving of the port allocation, I guess in the short term I can simply swop round my use of the ports to take account of the fact the port 1 will always default to RigSync enabled and use that for my LED fixtures and use Port 2 with RigSync disabled for the Betapacks. So for now I will pass on your Beta S/W offer, thanks. Re the DMX addressing, the Betapacks are not RDM enabled. I did try running with it on but found RigSync would insist on changing the DMX start address on each of the 5 packs making a nonsense of the labelling on the packs for patch purposes. What was happening was whilst the desk had reallocated DMX channels to the new Coloursource fixture i.e. 1-5 the Betapack was still seeing the DMX output and so I had the Betapack and Coloursource all running off the same channels on the desk. Re the RigSync control of the Coloursource Fresnels via the splitter, since these fixtures were previously discovered and known to the desk I assume there was no RDM management going on and the DMX was simply taking the fixture up and down. So I cannot say RigSync was working only that it was possible to take the control the fixtures in terms of setting intensity etc. Re the issue with the lack of DMX output, I will need to check this in the theatre when I can next get across, possibly tomorrow or Friday afternoon. If I still have problems I will phone direct as you suggest.

I have checked further this morning. It would appear that regardless of how I configure Universe 1 outputs the desk always reverts to Port 1 with Rig Sync enabled and the opposite for Port 2. Simply powering the desk off will reset to these settings. Why does the desk not retain the settings I input i.e Port 1 RigSync disabled and Port RigSync enabled? In terms of the use of the Chauvet RDMX Splitter 8 it appears that if I connect the new fixture direct i.e. bypassing the splitter the desk will see it and configure it. However it simply allocates the fixture to DMX start address of 1 and takes the next 5 addresses. This means the first 5 DMX channels that should be driving the first Betapack only is now driving both dimmer and ETC fixture. Why is Rig Sync not using the first free DMX channel for this additional fixture as the start address in our case 59?? I thought that was the point of RigSync, does it not ensure that such DMX clashes are avoided? It certainly worked fine with the previously installed ETC Coloursource Fresnel V fixtures that simply the allocated channels following on from those already in use. I can recover this by deleting the fixture and realocating the DMX chanels back to the Betapack. But this means the new fixture is still not in service. The next problem is why is RigSync not working via the Chauvet DMX splitter, as noted previously the device is RDM compliant. Does RigSync not work via other manufacturers products? This is well used by our supplier in his installations an hires and is made by one of the large lighting companies, surely it should be compatible. More alarming whilst investigating the desk has taken umbridge and has now completly blocked all DMX ouput from the desk! All the Dimmers and previously installed fixtures will simply not respond to the desk. I have powered off and restarted but still no output. What can cause such a wholsale inhibit on the DMX outputs? I am supposed to be starting to rig for our Christmas show and need a working system, how can I at least get my existign rig back and working??

The Chauvet splitter does support RDM. I will recheck the port settings when next in the theatre.

I have recently reconfigured our S48 desk to use both Output ports for our single unverse desk. The two ports are configured as per FLX 48S Universe Outputs That is Port one serves our 30 channels of BetaPack dimming with no RigSunc enabled. Port 2 has RigSync enabled and feeds an 8 way Chauvet DMX splitter, this currentlysupports our existing four Coloursource fresnels. All appears good with this existing set up. However when I have tried to add an additional ETC Coloursource Junior spot, the RigSync is not picking this new fixture up, the desk is showing the following message "RigSync is processing 35 devices". The additional fixture would indeed be number 35 but it has not appearing in the fixture schedule. What does this message mean and why is the new fixture not being picked up correctly. I have used the "discover all fixtures " button but it still does not pick up the new fixture. In looking at the fixture itself it was showing one on its display, when the DMX cable was connected the display simply went blank. This feels that it is probably something simple but offers no clue as to why it is not being correctly set up. Any thoughts. Over time we will be progressively adding more LED fixtures and the aim was that the use of RigSync would make this process a simple plug together task.

All OK, update successfully applied and all new lamps sucessfully connected and set up with full access to the colour menus, thanks for the help.