Well at least they are still continuing on with supporting Linux.Crossinger wrote: Tue Jan 13, 2026 1:11 pmIt's the rebranded successor of Presonus Studio One:
https://uk.fender.com/pages/fender-studio-pro
Fender Studio Pro 8 Released
- KVRAF
- 7023 posts since 19 Apr, 2002 from Utah
Vendor‑Dependent Copy Protection: Customers lose. Pirates win.
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
(Also: I'm Accused of lying about Linux—it boots, runs my pro audio workflow, stays stable, updates--though yearly dismissed as “niche”. Yet I'm the deluded one.)
-
Vocalpoint Studios Vocalpoint Studios https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=3112
- KVRian
- 893 posts since 20 Jun, 2002
No you are not misunderstanding.tumface wrote: Wed Jan 14, 2026 4:09 am I'm not sure what you mean? Supported & working in macOS 12: Ableton Live 12.3, REAPER 7.59, Renoise 3.5, Digital Performer 11.3, FL Studio 25.2, Bitwig Studio 5.3, ...Maybe I'm misunderstanding?
The vendors of the apps you have listed - have chosen to allow OS12 to be a supported platform - for those specific versions.
However - a day will come soon - for all those vendors - when they will drop OS12 as a supported platform for newer versions of the apps you listed.
In the case of Studio Pro 8 - the time to drop OS12 as a platform has arrived - starting today.
VP
-
- KVRian
- 671 posts since 11 Apr, 2006
macOS 26 will also not work for some software some day. I'm not sure what you mean, still.Vocalpoint Studios wrote: Wed Jan 14, 2026 4:36 am However - a day will come soon - for all those vendors - when they will drop OS12 as a supported platform for newer versions of the apps you listed.
So, it doesn't run, or it does run, on macOS 12? That's the question I'm asking. Sorry if I wasn't being clear enough.Vocalpoint Studios wrote: Wed Jan 14, 2026 4:36 am In the case of Studio Pro 8 - the time to drop OS12 as a platform has arrived - starting today.
- KVRAF
- 7660 posts since 2 Sep, 2019
The only right thing for them to do here is give everyone who bought Studio One 7 a free upgrade to Fender Studio Pro 8.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP
-
Vocalpoint Studios Vocalpoint Studios https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=3112
- KVRian
- 893 posts since 20 Jun, 2002
Thought I was pretty clear in a prior post. It will most likely not even install on OS12 - so no it definitely will not runtumface wrote: Wed Jan 14, 2026 4:45 am So, it doesn't run, or it does run, on macOS 12? That's the question I'm asking. Sorry if I wasn't being clear enough.
VP
-
andrei.tuduran andrei.tuduran https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=369504
- KVRian
- 590 posts since 11 Nov, 2015
That’s the same price for Studio One Pro 7.Danilo Villanova wrote: Tue Jan 13, 2026 10:26 pm I have S1 Artist 5, the upgrade still shows at $99 for me, which is more than fair!
This is weird.
-
Vocalpoint Studios Vocalpoint Studios https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=3112
- KVRian
- 893 posts since 20 Jun, 2002
-
- KVRian
- 671 posts since 11 Apr, 2006
Studio One / Fender Studio doesn't use an installer on Mac, so that doesn't really make sense, either.Vocalpoint Studios wrote: Wed Jan 14, 2026 4:55 amThought I was pretty clear in a prior post. It will most likely not even install on OS12 - so no it definitely will not runtumface wrote: Wed Jan 14, 2026 4:45 am So, it doesn't run, or it does run, on macOS 12? That's the question I'm asking. Sorry if I wasn't being clear enough.
VP
-
- KVRist
- 391 posts since 6 Aug, 2021
I doubt they will do it but I’ll wait a a few days before I pay for the upgrade just in case.
Another sad thing is that people that have SO5 and SO7 pays the same price for the update. I’d be happier if I paid $79 instead of $99 as a SO7 user.
-
andrei.tuduran andrei.tuduran https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=369504
- KVRian
- 590 posts since 11 Nov, 2015
-
andrei.tuduran andrei.tuduran https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=369504
- KVRian
- 590 posts since 11 Nov, 2015
Yep, I think the right thing is to have different upgrade prices depending on the version.Fornicras wrote: Wed Jan 14, 2026 5:10 amI doubt they will do it but I’ll wait a a few days before I pay for the upgrade just in case.
Another sad thing is that people that have SO5 and SO7 pays the same price for the update. I’d be happier if I paid $79 instead of $99 as a SO7 user.
-
- KVRist
- 188 posts since 28 Jun, 2013
Well the dsp lane is quite rudimentary regarding functionality. No drag'n'drop of the devices, only in the tiny overview. No shortcut to delete a device, no X button to delete a device. If there are more parameters than visible space, the device could have "page" buttons, or optionally expand. Color coded, connected automation could be indicated on the knob. If you mouse-over a knob, it could also highlight the opened dsp lane. Routing view, like parallel routes, could be also reflected in here directly.
So very basic in functionality currently. A lot of missed opportunities here. Hope that the next update will not focus on internal plugins, but instead on core functionality improvements. The Fender plugins seem to be high quality, yet you can easily replace it with third party plugins. It makes sense as being Fender, the guitar company or whatever. However it's a bit sad that precious developer time has been "wasted" here, to "reinvent" the wheel, instead of improving workflow and adding really unique/stand-out features and UX...
So very basic in functionality currently. A lot of missed opportunities here. Hope that the next update will not focus on internal plugins, but instead on core functionality improvements. The Fender plugins seem to be high quality, yet you can easily replace it with third party plugins. It makes sense as being Fender, the guitar company or whatever. However it's a bit sad that precious developer time has been "wasted" here, to "reinvent" the wheel, instead of improving workflow and adding really unique/stand-out features and UX...
Last edited by ffx on Wed Jan 14, 2026 6:48 am, edited 1 time in total.
-
- KVRist
- 172 posts since 12 Jun, 2025
Hopefully they continue to build it out. I would like to see the routing view, with splitting worked into it.ffx wrote: Wed Jan 14, 2026 6:27 am So very basic in functionality currently. A lot of missed opportunities here. Hope that the next update will not focus on internal plugins, but instead on core functionality improvements
- KVRAF
- 7660 posts since 2 Sep, 2019
I am still waiting for part containers for automation data, or what you might call automation clips. I am scared to click anywhere near an automation lane because if you do, you'll add unwanted automation data points and screw up your existing automation.
Also it's a real pain in the ass to duplicate it or move it and keep it aligned. Especially if you're trying to move it to a different track. And then even if you do get it on another track without screwing it up, it's still attached to the original plugin and parameters. And there's no way to simply reassign the destination to a new plugin and/or parameter.
So if you've got like 10 different parameters being automated on BlippySynth 1.0, and then you upgrade to BlippySynth 2.0, you're going to have to meticulously copy and paste all of your volatile unprotected automation data by selecting all automation points and then create new automation lanes in the new plugin and place the cursor at exactly the right bar/beat/clocktick as the first automation point and then paste it, and then repeat this process for every parameter you've automated.
Also it's a real pain in the ass to duplicate it or move it and keep it aligned. Especially if you're trying to move it to a different track. And then even if you do get it on another track without screwing it up, it's still attached to the original plugin and parameters. And there's no way to simply reassign the destination to a new plugin and/or parameter.
So if you've got like 10 different parameters being automated on BlippySynth 1.0, and then you upgrade to BlippySynth 2.0, you're going to have to meticulously copy and paste all of your volatile unprotected automation data by selecting all automation points and then create new automation lanes in the new plugin and place the cursor at exactly the right bar/beat/clocktick as the first automation point and then paste it, and then repeat this process for every parameter you've automated.
Last edited by jamcat on Wed Jan 14, 2026 7:50 am, edited 2 times in total.
THIS MUSIC HAS BEEN MIXED TO BE PLAYED LOUD SO TURN IT UP