sacred parcel
Curious one: When setting Master Output to “No Output” (for using a listening bus with something like AutoEQ), bounces are no longer correct in time. I've played around with my setup quite a bit checking through latency of plugins and arrived at the state where a pretty much empty project triggers this behavior just by setting the output to none.
NOT QUITE MY TEMPO
stiff juniper
not seeing that here (I have that kind of routing in my default template) for midi or audio tracks..
sacred parcel
I'm on macOS and I have a slight suspicion that it might have to do with Rogue Amoeba ACE
stiff juniper
that could be! mac os 15.6.1 here, but I am not using an external host for the monitoring chain (but either an FX or audio track in bitwig)
sacred parcel
Not using anything external either, but I have Rogue Amoeba stuff installed and I am experiencing some latency issues when running SoundSource, but only then. I think this might boil down to the same root cause.
south wyvern
Cannot reproduce with Beta 3 on Win 11. Master is set to no output, using a listening bus with headphone correction. Tried with drum machine and polymer, both were rendering fine.
stiff juniper
NOT QUITE MY TEMPO
as long as you don't hurl a chair at your screen, this is salvageable!
sacred parcel
Bitwig support answered with: why would you set the master to no output? The PDC will not work correctly when disabling the master output completely.
It did help in my case but apparently the issue is deeper than that? Polarity is running into similar timing issues with bounces as well.
stiff juniper
Bitwig support answered with: `why would you set the master to no output? The PD...
yes there appears to be at least one more reason PDC goes wrong..
wrt "why" a good reason to set Master output to none is of course that it enables a monitor chain that can sit between the master out and the speakers and be guaranteed not to be part of anything rendered/bounced out. (I guess that was your case?)
sacred parcel
Yeah, that was my case and I also answered that, they didn't reply after that. Actually previously they suggested a different setup from what I was using that also relied on no master output, so I think it was just a bit of confusion on their part
(They suggested using an FX layer on the master track instead of an extra FX track)
stiff juniper
(They suggested using an FX layer on the master track instead of an extra FX tra...
oh interesting I hadn't thought of that setup (sorry, I should not derail this issue thread)
sacred parcel
a better way to create a dedicated monitoring output if you need speaker calibration tools etc. would be an FX layer device on the master where you create a specific layer with the required VST and an HW FX device that sends to the desired output.
sinful quiver
stiff juniper
> a better way to create a dedicated monitoring output if you need speaker calib...
slight drawback of that suggested setup: at least in 5.3 you get no level meter on the master output (or the monitor chain) so need to view peak levels using a plugin.
sacred parcel
Yeah that's a good point