04-10-2019, 04:49 PM
(04-10-2019, 04:25 PM)T3t_one Wrote: Rests, never an error code. It happens sometimes when the memory is nearly full after switching samples from the LOAD SAMPLE menu. Like you have mentioned even when there is enough space for the new sample.
Oh, now that I think about it, this has happened before and last time I realised that I should delete the sample before 'replacing it' and also do this while the NerdSEQ isn't playing.
This shouldn't be a problem to save manually but when I am working with 100's of samples and sampleblocks, manually saving after each time I want to load a sample can get forgetful when you are in a workflow. Allas, I will be saving every time I play with the sample menu from now on.
Also is it common for the NerdSEQ to reset after saving (save back up ON)? It's only started resetting since having backups on.
Load Sampleblock from FX seems to work just fine. apart from the clipping sound when the samples are released and loaded into the buffer but I tackle this by placing the sample block command between note off and the first beat of the new block.
Anyway to expand the ram like on an Amiga hack?
Will Nerdsynth have more memory?
Cheers.
Deleting a sample before loading a new one won't help. Thats actually what happens with replacing a sample. Only deleting all samples would help to clean up.
The clipping when replacing a sampleblock is of course a result of unloading samples (which are maybe playing) and loading a new one. I assumed that when replacing they are not playing. Thats why i called it 'nearly seemless'.
Can you post me the file that crashes with the save backup? The only thing i can think of is a bad SD card or a already messed up samplememory caused by the replacing (which might lead also to a corrupt projectfile). It also never happens to me that it resets after saving. Bakup is always turned on.
One thing i could do actually is using the load/save sampleblock functions when loading/replacing samples. This might fix the fragmentation issue since all is backed and cleaned up onto the sd card. But it is not seemless anymore to just replace one sample as i would have to do this everytime a sample is being loaded/replaced. And i am not 100% sure yet if that would work.
No ram expansion possible unfournately.
Just a bit of history. The samples were not planned in the first place for the NerdSEQ. Thats why it's more a side-dish compared to the CV/Gate functionality. And thats why there is only limited memory. But still i think one can be very creative with it and can get good results regardless the limitations..and i will work on it to get it better. But in the end, it stays a small embedded system.
The NerdSynth will get plenty of sample memory.
PLEASE use the search function if something have been asked or discussed before.
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!
Every (unnessesary) forum support means less time to develop! But of course, i am here to help!

