Studio One Pro Update Releases?

[Gary Shepherd]

I am talking about Impact XT and Sample One.

Presence is also a stock sampler so it was difficult to tell from your post - Presence is a very good sampler and I use it for drum samples too. Impact XT has a limited use for me (unless I use the drum pads) but most of my drum sets are on Presence and you can have a full spread, all the way on the keyboard and note all these on the Pitch names in the drum edit mode. Maybe you should check out Presence and use the Editor function. I now have loads of patches from samples on my favourite hardware synths and drum machines.

 

[imacken]

I'm a little confused by the lack of updates to SO7. I mean, it has been about 7 months, I think, since the release, and we were promised 3 or 4 major updates a year and yet here we are with basically no major updates with only a few months to go till we (optionally) have to renew our annual subscription.
Any idea what is going on with Presonus?

Thanks.

(Please don't ask me what updates I would like to see. That's not my point.)

We are all patiently waiting....it's been 215 days since S1v7 was released and the one (and so far only) Feature Drop - was on Jan 29,2025

VP

Yep, that was my point. What is going on? Should we be worried about Presonus?

Yep, that was my point. What is going on? Should we be worried about Presonus?

No one has any idea what is going on. These guys do not talk about anything, share anything or give the slightest clue about anything.

I am not worried - yet. But I must admit - I am getting there.

VP

I am not worried - yet. But I must admit - I am getting there.

I feel the same.

I'm a little confused by the lack of updates to SO7.

Should we be worried about Presonus?

Why? They said 3-4 feature updates per year.
One came end of January.
So far, everything’s on schedule.

Studio One 7.1 is online!

Hey everybody, Studio One 7.1 is online. Click here for the discussion thread: https://studiooneforum.com/threads/studio-one-7-1-discussion-thread.434/ _________________________________________________________________________________________ Version 7.1 Released (January 29, 2025) New...

studiooneforum.com

3-4 feature updates per year.

Lukas - to be fair - actually it has not happened "as announced".

For one thing - please do not gloss over the fact that some of us might just consider the 'year' (for v7 specifically) not to be the calendar year of 2025.

For me - it is actually the "year" that those of us (who purchased v7 on release day) paid for our first "year" of major updates - Oct 9, 2024 - Oct 10, 2025.

And - in the time frame between Oct 9 - Dec 31 2024 - we got exactly nothing. Basically three months of our "year" - gone right there.

So - as you state - "schedule wise things are still on track" - that only really washes (for me personally) if you mean Oct 9, 2024 - Oct 10, 2025.

If the 3rd Feature Drop (of "three major updates per year") actually drops in November 2025 - that is gonna cost me yet another $150.00 to get.

In that Sept Announcement - Presonus was clearly promoting 'More features - into your hands - faster'.

For me - that video's message was very clear. Now - if the update schedule is NOT what was promoted in the video and has now regressed back to same as any other past year - Presonus should simply say so and we will stop worrying about it.

I for one - having now paid annually for updates - thought this new funding model was somehow going to result in me - you know - getting "more major features" - "faster".

So - is it?

VP

And - in the time frame between Oct 9 - Dec 31 2024 - we got exactly nothing.

One was released in late January. If there are three in total, it still fits the timeframe... even by an Oct to Oct count.

One was released in late January. If there are three in total, it still fits the timeframe... even by an Oct to Oct count.

It will only fit the schedule if we get two more “majors” before Oct 9.

And Gregor clearly stated 3-4 major updates in the video. Not 3.

That does not feel doable at the current pace .

And I completely agree with imacken. If 7.1 was a “major” update I might need to reconsider my update plan later in the fall.

VP

Why? They said 3-4 feature updates per year.
One came end of January.
So far, everything’s on schedule.

Studio One 7.1 is online!

Hey everybody, Studio One 7.1 is online. Click here for the discussion thread: https://studiooneforum.com/threads/studio-one-7-1-discussion-thread.434/ _________________________________________________________________________________________ Version 7.1 Released (January 29, 2025) New...

studiooneforum.com

Why? Because 7 months on and we have seen only one update, and I don’t think many would consider that to be much of one.
Do you think we will see 3 major updates in the next 5 months?

One came in January. Another is coming soon. Anything beyond that is speculation for now.

If 7.1 was a “major” update I might need to reconsider my update plan later in the fall.

I recently explained it: 5.0, 6.0, 7.0 are major updates. 7.1 is a feature update.

Do you think we will see 3 major updates in the next 5 months?

Obviously, I can't comment on what's ahead - only on what's been publicly delivered so far.

Personally, I don't care much for more features or even "major" revisions to existing functionality, but at least bug fixes should be coming more regularly.

I am not sure why they don't do regular beta drops for those that want in like Bitwig does - they would get so much more testing and S1 would be that much better for it.

I recently explained it: 5.0, 6.0, 7.0 are major updates. 7.1 is a feature update.

Correction. v6.0,v7.0 are major version upgrades. We all know exactly what those are. No one is asking about those.

And according to that video - there is not even supposed to be “versions” anymore.

All updates are supposed to be “time based” with no (v7,v8) versioning whatsoever.

Feature Drops are exactly what we expect them to be. And what was promised/described in that video.

Any release that is not a maintenance update.

VP

 

[Trucky]

@imacken - Before posting (per the Forum "Terms and Rules") please use the search function to check for threads that may already exist. Your "Confused by the lack of updates" thread was merged here to the "Studio One Pro Update Releases?" thread that addresses this topic.

Thanks!

Forum Terms and Rules

 

[imacken]

@imacken - Before posting (per the Forum "Terms and Rules") please use the search function to check for threads that may already exist. Your "Confused by the lack of updates" thread was merged here to the "Studio One Pro Update Releases?" thread that addresses this topic.

Thanks!

Forum Terms and Rules

Will do!

 

[dkaimone]

I'm just hoping they fix their broken MPE feature.

Do people here realize it does not actually work correctly? At least for me and a number of other people that I've asked to test for the problem. It does not play MPE pitch back correctly. You can verify this by playing/recording an instrument MPE track while simultaneously outputting that track to an audio track and recording both at the same time as you play. The audio track will be correct, but the playback of the instrument track will not be correct. You can play them together and hear the pitch difference.

I'd appreciate it if anyone who uses MPE test it out and put a ticket in to PreSonus. I've reported it back in January, and support told me they were passing it on to the developers and maybe it would be fixed in an update.

 

[stanft]

[..]

I'd appreciate it if anyone who uses MPE test it out and put a ticket in to PreSonus. I've reported it back in January, and support told me they were passing it on to the developers and maybe it would be fixed in an update.

However, it seems a ticket's already been filed. Why another then?

 

[Vocalpoint]

I've reported it back in January, and support told me they were passing it on to the developers and maybe it would be fixed in an update.

Agreed with stanft.

If support passed this on - logically the DEV team knows about it and will address it in the future.

Exactly when this is fixed could be a long time or a short time based on priority and planning.

VP

 

[Lukas]

I'd appreciate it if anyone who uses MPE test it out and put a ticket in to PreSonus. I've reported it back in January, and support told me they were passing it on to the developers and maybe it would be fixed in an update.

Can you send me the ticket number via PM?

 

[Craig Anderton]

Another MPE problem is how it scrambles MIDI channels. For most instruments this doesn't matter, but it's an issue with MIDI guitar, where different strings may be assigned to different sounds. So, the strings need to maintain their channel identification. PreSonus is aware of this, but I assume MIDI guitar isn't considered a significant enough piece of the market to prioritize a fix.

I use Jamstik's MPE MIDI guitar, and talked with the company about the channel scrambling issue. I know they've been frustrated by this issue. But to loop back to the original topic, I'm less concerned with new features than I am with bug fixes. If an update includes lots of bug fixes, that counts as a significant update to me. We all know bugs are inevitable in any piece of software, so minimizing the number of bugs is always welcome.

 

[Vocalpoint]

I'm less concerned with new features than I am with bug fixes. If an update includes lots of bug fixes, that counts as a significant update to me. We all know bugs are inevitable in any piece of software, so minimizing the number of bugs is always welcome.

This is why I am so disappointed with the last set of maintenance releases vs actual Feature Drops.

When I first saw that Sept video presentation - I was very hopeful that the new emphasis on "better, faster" might actually include more rapid work on bugs - where Presonus could take just 3-5 known bugs, work them, fix them and get that hotfix pack out the door. And then move to the next.

But it appears there is little appetite for this agile approach as the bug fix packs seem to adhere to the same non-existant update cadence that all the rest of the work is on now.

The fact that we have not seen so much as a decent bug fix pack since Feb 12 - is quite sad actually.

VP

 

[dkaimone]

However, it seems a ticket's already been filed. Why another then?

I've been told the more tickets, the higher the priority because they perceive more users needing the fix.

 

[dkaimone]

Agreed with stanft.

If support passed this on - logically the DEV team knows about it and will address it in the future.

Exactly when this is fixed could be a long time or a short time based on priority and planning.

VP

I've been told the more reports of an issue, the more likely it is to be fixed.

 

[Vocalpoint]

I've been told the more reports of an issue, the more likely it is to be fixed.

Hmmm - not sure where you heard that.

"Feature Requests" work that way - to show demand.

But one support ticket for any issue (big, small or otherwise) should suffice.

Sort of like - this forum. One main post on a subject is golden. No need for 18 posts about the same thing.

And I can speak from experience - no support team wants to wade through hundreds of tickets pertaining to the same issue.

VP

 

[dkaimone]

Another MPE problem is how it scrambles MIDI channels. For most instruments this doesn't matter, but it's an issue with MIDI guitar, where different strings may be assigned to different sounds. So, the strings need to maintain their channel identification. PreSonus is aware of this, but I assume MIDI guitar isn't considered a significant enough piece of the market to prioritize a fix.

I use Jamstik's MPE MIDI guitar, and talked with the company about the channel scrambling issue. I know they've been frustrated by this issue. But to loop back to the original topic, I'm less concerned with new features than I am with bug fixes. If an update includes lots of bug fixes, that counts as a significant update to me. We all know bugs are inevitable in any piece of software, so minimizing the number of bugs is always welcome.

Absolutely! I've eyed the Jamstick for a long time since I'm a guitarist (and vocalist) at heart. But I've found creativity with the Seaboard Rise 2. Tried the Linnstrument which didn't do much for me. Different people take to different approaches, but yes I can see that being a real problem with guitar strings being assigned to channels.

If you're going to have MPE, it might as well work. Otherwise remove the feature. That was my proposal to PreSonus.

 

[dkaimone]

Hmmm - not sure where you heard that.

"Feature Requests" work that way - to show demand.

But one support ticket for any issue (big, small or otherwise) should suffice.

Sort of like - this forum. One main post on a subject is golden. No need for 18 posts about the same thing.

And I can speak from experience - no support team wants to wade through hundreds of tickets pertaining to the same issue.

VP

Then I stand newly informed.

 

[Craig Anderton]

I can see that being a real problem with guitar strings being assigned to channels.

The workaround is to copy the guitar part into multiple tracks, and restrict the channels on each track to handle specific strings. This works, but then playing becomes more of an offline process.

 

[dkaimone]

The workaround is to copy the guitar part into multiple tracks, and restrict the channels on each track to handle specific strings. This works, but then playing becomes more of an offline process.

That's a kink in the creativity flow.

If I want to add MPE track, I need to take everything and bring it into Tracktion Waveform (if I can get it to work) and record the MPE parts there, then bring it back to Studio One. Also a creativity flow killer.

 

[Craig Anderton]

If I want to add MPE track, I need to take everything and bring it into Tracktion Waveform (if I can get it to work) and record the MPE parts there, then bring it back to Studio One. Also a creativity flow killer.

This is why I'm so glad that .dawproject is being improved instead of abandoned. It's unrealistic to think that a DAW can do everything you want a DAW to do. Different DAWs will always have special features. I'm sure it works both ways - how many people who don't use Studio One would love to be able to take advantage of the harmonic editing?

Another workaround for MPE MIDI guitar is to do a two-track song premix, import it into a different DAW that handles MPE properly, record the MIDI guitar part, export it, and send it back to Studio One.

I've lived through the days of window splices, head lapping, and bouncing premixes to open up tracks with tape, as well as the early days of digital audio when 1 GB hard drives cost $2,000 and virtual instruments were unusable. So I'm quite happy with the current state of the art. I've never had to make fewer compromises in the music-making process, so I don't mind having to compromise the workflow from time to time to accomplish something specific to my needs but is not relevant to most people.

 

[Lukas]

Another MPE problem is how it scrambles MIDI channels. For most instruments this doesn't matter, but it's an issue with MIDI guitar, where different strings may be assigned to different sounds. So, the strings need to maintain their channel identification. PreSonus is aware of this, but I assume MIDI guitar isn't considered a significant enough piece of the market to prioritize a fix.

Sometimes the devil’s in the details. MPE uses dynamic channel allocation. The spec doesn’t require notes to always use the same MIDI channels across playbacks - at least in poly mode. It only mandates that each note-on uses a free per-note channel, and the note-off must match the same channel. After that, the channel can be reused - meaning the exact channel assignments can (and will) vary between playbacks.

Some instruments apparently have made the design choice to encode the string number into the MIDI channel - even though that's not part of any official spec and often without verifying that this works across all major DAWs.

In Studio One, for example, per-note MIDI channel data is not persisted. When outputting MPE, it dynamically uses the next available channels, exactly as the spec suggests. So you could say Studio One doesn't support this particular workaround - or that the plugin relies on a non-standard hack that was never guaranteed to work in the first place.

 

[dkaimone]

This is why I'm so glad that .dawproject is being improved instead of abandoned. It's unrealistic to think that a DAW can do everything you want a DAW to do. Different DAWs will always have special features. I'm sure it works both ways - how many people who don't use Studio One would love to be able to take advantage of the harmonic editing?

Another workaround for MPE MIDI guitar is to do a two-track song premix, import it into a different DAW that handles MPE properly, record the MIDI guitar part, export it, and send it back to Studio One.

I've lived through the days of window splices, head lapping, and bouncing premixes to open up tracks with tape, as well as the early days of digital audio when 1 GB hard drives cost $2,000 and virtual instruments were unusable. So I'm quite happy with the current state of the art. I've never had to make fewer compromises in the music-making process, so I don't mind having to compromise the workflow from time to time to accomplish something specific to my needs but is not relevant to most people.

Makes sense!

Yes, I'm an old-timer too, started out with Dr. T's sequencer and TiGER on Atari ST (and a four track tape recorder).

We can complain, and we should if a feature is offered that doesn't work. Not meeting the MPE spec with channels is one thing, but having MPE pitch not playback in tune is another. I'm not sure how this got past QA, you'd think someone would have noticed. But yes, software is always developing, mutating and hopefully improving.