KVR Audio

gentleclockdivider · Post by **gentleclockdivider** » Mon Oct 28, 2024 1:28 pm

Michael L wrote: Mon Oct 28, 2024 12:32 am

I also occasionally use an old version, and my OS doesn't meet the new system requirements for v7 so I asked if I could upgrade to 6 now, and 7 in the future.

You're not on win 10 ( 22h2) ?
Or mac ?

jamcat · Post by **jamcat** » Mon Oct 28, 2024 1:37 pm

Songs that are saved on higher vX.0 versions can’t be opened on older versions. That’s always been the case in Studio One. So mixing new and old Studio One versions isn’t a great idea.

This has got me wondering though, when Studio One abandons traditional version numbers for date-based versions next year, is each new update going to be incompatible with older versions every 4 to 6 months, instead of every 2 years?

Resonant- Serpent · Post by **Resonant- Serpent** » Mon Oct 28, 2024 3:03 pm

jamcat wrote: Mon Oct 28, 2024 1:37 pm This has got me wondering though, when Studio One abandons traditional version numbers for date-based versions next year, is each new update going to be incompatible with older versions every 4 to 6 months, instead of every 2 years?

Support will only be given for the latest released version starting with v7.

electro · Post by **electro** » Mon Oct 28, 2024 7:23 pm

Still no 7 Demo? What's a shortlist of the most outstanding bugs? Anything to be wary of?

Aliens · Post by **Aliens** » Mon Oct 28, 2024 7:29 pm

"Anything to be wary of?"

The user base

EnGee · Post by **EnGee** » Mon Oct 28, 2024 8:31 pm

jamcat wrote: Mon Oct 28, 2024 1:37 pm Songs that are saved on higher vX.0 versions can’t be opened on older versions. That’s always been the case in Studio One. So mixing new and old Studio One versions isn’t a great idea.

This has got me wondering though, when Studio One abandons traditional version numbers for date-based versions next year, is each new update going to be incompatible with older versions every 4 to 6 months, instead of every 2 years?

I feel that most of the companies not only Presonus will implement Bitwig’s style of subscription. This system will allow them just to maintain the current version with minor additions. So I think future projects saved with version 7 would still be able to be opened after several years. This also will make them get rid of some developers because no new features will be added.
Let’s be honest, what new versions of OSes and main software we need in our daily life or work?! Maybe AI helping us in decisions making because we are lazy and stupid

mdstudio · Post by **mdstudio** » Mon Oct 28, 2024 8:42 pm

electro wrote: Mon Oct 28, 2024 7:23 pm Still no 7 Demo? What's a shortlist of the most outstanding bugs? Anything to be wary of?

It was probably mentioned already, but if you're considering upgrading, check the minimum OS version. For example Big Sur isn't supported.

Michael L · Post by **Michael L** » Mon Oct 28, 2024 11:33 pm

gentleclockdivider wrote: Mon Oct 28, 2024 1:28 pm
Michael L wrote: Mon Oct 28, 2024 12:32 am I also occasionally use an old version, and my OS doesn't meet the new system requirements for v7 so I asked if I could upgrade to 6 now, and 7 in the future.
You're not on win 10 ( 22h2) ?
Or mac ?

I have familiar software that is incompatible with newer MacOS, so I no longer upgrade.
It's a tradeoff that I am happy with.
[ I was born with AI, so don't need v7 ]

jamcat · Post by **jamcat** » Tue Oct 29, 2024 1:54 am

EnGee wrote: Mon Oct 28, 2024 8:31 pm This system will allow them just to maintain the current version with minor additions. So I think future projects saved with version 7 would still be able to be opened after several years.

I’m sure you’ll be able to open older songs on future versions indefinitely. That’s not the question. The question is if you will be able to open a song that was saved in Studio One 2025.Q4 in Studio One 2025.Q2. Because you can’t open a song that was saved in Studio One v7 in Studio One v6.

EnGee · Post by **EnGee** » Tue Oct 29, 2024 2:31 am

jamcat wrote: Tue Oct 29, 2024 1:54 am The question is if you will be able to open a song that was saved in Studio One 2025.Q4 in Studio One 2025.Q2. Because you can’t open a song that was saved in Studio One v7 in Studio One v6.

Who knows!

What scenarios make you do that? Cooperation with another person that has a current plan while yours is expired? I can't think of many situations you need to do that.

jamcat · Post by **jamcat** » Tue Oct 29, 2024 3:22 am

EnGee wrote: Tue Oct 29, 2024 2:31 am
jamcat wrote: Tue Oct 29, 2024 1:54 am The question is if you will be able to open a song that was saved in Studio One 2025.Q4 in Studio One 2025.Q2. Because you can’t open a song that was saved in Studio One v7 in Studio One v6.
Who knows!

What scenarios make you do that? Cooperation with another person that has a current plan while yours is expired? I can't think of many situations you need to do that.

Yeah, that would be one. I just wondered about it because Michael L said he occasionally runs an older version of Studio One on an old computer.

Trancit · Post by **Trancit** » Tue Oct 29, 2024 8:58 am

In general I would say there is never a guarantee that you can open a project in an older version which was created in a newer version...
Developers at max care about backwards compatibility but it never works the other way round as the older version never knows how to treat information related to new and therefore for the older version unknown features saved in the project.
I.e. you save a project with clips in the new clip launcher of V7... what shall V6 do with this information??
It doesn´t know and will not open the project or even crash...

Crossinger · Post by **Crossinger** » Tue Oct 29, 2024 9:22 am

Trancit wrote: Tue Oct 29, 2024 8:58 am I.e. you save a project with clips in the new clip launcher of V7... what shall V6 do with this information??
It doesn´t know and will not open the project or even crash...

In theory this would be not a problem: if you have a structured file format (e.g. xml, not some proprietary BS), you could simply omit the unknown chunks when reading the file.

But experience tells: when developing new versions, they sometimes also change the data structure of existing features. And then you're out of luck.

dellboy · Post by **dellboy** » Tue Oct 29, 2024 11:24 am

Trancit wrote: Tue Oct 29, 2024 8:58 am
I.e. you save a project with clips in the new clip launcher of V7... what shall V6 do with this information??

I have exported Bitwig sessions that included the clip launcher clips using the DAWproject format and imported them into Studio One. Certain information will obviously be missing, but the basic structure of the song is retained. So maybe it is possible to export from version 7 as a DAWproject file and re~import into version 6 using that method?

Trancit · Post by **Trancit** » Tue Oct 29, 2024 11:26 am

Crossinger wrote: Tue Oct 29, 2024 9:22 am In theory this would be not a problem: if you have a structured file format (e.g. xml, not some proprietary BS), you could simply omit the unknown chunks when reading the file.

But experience tells: when developing new versions, they sometimes also change the data structure of existing features. And then you're out of luck.

Ok, of course this could be solved... but... and this is imho the most important "but":
No developer want you to stay on older versions! They want to sell their updates... so they will never help opening newer projects in older versions...

PreSonus Studio One 7 apparently imminent