Hey guys, this may be just a bug, have you checked with support ?
I don’t think it’s a bug. The new project has the same save state as the original, if it had one. Counterintuitive but logical.
1 Like
No it doesn’t, I don’t think. The original project had been saved many times, but the new (saved as new) didn’t have a save state, as I discovered when I wanted to reload it. The save state doesn’t get duplicated with the project.
In that case I don’t see the logic. Maybe it is an oversight by the design team.
Sorry for uneducated comments, I don’t use those functions often.
I work with a Template-Project. With this I start every project via Save As New … very frustrating, that i cant use “reload” with this workflow …
Just think of the “Save” command as “store a backup/recovery point for the currently active project” and you’ll all be just fine… The sky is not falling. 
Can confirm, sky not falling.
Still, it’s silly.
2 Likes
Strange, didn’t work for me, even when i use “save”. it always says “save part first” when i try to reload?!
You’re thinking of the wrong reload. What is discussed in this thread is a reload option in the Project menu.
To reload a Part, it first needs to be saved via the Part “window” or whatever it’s called. Go find out about this, it’s a useful function.
1 Like
oh.
thanks. didnt know that there are two kinds of reload.
I think it is not normal too. When you do “save as” on a computer you have a “saved” state.
On the Octatrack it is like like a new project : Only .work files are copied on the card.
.strd files should be created at the same time.
You have to save twice. Not normal. The sky is grey. 
and I assume this gets clarified in the great new OS that will come with the mkii’s
Nope. New OT MKII user here, and as a longtime paranoid computer user, the first thing I did was make copies of stock projects via “Save as New” so that if I destroyed anything, I could revert. That’s exactly what happened: destructive changes to my copies. I kept re-doing “Save as New” to create working copies and found no way around the destruction. Forum search found this thread, and now I do a save after every save as new. I also went back and did a save on the stock projects in case I ever bump something. What a chore.
2 Likes
It should be called “copy as new”. 
5 Likes
I get the ”the project state has never been saved! Nothing to reload” even though I have saved the project many times. I solved it, when the same problem turned up a year ago, by Save to New and then I could Save and Reload. Until now. Had to Save to New AGAIN. Now it works. Silly. Or am I missing something?
And. I can’t load audio files to my Flex slots. I get an Error message. Static works. Any ideas? Will mail support though
Do you mean Save?
No saved state after Save to New, it behaves like this since a long time. I don’t think doing Save As New twice would solve this.
Memory Full, wrong audio file specs?
No. Save didn’t help. It says Done (as if a Save has been done) but if I then make changes in a pattern and chose Reload, it says that no Save has been done so there’s nothing to reload
No, the samples I try to load in Flex slots are possible to load in Static. Plenty of memory left
I read that someone couldn’t load samples in Statics, and it was possible with Flex. Wrong format.
Where did you check available memory? Once a guy increased Reserve Length > not enough available memory.
Maybe a problem with your project, corrupted files.
If project is saved, you can check if there are .strd files* in the project folder.
*A new project has .work files only.
A saved project has additional .strd files, a copy of .work files. When you use the Reload function, work files are replaced by strd files.
Yes, if your project is corrupted, Save to New can correct errors.