8 posts
Page 1 of 1
Hey all..
Another issue I've been dealing with in recording sessions which seems to have only happened since v5...
I normally have my device block around 128/256 when recording or producing which is fine but as I'm getting into finalizing the song I bump it up to 1024/2048 as the plugins and processing becomes heavier.
Well recently I've wanted to quickly throw in some overdubs (vocals, guitars etc) so I choose my 256/128 block size again but the latency is a bad as when I have it set to 2048. in order for the new latency of 265/128 to kick in I have to restart S1.

This was never the case with v4.6.. I would switch back and forth between max device block and a much lower one as sometimes you wanna add things towards the end of the mix... but whenever I'd change the block size, the latency would reduce immediately no problem... Now, when I change to 256/128, there is still at least 2 seconds latency and I have to restart S1 in order for it to take effect.

Anyone got any clues?? Honestly it feels like these days I'm just dealing with issue after issue so really hope this is pilot error... BUT, never happened in v4.6 and I've been working this way for 10+ years.
Thanks!

Producer/writer
MacBook pro i9 - OSX 10.15 - Studio One v4/v5 - Apollo x8 - Dangerous Convert - SSL Fusion - Neve 8816 - LLD Silver Bullet - Dangerous Monitor ST - Faderport 1 - Console One - Amphions -
User avatar
by robertgray3 on Mon Oct 12, 2020 4:18 pm
Are you using green Z or dropout protection?

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by Robdp on Mon Oct 12, 2020 4:22 pm
Yeah green Z is on and dropout protection is max. I've tried using minimum dropout protection and still get the same behavior.
The weird thing is, I've never had to adjust these settings before. That h.as been my daily workflow since forever with S1v4 which is why I noticed it the very first time it happened with v5
The only setting I ever mess with it the Block size and thats it.

Producer/writer
MacBook pro i9 - OSX 10.15 - Studio One v4/v5 - Apollo x8 - Dangerous Convert - SSL Fusion - Neve 8816 - LLD Silver Bullet - Dangerous Monitor ST - Faderport 1 - Console One - Amphions -
User avatar
by robertgray3 on Mon Oct 12, 2020 4:25 pm
Maybe S1 isn’t talking to your interface correctly. I’ve seen some interfaces have issues with this. Just because it worked great in the past doesn’t mean it will work forever. Updates happen, issues come up, etc.

My interface switches fine without resetting S1.

By the way if Dropout Protection is at max then your whole session is at 2048 no matter what. Only the monitored track’s buffer will be set to the device block size.

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2
User avatar
by GMHague on Mon Oct 12, 2020 5:36 pm
Do you have any plugins over the master output? I have a couple, like Izotope, that create huge latency no matter what the settings.
User avatar
by Robdp on Mon Oct 12, 2020 6:50 pm
GMHague wroteDo you have any plugins over the master output? I have a couple, like Izotope, that create huge latency no matter what the settings.


Yeah I do but they've never had this effect on the latency when changing buffer sizes before. Taking them all off results in the same behavior sadly.

Producer/writer
MacBook pro i9 - OSX 10.15 - Studio One v4/v5 - Apollo x8 - Dangerous Convert - SSL Fusion - Neve 8816 - LLD Silver Bullet - Dangerous Monitor ST - Faderport 1 - Console One - Amphions -
User avatar
by Robdp on Mon Oct 12, 2020 6:52 pm
robertgray3 wroteMaybe S1 isn’t talking to your interface correctly. I’ve seen some interfaces have issues with this. Just because it worked great in the past doesn’t mean it will work forever. Updates happen, issues come up, etc.

My interface switches fine without resetting S1.

By the way if Dropout Protection is at max then your whole session is at 2048 no matter what. Only the monitored track’s buffer will be set to the device block size.



Hmmm yeah that could be it. How would I check if this is actually the case?
Apparently Support told me that Studio One still isn't "Officially supported" by Universal Audio for their hardware products which is crazy... maybe a little pointing the finger going to as always.

Producer/writer
MacBook pro i9 - OSX 10.15 - Studio One v4/v5 - Apollo x8 - Dangerous Convert - SSL Fusion - Neve 8816 - LLD Silver Bullet - Dangerous Monitor ST - Faderport 1 - Console One - Amphions -
User avatar
by robertgray3 on Mon Oct 12, 2020 8:34 pm
Robdp wrote
robertgray3 wroteMaybe S1 isn’t talking to your interface correctly. I’ve seen some interfaces have issues with this. Just because it worked great in the past doesn’t mean it will work forever. Updates happen, issues come up, etc.

My interface switches fine without resetting S1.

By the way if Dropout Protection is at max then your whole session is at 2048 no matter what. Only the monitored track’s buffer will be set to the device block size.



Hmmm yeah that could be it. How would I check if this is actually the case?
Apparently Support told me that Studio One still isn't "Officially supported" by Universal Audio for their hardware products which is crazy... maybe a little pointing the finger going to as always.


Does UA have it’s own program for changing buffer sizes? I *believe* on Focusrite and Roland interfaces if you switch the buffer in S1 then open that program it’ll show the current buffer.

Also, have you tried reaching out to UA and asking them about it? S1 may not be officially supported but they have made firmware fixes that address issues in S1 before if I recall.

Unfortunately, though UA’s product offerings were tempting, this is why I use a Presonus interface. If an issue like this pops up I don’t get stuck in a support gap. I’m not sure if it actually is an interface issue (though it sounds plausible), but it’s enough of a headache when something like XLN Addictive Drums turns out to not “officially” support Studio One. I don’t want it happening with my interface as well!

Mac OS X Mojave 10.14.6
Mac Pro (Late 2013)
3 GHz 8-Core Intel Xeon E5
32 GB 1066 MHz DDR3
Dual AMD FirePro D500 3072 MB
Quantum 2

8 posts
Page 1 of 1

Who is online

Users browsing this forum: peterbaird and 31 guests