Word to the wise: when you re-open Caustic and the track you've been working on is already open, RE-OPEN IT ANYWAY from your last save.
Lately I've been working on a new EDM track for my wife, as our 11-year is coming up at the end of this month. I've been working while on the bus to and from work; yesterday morning I had it just about finished, with all the patterns completed and sequenced. Then in the afternoon I opened Caustic back up and started working again, changing a few patterns and automations, and quicksaving as I went along, but at one point noticed that the previously finished ending had reverted back to an earlier state. WTF?
So I had to reconstruct the ending to the best of my memory.
Never again will I open up Caustic and just start working. Every session now begins with "NEW" or "LOAD".
You know? I've noticed that too, on occasion, but haven't nailed the trigger event for such a "revert" after saving, but putting the app on standby doing other things on my device.
But this is a good method of practice, no doubt. I'm glad you brought this up.
Congrats on your upcoming 11..... I got my 16th in July....
@Steph Huh? You too!
I experienced this today too. Is this a computer issue?
https://soundcloud.com/squirrelonmars
https://www.youtube.com/c/squirreIs
https://www.facebook.com/squirrelonmars
Yup, I learned this lesson early... it's a bit of a curse of using the same Caustic files on more than one machine.
I don't trust quick or auto save. When I make significant changes I save and either overwrite or save as a new file (sequentially numbering so you can roll back if necessary)
My latest track on show and tell
My Soundcloud page
If it's a computer issue, it's got to do with Android because I only use Caustic on my Toshiba Thrive.
But I see that I'm far from being alone in experiencing this problem, so I'm glad I brought it up here and might possibly save somebody else from some future grief.
I always save by overwriting, no problem with those files. The track that lost some data on is a song I developed further and saved as "song2.caustic". I don´t know if that should matter...?
Oh well... no big loss, but strange. (Using Mac and I know that the computer versions are not supported.)
https://soundcloud.com/squirrelonmars
https://www.youtube.com/c/squirreIs
https://www.facebook.com/squirrelonmars
yup its happened to me too :-( seems to be with the quick save and device memory when it happens to me. coming back to work and not loading from last save. it can be a bummer sometimes ;-)
https://billdough74.bandcamp.com/
I have noticed that the longer you work on the same track the more weird things start to get, almost like the program gets fragmented. I will have track audio dropouts where I will have to hit the stop button and return to the beginning of the track to get that machine to make noise again. I have noticed the more you move/delete machines the more wiggled out things get as well.
There are 2 seperate problems I've noticed.
1/ The more samples you have in the file, the larger it gets, the longer it takes to autosave, the more likely it is that android will cut off the process mid save.
2/ If quick save saves too quickly, it probably hasn't saved. You need to save under a new name.
Basically, do as rob says. If you've done significant work, save as a new file (with sequential numbering). It it also nice to go back sometimes, even if just to hear how the track progressed.
My Soundcloud profile is _dredge_
Yes, saving backup version builds of a serious project is essential (no matter what DAW platform you're on.
But especially on mobile, it is strongly recommended to save your project before you drop to your device's HomeScreen or jump to another program. This is also why I recommend to not run other programs or social media in the background.
These phones may have the RAM, but may not be guaranteed to hold your data when you go away from it. Caustic is unique in its own because it really bends your device in behaviors that are not typical for a mobile device.
Realizing this will help change your perspective of this, and encourage better steps to take in maintaining and preserving your project data, to avoid such situations as this, especially for usrrs who are involved in serious work with this particular app.
I realised this a few months ago and I still forget about it every now and then
'Askar
https://www.soundcloud.com/xenoplas
In related news, I finished the assembly of my track yesterday. All the patterns are in place; all that remains is to tweak the levels, EQ, and effects.