PreSonus Forums

due almost already 3 years pass from PreSonus released studio one 3 looks like this may we expect to have studio one 4 what your expectations? this great update can be the big step to go over Cubase and logic in midi features due on audio features is already on the top.

Don't know when Version 4.0 will be released. All I know is that I switched to Studio One from Sonar last November and it already does everything I expect from a DAW. Anything added will just be icing on the "Cake" (pun intended!)

Hopefully we get a release, or at least some info in May

v4 in less than a month....! Time to start thinking about what we want from v5 then

I have NO insider information, but having looked back on the release pattern for Studio One, I am predicting/speculating/hoping that there is HIGH probability that we'll get Studio One v4 in late May or late June, before the big Summer break in Germany. Crossing fingers!

Let's see what happens!

I expect an update in may this year with ARA2 integration, and v4 next year as a 10 years anniversary version.

I'd be ok waiting another year for 4.0 as long as we get a robust 3.6 update soon.

I have plenty of wishes for new or enhanced features, but the number one wish is that we can have all bugs and weird behaviors ironed out.

I’m excited for whenever it comes out. I’ve said it before but as I watch tutorials and learn the program it’s really awesome how many daily use features were added between version 3.0 and now.

Skaperverket wroteI have plenty of wishes for new or enhanced features, but the number one wish is that we can have all bugs and weird behaviors ironed out.

Playing devil’s advocate here (I really don’t like software bugs) I don’t think there’s a difference to the user between bugs and missing features that would greatly improve their workflow. They’re all things that get in the way of using the program the way the customer wants to use it.

For example, it’s a little annoying to know that somewhere between v3 and v3.5.6 Multi-Instrument presents stopped retaining their color and naming when recalled. But if they added a ”mix” knob to the splitter in the channel editor or a ”mix” knob for inserts in general it would probably save me more time in the long run than I’d save renaming and coloring the first track of my Multi Instrument presets. I’m purposefully using small examples so it’s not the difference between a small bug and a huge feature

Skaperverket wroteI have plenty of wishes for new or enhanced features, but the number one wish is that we can have all bugs and weird behaviors ironed out.

WORD.


It's not like the version 3 development would ever have reached a single, stable update. Simply inadequate code, and the "clients are beta-testers"-policy is very unethical, still.

I dunno what the heck happened, since v2 was perfect. Never ever crashed on me.

I have e.g. a song file I cannot open with the latest version, as it simply crashes after a minute.


-Santeri

santeripilli wrote

Skaperverket wroteI have plenty of wishes for new or enhanced features, but the number one wish is that we can have all bugs and weird behaviors ironed out.

WORD.


It's not like the version 3 development would ever have reached a single, stable update. Simply inadequate code, and the "clients are beta-testers"-policy is very unethical, still.

I dunno what the heck happened, since v2 was perfect. Never ever crashed on me.

I have e.g. a song file I cannot open with the latest version, as it simply crashes after a minute.


-Santeri

I have had no stability issues with V3. I would say your system is having issues, not Studio One. I support dozens of people a day and any stability issues I see are most times system related and rarely Studio One related.

As to what you describe above, it sounds like a 3rd party plugin is having issues. That's my experience with my support group. But let me know if I can help in any way.

themuzic wrote

santeripilli wrote

Skaperverket wroteI have plenty of wishes for new or enhanced features, but the number one wish is that we can have all bugs and weird behaviors ironed out.

WORD.


It's not like the version 3 development would ever have reached a single, stable update. Simply inadequate code, and the "clients are beta-testers"-policy is very unethical, still.

I dunno what the heck happened, since v2 was perfect. Never ever crashed on me.

I have e.g. a song file I cannot open with the latest version, as it simply crashes after a minute.


-Santeri

I have had no stability issues with V3. I would say your system is having issues, not Studio One. I support dozens of people a day and any stability issues I see are most times system related and rarely Studio One related.

As to what you describe above, it sounds like a 3rd party plugin is having issues. That's my experience with my support group. But let me know if I can help in any way.

It’s probably mostly plugin related but we all use plugins. What’s wrong with the suggestion/wish that Studio One sandboxes its plug-ins like a few other daws do? I don’t really see a benefit from a system where an error in a VST or AU crashes the host entirely and make me lose my work.

I expect at least one terrible usage bug that has been lingering since the first day I used S1 to be fixed...solo in place is broken...and it has prevented me from using S1 in any professional manner, mixdown or tracking. It makes an otherwise brilliant software package useless, for me. I've done the complete description of the bug, made a video, documented the issue, and made a step by step procedure to vet it out. It was sent to engineering and it was confirmed but the response I got was that there were no plans to fix it in the immediate future and to look towards future releases for the fix...

I guess nobody uses solo in place except for me, because it only got a few votes...and no, the mute tool is grossly inadequate for that task.

I've stopped investing in any of the offers S1 has put out as it kind of makes it pointless to continue invest in a product that has a major flaw, IMHO, and so I won't be investing in S1V4 unless the SIP issue has been fixed.

...and yes, I'm a bit miffed that this has been 'blown off' as a rare case... I came to S1 to get away from Pro Tools, and this is the one issue that keeps me a hostage of PT...

Ok just to remind us, can you tell us in one sentence what is the issues with Solo?

ArKay99 wroteI guess nobody uses solo in place except for me, .......

I used to...but then I bought S1 and was told my antiquated workflow was out of fashion, and it would be best to just forget about it.

V4 - could it maybe play nicer with Izotope? RX6, Ozone and thumbnails....

Steve Carter wroteV4 - could it maybe play nicer with Izotope? RX6, Ozone and thumbnails....

You'd have to ask iZotope.

I would like to be able to adjust the cue sends from the faderport 8/16. But headphone mixes appear to be yet another antiquated workflow item.

jpettit wrote

Steve Carter wroteV4 - could it maybe play nicer with Izotope? RX6, Ozone and thumbnails....

You'd have to ask iZotope.

What’s wrong with asking both of them? DAW developers can reach out to popular plugin developers and vice versa.

The shortcoming can often be on the plugins end but that doesn’t mean both parties can’t be involved.

Thier busy. I personally report the anomalies to Izotope like the fact that their new interface falsely reports a dirty bit to S1 if left open.
They acknowledged the issue the week after V8 was released but have yet to fix.

The point is it is best to put pressure on the source of the issue.