Presonus Studio One 6.1.2 Released

[andypryce]

where the program will *sometimes* simply ignore automation partway through when rendering a mixdown.

One of the main reasons I went back to Cubase after so may years. (Compared to Studio One clunky but no PDC issues or surprises).
Not many people reported this and there were no comments from developers. I wonder if it is fixed.
Studio One started great and they add nice features and workflow improvements but the foundation is not solid. At least it was not when I left at V5.

[jamcat]

Since upgrading from Studio One 5 to Studio One 6.1, I can honestly say this has been the best, most significant Studio One upgrade yet.

The ability to customize and simplify most every aspect of the interface, plus aux sends on the FX channels has completely revamped the way I work in Studio One. The interface is extremely refined now, and a complete joy to work in.

[force_redo]

I have no dog in this fight, I'm just curious:

The people who are flagging these sync issues here, have you reported these to tech support as well? And if so: What was the reply?
And if not, would you mind doing so, please? It would help the user base a lot if issues like this could be found and fixed, methinks.

More productive than looking for answers here, but nothing wrong in making others aware, of course.

[Bartone]

I have no dog in this fight, I'm just curious:

The people who are flagging these sync issues here, have you reported these to tech support as well? And if so: What was the reply?
And if not, would you mind doing so, please? It would help the user base a lot if issues like this could be found and fixed, methinks.

More productive than looking for answers here, but nothing wrong in making others aware, of course.

This is true.
Would be interesting here, if people reported the issues what was the reply?

[Vocalpoint Studios]

I have an Nvidia 1660 super GPU, 32GB RAM, SSD, etc. Everything runs very well otherwise. Any ideas?

Can't speak to that graphics card but all my trouble went away when I stopped using video cards altogether and now just use integrated graphics from the CPU. Been doing it this way for years now.

Totally understand the situation if you use you DAW machine for more than music - but S1 does not require a huge GPU layout at all.

And I doubt they would be testing any S1 build against specific high end nVidia gaming cards either.

VP

[bilrobins]

VP - Thanks for the response. The PC has to do many things, some requiring the Gphx card - which is pretty mid-range. I've a feeling that the issue is to do with GPU use and it would be great if S1 allowed the user to turn off, or select, the display card to use. Strange that the Mac version does allow this option. I think I'm stuck with it just being 'laggy' when S1 native plugins are displayed (only slightly annoying). I have informed technical but TBH they didn't seem very interested + they didn't even know whether S1 uses GPU in Windows - apparently the developers haven't shared that information with tech support, which seems very odd to me.

CHEERS

[Vocalpoint Studios]

I have informed technical but TBH they didn't seem very interested + they didn't even know whether S1 uses GPU in Windows - apparently the developers haven't shared that information with tech support, which seems very odd to me.

Well - the world of "GPUs" is a class by itself and its usually buyer beware in this case. Presonus has neither the time nor the resource to build\test Studio One to interact with all the possible permutations of GPUs out there.

Especially nVidia - who seem to have a new set of video drivers out every half hour most weekdays - designed to wring one more frame out of some hip game.

Can't imagine trying to be proactive designing Studio One to handle all these drivers, shaders and all the other stuff that these cards ship with these days.

That it works at all with most of these gamer cards could be considered a victory.

Cheers

VP

[bilrobins]

In fairness, every other DAW I've tried (many of them) don't seem to have any issues like this. Also, many VST plugins use GPU acceleration without any issues at all. Indeed, every other piece of software I use (and quite a lot use GPU these days) works just fine.

[Vocalpoint Studios]

In fairness, every other DAW I've tried (many of them) don't seem to have any issues like this. Also, many VST plugins use GPU acceleration without any issues at all. Indeed, every other piece of software I use (and quite a lot use GPU these days) works just fine.

You may then want to compare notes with other S1 users who are using a similar card (and Windows 11 - which is also a different ball game vs Windows 10) and see if anyone else has this issue.

I am not a good compare since I do not use a third party GPU and have stayed far away from WIndows 11 as well.

Also in fairness - third party GPU or otherwise - have never heard of the Presonus internal plugs having any "lag" issues with ANY cards in my travels.

Conversely - I have read a ton of differing opinions on "lag", stutters and other issues (in general) with nVidia GPU and WIndows 11 like here for example:

https://www.tomshardware.com/news/windo ... a_GPU_woes

Or here...

https://www.getdroidtips.com/low-fps-nv ... indows-11/

Hope you figure out what's up.

VP

[Digivolt]

I asked this on the presonus forum but no response, maybe somebody here knows

Is there a way within Studio One to see time signature and tempo of a specific midi file without opening it ?

I currently only know of one option to get this info and that is to Ctrl+O and select the midi file, this loads up all the data along with setting the time signature & tempo basically as a new song, an issue I have with this however is it always defaults to 44khz when I have my interface set at 48khz so it causes some issues where I have to reset the sample rate.

Is there a way to force midi files to open at 48khz and not 44khz, they're midi data so really there should be no reason they alter the sample rate when being opened

Or is there a way to get tempo and time signature information by just dragging the midi to a new track ? Or some other method I haven't discovered ?

Thanks in advance