Sure thing, export/import are on the todo list as discussed earlier ![]()
I plan to work on that after current features:
- Rework of Copy Sample Slots
- Automatically handle copy of sample slots in Copy Banks
- Then Sample Sots improvements: load samples directly, re-organize slots, locate un-used samples, etc - this kind of things

Ohh
that’s an intersting idea!
Note that you - kind of - already can do that using “Copy Tracks” feature
With “Copy Mode: Both” you can copy tracks around freely - Of course it’s a bit tricky to use that to re-organize them all and you would need to copy some elsewhere temporarily or something but it would work !
In any case, i’ll add it to the backlog and look into it ![]()
Teaser of the reworked Copy Sample Slots : now with ability to copy distinctively Samples or Slot Settings - with granularity
(edited - 2nd screenshot was same as 1st one ^^)
New Release: Improved “Copy Sample Slots” (v0.35.0)
What’s new:
- Ability to copy only Sample Assignments (and audio files) - without Sample Slot Settings
- or only Sample Slot Settings - without Sample Assignments
- or both
- with granularity of which Sample Slot Settings to copy or not
User-guide has been updated to describe all this - I’ll update screenshots soon
As always; testers, feedback and requests are welcome
Meanwhile I’ve already started working on next feature → Automatically handle Samples when copying Banks
Okaaay… tried to create a new set in which I copied a few banks.
However, the sample slots list stays empty.
Copying of banks towards a new project within the set works ![]()
It’s a bit click-heavy at the moment.
- Select bank at the left
- Select target bank at the right
- De-select the previous target bank (otherwise it gets overwritten
Some other features that might be useful
- Remove unused sample slots
- Sort sample slots (removing blanks in between slots)
- Append slots from another project (so that banks can be moved that use those samples)
Sorry if some of it already exists. Not a lot of time to find out today ![]()
Yeah that’s expected - I’m working on it, it’s gonna be part of next release ^^
Here is what it looks like so far:
With option to either:
- copy only samples slots/files which are actively being referenced by parts/patterns
- all samples slots/files with sample assigned
cc @Tapepusher
Ahah good call, most of it is already on my todo and planned for release after next one
(along work for in-project drag & drop of samples to slots)
I’m also thinking of including things like:
- Ability to re-organize sample slots using handle/drag&drop
- Adding some one-click re-ordering like alphabetical, or grouping per sample length, or grouping per sample type found in name
- Ability to locate un-used samples from project and audio pool
- Ability to locate duplicated samples in project and audio pool
Thanks for your feedbacks @rosiusyves btw
Re-uploaded demo video - it was made from a previous dev build and actually showcased something wrong - I’m glad no-one seem to notice ![]()
A flash of news ![]()
Work is well underway for the “Automatically handle Samples when copying Banks” feature - and base scenarios are already validated
The complexity lies in Flex Samples Slots, for which all assigned sample use some of the 85mb of RAM available to project - and from which should also be whitdrawn the Mb pre-reserved for recorder tracks, whose exact calculation is quite complex and depends on the project’s memory settings
In other words - need to reverse engineer how OT does it, raises the “Out Of Memory” error, and implement the exact same thing
Quite an interesting topic to dive in ![]()
Cool!
I think you might be able to just do it? So, copy samples? Won’t the OT just list the samples and give an error when over memory budget?
And then later make a kind of progress bar, so that we can pick and choose samples? Show which samples are largest.
Just ideas ![]()
Nailed it ![]()
- Memory available to Flex slots = Total amount of memory available to project - memory allocated to recorder tracks
- Total project memory = 85.5 MB
- Recorder tracks memory depends on project’s “Memory Settings” =
- Number of recorder tracks x buffer duration in seconds x 44100 Hz x 2 channels x bytes per sample (2 for 16-bit, 3 for 24-bit)
So for each sample, we parse WAV/AIFF headers to get the exact PCM footprint (frames x channels x bytes_per_sample) rather than relying on file size on disk to get the precise amount of memory needed
The app validates before copying and shows a message similar to OT “Not enough memory” if neeed - This should all behave exactly like the OT does
First tests are conclusive.
Would you like to test it in preview @rosiusyves @Tapepusher @Supermows @phading ? I can provide you with a link to download current wip version
Sure! Excited to test it out!!!
Hey! I’ve been completely out of this project, pretty amazing progress seeing the last video! I can test it next week, sure!
Thanks!
Yes please ![]()
One small thing missing here, we’ve ommitted the part where OT makes sound. heh
I know what it’s like to work hard on something like you are, so ignore this if you’re sure, but I meant this, I think the UI for the tools page should be this and NOTHING else on the surface imo:
and you simply copy banks to other projects.
On the rare off-chance that you may want to copy pattern data without sounds you’d menu dive to do so. Correct me if I’m wrong but other OT people don’t need this either, and the functionality is front and centre currently. (however btw features impossible on OT like swap tracks would be amazing, as suggested by another user above)
What I want:
User: Copy bank
UI: done.
What I see in the app:
User: Copy bank
UI: you wana change how it sounds?
User: What, of course not.
UI: what samples
User: whatever I used in the bank…
UI: showing loads of options
User: Just copy the bank ![]()
This is what we’ll use it for 99% of the time imo, but if my perspective doesn’t represent the majority I’ll stand corrected, but maybe you could at least put the copy bank (with everything included) as the default setting so there’d be no config each time.
Having said all that, I’d be over the moon just to see banks be properly copied, and a simple UI would just be a bonus, so I respect however you wana do it. Also, I’m aware I may have gotten details wrong, I’m just writing this way cuz I care about the project. As I’ve said, if I get to see banks get copied to other projects…
I think you will be pleased by wip release then ![]()
I’ve consciously set sane defaults for all options - we can adjust further all together as much as needed
Like stated a few times, current phase is focusing on functionalities - UI revamp will come
Swap tracks is definitely on the roadmap
In any case, feedback appreciated
Hello! This great project made me register to this forum
just in the middle of getting ready for a few gigs when I bumped into this, jumped right in!
A couple of questions:
- Is there a way to see the track default assigned samples for each track in PARTS? I haven’t been able to find the sample assignment
- What’s your overall workflow editing projects? Do you work from a backup on the computer and then transfer the project folder when done? Or did you manage to use it while connected live to the CF card in USB disk mode? I tried a few times but OT got disconnected and froze every time

Hi @dada.sandor , how do you do ?
Connected live to the CF card in USB disk mode works just fine ![]()
Although I remember that I had the exact same issue as you do, a long time ago with the original CF card, the one that came with the OT. Since I purchased I brand new one I never had the issue again. It got nothing to do with the app though ^^
You mean a way to see which Slot ID / Sample is assigned to a track in case Track is Flex or Static ? You are right, it’s not implemented yet but I do like the idea - I’ll add it to todo ![]()
Thank you @imacactus for the information!
May I ask what CF card you use? I’m not using the original but a 64GB Sandisk, (Extreme Pro, 160MB/s), I would think that should be fast enough!
That would be amazing! ![]()
I’m using exactly that one too ^^ it’s not about speed, it’s about reliability though
Sometimes cf cards don’t like some hardware (or the other way around), it’s possible your card has some issue, I suggest testing with a another one
I’m really impressed with what this seems capable of. I’d overlooked this thread for a long time because I incorrectly thought it was about managing samples. It looks so powerful!


