current version: release 0.80 as of 2018-01-09
current development under 'Trio+Tool' branch
updating the Trio+ hardware with 'TrioUpdaterInstaller_v2.0.2.exe' from Digitech website might be necessary
this is a Python 3.x script - it will NOT run under Python 2.x
CONTENTS:
00 Status-miniblog
01 TLDR
02 Project Status
03 Working
04 Not working
05 Getting started
06 Going further
00 miniblog:
2018-01-09
Released version 0.80. This release features a graphical user interface (GUI) based on Tk (comes included with python). The release includes all source files as well as a windows binary (.exe). If you're on linux, you can compile a binary from source. I have added a readme on some issues with that. If I find the time and motivation, I will polish the linux version and release an updated source along with a binary. Since you will need windows anyway to generate the .tlsd files with the Trio Manager from Digitech, I thought a windows release will do for the moment.
I will be happy to fix bugs - if you find any - but consider the tool more or less feature complete. I don't think it will be possible to extract midi data from the .tlsd files. I suppose these are generated 'on the fly' within the pedal. Nonetheless, there are some suspicious areas in the binary files that look somewhat like drum pattern. We'll see... As always: If you are interested, your help on reverse engineering the binary files would be more than welcome!
Cheers!
2017-12-20<
Ho ho ho - christmas time is here and so I have uploaded the new release v0.75 of The Trio+ Tool. Now you can upload wave-audio to parts and show info on your .tlsd files. Info has been enhanced with part-duration in seconds. 'pyaudio' is required to enable upload-mix-preview. Will run without it but is much more convenient with pyaudio installed on your system. Automatic install of pyaudio has been tested under win and linux. Next up I will try to compile native binaries for win and linux ('.exe' files) with the help of 'pyinstaller'. Anybody out there willing to help with compiling for mac?!
Merry christmas and happy new year folks!
Cheers!
2017-11-27
Been working on 'upload audio' feature. Was looking into ways to make a preview of the results since you might want to adjust the level of the uploaded audio to match the recorded guitar level within the song. There is the 'pyaudio' module which looks suitable. This implies that the user would have to install this module on their platform. At the moment I am able to test a guided install of pyaudio on Linux and Windows. From a bit of google search it looks as MacOs might be a bit troublesome. I cannot run tests on MacOs. However I will implement the 'upload' feature in a way that even without pyaudio the user will be able to use the feature - but then without previewing the results. So this might then be a bit trial and error to match the audio levels. As for now, the audio from the song will be read to memory and the mixing/preview is coded. I will now have to write the code to patch the mixed audio back in the .tlsd file and do a bit of testing. Also the implementation of the guided pyaudio installation is heavy time consuming but it will be an important part of the overall function so I feel this need to be done. As an experienced python user you might think it was easy as 'pip -install pyaudio' but this holds true only for windows. I was also experimenting with 'pyinstaller' to release a native Linux/Windows executable. Looks promising. This would of course be a more hassle-free approach since it would bundle the dependency on pyaudio. However you cannot cross-compile with pyinstaller thus no luck for a MacOs executable. Maybe a memeber of the community could provide a MacOs compiled version once the new release is out. As for now be patient and
Cheers!
2017-11-08
There still seems to be interest in the project. Just received an email asking if there was progress on the 'upload audio' feature. Have had no time for coding the past months but will take this as an incentive to re-start working on this. So hang on please ;-)
Cheers!
2017-08-03
Version 0.74 has been released today. I was requested to add a feature (song creation of parts from different songs). Done. Also made the UI a little nicer. Enabled copy/move of 'trained only' parts.
... Ahhh and added some 'Yoda says...' messages if user input is incorrect ;-)
Cheers!
2017-05-24
Working on the 'upload audio' to a song functionality. Have not worked out how to determine which part of the interleaved audio that has been recorded is the one actually being in use currently. As a last resort, one could ask the user to decide but I am still hoping to figure that out. Maybe I will be pushing some code in the next weeks. Had to attend to other issues the last weeks.
Cheers!
2017-04-04
New release (0.73, recommended). Copy, erase, move parts implemented.
Cheers!
01 TLDR:
- Ultimate goal is to extract audio and midi data from the Digitech Trio Plus pedal's SD card for further use in your preferred DAW.
see: http://digitech.com/en/products/trio-plus
- Written in PYTHON3 (no dependencies)
- Tested on Windows, Linux
02 Project Status:
good to work with; always get latest release!
03 Working:
extract audio; copy, move and erase parts; build new .tlsd file from parts of other .tlsd files (i.e. song creation of parts from different songs).
04 Not working:
upload audio to part;
Any MIDI data support is missing at the moment
05 Getting started:
download and install the latest Python version (3.x) for your computer from
https://www.python.org/downloads/
Record some stuff with the Trio Plus
Export the songs (the single files) onto your computer using the Digitech Trio Manager http://digitech.com/en/softwares/
Download the latest RELEASE version of the script. Unpack the .zip file. Place the exported songs (*.tlsd) from the SD card into the unpacked folder and start 'The_Trio+_Tool.py'. Follow the instructions.
-> LINUX users remember: you might need to change the endlines of the script (as it was edited on windows) <-
The subfolder 'Trio_wav_export' will be created and the audio contents of the songs will be written herein
06 Going further
NEED YOUR HELP to further reverse-engineering the data.
Look at my 'findings.txt' for what I found out so far
Let's have fun!