|
|
This topic comprises 2 pages: 1 2
|
|
Author
|
Topic: GDC Cue fails to fire
|
|
|
|
|
|
|
|
|
|
|
Ian Freer
Expert Film Handler
Posts: 135
From: Wellington, New Zealand
Registered: Oct 2003
|
posted 04-08-2015 10:13 PM
A few notes if you're going to use the Jnior AND the Cinema.Jnior application to run Macros etc... This might be specific to GDC, I am unsure, as in my case it is with a GDC...
Long story short: I am just trialling Cinema.Jnior 2.34.212.1338 as we had significant dropped cues with an earlier version. I don't know if it's up on their website yet, but it's been running for a few days with no issues so far.
For more details read on...
I have several sites with GDC, Jnior and the Jnior manual control panel, so running Cinema.Jnior is needed to make the control panel work.
I had been running Cinema.Jnior 2.22.1115.1501 for a while, but every so often a site would let me know the Jnior had become unresponsive and needed a reboot.
The guys at Integ looked into it and found an issue and a fix, so gave me version 2.30.939.1430, which I installed into one nearby site, connected to a GDC, and it has not since missed a beat. So feeling confident, I recently updated another 'occasional reboot required' site to 2.30... (and updated the GDC to Build331 at the same time). It broke the Jnior automation. i.e. other than a very occasional reboot required, it had been functioning well, now it was missing many cues per day.
After lots of back and forth with Integ looking through logs, they found an issue where some characters were being dropped meaning two messages were running together as they were received from the GDC, resulting in invalid commands and missed cues. It seemed only to affect multi-cue macros from the GDC, i.e. a simple House Lights Up command was fine, but a SCOPE FEATURE Cue, with Lights Down, Masking Open, Volume x.x all trying to fire from the GDC to the Jnior and the last message or two got dropped, but only sometimes...
I also run duplicate commands and a 500ms gap between commands to the same device in a setup like this to ensure things run smoothly, but was finding I had to really space things out to 2000ms, and while that improved things, it still missed many cues.
Luckily one site had reported this to Integ a couple of weeks prior to me, so a fix had already been developed but not tested in the field... But it's all looking OK at the moment. No complaints from my site since the upgrade to Cinema.Jnior 2.34...
Cheers, Ian
| IP: Logged
|
|
Steve Guttag
We forgot the crackers Gromit!!!

Posts: 12814
From: Annapolis, MD
Registered: Dec 1999
|
posted 04-09-2015 06:23 AM
See generally when I use an automation...I only have the GDC fire ONE cue to the automation and if there are multiple tasks, then the AUTOMATION handles the Macro or sequence of events. With the eCNA line of automations, there are currently 50 macros one can set up, 9 programs as well as direct out commands (and RDI commands).
So I'll have Start Show 2D Flat (or words to that effect) and everything one needs to happen to get the show going will be handled by the automation once it receives that command. Projector, curtain, masking, lights...what have you. And it will do it without fail and you can trace the command coming from the server (anybody's) as well as the macro being executed.
It doesn't really complicate anything either, it actually greatly simplifies it. Your commands become VERY uniform regardless of projector or server company you are integrating with. The commonality is the automation itself. The same macros can be used throughout the chain and even if Christie is used on one site and NEC is used on another and Barco is used on another (you can do the same with the sound processors too), the whole operation remains very uniform. Via the eCNA's RDIs, if you are uniform in how you create them (function 1 is Lamp on, Function 2 is lamp off...and on down) such that when you switch out the RDI file based on the projector or sound processor...you don't have to reprogram anything other than the IP addresses.
Even the "greatest" DCinema system out there (Film Tech's DCS) uses the AUTOMATION as the central control point (The FT-21) such that it is equipment agnostic.
Having an automation just makes much more sense to me and honestly, our cue related complaints are effectively zero. It is nice that servers have some capability to control stuff out of the box and in the most basic of systems it might be sufficient but it isn't what I would want to design anything around.
| IP: Logged
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 2 pages: 1 2
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|