Just discovered something strange with the Octatrack.
First, I normalize a sample, then I save the project, then turn the OT off. When I turn it on again and load the project, the sample has reverted back to it’s nonnormalized state.
What’s going on, and how do I stop this from happening?
Sorry if it’s a stupid question, I’m not an OT guru yet.
You need to Save the sample. Normalising just affects the version held in RAM. (I think!)
Also found this but if you save the sample it gets put in a different location.
Can I save it in place and have normalisation saved?
System > Personalize menu
SAVE SAMPLES TO offers two settings.
• AUDIO POOL will when saving recorded audio or saving samples in the audio editor save the data to the audio pool of the set.
• PROJECT DIRECTORY will when saving recorded audio or saving samples in the audio editor save the data to the project folder.
So if I want to normalise a sample and keep using it
I just normalise then save and assign sample then save in place
and it will save to one of those locations if selected?
So the original sample will stay in its original location?
AFAIK you can save and replace only if the sample is in AUDIO or project folder (root for both) depending on Personalize choice.
I chose project folder so that I don’t have to reorganize AUDIO mess.
Use Card Tools > File manager or computer to copy/paste/delete.
Limited.
Ok thanks man, tbh I’m still slightly confused,
I guess you mean if recorded material vs samples from in your audio library…
I’ll just try a few tests on empty project to try fully understand it… cheers!
Same behavior when you save them. Saved in Audio or project folder, no other choice.
Thanks, I’ll check out the file manager I haven’t even looked at that yet.
I was struggling with this the other week. I was just using ‘save sample settings’ and it would just revert after powering off/on. It was driving me nuts so I just gave up an turned the sample gain up. This saved fine using the same method. Not sure why theres a difference between saving these parameters @sezare56
Will need to try messing with those system settings!
It only saves TRIM, SLICES and ATTRIBUTES settings in the .ot file associated with the .wav file.
sample.wav
sample.ot
Thanks!
I’m interested to know this too. I would find it hard to believe* that there is no way to save normalisation changes to the sample. Is this also true for +3db boost?
*But it wouldn’t be the first thing about the OT I found hard to believe!
If you use SAMPLE SAMPLE COPY or SAVE AND ASSIGN SAMPLE, it behaves as “save sample as”, as written in the popup.
If you use the same name, you can overwrite the file if it’s in the same folder (Audio or project).
Yeah this seems to be the way to save the normalise.
if you save to project it shouldn’t get lost.
If you save it to audio pool then tidy it up later it could get lost
and it can be too hard to find original sample and replace it if you have a large sample collection
Only problem is if you want to use the same sample in a different project,
If you get the sample from the original location you will have to normalise it again and save it to project again… But that’s not really a huge problem.
Think this is right going off what @sezare56 has said…
I’m still yet to completely test this
Interesting, I may have to rethink how I am working…
I only save to the pool and this hasn’t been an issue yet but I can see things getting out of hand eventually. Glad I read this thread : )
I Just tried “collect samples” from the project menu
and it puts all samples in the project folder and I also purged all unused samples while was at it. Think this is the best way for me so far.
If I want to use certain samples I may have recorded from the project in another different project I can just Go into USB disk mode and copy them and put them in a new folder in my
AUDIO samples collection on the computer.
That way all the normalised samples will be all self contained with the project samples And it basically the same as Abletons collect all and save.
It does mean that it is saving duplicates of samples used from audio library, But you can save unused projects on your computer for back up and delete them from the Octatrack and samples won’t be lost.
Just thought I’d share because I’m only just working it out and thought could be helpful for others currently learning the OT
It’s actually a pretty good system and very similar to ableton live
Precisions about PURGE SAMPLES :
Once I realized it doesn’t purge the first 8 slots* of Static and Flex machines. It make sense because they are default track samples in all parts, as @Rusty pointed out.
(*Not Recordings 1-8 for Flex)
I thought it was better to use PURGE SAMPLES before COLLECT SAMPLES, but reading manual again, now not sure it makes a difference :
COLLECT SAMPLES copies samples that are used by the currently active project into the project directory, which will effectively disconnect the project from the audio pool.
PURGE SAMPLES will remove all unused samples from the project. Note that samples are only removed from the Flex and Static sample slot lists of the project; the actual samples will not be deleted from the audio pool.
I saw you mentioned that 1st 8 slots don’t purge… guess it just how it is
yes I realised that after I done it,
should have purged first now have unused samples in the project folder.
I will know for next time… at least I think I understand how it works now
because was worried about losing everything I made recently and that would suck…
Now only have to worry about not losing Rytm samples. Because doesn’t seem to have a collect samples feature and no easy way to link samples to a project?
I haven’t used the collect samples yet…or have I hah can’t remember…I looked into it when I thought about reorganising my audio pool and didn’t want to break file locations.
This makes a lot of sense as a good way of managing things and keeping everything relatively tidy. It’s pretty hard to stick to a good filing system for recorded samples on the pool - I have a ton of octa sampled stuff that is just sitting folderless in alphabetical order so I may try and do a spring clean with this method.
Thanks for sharing : )