Hi there,
Has anybody tried to rev-eng the TLP file format? There is only ToneLab editor for Windows and Mac, there is no Linux version. I've written to Korg about the need for Linux version but they simply haven't answered. I guess that waiting for it makes no sense so I'd like to write a Linux app to operate TLSE. I guess rev-eng of the TLP is not so hard but inventing a wheel is not what I like the most 
Best regards,
teel
Personally, I would love to
Mon, 2007/09/10 - 2:14pm — firebrandPersonally, I would love to have an editor for the Palm OS. Then I could have a small, touch-screen based editor/librarian for use at gigs.
If you use Wine in Linux I
Mon, 2007/09/10 - 6:25pm — mself61If you use Wine in Linux I think it may work, SV uses linux and has the editor working, WHERE YA AT SV ?, I was looking into a small tablet PC like the OqO, or a samsung ($1,200 greenbacks) PRICEY but easyily portable and the ease of importing patches plus lots more, But I've decided to stick with my Laptop to do the trick.
www.selfdistruction.com
Hi teel, the tlp file format
Thu, 2007/09/13 - 12:52pm — kaalHi teel, the tlp file format is actually quite well known, although VOX doesn't want to talk about it a lot. The tlp files start with a header (which looks always the same - there is one version for a single patch file and another one for a 96-patches file. It also contains somehow the information of the Soundeditor it has been created on (Soundeditor for TL desktop or for TLSE). You can actually create valid tlp files by just copying the header from an existing tlp file (1 patch or 96 patches, that must fit), and append the data parts as described below.
After the header, its simply the data as described in http://www.voxamps.co.uk/downloads/PDF/ToneLabSE_midi.pdf starting in the [TABLE 1] section. This data part exists once in a single patch file, and of course 96 times for a 96-patches tlp.
The TL Desktop midi format (see http://www.voxamps.co.uk/downloads/PDF/ToneLab_midi1.pdf) is a subset of the TLSE format but has the same length, it just leaves the places used for the additional TLSE features empty - therefore you can load TLDT files in the TLSE and vice versa.
I did write a program (VB - sorry no Linux) that can display the main settings in a tlp file (http://www.tonelab.net/node/461), and another one that can "assemble" new tlp files from a selection of patches (http://www.tonelab.net/node/1170). I never programmed something that would decode all the control-knob values, but at least I think I understood how this looks like in the tlp file (the "effect parameter structure" tables). If you want to know more just drop me a PM.
PS: tllp files (TLLE) basically also use the same structure.
Kaal