• Hi and welcome to the Studio One User Forum!

    Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!

Studio Pro 8 - Discussion Thread

Yeah I have the old version up and running in ver 7.3 on a touch monitor, but from what Daw Stew said there is a New Studio Pro version 2.
I am trying to get it recognise the old version but is not connecting to FSP8 for some reason.
Not to worry I am still using SO1 7 untill I am hooked into the New "SO1 8" .

Kindest regards
Scroll down 2/3rds of the site and click the +at Resources and you'll see downloads for Windows. There is the Arm and non Arm version
 
Hey guys, before I consider studio pro 8, I want to ask if on install version 8 will keep my studio one 7 configuration. I have spent a lot of time creating a custom view in the browser categorising all my plugins specific to how I like to seec them. I don't want to have to do that again.
Also anyone successful in importing your custom keyboard shortcuts to the new version
 
Hey guys, before I consider studio pro 8, I want to ask if on install version 8 will keep my studio one 7 configuration. I have spent a lot of time creating a custom view in the browser categorising all my plugins specific to how I like to seec them. I don't want to have to do that again.
Also anyone successful in importing your custom keyboard shortcuts to the new version
Install to a separate directory.

You can have many versions of S1/SP installed side-by-side.

VP
 
Thanks I'll try that, I'm assuming the V8 when installed will be the factory default. How would I go about importing my v7 settings so that V8 is exactly like v7
The installer will do all the work for you.

When you land in v8 after install - it should appear exactly as it did with v7 - settings and all

VP
 
Mojito bug: AMP Envelope adjustment is not possible. The ADSR pots works fine, but moving the AMP envelope points horizontally in the GUI always resets the value to 0.
Can you make a video? I don't see that here.
 
Great stuff. I'm hoping I can import my mixing template and then save it as version 8
It should all just come right in - been that way for me since S1v2

VP
 
Thanks Lukas. You're right, I'm referring to this issue. Now I understand why it's there and what it's good for. I just never noticed it in Studio One Pro 7, but maybe I have overlooked it.

But how about the solo button? Is the strange behaviour intentional too?
Now I tested mute and solo buttons with Studio One Pro 7.2.3. Both DAWs behave exactly the same regarding these buttons: mute buttons in track and channel act independently (now I know the reason for that), while behaviour of solo buttons in both DAWs is still a bit strange in my opinion (as described here). But maybe there's also a good reason for that.
 
It should all just come right in - been that way for me since S1v2

VP
Same here (since v5 that is for me). Just run the installer and even the new version opens in the custom windows size I use to accommodate for a vertical Level meter alongside the main view. That level meter loaded up with my songs.. ahem sessions just the same. Custom keyboard shortcuts work as wel... No interference from my side, all done automagically.
 
There is definetly something to the mentioned Plugin trouble and crash issues. Seems like some combination of plugins cause the noise issue before the crash.
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Install to a separate directory.

You can have many versions of S1/SP installed side-by-side.
After having installed Studio Pro 8, I noticed that Pro 8 copied many settings from Studio One Pro 7, such as ASIO settings or the project history. In fact, I didn't have to configure much before I started working with Studio Pro 8.

This tells me that Pro 8 might use the same configuration data as Pro 7. But Pro 7 and Pro 8 could co-exist, if Pro 8 just reads the Pro 7 configuration once upon installation and then creates a copy for its own. However, if there is only one configuration database which is used by both DAWs, then changes made in one DAW will overwrite the settings of the other. I can't tell yet which is the case.
 
After having installed Studio Pro 8, I noticed that Pro 8 copied many settings from Studio One Pro 7, such as ASIO settings or the project history. In fact, I didn't have to configure much before I started working with Studio Pro 8.

This tells me that Pro 8 might use the same configuration data as Pro 7. But Pro 7 and Pro 8 could co-exist, if Pro 8 just reads the Pro 7 configuration once upon installation and then creates a copy for its own. However, if there is only one configuration database which is used by both DAWs, then changes made in one DAW will overwrite the settings of the other. I can't tell yet which is the case.

You can have 6 or 10 or 20 versions installed. They all have unique configuration data. There is nothing "shared" whatsoever between any of them.

Back in 2018-ish - the most I ever had was 7 installed side by side. Nary an issue between any of them.

And I would not expect any issues with v8 being installed beside anything else now either.

VP
 
Is there a thread or information somewhere here that helps explain Account/registration/subscription changes now, apart from the software changes? I am getting precious little explanation from Support tickets. I am sure they are very busy, but it's a bit confusing out here for those of us who weren't following all the drama. My example: I had just paid for a full year (upgrading from previous month-to-month) of the (I think is was called) "Hybrid" license of Studio One Pro+ about a month and a half ago. Now it's called Fender Studio Pro+, and I went ahead and installed it. Fine. I don't mind at this point.
But on my (now) my.fender.com account page it shows my product key for FSP and registration date of yesterday and the "Eligible for all updates until Apr 11, 2026", 3 months from now! I am paid up to Nov-Dec. This I do not understand. So... I know most everyone is here to gripe about the software, but is there a place for "membership issues" or does anyone understand this here??
 
With a perpetual license you get all updates for a year, so if you bought it 1-11.9 months ago you're eligible for a free upgrade to Fender Studio Pro 8.
IDK about that. My Presonus is telling me it's a $99 "upgrade." Pretty ironic since they improved nothing but managed once again to break stuff that was fine. Keeping it real. Venture capitalists have destroyed everything Fender touches and this is the same.
 
Flashbacks to Gibson acquiring Cakewalk and effing that all up.
Feels like a big misguided effort to leverage a DAW into more guitar related purchases - somehow?
Pasting the Fender logo all over the software is not a 'plus'. I'm a guitar guy through-and-through but it turns me off.
Strongly suggests that Fender leadership misunderstands the DAW market.

Replace Ampire with a Fender/Mustang branded plugin, fine (which I tried and I find the UI very frustrating) but I don't want a guitar company making my music composition & production software and I don't want my music-software company making my guitars.
 
You can have 6 or 10 or 20 versions installed. They all have unique configuration data. There is nothing "shared" whatsoever between any of them.

Back in 2018-ish - the most I ever had was 7 installed side by side. Nary an issue between any of them.

And I would not expect any issues with v8 being installed beside anything else now either.

VP
Thanks. So if I run v8 with v7 still installed I should expect V8 to look and feel the same as v7. Could I then uninstall v7 without fear of V8 reverting back to default?
 
Thanks. So if I run v8 with v7 still installed I should expect V8 to look and feel the same as v7. Could I then uninstall v7 without fear of V8 reverting back to default?
Yes. But I would recommend keeping the previous version for a while.

For some context:

To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.
 
Back
Top