- [26/09/2025] Group A merging added for DAWProject and MIDI transformers
- [23/09/2025] ABLETON: FX support! The return track will be added with attached effect and each track(or group) will be sending to this return track
- [19/09/2025] Added feedback functionality with ability to attach your project for research
- [17/09/2025] ABLETON: Export tracks from group A into Drum Rack (with choke group!)
- [16/09/2025] ABLETON: Added play modes support: KEY and ONE
- [16/09/2025] ABLETON: Added sample stretching (both BPM and BAR modes are supported)
- [12/09/2025] ABLETON: Added the ability to group tracks (4 groups, same as EP) + bugfixes
- [09/09/2025] ABLETON: Minumum supported version is now 11.3.35
- [09/09/2025] App is now working offline (PWA mode)
- [08/09/2025] Added Ableton 12 support + more note duration bugs are fixed
- [03/09/2025] Fixed several bugs, including issues with velocities and note durations
- [29/08/2025] Added MIDI export
## Motivation
If you’ve been producing with the EP-133 (or EP-1320), you already know the frustration: there’s no clear way to export your projects directly into a DAW.
The official EP Sample Tool only lets you manage samples and backups. That’s it.
Sure, you could record MIDI notes or capture audio track by track, but it’s slow, tedious, and not fun.
While exploring the backup files generated by EP Sample Tool, I discovered that the device exposes a structured internal filesystem. Projects, notes, settings,
and other device data are stored in files, while the backup process simply packages this filesystem into an archive.
This opened the possibility of accessing and interpreting the device data directly. Since Teenage Engineering does not publish
the implementation details or source code behind Sample Tool, I began reverse-engineering the file structures and studying
the application behavior. A significant amount of work went into analyzing file formats and reconstructing the underlying
