Studio One 7.2 - Discussion Thread

[Craig Anderton]

Re boring improvements vs. flashy new features: Now that vetted product reviewers are essentially extinct, positive word of mouth is the best marketing a company can have. Retaining veteran users who still talk about how much they like Studio One, while attracting new users, is a marketing department's dream. A development team that can navigate that balance is crucial to a product's long-term success. Consider how Line 6's Helix firmware updates, which have always balanced boring and flashy, have kept the hardware viable (and the sales pretty much constant) for 10 years.

Re stem separation: I've used it lot for restoration with masters. To be able to, for example, fix a vocal (and I don't necessarily mean pitch correction - mostly EQ and DSP processes), or process a bass properly that was recorded in the 60s, is fantastic. Thanks to stem separation, I've been able to salvage masters that were considered unsalvageable.

 

[danam]

My philosophy these days is "Use as few tracks and layers as possible, and no less"; so your method would bring me full circle to the same 'unpack takes to new layers' problem I outlined in my OP, essentially having to delete 'new layers' I don't want added to the track when I'm just trying to fill existing empty layers with loop-record.

I guess nobody has the philosophy "Use as many tracks and layers as possible, if it makes sense or not"
But I hope I understand now how you want to work and what you tried to explain:
1. record 3 takes
2. record 3 more takes
=> the take menu of the event should then have 6 takes. But this is not possible. If you don't unpack the 3 takes from the first pass before doing the second pass, those first 3 takes will be lost, because the second pass would overwrite them
3. rename event
4. unpack those 6 takes to the next 6 layers that have no takes at the recorded region (no matter what those layers are named) => This is also not possible. You can only overwrite the first 6 layers or append 6 new layers.

I think you have a point here.

Now this is interesting. Also proves that what I'm asking for (ability to stop/start loop-recording and keep adding 'takes' to the same event container before unpacking) is already possible within the tech.

Honestly I have no clue what this has to do with the fact that using looped auto punch with pre/post roll creates a wav file per take.
But as I just noticed there is in fact a bug here:
1. deactivate "Takes as layers"
2. Do a couple of takes in a loop with auto punch and pre/post roll active
=> The event has no menu to choose between the different takes, only the last take is visible !!!
I understand the technical reason but it is not what I expect as user.... thankfully I am fine with using "Takes as layers"...

 

[lokeyfly]

Yeah danam, I invariably use takes to layers as well when comping.

@ TonalDynamics, Well, you seem to have a consistent workflow so Im not going to try to understand it. ; ) Your point was good about coming back to a song after a long time. I do as well at times, only I dont care if I used a Neumann U87 or a Fisher-Price knock off. Its going to amount to what's needed at the time. You can always list in the song info, or track info any equipment usage/stratagy. But that's how we all choose to work. Different is a good thing if it yields positive results.
Bye for now.

 

[TonalDynamics]

I guess nobody has the philosophy "Use as many tracks and layers as possible, if it makes sense or not"

Hah, you'd be surprised man... for me 'track creep' became a HUGE problem when I started getting into multi-mike setups...something had to be done.

Fortunately being able to use a single DI track with virtual amps/FX simplifies things a lot, as well as Studio One's own routing editor (which is unique in DAWland AFAIK, someone feel free to correct me if I'm wrong)

Horses for courses!

1. record 3 takes
2. record 3 more takes
=> the take menu of the event should then have 6 takes. But this is not possible. If you don't unpack the 3 takes from the first pass before doing the second pass, those first 3 takes will be lost, because the second pass would overwrite them

They don't get overwritten, just covered up by the latest loop pass so as you can't access them unless you unpack one event, DELETE it, unpack the next, etc (which also causes takes to be committed into layers out-of-sequence as well)

4. unpack those 6 takes to the next 6 layers that have no takes at the recorded region (no matter what those layers are named) => This is also not possible. You can only overwrite the first 6 layers or append 6 new layers.

Bingo, this is the issue.

Honestly I have no clue what this has to do with the fact that using looped auto punch with pre/post roll creates a wav file per take

I just mean it's proof of concept that you can append separate .wav files into the same event container via loop-record without needing it to all be a single continuous .wav that loop-recording typically creates.

I mean I guess they could (as I was posing earlier) concatenate a new looped-take .wav file with the previous one a la Ffmpeg or some similar program... but the behavior you've shown with the new pre-roll simplifies it a bit without needing to implement this.

So you would basically just allow this 'create individual audio file per take' behavior you've demonstrated to continue between stopping recording and starting back again and add some kind of toggle for 'continue recording takes if audio event is on timeline', or some such.

But as I just noticed there is in fact a bug here:
1. deactivate "Takes as layers"
2. Do a couple of takes in a loop with auto punch and pre/post roll active
=> The event has no menu to choose between the different takes, only the last take is visible !!!
I understand the technical reason but it is not what I expect as user.... thankfully I am fine with using "Takes as layers"...

Wow, nice one. Go ahead and make a BUG report if you would with your findings (How the heck does one even do this now since this forum isn't 'official' per se?)

Good catch!

JB

 

[danam]

@TonalDynamics I just did a bug report (was too late yesterday)

Bingo, this is the issue.

You can submit a support ticket here (I got the link from the signature of moderator Trucky):

https://support.presonus.com/hc/en-us/requests/new

Although you actually have 2 issues. I would report them separatly.

I just mean it's proof of concept that you can append separate .wav files into the same event container via loop-record without needing it to all be a single continuous .wav that loop-recording typically creates.

Ah ok, got you Though it actually does not work. The problem after step 2 of my last post (where I tried to streamline your process description) is the same as the bug I found. What they managed to do yet is to connect a layer event to a single .wav file.

Wow, nice one. Go ahead and make a BUG report if you would with your findings (How the heck does one even do this now since this forum isn't 'official' per se?)

Done! And I think you should too ASAP, because NOW they are working on this stuff and ironing out bugs users find for 7.2.1 (hopefully).

 

[lokeyfly]

I immediately noticed some nice visual tweaks to version 7.2 along the GUI. things like the events when displayed as a pattern editor have little squares along them and they somehow appear quite clear.

I haven't had a chance yet to install the Sub Zero Bass and its going to be a while before I do. I'm currently too much in the middle of some songs, but the auto-scroll, or more importantly lack of, and the center playhead movement are simply elegant. Real world stopping the scroll is just fantastic. Why? because Autoscroll doesn't auto kick in again, once dissabled. Wonderful.

When I get out from under this one song, I'll probably load Sub Zero Bass, to genuinely use it, combine it, or test it as a replacement for some upcoming bass tracks with new material. Version 7.2, has me pretty enamored with buying into the system, further. Meaning paying for version 8, 26, or whatever it's going to be called.

Enjoy!

 

[TonalDynamics]

I just can't get over how good the audio engine upgrades are on this release. Simply perfect. Fantastic release.

Sorry, can you be more specific here?

Are you talking about the export/mixdown reworks?

Did not see any direct reference to audio engine upgrades, I may have missed it

 

[ianaeillo]

Sorry, can you be more specific here?

Are you talking about the export/mixdown reworks?

Did not see any direct reference to audio engine upgrades, I may have missed it

Whatever inner-workings they did to the realtime mixdown process has eliminated nearly all of my time-wasting bounce issues. I’m no longer spending 40 minutes attempting to bounce a project without audio dropouts or suffering from phantom static pops during realtime bounces. It’s is substantially improved.

 

[apessino]

After a few days of banging on 7.2 (Mac M3 Ultra 32/80/256Gb, 15.5) I can confirm that S1 has never been this solid on an Apple Silicon Mac.

I have pushed it hard setting up a large orchestral template and I have had 0 problems. I am using a PreSonus Studio Live 64S mixer with a Studio Live 32R in stage box mode integrated via AVB, running 128 sample buffers and medium dropout protection. 12Tb of sample libraries on 3 Tb5 SSD drives from OWC, large number of external instruments and fx, and everything has been smooth as butter, even with as much as 100Gb of samples loaded and playing back dozens of instances of Kontakt and SINE.

Not only are all the rendering issues with Apple GPUs fixed, the playback glitches and stutters I had been experiencing non stop for the last two years seem to be gone too. I am sure there are some bugs left here and there, but this version of S1 makes me very happy.

Studio One is still by far the most productive and elegant DAW out there, as far as I am concerned. I love it.

 

[TonalDynamics]

Whatever inner-workings they did to the realtime mixdown process has eliminated nearly all of my time-wasting bounce issues. I’m no longer spending 40 minutes attempting to bounce a project without audio dropouts or suffering from phantom static pops during realtime bounces. It’s is substantially improved.

Ok I've pretty much never had mixdowns render pops/cracks, but I don't mixdown in realtime for this reason (technically it's not supposed to be possible with non-realtime MDs, because the computer calculates the required overhead somehow and slows down the process to avoid dropouts)

But this is great to know.

To be clear you're saying before the update realtime MD would give you pops and cracks you normally wouldn't get during playback of the same project/settings?

 

[Midiboy]

So, I think (at least for me), Tempo Detect is broken in 7.2. If I try to extract a tempo to the track, it crashes. I've now tried on 4 different MP3 files. (My goal is to take some of my old songs I recorded years ago and redo them). So far, no joy at all. I even took an Mp3 from another band (Styx's new album) and tried to detect tempo on it just to make sure it wasn't my files...nope. No joy. Can you all try to see if this is working for you?

The error simply says "An unexpected error occurred in this application or in a plug-in. A problem report has been created at:"

And then gives the location. Of course, you can't actually open these reports. I imagine Presonus can. But they aren't readable by us.

I did submit a bug, but just wondering if anyone else is seeing this. This is something that may make me go back to 7.1 for this project I'm working on.

 

[Trucky]

So, I think (at least for me), Tempo Detect is broken in 7.2. If I try to extract a tempo to the track, it crashes. I've now tried on 4 different MP3 files. (My goal is to take some of my old songs I recorded years ago and redo them). So far, no joy at all. I even took an Mp3 from another band (Styx's new album) and tried to detect tempo on it just to make sure it wasn't my files...nope. No joy. Can you all try to see if this is working for you?

The error simply says "An unexpected error occurred in this application or in a plug-in. A problem report has been created at:"

And then gives the location. Of course, you can't actually open these reports. I imagine Presonus can. But they aren't readable by us.

I did submit a bug, but just wondering if anyone else is seeing this. This is something that may make me go back to 7.1 for this project I'm working on.

"Tempo Detect" or "Extract to Tempo Track" work as expected for me using Studio One 7.2 and Windows 11.
Make sure you set the track to "Don't follow" in the Inspector before running the command.

MP3 files need to be converted to Wave files first which Studio One does automatically.
What method (Browser, Drag and Drop, etc.) are you using to bring MP3 files into Studio One and when does the crash occur?

 

[Midiboy]

Yeah. Definitely not working for me. I do it the same way I've always done it. Drag the MP3 over from Explorer. That part works just fine. It converts it to a wav and everything. When I right click and Detect Tempo, I get the crash. Same if I right click and Extract Tempo. Don't Follow is selected as well.

 

[Trucky]

Post a download link for one of the MP3 files that's crashing and I'll try it on my computer.

 

[Midiboy]

Nah, it's happening on every single MP3 file I've thrown at it, including ones was able to detect tempo before, and brand new ones from Styx's new album, Metallica's latest album, etc. It's something with my system. Not sure what, but I'm going to try the uninstall / reinstall thing.

 

[Midiboy]

Would love to see if this is happening to other people as well. I just did a COMPLETE uninstall and deleted my setting directory as well (after backing it up). Still no joy.

 

[Trucky]

Nah, it's happening on every single MP3 file I've thrown at it, including ones was able to detect tempo before, and brand new ones from Styx's new album, Metallica's latest album, etc. It's something with my system. Not sure what, but I'm going to try the uninstall / reinstall thing.

OK, I was just trying to help...

 

[Jeff]

No problem with WAV files for me.

 

[ianaeillo]

Ok I've pretty much never had mixdowns render pops/cracks, but I don't mixdown in realtime for this reason (technically it's not supposed to be possible with non-realtime MDs, because the computer calculates the required overhead somehow and slows down the process to avoid dropouts)

But this is great to know.

To be clear you're saying before the update realtime MD would give you pops and cracks you normally wouldn't get during playback of the same project/settings?

Correct. I was getting irregular and unpredictable popping and clicking similar to a digital clocking error at region starts and ends, regardless of fade status. For the most part, I can only do realtime bounces.

The largest problem was audio engine dropouts during mixdown when there was 8+ instances of pipeline on a project. The entire audio engine felt unpredictable at times. Now it is wonderfully smooth and reliable.

 

[Midiboy]

OK, I was just trying to help...

Oh totally! Sorry if that came across rude. Was not my intention. Most of the MP3 files I tried are copyrighted and I don't want to put them up for that reason. I could see you thinking it could be file I created myself, but these are even commercial ones from Amazon that I've purchased, etc. Since that's the case, and since this only started with 7.2, it's got to be something with that. I may go back to 7.1 to see if that fixes it. If not, then maybe a video card driver that was updated (cuz nVidia just did one). Video card drives cause ALL kinds of issues...even things you wouldn't expect.