Thanks @JarlLyng for confirming that I hadn’t missed anything in the recent releases. Totally agree with the need for it to be fully reliable for release, or at least be able to report that the export had worked/failed, rather than incomplete.
1 Like
This would be incredibly useful. I would easily pay 10 times the app’s current price for this!
In the meantime, if it finds a missing sample reference, and that sample exists elsewhere on the card, can the app help find it? (In the scenario where I break a project by moving a sample from its folder to another folder on the same card.)
1 Like
@square_wave Thanks!
Not for projects yet. TonVault would first need to read which samples a project uses before it can tell that one has gone missing, which is the same groundwork as the project backup. Once that exists, finding a moved sample elsewhere on the card is the easy part.
For presets and instruments it is closer. TonVault already flags a preset whose sample is no longer where it expects it, but it does not yet tell you where the file went. Pointing at a file with the same name elsewhere on the card is a small step from there, so I will look at adding that.
Ok thanks for your answer!
Are project files even readable on Tonverk? I tried poking around but I couldn’t figure anything out. But I’m pretty ignorant about coding so that doesn’t mean much.
@square_wave Partly. From what I could see on my own card, a project is a folder with a standard database inside (RocksDB), and its keys read like a path: samples, kits, sequences, tracks. The values are in Elektron’s own format, compressed, and each part carries a version number. So the sample references are in there, but not as text you can open and read.
Reading them is doable, but it needs care. Opening that database can write to it, and the Tonverk itself writes to it when it loads a project. Anything that reads a project should copy the folder to the computer first and only ever open the copy. I wouldn’t point other tools at the project folders on the card.
TonVault still doesn’t read projects. That’s the groundwork for a project backup, and I’m not there yet. What I said I’d look at for presets did land in 1.5: when a preset’s sample has gone missing, TonVault now names any file with the same name elsewhere on the card, so a moved sample is easy to find. 1.5 also fixed the check for samples outside the User folder, which never fired before because it looked for USER and the card says User.