Blast from the past... GVG 300 question
- Login to post comments
Hi all...
Here's one from a long time ago that I was told was a bug in the software of the old 300. It cost me a gig with a regular client as I had a problem with it on one show. The client chose to go to another TD to duplicate the problem the next day (which he couldn't) and so I got boned by that mobile company for about 2 years.
Anyhow, here's the scoop... drag out your dusty memory banks on this one....
Doing hockey on a 300. Had M/E 3 Key 1 as Chy 1. Key A as Chy 2. I was flying my replays in on PP Key A and telestrator on DSK. I programmed two emems on the master for tele on and tele off just in case it died. When I programmed this, I changed the key source for DSK on the "tele off" emem from telestrator to Chy 1.
At the time of programming the master emem, depending on what I had selected for the source for Key 1 on M/E 3, a recall of my tele on and tele off emem changed the hole cut source for Key 1 on M/E 3. For example, if I had Chy 2 selected on Key 1 source on M/E 3 when I programmed the master emems, if I did the recall, it would change the hole cut source on M/E 3 to Chy 1. It would do the exact opposite if I had Chy 1 selected on M/E 3, it would change the hole cut to Chy 2 ON AIR! Note, the crosspoint for Key 1 on M/E 3 stayed lit with the correct fill source. Just the hole cut source changed behind the scenes.
The EIC in the truck I was in was obviously totally unaware as to what the problem was (even though I was able to duplicate it 100% consistently) yet an EIC on one NMT truck told me that this was a known software bug in the 300. At this point in time, the 300 had been discontinued so there were no new software updates available.
I'm just curious if anyone else ever came across this "bug" in the old 300.
John Phillips
Edmonton, Alberta, Canada
- Login to post comments
Dan, I'm also running the Mac M1 with Windows 10 ARM on Parallels, and was able to get it to...