Lately I have been using scenes on my QU-16 to simply recall custom fader layouts. Effectively, this just creates more custom layers. In general, everything works great - with one large exception: Whenever I hit the soft key that recalls a given scene, there is a brief dropout in the audio, which renders this mixing workflow useless. I know that I am, perhaps, bending the rules of how scenes are generally used, but is there any way for me to achieve a seamless transition between scenes?
If this isn’t possible, it would certainly add huge value to the QU series if there was a software update that added more custom layers and could be assignable to soft keys.
Lately I have been using scenes on my QU-16 to simply recall custom fader layouts. Effectively, this just creates more custom layers. In general, everything works great – with one large exception: Whenever I hit the soft key that recalls a given scene, there is a brief dropout in the audio, which renders this mixing workflow useless. I know that I am, perhaps, bending the rules of how scenes are generally used, but is there any way for me to achieve a seamless transition between scenes?
If this isn’t possible, it would certainly add huge value to the QU series if there was a software update that added more custom layers and could be assignable to soft keys.
I did some further troubleshooting and found the source of the issue. When recalling a channel that is on a console preamp, the transition is completely smooth, however when using a D-snake preamp, there is a quarter second (roughly) dropout, even when recalling the same scene that is currently being used. This glitch even occurs when every single parameter is blocked from recall and all channels are safed.
The fact that the transition is seamless, with the onboard preamps tells me that the transition should probably be seamless with the D-snake preamp as well, but that is not the case. Additionally, the fact that this glitch happens even on safed channels, negates the usefulness of a safed channel.
I did try using a global filter rather than the individual scene filter and there was no difference.
Also, I am sorry that this post is in the wrong area. I tried to delete and re-spost in troubleshooting, but this post didn’t delete, so now I have two identical in General and Troubleshooting…
When you create these scenes are you allowing the scene to change every single channel and routing parameter or have you selected only specific parameters to change?
Thank you for your responses. I accidentally duplicated this thread in the General section and most of the replies have been in that thread, so in an effort to keep everything in one thread, please post any further responses there. Sorry about the mess!
Here is what further troubleshooting found:
I did some further troubleshooting and found the source of the issue. When recalling a scene with channels that are only a console preamp, the transition is completely smooth. However when using a dSnake preamp (on the AR2412), there is aproximately a quarter second dropout across all active channels that are using the stagebox’s preamps. This happens even when recalling the same scene that is currently being used as well as when every single parameter is blocked from recall and all channels are safed.
The fact that the transition is seamless, with the onboard preamps tells me that the transition should probably be seamless with the dSnake preamp as well, but unfortunately, that is not the case. Additionally, the fact that this glitch happens on safed channels, seems to negate the usefulness of a safed channel.
This issue renders much of the scene functionality on the QU console useless to me, because I always have open, safed channels that should not drop out when I switch scenes.
I haven’t tested the scene change directly yet, but the soft keys did work flawlessly with the console’s preamps. The problem occurs when using the AR2412 preamps.
“there is a brief dropout in the audio, which renders this mixing workflow useless.”
I get the same exact results here with my Qu24 running 1.82 and an AR2412, and could not agree with you more.
In my experiment, I was not using the custom layer.
I made the L/R safe with the left and right mains connected to the AR2412 L/R (11-12) outputs and get the 100 millisecond dropout you speak of Alex. That is just a guess on the time of the dropout. When the left and right mains are connected to the console’s L/R outputs it yields the same unacceptable results.
I even set scene filters to block Output patch, Mix and L/R processing and those don’t help either.
I am reasonably confident that A&H will fix this. I refuse to believe that this is a problem with the D-snake design or the AR2412 because I too do not have this issue with a GLD,… well not that I am aware of.
Alex said…
“there is a brief dropout in the audio, which renders this mixing workflow useless.”
I get the same exact results here with my Qu24 running 1.82 and an AR2412, and could not agree with you more.
In my experiment, I was not using the custom layer.
I made the L/R safe with the left and right mains connected to the AR2412 L/R (11-12) outputs and get the 100 millisecond dropout you speak of Alex. That is just a guess on the time of the dropout. When the left and right mains are connected to the console’s L/R outputs it yields the same unacceptable results.
I even set scene filters to block Output patch, Mix and L/R processing and those don’t help either.
I am reasonably confident that A&H will fix this. I refuse to believe that this is a problem with the D-snake design or the AR2412 because like Chris, I do not have this issue with a GLD and an AR2412 either… well not that I am aware of.
I opened a support ticket with A&H and I have a feeling that this issue will have to be fixed in the next firmware update, rather than by any setting that we may be able to adjust.
As far as the GLD goes, I have extensively used its scene functionality with the AR2412 and it did not exhibit the dropout. I have not, however, used the GLD with the latest Firmware, so you might want to test it.
