• 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 SSL 360

Peter Clipson said:
I think it's all in a name. Until it's updated, SSL 360 of course has no option on the settings drop-down menu to select Studio Pro as your DAW.

I have renamed my Studio Pro.exe file to Studio One.exe and everything works fine.
Click to expand...
Brilliant!!! I just did the same thing and all is well. I'm going to update my SSL support ticket to let them know.
 
Anyone try this on a Mac?
Peter Clipson said:
I think it's all in a name. Until it's updated, SSL 360 of course has no option on the settings drop-down menu to select Studio Pro as your DAW.

I have renamed my Studio Pro.exe file to Studio One.exe and everything works fine.
Click to expand...
 
I just did this on my MAC - and preliminary check is that IT WORKS!
I renamed 'Studio One 7.app' to 'Studio One 7OLD.app' (it still works)
I renamed 'Fender Studio Pro 8.app' to 'Studio One 7.app'
Brilliant x2!
 
Gadgetman said:
I can verify that SSL 360/UF8/UF1 do not work correctly with Fender Studio Pro.
From SSL support :
"We are aware of the issue, we have not brought support to Fender Studio Pro 8 yet and don't currently have an exact timeframe for when we will."
Click to expand...
These are the kind of issues that need to be tracked. Oh, Fender, Presonus or whatever will tell its Studio One users to buy into the new DAW. Same team, etc, etc. What you are finding out now is some things simply worked in version 6 or 7, and not in version 8. Even ver 7 had hiccups with NI's S mkIII series controller. Now with the advent of a new version 8, will that suddenly work? Was the issue with NI's controller only? Doubtful. As it now works with the other major DAW's but not Studio One. And potentially not with this version 8.

There seems to be some very clear oversites to version 8. So the "same team" has this all covered? You can run with that, and I hope it works out for you, but I'd track all of this info into one tidy place. I used to do that sort of thing if it effected me, only I'm not anymore. The proof will be in how Fender track compliance, and not the many ways a user can open version 8 to the various would-be user needs. Probably a good idea is make a list and note all these issues. Just saying.
 
lokeyfly said:
These are the kind of issues that need to be tracked. Oh, Fender, Presonus or whatever will tell its Studio One users to buy into the new DAW. Same team, etc, etc. What you are finding out now is some things simply worked in version 6 or 7, and not in version 8. Even ver 7 had hiccups with NI's S mkIII series controller. Now with the advent of a new version 8, will that suddenly work? Was the issue with NI's controller only? Doubtful. As it now works with the other major DAW's but not Studio One. And potentially not with this version 8.

There seems to be some very clear oversites to version 8. So the "same team" has this all covered? You can run with that, and I hope it works out for you, but I'd track all of this info into one tidy place. I used to do that sort of thing if it effected me, only I'm not anymore. The proof will be in how Fender track compliance, and not the many ways a user can open version 8 to the various would-be user needs. Probably a good idea is make a list and note all these issues. Just saying.
Click to expand...

The Kontrol S Mk3 keyboards don't work properly with any version of Studio One/Studio Pro because PreSonus/Fender have not updated the scripts to accommodate NI's v2 firmware for these devices.
 
TimC340 said:
The Kontrol S Mk3 keyboards don't work properly with any version of Studio One/Studio Pro because PreSonus/Fender have not updated the scripts to accommodate NI's v2 firmware for these devices.
Click to expand...
And that will happen when it happens in ver. 8 only v8 is out now. Thats a few months of not fixing what is a major player in a branded ecco system across many platforms. So those newer controllers are not optimum with Fender Pro whatever its called. My overall point is there are a lot of snags in version 8 that ultimately did work in v7. Some misses are so obvious that they never got through the beta testing? One place Fender and developers may want to have a better handle on is quality control. That includes beta testing. My point is only to encourage better quality. Something evidently missing. I have counted about one dozen items now. Only its not my place to list them. Of course some claims can be user error but the whole thing will benefit by tracking and proofing said claims.

I'm sure its being tracked and rolled up by someone, but I dont see a clear listing of it. For some, such a list isn't good for business. But you guys as a consumer paid into something. Are the same giddy smiles from a video release (like last year) going to win over those waiting on fixes?
Hey, lets see.
 
Last edited:
lokeyfly said:
And that will happen when it happens in ver. 8 only v8 is out now. Thats a few months of not fixing what is a major player in a branded ecco system across many platforms. So those newer controllers are not optimum with Fender Pro whatever its called. My overall point is there are a lot of snags in version 8 that ultimately did work in v7. Some misses are so obvious that they never got through the beta testing? One place Fender and developers may want to have a better handle on is quality control. That includes beta testing. My point is only to encourage better quality. Something evidently missing. I have counted about one dozen items now. Only its not my place to list them. Of course some claims can be user error but the whole thing will benefit by tracking and proofing said claims.

I'm sure its being tracked and rolled up by someone, but I dont see a clear listing of it. For some, such a list isn't good for business. But you guys as a consumer paid into something. Are the same giddy smiles from a video release (like last year) going to win over those waiting on fixes?
Hey, lets see.
Click to expand...
You might remember that VP and I had a fairly long discussion about this last year. You're probably right that if Fender ever does enable the Kontrol Mk3 v2 firmware update, it'll only apply to SP8. However, I have some doubts that Fender regard this as in any way a priority, and I wouldn't be surprised to see it never enabled in S1. In my case, I have other controllers that do offer the functionality that NI promise, so I can live without it - and I haven't seen any of the other DAWs that weren't in on the initial launch now be enabled. The ones that were enabled (at least in part) were Cubase 13+, Logic Pro 11+, Ableton 12.2,+, and Bitwig 5.3+ IIRC.
 
TimC340 said:
You might remember that VP and I had a fairly long discussion about this last year. You're probably right that if Fender ever does enable the Kontrol Mk3 v2 firmware update, it'll only apply to SP8. However, I have some doubts that Fender regard this as in any way a priority, and I wouldn't be surprised to see it never enabled in S1. In my case, I have other controllers that do offer the functionality that NI promise, so I can live without it - and I haven't seen any of the other DAWs that weren't in on the initial launch now be enabled. The ones that were enabled (at least in part) were Cubase 13+, Logic Pro 11+, Ableton 12.2,+, and Bitwig 5.3+ IIRC.
Click to expand...
Well, perhaps the NI mk3 isnt the best example I could have raised. Although its applicable. Again, and now again, I'm noting it would be a good idea if users note the many items being found that are not working. That's the SSL 360, along with other issues.

I also went over this discussion with VP. He has one and is keeping it in wraps as last I recall, anyway. I have a Mk2, but I was prepared to purchase the Mk3. I'm glad I didnt, but that certainly doesn't get people off the hook of being THE ONLY DAW, that hasn't fixed this issue. Was Fender or software developers going to prioritize fixing the Mk3 issue first? If you think that is what I'm proposing, than you've completely missed my point (twice now).

These conversations can go every way but the practical point given. Record the hits, and not the misses is typical with human nature (Carl Sagen - "Broca's Brain"). Of course starting a new frilly fresh look is going to sell more than a few hardware compatability issues. We know that. But we also know that only glosses over the problems or standard misses that Studio One has never addressed. This has been an ongoing conversation in this forum. I'm sure you've been in on, and seen those conversations. So there's a new release, a new badge, a new look. Aside from the instant reach into the back pocket to buy new, the industry will look upon how this DAW proceeds. Maybe that's an AI commercial everybody's DAW approach. Or something that utilizes more present hardware compatability. Again, time will tell how this DAW meets the expectations of others. Remember, just last year, new releases were going to be quarterly based on the year. So this is the year of Fender.
Along with some ridiculously missed errors.
But only count the hits, as it were.
 
Last edited:
I do think that we’re collating the issues of SP8 fairly effectively across the forum, and I’m sorry if I missed your point! I agree that there are several issues, going back over a few whole-number releases, that should have been addressed. I’m not sure I agree with you about any promises for quarterly updates. I remember Gregor stating an aim (not a promise, or even a target) of three to four updates a year but nothing was ever put in writing or even explained further, and I suspect the decision to go for the rebrand and a new version was made fairly soon after that video was made.

Anyway, that’s water under the bridge now and we have to deal with what we have. I hope that this new start will motivate a bit more ambition in the devs to both address some of the long list of requested or missing features, and the bugs which are an inevitable corollary of a new (or revised) product.
 
I've had many conversations with DawStew, Vocalpoint, a slew of others and you Tim on improving this DAW. Many conversations both stimulating, practical, and addressable. But here we are. What, to have those many seriously good points now come up in version 8.2? I dont expect an answer because no one could answer that. But if history tells us something that allows connecting of the dots, its that there will be more unfinished symphonies than there will be completed, or even missed entities with this DAW.

I'm good going forward, but lets keep our feet on the ground when we talk about Gregor, Joe, and the other character in that v7 promo vid shall we. You say they didnt promise anything. I say they held a carrot up to those with their hands on their wallets at version 7. Little happened. "So we can get those new releases to you sooner as they are developed" as I recall was the comment. On Fender release 8, Gregor mentions the exciting new clip launcher. Ah, another carot! Ask if anyone finds the clip launcher in this forum if rhe word "excited" comes to mind.

I'll be totally involved with creating with version 7. Its stable and fast. As 8 will eventually be. But I've removed myself from hoping things will get better in a way that competitive clip launchers are already laid out in some other DAW's or even standalone. Add to that the other fundamental points many of us have made at nauseum.
The common denominator that I see is that results continuously show themselves. Including lack thereof.

I also mentioned earlier that the NI issue with the Mk3 wasn't fixed in version 7.

The various comments and complaints of things wrong in version 8 are in many different threads. My earlier point was that its probably a good idea that some user of the product keep tabs, so you dont get snowed. After all, there's a blizzard coming!
Anyway, good speak, TimC340.
Best, going forward.
 
TimC340 said:
The Kontrol S Mk3 keyboards don't work properly with any version of Studio One/Studio Pro because PreSonus/Fender have not updated the scripts to accommodate NI's v2 firmware for these devices.
Click to expand...
Neither do the Arturia Keylab mk3. There would appear to be something about the S1/FSP code that's particularly challenging for third party software and hardware manufacturers to interact with. I don't want to repeat all the pending unsolved integrations yet again, I think at this point most of you know what I'm talking about. It's gone past one guy's personal opinion into the realm of undeniable fact.
 
From SSL support: “I have reported this to the product manager and the software team to log this bug. We would look to fix this with the next release of the software”.
 
ETNABASS said:
From SSL support: “I have reported this to the product manager and the software team to log this bug. We would look to fix this with the next release of the software”
Click to expand...
That's going to be a long wait then. Typically SSL only release 2 versions over 12 months. We won't be seeing a new version this month or February
 
Last edited:
Peter Clipson said:
I think it's all in a name. Until it's updated, SSL 360 of course has no option on the settings drop-down menu to select Studio Pro as your DAW.

I have renamed my Studio Pro.exe file to Studio One.exe and everything works fine.
Click to expand...
Thanks for this! I can also confirm this worked for Mac as well. All is as it was with Studio One 7. :)
 
IS anyone else finding that even with the name change, it doesn't follow along for the tracks? If I click a track in the daw, it doesn't jump to that track on the UF8? Anyone else? I just put the app in a folder called Studio One 7 on mac?
 
You must log in or register to reply here.
Back
Top