Studio One 5 Available Now (5.3 Out June 29th, 2021)

[oneway]

The irony - they add a bunch of composer-related features...and still have a deal breaking bug for composers given many sample libraries (especially for strings) require a track delay. You can nudge the MIDI but most of us prefer track delay as you can easily turn it off and on when needed.

Yes, ironic, but as with many companies I doubt the developers are doing enough orchestral composition every day to notice . So they rely on feedback from users, many of whom were not even on-board yet due to the lack of other composition features. It’ll get addressed now that enough card-carrying users are talking about it I’m sure.

It’s all about the number of users talking about it. I remember they said officially that they had no interest in supporting NI’s KK system right up until it became the most popular feature request and they started supporting it.

[tonedef71]

This issue was reported a year ago so i dont think theyre in a great hurry to fix it.

Does this exist as one of those threads on the PreSonus website that we can vote on? If so, do you happen to have a link to it?

[jkez]

This issue was reported a year ago so i dont think theyre in a great hurry to fix it.

Does this exist as one of those threads on the PreSonus website that we can vote on? If so, do you happen to have a link to it?

There is a lenghty topic in the forums: https://forums.presonus.com/viewtopic.php?f=151&t=35636

Hopefully theyll notice now that quite some noise has been done.

I personally moved away some time ago- the MIDI and its automation (conequence of the Low latency monitoring options and block size dependancy) in S1 is just too erratic in its performance and rendered results.

[tonedef71]

There is a lenghty topic in the forums: https://forums.presonus.com/viewtopic.php?f=151&t=35636

Thanks for the PresSonus forum link.

Voxengo have these free plug-ins:
https://www.voxengo.com/product/sounddelay/
https://www.voxengo.com/product/latencydelay/

Would either of these also work to compensate for the scripting delays?

[MillerSam]

New Studio One controller announced
https://www.synthanatomy.com/2020/07/pr ... oller.html

[jkez]

There is a lenghty topic in the forums: https://forums.presonus.com/viewtopic.php?f=151&t=35636

Thanks for the PresSonus forum link.

Voxengo have these free plug-ins:
https://www.voxengo.com/product/sounddelay/
https://www.voxengo.com/product/latencydelay/

Would either of these also work to compensate for the scripting delays?

I dont think these go into negative values. Thanks for the links
One option is this one : https://www.kvraudio.com/product/minusdelay-by-bakuage but its Windows only.

[tonedef71]

There is a lenghty topic in the forums: https://forums.presonus.com/viewtopic.php?f=151&t=35636

Thanks for the PresSonus forum link.

Voxengo have these free plug-ins:
https://www.voxengo.com/product/sounddelay/
https://www.voxengo.com/product/latencydelay/

Would either of these also work to compensate for the scripting delays?

I dont think these go into negative values. Thanks for the links
One option is this one : https://www.kvraudio.com/product/minusdelay-by-bakuage but its Windows only.

I think the second plugin https://www.voxengo.com/product/latencydelay/ may compensate for the latency delay by coercing the DAW to push the timing of everything else forward, but I'm not really sure.

Thanks for the link to bakuage. That is the plugin that will achieve up -400 ms correction, but it does not report the latency value on the GUI for anything between 0 and 400 ms, correct?

[woodsdenis]

https://dmgaudio.com/trackcontrol does this work ?

[jkez]

Thanks for the link to bakuage. That is the plugin that will achieve up -400 ms correction, but it does not report the latency value on the GUI for anything between 0 and 400 ms, correct?

Havent tested it personally. It was suggested as a workaround in the Presonus forum topic.

As woodsdenis posted DMGs Track Control is also an option and its both Win/Mac. Maybe this one acts better with the latency reporting on GUI.

[Trancit]

I never used instruments like the bespoked here and perhaps I don´t understand the topic correctly...

But in general I find it a little bit the wrong way round... It´s not the Daw´s job to offer something to compensate a flaw inside some wonky Kontakt scripts... many DAWs do not even offer negative track delays (while I wonder why you not just place the midi events a bit earlier)...

Why do you not blame NI (and perhaps others) for not being able to bring something working on the market but relying on some weird workarounds people have to figure out themselves to line up the audio properly...??

[oneway]

I never used instruments like the bespoked here and perhaps I don´t understand the topic correctly...

But in general I find it a little bit the wrong way round... It´s not the Daw´s job to offer something to compensate a flaw inside some wonky Kontakt scripts... many DAWs do not even offer negative track delays (while I wonder why you not just place the midi events a bit earlier)...

Why do you not blame NI (and perhaps others) for not being able to bring something working on the market but relying on some weird workarounds people have to figure out themselves to line up the audio properly...??

There are a lot of good reasons why extremely heavy sample libraries with detailed articulations have, over the years, landed on recommending those delays for optimal performance. That is also one of the reasons many DAWS (Logic, Cubase, and Studio One) offer negative track delays.

They don't work correctly in Studio One, they've acknowledged they aren't working correctly, they just will get around to fixing it when they decide it's an opportune/important time to fix it.

I'm not one of those "my bug needs to get fixed NOW because I don't want to do any workarounds EVER" guys but I also don't think it's productive to say that it's not worth fixing something that doesn't work just because it's primarily for compatibility with other companies' products. You could make the same argument for any time there's an issue with hosted plugins or particular hosts, but good developers don't. Well, most of them don't

[WatchTheGuitar]

I find it a little bit the wrong way round... It´s not the Daw´s job to offer something to compensate a flaw inside some wonky Kontakt scripts...

I also haven’t used track delays, but if Studio One gives users somewhere to set a negative track delay and it doesn’t works as expected, especially if it does work well in other DAWs, then I’d say it is an issue in Studio One.
This looks like one of those issues that is massively important to the tiny percentage of people it affects, but most of us haven’t noticed.

[nusound mind]

Has anyone found cpu improvements on 5 from 4 or 4.5/6?

[jinotsuh]

No better or worse for me, but no scientific tests done either, just feels the same, and that's all that really matters.

[tonedef71]

https://dmgaudio.com/trackcontrol does this work ?

That looks worth checking out. My handy-dandy HoRNet TrackUtility plugin does not include a forward/backward delay utility.

Thanks for sharing the link!