Kayenne/PBus/Lance/Spotbox issue
- Login to post comments
Had an issue last night that another TD and I worked on and couldn’t solve. Kayenne2.0, new MU (2nd event), 6-channel Spotbox split 2-channels for TD via Lance, 4-channels for use as EVS for replay. We had an issue with the 2nd TD channel. Any effect would cue properly, but not play. It would act like there were simultaneous play and stop triggers. The length of delay between recall and play did not have an impact. Everything worked properly when triggers were tested from the menu panel. We tried swapping pbus addresses, ganging, independent timelines, etc. The problem always stayed with the 2nd channel. Multiple clips, cues were also attempted. Time was short so we gave up, and I built the effects using macros to do the recalls and triggers. I am not scheduled to see this truck again, so a quick solution is not needed. I am just frustrated that I needed to use a work-around as opposed to solving the problem. Given that a) this was my first Kayenne show, b) it was a new MU, and 3) the Spotbox was being used in a less than ideal configuration; any thoughts?
- Login to post comments
Hi Seth
I'm not sure if this might be part of the issue, but since the Kayenne is based on the Kayak frame this might be one cause. I remember that in a dual situation elements would cue, but misfire upon doing a replay for instance.
In the dual world and with the Kayak only, this problem presented itself during a NHL game I was working on the Dual side. We all seem to go to a replay at the same time, but there were triggers happening causing the "dual side" Lance to miscue and also misfire at times.
This was very embarrassing because everything worked fine in pre-pro but not during the show and it was intermittent. After the show I looked into the problem because it really ticked me off and I was curious how this could happen with each getting different PBus commands.
I found that the home TD was sending a recall command higher than 100 to his Lance to recall effects and that communication sent an additional command (somehow) to the "dual Lance" causing it to misfire. It had to do with the way the home TD built his show. I merely corrected his timeline to have the Home Lance call up a register number only and not send the command 100 cues and that solved the problem. I'm not sure if this is what your are experiencing, but it could be part of the problem.
That happened to solve our problem and it never reared its ugly head again. I'm not even sure if software was developed to stop that from happening, but it could have worked it's way back into the Kayenne build.
Hope all else is well.
Best,
Rick.
<!--EndFragment-->