Why Lighting Sucks. (When done wrong)
The History
The current lighting system consists of a mixture of a lot of Old and new-fangled hardware/software solutions.
Currently, we utilize both older Bulb fixtures and newer LED fixtures.
Let's go over how the system changed
Originally, we started with a Strand Palette that was put out of order due to issues with its DMX output
Moved onto a Mac Mini Setup running Vista Chroma Q, utilizing a Jands Vista M1. I would've preferred to have the Strand over this, even know it's not even functioning anymore. It was extremely funky and overall unreliable.
After we realized that Vista is completely unreliable, and failed to accomplish basic functionality. We received a temporary Rental GrandMa2 On PC command wing that was probably the nicest and most capable machine that we've had in that venue. (I miss her)
To our present-day console, which was installed last year, the ETC Ion Xe. As an industry standard in Theatre. I was a bit disappointed after moving over from GrandMA 2 after studying and learning the system for close to 6-7 months. ETC, in my opinion, is not nearly as capable as the GrandMA systems.
BUT, in ETC's defence, it's made for theatrical performances, meanwhile GrandMA is made for concert lighting, Lasers, etc.
They're both extremely well-suited to their designed purpose, so no complaining.
Very clearly, they're both intended for two very different use cases.
So how is it going?
Many would say that this is quite the upgrade! But I'm afraid I do have to lie to you, I am very much complaining.
The ETC system is pay-for-features. Want Timecode or Midi in? Don't worry, ETC has you covered!
With a one-time purchase of an ETC Show Control Gateway for the small price of $550.00!!! Sending SMPTE RX also did not work, nor did any of the Networking alternatives to physical connections. I will be attempting to test a method that's worked for others, and it's using Qlab to communicate with the console to trigger cues.
Overall, the ETC is user-friendly, with good training tools that can be found easily online, and I've personally been using it for well over a Year now. Even know it has flaws and quirks, it is a very solid lighting console that I can say is very reliable, and gets the job done.
The Issues
What happens when you put old junk and new junk together? You make a big mess.
Networking
The networking was treated as a plug-and-play, never documented or maintained. The system would require a complete overhaul to function properly. The picture below of my automation system should showcase how bad this issue is (Reflex Manager, Q-Sys)
Abused/Never Maintained
We utilize a Strand Dimmer Rack for our Universe 1. As of the moment, it connects to our
- House Lights (All Dimmer)
- Canopy (3/4 is Dimmer) (1/4 LED)
- Wall Lamps (All are Dimmer)
- Older Electrics (Raceways) (Currently All LEDs)
So far, the only bulb-operated fixtures that work are the houselights. The Rest of the fixtures were abused and never maintained, leading to literally every single one of them burning out and needing replacement.
We also operate using StagePin Connectors, so if our LED lights need power, it has to come from the StagePin Connector on our Raceways.
Our Strand Dimmer Rack features 1 extremely important Item, and it would be a shame if that item suddenly stopped functioning right... Oh wait
I present to you the C21 Processor!
I first set it up around mid-last year to properly power our LEDs and manage power over different circuits to prevent overvoltage issues. But as of a few months ago, the Buttons on the Processor have become completely unresponsive, refusing to allow me to make any changes at all. It also doesn't help that there's a lack of a management port or any actual service port at all.
But this wasn't that big of an issue, since I already set up everything I needed, and everything was completely functional and correctly patched. Until...
As of recently (Issue now Fixed), the Processor has lost all DMX contact from all ports, and there was no way for me to properly diagnose this without -
- Lighting Schematics
- Access to Physical Wiring
Without any lighting Schematics or Topology, I have no idea how the flow of Data actually takes place, where it's sent, processed, etc. As none of my prior maintenance work actually required a deep understanding of this topology and just the surface details, it was never invested in, as I am a 1 man team, and when I requested resources, I was never given any. When I submited a request for the Professional industry, it was never given.
So what's the goal? Create a somewhat Correct DMX Flow based on the equipment I know. Below will be a picture of just a rough layout
But as of right now, this layout seems very simple to understand and follow. That was the goal, to create a logical flow based on educational guesses and evidence and lay it out in an easy-to-follow to follow guide. Hopefully, it's as easy to follow in practice.
This is it for now. I will try to post more information later on.
This is it for now. I will try to post more information later on.
(UPDATE)
It seems I was correct on most of this flow; instead, the DMX wall panel for the ETC actually does nothing and is just decoration. Making the ETC fully sACN-based. Meanwhile, Q-Sys is also fully sACN-based and transmits a multicast sACN message over the entire network. The way this works is that each gateway has a universe, and if the sACN message has the right universe, it accepts the DMX and sends it through.
Thank you for reading.
Comments
Post a Comment