An unofficial librarian/editor/data tool for the Elektron Machinedrum, in a post C6 world, for reading, editing, manipulating, storing and writing all Machinedrum data.
Complete system states can be imported, edited, combined and exported back into to the Machinedrum. There’s Global, Kit, Pattern and Song editors for remote access, you can create entire projects without an MD connected.
MDDT has been independently developed with a MK1 UW but implements functionality for all Machinedrum models including Turbo MIDI speed.
Normal midi speed is robust, Turbo speeds are still being optimised… Your feedback is appreciated.
DisclAimer
This idea birthed ages ago when Rusty shared his (now abandoned?) MDEdit project and i really wanted that desktop based song editor, spiralled from there.
What kind of lunatic thought attempting this with JS was a good idea…
I’m sharing the beta in the hope people jump onboard and feedback to make it better for all users.
I love the MD, MDDT comes from a place of wanting data secure, disparate snapshots mixed up and creativity sparked.
There will be bugs and improvements can be made. So it’s time to share and get roasted and move forwards.
Requirements: Chrome, an MD, a decent midi interface or TM-1 for turbo.
Zoom out to find a best fit for your screen resolution.
MDDT enables some new creative opportunities with the Machinedrum in extended mode, i’m excited to explore them further and hear what other people do with it…
A Monomachine version you say? Not impossible….
Man, that looks like a really impressive project. I really wish I had an MD to support testing, but I don’t. Too bad. Seems I’m missing out on big fun.
incredible work, and a great use of LLMs. I look forward to tinkering with it once its done. Given the relative size of MD community, i reckon open source wouldn’t be a bad way to go? Reading your disclaimers it would probably help you find some less obvious mistakes etc.
Well done my lord. I’ve got a MD MKII UW, no +Drive.
Still on OS vX.07, but can upgrade (haven’t upgraded because I got several blank screens of death before x.07, and had to wipe everything out and reinstall the OS. Not sure if it was due to the unofficial os though).
Getting a bit busy, so can’t commit full-time to testing, but happy to debug/test, even write some code (in C++/JUCE…).
for fragile midi stuff that’s a much safer bet i reckon, running out a browser seems really susceptible to other usb stuff plugged into/running on my computer, trying to capture with OBS and camera isn’t fun. that being said we still have stable full memory import and export. and i think most uses cases will just be focussed on individual/small batch in/out operations.
edit:
testers report turbo not happening. a real help would be some in out midi monitor of just sysex comms when checking turbo toggle in C6 connected to TM1.
and during some data sending just to see how the turbo headers and syx are occurring.
please dm me some copy and paste!
does anyone have a tm1 for sale/loan in south england?
really want to sort this without sending out 1000s of fail patches!
thats been the modus wafterandi of this whole project.
update: turbo speeds achieved with a TM1. Stability: not good.
Next steps: improve stability.
also a guide has been created for JS confident devs to create data modules that can be inserted into the LAB.
i’ve created some kit/pattern/song generators (thats are basically randomisers with weighable ranges), and a tonal mask which is pretty good, and a kit/pattern or song seed morph, which needs work.
but the opportunities are limitless, some kind of machine learning that could analyse all your kit’s patterns and create new forms and structures around your md programming style would be nice!
i was thinking some kind of pattern/song structure creator that could deterministically shift the swing value to create shifting time for short patterns (2 step length etc) over song rows. can be done by hand but the lab allows batch processing opportunities in one click for things like this.
any other lab md data ideas?
Beta version 1.1 is now being shared, featuring new OS switch at request of testers for users who wish to work securely with their 1.63 data.
Sample manager has been reworked for stability and now includes open loop to send samples directly outside of sample mgr.
Other performance/ui tweaks.
Users are reporting stable import export at 5X turbo speed so far so still some optimisation and development required for full speed. So tricky without personal tm1 but thanks to diligent testers so far we are getting there.
But bottom line we have turbo TM-1 access working.
Interested in testing? please get in touch.
need more feedback to help steer this towards a best fit for all md users.
May I say this is another great project sparked by awesome human beings and one of the most inspiring pieces of hardware we have had in decades?
Kudos to you @waftlord! I wish I had the time to help you, but unfortunately, I don’t - best of luck and all my love.
We are still in beta.
Turbo speeds possible for Global, Kit, Pattern and Song data. Needs optimisation, currently we’re pummelling the TM-1 until it provides expected payload. Sample turbo receipt and transfer isn’t super robust for bulk operations yet, but for single slots and at standard midi speed it’s stable.
Feedback is appreciated.
Will make a vid detailing instructions & possibilities soon. Mildly interested in how intuitive it is without instruction.
