Yeah I read this part many times including today lol, and it isn’t super clear imo.
^ this.
That is not what I meant. I don’t want to have longer samples in my multi chops, because then the access time of a SD makes it unstable.
But I use it when triggering long one shots. Triggering a rap acapella that plays for 3-4 minutes is working well for me. Also with a slower SD card.
Has someone properly, officially reported this issue to @Mickey or @bradholland ? Just wanted to make sure it got tracked down in the “bugfix firmware update” that is forthcoming!
Best,
AVERY MOSS
This is a bug report on the Isla forum that is marked as in progress. Not sure it gets more proper or official than that.
1 Like
Please do not mention users for no specific reason, especially developers. I am sure it is not their main responsibility to read through tons of that crap we write here every day.
The ticket is already triaged so there’s no need to worry. It doesn’t mean that it will be resolved in the next software update. It means that eventually it will be definitely looked at depending on the task priority.
We need to learn to write bug reports properly, i.e., in a clear and concise way, and not have a conversation that’s dragging on for 30 pages discussing all sorts of user errors if we want anyone in the development team to ever participate in such discussions. Not bashing on this specific thread, though!
2 Likes
Sorry, didn’t realize that it had already been addressed (I see the title formatting now.) Didn’t mean to pull in any further ire or hold developers feet to fire to be a d*ck, just also agreed that this thread was long and meandering - again, no shots either - and wanted to make sure SOMEONE who know what was user error and what was a corroborated bug (i.e. the development team) could look it over.
I am sure they will, I am not worried.
Peace!
1 Like
Yeah, I feel you. There’s a couple of issues that I am particularly sensitive about and really want them to be resolved, so I totally understand where you are coming from.
Hi all,
Just wanted to dive in and clear up some things as there seems to be some confusion in this thread.
- samples under 2Mb are loaded and edited in RAM
- samples over 2Mb & under 64Mb are streamed, but can be loaded into the waveform editor
- samples over 64Mb are streamed and cannot be loaded into the waveform editor
- limit on the length/size of audio file that can be streamed is dictated by FAT32 SD card file-size limit of 4Gb
- 64Mb is the largest sample that can be recorded.
- 2Mb is the largest sound that can be looped.
How is all this relevant to the original problem:
- Any project that uses disk streaming can (but not necessarily) suffer from timing issues. Rather than impose limits, the S2400 allows you stream every Pad from disk if you choose, but there’s obviously a limit to how quickly an SD card can deliver the data.
- Not all SD cards are equal. We have tested some cards which are terrible at delivering data reliably, even just streaming one sample >2Mb (Lexar I’m looking at you).
- Most importantly to this thread, if you have a project where all samples are under 2Mb AND you’re still experiencing timing issues, please let us know. Either tag me here, or send in a bug report via the website.
Hope that’s helpful.
4 Likes
Another little update on the timing issues in regards to samples above 2MB from last night…
So I’ve been sequencing the S2400 from the Amiga for a couple days, and last night I noticed timing issues for the first time, because there was a sample over 2mb in the project.
The problem I had is, just resampling/ saving and replacing with a new file smaller than 2MB didn’t fix it, what fixed it was saving the project to a new project, that way the older sample didn’t even exist in the folder, then it was fine again.
Is there some sort of “flush ram” type feature I’m missing to clear out unused samples? If not, this would be a very useful addition.
1 Like
So I’ve had this unit for under a year now and I this whole 2mb file size “issue” all makes sense now with this machines behavior. It’s not even a big deal but it’s nice to know.
Gotta ask…
The “Delete Unused WAVs” in file doesn’t help with this?
Yeah I have no issue with the 2MB limit, now that I know it actually exists.
I don’t think this info is very clear anywhere besides now on this forum. It very heavily implies the limit per track is 64MB. This imo should be made clearer in the manual at the very least.
Delete Unused WAVs will delete the actual files from the project folder, and I mean, I don’t wanna do that (generally speaking)… I wanna keep any original recordings.
1 Like
This does raise the question if larger than 2MB files simply existing in a project folder can cause these timing issues?
I don’t THINK that is the case, but haven’t really experimented with that. If that is the case however, I guess a “flush ram” type feature wouldn’t be of any use. Like I say though, I don’t THINK that is the case.
1 Like