Where would I find the Preference File list for S1 now? Used to be at Library/Preferences or User/LibraryPreferences. I can't seem to find them now?

This new feature is very interesting : • MIDI program change for VST3 plug-ins

I wonder if Steinberg tweaked the VST3 spec, or this is something that Presonus was able to do, which is unique to Studio One ?

Hi folks,
great to hear about the new update - only, when will I be able to use it without losing Melodyne ?
I used the bundled Essential license to upgrade to Editor 2 (not too long before v4 was announced), quite some extra money, but ultimately worth it.
However, with that 3.3 bug I can't use Editor 2 anymore, and to add insult to injury, my Essential serial has been burnt by the upgrade so I could not even use Essential 4 as "poor man's workaround" if I wanted...
Somehow this mess doesn't exactly motivate me to throw another 150 after the already spent good money ...
not happy,
Rhino

This is my first update since purchasing Studio One last month.

We have to install in a new directory. What happens to all our settings from 3.3.1?

Is this the norm with Studio one? It's only a point release.

gavinsteiner wroteThis is my first update since purchasing Studio One last month.

We have to install in a new directory. What happens to all our settings from 3.3.1?

Is this the norm with Studio one? It's only a point release.

Yes this is normal so you can use both versions if you have older Songs just open them in the older version, new songs in the current update

Settings are preserved

profirhino wroteHi folks,
great to hear about the new update - only, when will I be able to use it without losing Melodyne ?
I used the bundled Essential license to upgrade to Editor 2 (not too long before v4 was announced), quite some extra money, but ultimately worth it.
However, with that 3.3 bug I can't use Editor 2 anymore, and to add insult to injury, my Essential serial has been burnt by the upgrade so I could not even use Essential 4 as "poor man's workaround" if I wanted...
Somehow this mess doesn't exactly motivate me to throw another 150 after the already spent good money ...
not happy,
Rhino

This is all on Celemonys end that you are describing here, the burning of the license and all that. You either upgrade or ya dont man. Problem you are having is you have to have the correct DAW to run with the correct Melodyne plugin, it dings us twice , I get that, nature of the beast Im afraid

This is all on Celemonys end that you are describing here, the burning of the license and all that.

sorry, but I fail to see the logic.
- Celemony's part is clear, that's why I don't want to reward them by spending more money with them.
- However, that's not the point I'm talking about.
- here's what Mr Kaiser wrote in the sticky (in August !) :

we're sorry to hear that a few of you are having problems running the new Studio One version on their systems.
Although our software undergoes hundreds of man-hours of beta testing, we cannot avoid bugs from ending up in a release version. In this case, we didn't recognize that there's a compatibility issue with Studio One Professional 3.3 and older versions of Melodyne.
Here's what we know so far:
Studio One users running a Melodyne version older than 4.0 (Essential or Editor) can't launch Studio One 3.3 after updating. Only Windows operating systems seem to be affected. There's no problem with Studio One Professional 3.3 and Melodyne 4.
If you're currently running Studio One Professional with the included Melodyne Essential 2.x, there's a very simple solution: you can upgrade to Melodyne Essential 4 for free! All you need to do is log into you MyPresonus account, navigate to your Studio One 3 Professional downloads, scroll down to "Extra Downloads" and download the latest Melodyne Essential installer. This installer will upgrade Melodyne Essential 2 to version 4.
If you're running Studio One Professional with Melodyne Editor 2.x and don't wish to upgrade to Melodyne 4, please stay on Studio One 3.2.3 for now and give us a little time to fix the problem and issue a Studio One 3.3 maintenance update. If we come across another solution to this problem, we will post it here and in the PreSonus Knowledge Base.
Once again, apologies for this inconvenience.

- fair enough, we all know stuff can happen, in this case with v3.3 Win, but here it's not Celemony to blame.

all I'm asking for is that promised, long overdue bugfix, no more, no less.
We're talking core DAW functionality here.
I'm sure I'm not the only one affected.

peace,
Rhino

profirhino wroteall I'm asking for is that promised, long overdue bugfix, no more, no less.
We're talking core DAW functionality here.
I'm sure I'm not the only one affected.

peace,
Rhino

Plugin issues like this really bug me < Get it? Lol) Nah but seriously, can you kindly elaborate on the problem in more detail, what exactly is causing this issue and why it's a pain. Is it something unique to your situation or does it affect every user?

multifederal wrotePlugin issues like this really bug me < Get it? Lol) Nah but seriously, can you kindly elaborate on the problem in more detail, what exactly is causing this issue and why it's a pain. Is it something unique to your situation or does it affect every user?

it's all in the official Presonus statement I quoted above.
as I understand it, Melodyne 2 crashes S1 v3.3 on PC, considering this explicit warning I'm still on 3.2 here.
Not having 3.3 won't kill me, but aren't we all expecting true greatness in 3.4, 3.5 and so on ?
I would hate to be locked out of that blindingly bright future, simple as that.
ymmv,
Rhino

profirhino wrote

multifederal wrotePlugin issues like this really bug me < Get it? Lol) Nah but seriously, can you kindly elaborate on the problem in more detail, what exactly is causing this issue and why it's a pain. Is it something unique to your situation or does it affect every user?

it's all in the official Presonus statement I quoted above.
as I understand it, Melodyne 2 crashes S1 v3.3 on PC, considering this explicit warning I'm still on 3.2 here.
Not having 3.3 won't kill me, but aren't we all expecting true greatness in 3.4, 3.5 and so on ?
I would hate to be locked out of that blindingly bright future, simple as that.
ymmv,
Rhino

The bug was fixed with the 3.3.1

Version 3.3.1 Release Notes (September 6, 2016):
The following issues have been fixed:
• [Win] Melodyne 2.1.2 causes Studio One to lock up on launch

Is it required to install in parallel?? What happens if I overwrite my current installation?

I opened a song I did edits on yesterday in the former version and no hassle. I saw no issues. I guess it works.

patricemazmanian wroteThe bug was fixed with the 3.3.1

Version 3.3.1 Release Notes (September 6, 2016):
The following issues have been fixed:
• [Win] Melodyne 2.1.2 causes Studio One to lock up on launch

thanks, Patrice !
With that sticky warning in plain sight I didn't bother to dig deeper of course ...
I'll check over the weekend and report back.
My apologies if this proves to be fixed indeed !
cheers,
Rhino

Hi i update yesterday to 3.3.2 and now my MCU Pro do not work any more, any one have that problem.

It shows on the MCU Pro screen '' security unlock failed''

Still crashing on startup in connection with rewire. Too bad.

Hello Everyone.

I updated to 3.3.2 today and opened a recent session. When it opened the Maag EQ4 plugin could not be found and it turned red on the track unusable. It still appeared in the browser as an available effect but if I tried to drag it onto a track as before, nothing happened and it would not appear. I didn't see this with other plugins in the session but didn't try them all. I tried reinstalling the Maag EQ4 from Plugin alliance with the latest installers and still same problem. This is not the UAD version of Maag EQ4. It is the regular VST3 version. I don't have the UAD version, but my other UAD plugins appear to be working as normal.

I then opened with the previous 3.3.1 version with no problem. So, this is feedback that may be useful. I use a late model Mac with Sierra. It would be helpful if some of you would check your mixes, if you use the same Maag E4 or E2 plugin to see if the same thing happens.

Chris

In regards to the problem i have with MCU Pro not working after up date 3.3.2, It is working on 3.3.1.