There were some initial issues for some with 4.0.0 but now we have a version which has addressed many things at 4.0.1. Personally for me the whole process has been totally painless and I just love V4. I think it is way ahead of V3.

Sample One XT and Impact XT are vast improvements over the original versions which have been in need of an update and now have been refreshed very well indeed.

There are many new features in V4 not in V3. Check out some videos on Studio One Expert for example to get a handle on all the new features. See if the new features interest you and will improve the way you work e.g. Chord Track, Pattern Editor, Drum Editor, Import Song data, AAF import/export, Ripple edit mode, bar offsets now, Track notes, some great GUI improvements etc..

Some with Waves plugins have had a few issues as Waves has just gone from V9 to V10 and in the process there have been some hiccups. If you do the Waves upgrade carefully and correctly you won't have any issues.

Plug-in scanning has caused some things for some but I think most of that has been resolved now. I had no issues and my effects and synth plug-ins were all found and work no problem.

A cursory glance told me the plugins problems was with Windows 7, which I'm not running. Would you recommend I go into my Waves central and update everything there first and then go and update to SO4, or the other way around?

Good question and maybe others might chime in with some ideas on that.

To be honest I cannot remember what I did first because I did them both very close to each other. I think what happened in my case was I went to V4 first and all my Waves plugins showed up after the V4 install. Then I went from Waves V9 to V10.

It gets a little tricky if some of your Waves plug-ins are out of their WUP (Waves Update Plan) and are no longer getting free updates. When you go from V9 to V10 you will be asked if you want to keep your V9 stuff. I answered NO (I should have thought that first, I was a bit quick there!) and the 2 out of my 25 Waves plugins that I had that were not getting free updates anymore disappeared all together under V10. You are able to buy individual WUP plans for just one plug-in for around $10 or so and I did this for the two missing ones and all was fine again.

But say YES to this question instead and your V9 out of date plugins will still be there under V10 (except they will be at V9). They should all work fine too.

You just have to decide then whether to pay for all of them to update and stay updated ($225 capped price for all Waves plug-ins for a year) Or just leave them alone and keep using them as they are. Or just buy the odd individual update plan for them. Mostly the updates are nothing world shattering so you just keep using them after they run out of their WUP. But if a plug-in gets some serious improvements and new features then maybe just get the plan for that one. It is possible to find out what the updates are up to here I believe:

https://www.waves.com/downloads/release-notes#v10

For me it was painless and worth the price of admission even if you didn't use all the new stuff, well worth it to have the current version with updates for the next 2 or 3 years (if things are the same as v3 -v4), and keep the same rock solid stability and speed that I always had with v3. ymmv

As for Waves, I had zero issues updating my eligible plugins to v10 while keeping the rest at v9, have a read, the process was easy as. As for before or after Studio One v4, not sure it matters, I done Studio One 4 first then Waves v10 simply because that's the release timeline, everything works perfectly.

For me - it was amazing. And I have a bunch of Waves stuff as well. Be sure to get your Waves stuff working 100% in v3 - upgrade the Waves installer etc so that is set. Then use the 4.01 installer for S1v4.

My install was so tidy - when S1v4 started for the first time - it even remembered the exact positioning (On the Windows desktop) that I used with v3. It was so uncanny - I thought it was my v3 install - so I just started a new project and got right back to it.

Yesterday - I gave v4 the big test which was a 50 minute voiceover session with all the usual heavy editing, wav file creation etc - it was flawless.

I say get in there!

VP

I had no hiccups at all. I think there was only one new soundset (or i never downloaded it before).
Waves and all VST worked. Just had to add some paths in S1 options.

I feel lucky, not bragging.

On Mac I seem to recall having to re-do all my keyboard shortcuts and preferences.

It sounds like you're matching a v3 workflow with Sample One and Impact for a client. If that involves using v3 patches and kits you may want to set aside some time to use the Demo version and play with Sample One XT and Impact XT for your specific application. They've improved the v3 compatibility a ton in v4.0.1 but you may just want to make sure it fits your bill. If you’re using an old song file make a copy because once you save it you can’t open it in 3 again.

I think v4.0.1 is pretty great but it's always hard to gauge how happy someone is going to be with switching and preserving an older version's workflow, song file, etc. Especially if the changeover is expected to be done quickly, seamlessly, and "on the clock" so to speak. Every user's situation is different so demoing it and leaving your v3 install is imho the safer of the options.

In my case, not only was it painless, it cured pains I already had

Just as a point of reference, I haven't updated any waves plugs for over a year or more, and had no issues moving over to 4. Pretty much the same experience I have had moving from 1-2, then 2-3.

I think the major thing I haven't seen mention:

By default, S1 4 installs in its own folder, doesn't disturb your v3 install. You will have both on your machine, and if there is an issue, you can go back to 3.

For most of us, it was a seamless update, especially if you're on Win10 or the Mac. But everybody is unique, so the parallel install is a huge win.

Once you save a song as v4, it can't be opened in v3, but if you do a "Save As" after opening in v4, you'll have both versions available to you.

Very low risk. Go for it.

Unsure whether this should be on a new thread but...

I'm on the cusp of (finally) getting my mixes (all S1v3) into the Project page for burning to CD. Should I do this before upgrading to S1v4 or will I be able to apply a mixture of songs mixed in v3 and v4 to the Project page in v4 without issues?

Regards.....

Hi All

I've just leapt into the unknown and splashed out on 4.0.1 via this site (at work when I had a moment). So tonite I will discover exactly how painless or painful this is

I shall report back!

I will do a parallel install as has been recommended - my DAW machine only runs DAW stuff, so should be nothing there to interfere with things.

If you were on V3 before upgrading to V4.0.1 then the V3 folder will already be there and it will be left alone. When you install V4 it automatically creates a V4 folder. You do not have to do anything special here in order to create a parallel install.

Anything else that you may do might mess this up. i.e. do not create any special folders for V4.

Studio One always creates a new folder when there is a major upgrade in versions e.g. V3 to V4. Updates of a current version are put into their original folder. i.e. when 4.1 comes out it will overwrite 4.0.1 and go into the same V4 folder.

Painless

No worries (so far)

Jemusic wroteIf you were on V3 before upgrading to V4.0.1 then the V3 folder will already be there and it will be left alone. When you install V4 it automatically creates a V4 folder. You do not have to do anything special here in order to create a parallel install.

Anything else that you may do might mess this up. i.e. do not create any special folders for V4.

Studio One always creates a new folder when there is a major upgrade in versions e.g. V3 to V4. Updates of a current version are put into their original folder. i.e. when 4.1 comes out it will overwrite 4.0.1 and go into the same V4 folder.

Very true - what I was trying to say was I wasn't going to purposefully replace V3 instead during the install, ie I was going to let the thing do what the thing does .

I'll be loading v4, myself soon, so just a thanks of your experiences from my POV. Not that i had any concern of a new install. My delay was more about finishing a project is all, or I would have jumped on updating. Still a few weeks away. I'm picking up a DAC amp, and CD publishing. I am using win7, so ill keep an eye on that, so if it's smooth sailing, I'll report that it goes well for any others inquiring.

Someone will always have an issue somewhere. It's like hearing about a plane crash. Suddenly, some people are hesitant to fly thereafter, discounting the thousands per day successful flights. It's that little ink dot on a sheet of paper that ruins it. Oh wait, bad example. We don't use paper any longer.

I have to say, I find this thread very reassuring. Like someone else said, I am not convinced that I need any of the new features as such, although some might be fun. My motivation is simply having up to date and supported software for music making, which is an important part of my life.

I don't object to investing in V4 simply for that, so long as it is painless and as wonderfully stable as V3 has been since I left Sonar behind last year

Guess I'll press the upgrade button very soon.

billsaunders1 wroteMy motivation is simply having up to date and supported software for music making, which is an important part of my life.

I don't object to investing in V4 simply for that, so long as it is painless and as wonderfully stable as V3 has been since I left Sonar behind last year

Guess I'll press the upgrade button very soon.

Yeah all that was my motivation to upgrade... bug fixes and eventually new features that will apply more to what I do. Also a Sonar refugee.

darrenporter1 wrote

billsaunders1 wroteMy motivation is simply having up to date and supported software for music making, which is an important part of my life.

I don't object to investing in V4 simply for that, so long as it is painless and as wonderfully stable as V3 has been since I left Sonar behind last year

Guess I'll press the upgrade button very soon.

Yeah all that was my motivation to upgrade... bug fixes and eventually new features that will apply more to what I do. Also a Sonar refugee.

This is a me too

I probably won't be using most of the new functionality either, except maybe drum editor - more interested in behind-the-scenes improvements and fixes, and future upgrades/hotfixes etc.

The main thing I want in S1 is a halfway decent staff editor - I dislike using this crazy link between S1 and Notion, it don't do the creative flow a lot of good

Ditto on the Sonar.