Number6
Active member
Just be careful when moving projects/songs to older versions of Studio One.
Going backwards may corrupt projects.
-
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 One 7.2.1 - Discussion Thread
- Thread starter Ari
- Start date
Going backwards may corrupt projects.
marrybanilow
New member
Studio One 7.2.1 (or 7.2) looks to have fixed all the crashing issues i was previously having. Cannot lie, it's such a relief to be able to use it again! I was working with Cubase the past couple of months but using Studio One just feels like 'home'
Number6
Active member
I've read this several times and I could not understand this (sorry I tried):
*and then my macos asked me to move the application to my application folder."
Maybe a screenshot.
Regardless you know you can back up your settings folder before you update in case of issue?
I'm using MacOs so it doesn't update like windows...you have to drag an application to an application folder to install it. But yeah I was planning to update my settings folder before I do it so I'll find out soon....was just wondering if someone has done it before on MacOs
Let's clear up some confusion 
Yes, it's perfectly safe to overwrite the application. Your personal settings and preferences are not stored inside the application itself - they're saved in the Studio One settings folder (usually under ~/Library). So updating or moving the app won't affect them.
Number6
Active member
3 things when updating if you value your data.
1) Ideally back up your whole computer, clone it using something like Acronis True Image (and there are plenty of other alternative apps, probably better, out there that do this nowadays)..do this to an external hard drive or server or another computer (or cloud if you trust them).
2) Backup your data. With the projects/songs you backup take a note (maybe the title of the parent backup folder) of the version of Studio One you backed up with. Again to an external source. Bare in mind if you roll back studio one these files may become useful as backwards compatibility isn't guaranteed.
3) Backup your entire settings folder.
1) Ideally back up your whole computer, clone it using something like Acronis True Image (and there are plenty of other alternative apps, probably better, out there that do this nowadays)..do this to an external hard drive or server or another computer (or cloud if you trust them).
2) Backup your data. With the projects/songs you backup take a note (maybe the title of the parent backup folder) of the version of Studio One you backed up with. Again to an external source. Bare in mind if you roll back studio one these files may become useful as backwards compatibility isn't guaranteed.
3) Backup your entire settings folder.
Why? This makes it sound like you're potentially losing songs and other important data with a Studio One update.
Backups are always part of productive work anyway. However, this has nothing to do with updating Studio One.
Number6
Active member
Well why not?
There is always a risk updating any software. It's small but issues can happen. Precautions are precautions, if you don't want to take them, fine..one day you may learn the hard way. Hopefully you won't however.
And if you end up rolling back studio one because of some bug you don't like (and that sometimes happens to people does it not?) then you've got your projects and song data which are compatible with that version of the app haven't you? Rather than risk running a file created on a newer version of S1 which may end up being corrupted.
Why would you find anything wrong with this advice? Precautions are precautions.
There is a absolutely nothing wrong with taking a backup, there is however everything wrong with never taking a backup.
But hey people can do what they like, I like to be super careful. And I never said it was specifically Studio One, however doing it when upgrading any important software is a good thing to do. Why would it not be?
Unless you maybe have a daily or weekly backup plan. I'm willing to bet most people don't. I do, my 3 machines are scheduled to turn on, back up to my server at periodic intervals, then turn off. Once a week I backup my server to an external hard drive. I have two external hard drives in fact, and I leave one of them in a different building (swap them out) in case of theft and fire. At some stage I will be building a server at a remote location anyway and get data copied over remotely so I won't have to do this anymore.
Call me paranoid if you like. But paranoia is better than losing data.
But hey do what you want to do.
As I said:
We always recommend installing new Studio One versions to separate folders - so in that case there's no need to roll back because you can still use previous versions even after updating.
Number6
Active member
Which seems sensible to me.
But you're missing my point about data.
Opening a 7.1 project with say Studio One 7.0 (after rolling back) is probably not a good idea is it not? I wouldn't want to risk corruption, and I very much doubt QA tests for these scenarios. Hence making backups of your data. I don't know if it's supposed to be backwards compatible or not, but I certainly would not risk it (even if QA does test).
Like I say I would recommend taking full backups anyway before upgrading any major software unless you have a regular backup plan in place. I don't see anything wrong with having that opinion.
Last edited:
It is a good idea as long as version 7.0 will open it. Studio One versions that break compatibility because of major data structure changes will introduce a new file format version. Songs stored with higher file format versions won't open in previous versions of Studio One.
Again, even if you're cautious about opening songs in previous versions, it's technically not necessary to create full backups - as long as you save the songs under new names, which essentially serves as a backup. In this specific case, there's no need to back up all the data, including audio files, since Studio One won’t modify them anyway.
Studio One Toolbox (https://s1toolbox.com) can tell you which Studio One version was used to create a specific song file.
Number6
Active member
So that's pretty much what I've been saying. Otherwise risk data corruption if you open file created under a newer version of Studio One.
And if we accidently open another work in progress song, and just save it one day without renaming, just forget to do it, maybe several weeks or months later, hey ho, nevermind...we've got a backup... oh hang on we don't.
And let say we have one of those renamed file backups, so we trust the existing newer audio files and going to stay in sync with the old project? Yet maybe we renamed them, maybe we altered them, maybe we moved them. Maybe we overwrote them.
BTW I never said that Studio One could be the sole reason for data corruption, there are lots of other reasons for data corruption, viruses and hard drive failure for instance.
In my book if your strategy is doing the bare minimum when backing up, you aren't doing it right. External hard drive space is cheap, there is simply no need whatsoever to take shortcuts.
Yes it is, and we agree.
But my posts were targeted for those people who may not practice this. Lots of people don't bother with backups until one day something catastrophic happens, and for some people the thought has never crossed their minds. Those people aren't us.
Last edited:
Number6
Active member
I think it's useful to link this post and video here:
studiooneforum.com
Are Daisy-Chained Virtual Instruments not Plugin Delay Compensated?
Hey guys, quick sanity check here... I'm realizing that when a MIDI line is recorded, playback from an instrument which is feeding it's output into another instrument's input will not be PDC-compensated, causing it to arrive on the beat late by the amount of samples incurred by the interface...
studiooneforum.com
The linked article states: 'Ripple Edit doesn't work inside Editor (under fixes)'. Does this mean that Ripple Edit is supposed to work in the (Pianoroll-)Editor? For me, it only works in the Song-Page, and I haven't found a video yet where someone is using Ripple Edit within the Editor. Or am I getting this wrong?
