Is X.11 compatible with MCL or should I remain on X.10 if I want to use my MCL? Thank you for your time
Itās compatible, but you have to update MD AND MCL.
Worth to check the changelog (not sure whatās the advantage of X11 - I am still on X10 
).
Usually there are some bugfixes 
wasnt x11 a big update with new machines?
Bugfix only:
List of changes from Machinedrum SPS-1 OS X.10 to X.11
Restored functionality of the Master EQās Low Shelf Filter.
Hi all, picked up a non functional machinedrum sps-1 MK1 from a friend and had it serviced
Got to play with it and then discovered the update
(I believe the last version installed was 1.6.3?)
Anyways I tried to update it via sysex from my Mac and it was successful all the way until the booting part which got stuck on the starting screen
I tried everything, unfortunately it wonāt even let me do a factory reset as it goes back to the booting screen displaying the os j X.11
I have read this whole thread and donāt seem to find a solution to this problem can anyone please assist ?
I was so eager to get this bad boy going at this point Iām willing to downgrade if possible but somehow the factory os wont transfer as well
Only X.11
Iām currently trying at a very low speed in sysex librarian will update here if that worked but not looking good
Oh also I tried firing up test mode the welcome screen said ok on
Thanks in advance !
Hello, hoping someone can help me with sysex message 0x70 0x41:
0x41 Kit Recv Workspace:
%0bbbbbbb | kit data 0
....
%0bbbbbbb | kit data end
Iām assuming this is a way to overwrite the kit in current memory. Iām sending the same payload as a 0x52 message except replacing (0x52, version, revision) with (0x70, 0x41). The message is therefore 1 less byte. However when I send this, the MD seems to ignore it, so I must be doing something wrong.
I have 0x40 working. It seems to be equivalent to sending 0x53 with orig_pos=0x7f. Both respond with the same 0x52 message.
Reason Iām looking into 0x41 is because I was having trouble updating the current kit via 0x52. Sending orig_pos=0x7f appears to work, as in the UI shows all the updated params correctly, however the MD wonāt produce any sound after that. I must be doing something wrong.
Running X.11
I fixed my issue with 0x52 seemingly by making sure the kit name ended with a null-terminator. Maybe I was causing some sort of buffer overrun?
Still interested in how to write the current kit memory with 0x41 though.
Hi, I made this on your firmware the other day. Thank you thank you thank you for keeping up the support, I really appreciate it.
14 Likes
Great video - thanks a lot!
I never thought about re-sampling capabilities.
Now I have to kill my GAS getting an MD- UW.
Thought, would have been over it ā¦
1 Like
Machinedrum SPS1-UW OS X.12 
Download
List of changes from Machinedrum SPS-1 OS X.11 to X.12
-------------------------------------------------------
The MD should no longer skip incoming MIDI bytes when under high load.
Improved MIDI clock stability when in Enhanced Mode
Added length checking to ASSIGN sysex commands
X.12 is also required for MCL 4.70
22 Likes
Thank you 
Awesome, thanks so so much!
1 Like
Hi,
Iām sure this is already known and has been discussed (but somehow I canāt find anything about itā¦): The added LFO waveforms in the unofficial firmware only work when applied to a parameter of the same track (i.e., locally, so to speak), right? So not like the āoriginalā ones, which work globally.
Have I overlooked something? Should I reinstall, or is that just the way it is?
Thank you so much @JustinValer and @v-yadli , itās beyond insane what you did for the machinedrum <3
Have a look:
1 Like
Thank you! This looks crazy and iāll have to get/build a MCL sometime, but for now i have just the machinedrum - so my question was only referring on using the MD without an MCL (should have mentioned that, sorry!).
As i donāt have a MCL and the video is 17mins long I watched it on faster speed and maybe missed the information about how the LFOs / their new waveforms work when using the MD without an MCL (if thatās the case: sorry!).
Wohooo! Thanks a lot 
!
Is it currently possible to use MIDI tracks (Midi machines) via MCL?
Cheers
flo
The extended LFO waveforms on the MD should be able to modulate parameters on any track, thereās no limitation there.
1 Like
Blockquote
Is it currently possible to use MIDI tracks (Midi machines) via MCL?
Yes, mostly.
Crazy! 
In which version was this feature added?
(Seems, I missed it completely)
Cheers!
Thanks!
Unfortunately, that doesnāt work for meā¦ Only when I assign the LFO to a parameter on the same track (in other words, when I use the LFO of the corresponding track). When I change the waveform of the LFO to an original waveform, the controlled parameter moves as expected. When I change the waveform back to an extended one, there is no movement.
Can anyone confirm that the extended LFO waveforms assigned to parameters on other tracks work for them (without an MCL connection)?
Is it possible that reinstalling could help?
EDIT: Ahhhh is it possible that some of the waveforms (original and extended as well) are exclusively working when updated by trigger or hold? Because then it would make totally sense nothing will happen when using these on another track (if the track hasnāt any triggers on it)ā¦
i would have thought that the would cycle anyway (just as waveforms like triagle or sine) - but they donāt, right?