When I try to send samples to my TBD, I get an error.
These are the steps I follow:
-click 'Edit sample ROM' button
-select compatible (4416 mono wav) audiofile
-click "compile, send to TBD"
Then, the error "Erase failure" shows.
Tried different webbrowsers without succes. All other features see to work fine. For instance, in the tapp terminal I can erase the TBD, or flash firmware or the samplerom. To exclude any aspects, I also tried to run the tapp tool as administrator. I even tried it with my laptop rather than my desktop. Same story.
Tried different audiofiles too,just to be sure. When I check "Prelisten wav files" they play just fine when I hover over them.
- Then click on "Code" and save the whole repository as a ZIP-file, you then will find the wavetables at: <<yourdrivepath>>/ctag-tbd/sample_rom/wavetables
- You can load all of those at once via multiselect (depending on your OS) during the comilation-process via the Webbrowser as mentioned above
- Then you'll have to mark all of those as wavetables in TBD's webbrowser sample-compiler-list
Please note: if you are not using Wavetables with any Wavetable-related plugin for TBD you of course can leave them away and then gain more space for your samples!
When you have your compiled samples file on you PC, instead of uploading them via the default Webbrowser, please close your USB-connection programme "tapp"
and start it again. Then please select "FLASH SampleRom TBD"via tapp ('Terminal Application for TBD') - after you click that you can select a sample-file for TBD, which would be the one you saved prior to that. Again the behaviour here is a bit different depending on the OS you are using.
After that you have to start TAPP TBD again, in the mode you already know to be able to access TBD via your webbrowser as you already do now.
The process here is a bit complicated, because so far flashing the samples directly via the Webbrowser (over USB) is so slow that in contrast to the Eurorack version of TBD, which also supports WiFi-connection, it currently is not supported. Afaik, this is a flaw in one of the libraries used to drive the underlying processor / USB-stack, so this may or may or may not be improveable at some point in time.
Many thanks for all the useful information! Not sure what goes wrong on my desktop, but I just tried it on my laptop again and by following your instructions I could get it working. I'll check the issue on my desktop later. It must be some local issue. All works fine with my laptop. Thanks again 😊