Wow, thanks for adding the copy track feature!
I just tested it, so cool, the only problem is that it doesn’t recognise they are the same samples and it duplicates them when exporting. I was hoping it would be able to export only the samples once and but use them in all the tracks.
Right now when you export a kit it duplicates the samples into a folder and adds the eldrum file with it. What I meant is an option to don’t export the samples to the folder(they should be already a toneverk playable file type).
Then you can have a library of samples in the user sample folder and the eldrums reference those samples with a relative path (I think it should work).
The advantage of this is that the samples can remain organised and be used in single sample machines or even in different kits.
Ah i see what you’re getting at - sample pool / size optimization via clever file referencing. Love it. I originally did some experimenting with sample chains (since the number of files on TV affects load times as much as the size of the files) but it didn’t work out for some reason. I thiiiiiink I also tested your proposed use case but I’m not 100% sure I remember correctly. It makes sense conceptually to me.
Have you tested it otherwise e.g. via hand-editing the files or using an llm to do that? If you can get a working proof of concept and an .eldrum file over to me to analyze, also maybe a screenshot of the filenames in the folder, i can use that as a starting point.
It would also mean a new workflow which would need a new UI flow in BONK, and potentially also implementing a new feature I anyway had on the roadmap (bidirectional syncing with TV) to manage a shared global subtracks sample pool and create new eldrum presets referencing that global sample pool. Otherwise things drift out of sync or risk duplication.
Meta: these days time with my own TV is hard to come by (baby arriving very soon) so rapid QA and testing new use cases at the moment on device is difficult. Small tweaks on BONK UI side / mac side are way easier. thats why if you do have any example files I can build off of its helpful - I’d like to know that I have a good chance at oneshotting this without needing to bust out my TV in our cramped living room every night for a week 
Will have a chat with Claude about it and see how far i get
Universal and MacOS 13 would be amazing.
My workstation is frozen at 13 but I’d live to be able to run this.
S.
+1 for this feature, I’d love to be able to use the samples for several different kits without copying all of them into a separate folder each time.
patiently waiting for a Windows release
Hey James,
Thanks a lot for your work, I’m glad you are interested in the sample pool idea. I will try to get an example file this weekend to share with you.
Any thoughts about the other question, when duplicating tracks to not duplicate the samples?
Just an FYI, the multi and drum TOML configs can reference either the current folder, or absolute file paths from the Tonverk SD card.
So to support a sample pool, you’d need to write the file path as something like sample = '/mnt/sdcard/User/Single Samples/Path/To/Sample/filename.wav'
I tested this with some presets and it works, using relative paths didn’t work unfortunately.
Firmware 1.4 also lets you nest folders in the ‘Multi-sampled Instruments’ folder which I found interesting, several folders deep too, and the order of the multisample selection list takes the folders into account, but flattens their contents to a single list - I’m hopeful this is the seed for proper folder support on the drum and multi preset lists 
Just to check
If I were to put all my tb303-xxxxxx multi folders into an actual tb303 folder , it’ll tidy up my folder structure but … on tonverk it’ll continue to display them as it does right now ? ( a bit weird and random but I’m used to it ) ?
Would it break existing projects ? ( I’ll probably try it tomorrow anyway … report back )
Tonverk will display them in a different order, each folders contents get grouped together in the single list of multis.
I’m not sure if it would break existing projects tbh, I do not know if the project links them by just the multis folder name or if each sample also gets stored in the project.
I also found that multis need to be in a folder of the same name as the config file name to show in the list (even if the samples are referenced by their absolute path on the sd card).
BONK 1.4.0 is live! 
New features: In-kit Sample deduplication (space-saving!) @andreu + Direct reading of kits from mounted Tonverk SD Card (Bonk Pro) + common Sample Pool functionality (Bonk Pro)
Note - i put this behind bonk Pro because it was more complex and will require more maintenance going forward. Lots of edge cases and lots of things that can break for the user, so I’m assuming I’ll be hearing some feedback of things that need addressing especially on the kit reading side. So far it successfully reads/loads both user and most if not all factory kits. But there are more UI / UX cul-de-sacs to be discovered especially trying to bidirectionally manage things and reference files that may break links. It’s def a pro/advanced user type of thing…but it’s really awesome being able to audition TV factory and user kits directly through BONK!
Auto-update will notify you if you already have BONK. Download it here and, if you’re interested, pick up a Bonk PRO license to upgrade..
.
Thanks also to @brian3kb for the tip on file referencing.
Windows build is queued next!! I’ll drop it here when it’s verified later this week hopefully.
I just realized the new release basically allows you to directly edit and customize the factory kits - or borrow samples from them into new kits ! Wild. Updated the release notes to make that clear
just downloaded this but its silicon only? says intel and silicon on website but its in fact silicon only is that right?
Currently yes. Sorry for the error on the website. Intel version should be coming in the next week alongside Windows - let me know if you’re up for testing the Intel version, happy to send you a discount if so!
Also if you already bought PRO and want a refund until Intel is ready, PM me. Sorry about that!
I bought the pro version but no worries will just use the code when intel drops
Edit: actually maybe i was able to make an intel build after all. Testing
Unfortunately building for intel is proving harder than I assumed… Running into lots of different walls. Github actions doesnt support intel anymore and its complicated building for Intel from a silicon mac… I’d like ot process a refund for you as I cant promise I’ll be able to ship this this week (and I have a baby on the way so dont wnat to hold onto your money if I can’t deliver properly!) Please check your dms:)
Summary:
Intel build is in beta testing
1.4.1 for Windows is also in beta. Crossing my fingers it goes well 
1.4.2 for apple silicon en route, will add
Later roadmap:
BONK 1.4.3 is live and its a big one… drumroll… 
WINDOWS VERSION IS HERE!
Download windows installer here // Pick up a PRO license
With 1.4.3, some nice new updates to make BONK smoother, faster, funner on all platforms (except Intel, see below):
Added (All versions)
Fixed (All versions)
Added (PRO)
Fixed (PRO):
Upcoming:
pictured below - reading tonverk sd card, loading user and factory kits, importing user and factory subtracks into editor, live sample search by filename
Thank you for making this happen!
Huge if true!!
