Studio One 7.2

[wikter]

I guess it also shows how few people are using midi sequencing plugins who use Studio One if the complaints about the issue aren't widespread or there's a lot of user who don't realise it's not supposed to work that way and think aligning the midi manually is just the "done" thing but you're right at some point if you're having to use another DAW to solve a problem, you may as well just use that DAW entirely, although the one thing I love most about Studio One is the ability to categorise all your plugins into folders and sub folders and have pictures of them to help remember exactly what you want to pull out, I'm not sure I could live without that now that I have it

Yeah, Studio One was born with poor MIDI spec. It's been always an audio priority sequencer and some General MIDI specs are not fully implemented.

[J Veronica]

If they stick to yearly versions, we're only 10-11 weeks away from the next big update. Maybe they'll call it 7.5, or begin the dated version numbering system (10.25).

Realistically, what could they add to bring people back in after a mixed year of updates?

[dastewart]

Realistically, what could they add to bring people back in after a mixed year of updates?

I've made my peace with sticking with Studio One v6 but I'll update if they introduce anything which is going to make my life better/easier and doesn't introduce a whole heap of bugs.

At the moment Presonus would need to pay me to upgrade to v7.

[starflakeprj]

Realistically, what could they add to bring people back in after a mixed year of updates?

Defnitely not more of the sampled instruments at least. It feels like: "We're out of ideas, let's give the customers a new sampled instrument instead, that will (hopefully) keep them happy a couple of months"

[wikter]

Fixes are always welcome... Even if they don't add features.

[Nameerf]

Are the midi timing issues not solved by doing that loopback latency test? I'm not sure if there's another midi timing issue but there's a PreSonus video where they show you how to set the audio and midi offsets...
Found it -

[Crossinger]

Fixes are always welcome... Even if they don't add features.

Here we go:

Version 7.2.2 Release Notes (July 29, 2025):

New features and improvements:
Added support for StudioLive Series III SE
Improved visual contrast handling for waveforms
Improved presentation of gain/fade handles on events

The following issues have been fixed:
[CLAP] Surround configuration not applied correctly
[Console] “Auto-expand selected channel” setting not retained
[Score Editor] “Show Chords” command displays incorrect positions
[Score Editor] Diminished/augmented/power chord symbols missing when using Roman numerals
[Score Editor] Synchronization to Arrangement fails with lyrics attached to notes
Audio Event may stop playing when using Mix Engine FX in combination with high-latency plug-in on FX channel
Bend Marker not displayed in Audio Editor when Audio Part double-clicked
Certain Audio Parts do not audition in Loop mode
“Cursor follows Edit Position” behaves incorrectly with 'Loop Follows Selection' enabled
Incorrect Metronome tempo on playback start with Ableton Link enabled
Note Editor shows wrong part when double-clicking multiple selections
Potential crash when Alt+dragging Audio Event with clip gain envelope enabled
Track Inspector doesn't show currently selected track after multiselection
UI lags near maximum zoom when “Show grid on events” is enabled and timebase is seconds or samples
Wrong tooltips in Multiband Dynamics plug-in

[Bowsy]

Are the midi timing issues not solved by doing that loopback latency test? I'm not sure if there's another midi timing issue but there's a PreSonus video where they show you how to set the audio and midi offsets...
Found it -

This is normal. You have to offset the RTL depending what buffer size your running etc. This works from what I gather but I also havn't tried it for a while. It's the DAW's internal PDC were the problems are. I'm totally ITB these days so external Instruments are not something I use to much. I always prefered Cubase when I had all my hardware synths etc. Cubase was way more flexible in this departement.

[Bowsy]

Realistically, what could they add to bring people back in after a mixed year of updates?

I've made my peace with sticking with Studio One v6 but I'll update if they introduce anything which is going to make my life better/easier and doesn't introduce a whole heap of bugs.

At the moment Presonus would need to pay me to upgrade to v7.

Snap. I don't care how cheap it is. After all the Fender hoo haa and the very first price increase, the old forums being wiped, so on and so forth. I thought yeh no chance, deliver what you promised and I will come back to check in a years time. The cost means nothing to me over doing the right thing with regards to the DAW.

The question mark still remains as far as I'm concerned. I'm one of the gang that pay's up within 24hrs as well, not this time though. As you say V6 is fine for my needs.

[dellboy]

Just received an email for new "StudioLive Series III SE". So the "update" was for support for a new product. Glad I stuck with version 6.

[Digivolt]

Those Studiolive do look nice though not a bad price either

[stanft]

Are the midi timing issues not solved by doing that loopback latency test? I'm not sure if there's another midi timing issue but there's a PreSonus video where they show you how to set the audio and midi offsets...
Found it -

This does not solve all the problems ... at least not mine: https://studiooneforum.com/threads/dela ... ments.733/

[tonedef71]

Does anyone here use the Scratchpad feature in Studio One 7 anymore?

I added a single Scratchpad to a project and then found horizontal seeking within the project to be quite cumbersome, and it did not matter if the Scratchpad was visible or not. The scaling factor when dragging the horizontal thumb on the scrollbar was over-the-top. The thumb became smaller and was harder "to grab" with the mouse pointer. A couple of simple clicks on the horizontal scrollbar and the cursor would seek out to like measure 10000 (but there were just over 100 measures in the project).

From my experience, the Scratchpad feature is best left ignored. Was it always this messed up, or did it get messed up after the integrated launcher feature was added in version 7?

[wikter]

I erased the scratchpad command after some wrong Ctrl+V press, I find It useful for demo creators, but useless for self producers.

[tonedef71]

I erased the scratchpad command after some wrong Ctrl+V press,

That's not a bad idea. I have also triggered the Scratch pad command unintentionally a number of times.

I find It useful for demo creators, but useless for self producers.

Interesting. I had traditionally been using Scratchpads as a way to put aside ideas that I might want to revisit later in the track (although I rarely would revisit those parts; but it did gives me some peace of mind that I could easily pull them back into the track if need be). But with the hassle it seems to add to navigating horizontally through a track, I don't find the feature worth using anymore.