Not signed in [Sign In]
[Apply for membership]

Vanilla 1.1.8 is a product of Lussumo. More Information: Documentation, Community Support.

MiniCommand: MD pitch Euclid communication problem

Bottom of page arrow

1 to 8 of 8

  1.  
  1.  
    Hi,

    I just got my minicommand and it rocks!

    I paticularily like MD pitch Euclid, but have experienced some bugs.
    I don't know why, but sometimes the MC suddenly stop sending info to the MD, when I use the pitch Euclid patch.

    For example : I'm connected in handshake (midi out of MD to midi in 1 of MC, and midi out of MC to midi in of MD). Then I chose a bassdrum to play with, and then I play with the pitch euclid and all is fine. Then I change track on the MC to play with another sound. Still works. But suddenly it doesn't. I'm not sure why. So I reload the patch from the software, shutdown MD and MC, restart them up and still nothing.

    Then I try to upload another patch which contains the pitch Euclid program. Still nothing...

    So then I upload a patch which contains PATTERN Euclid (and not pitchEuclid), and the MD receives signals from the MC normally.

    Then I reload a patch with PITCH Euclid in it, and then it works fine.

    -----------------------------------------------

    So I don't know why, but when pitch Euclid get stuck, even if I reload a patch which contains it, it will still be stucked. But, if I load a patch with PATTERN Euclid, try it on the MD, it works, then load a patch with Pitch Euclid, then pitch Euclid works again. As if it was the Pattern Euclid program that would unstuck PitchEuclid... Weird!

    Anyway, that being said, I only tried the MC for 3-4 hours or so, so maybe I did something wrong...


    Second bug : When pitch Euclid sends ifon to the MD, it seems to trigger the M2 (track 14) or M3 (track 15) tracks on the MD every first step of a bar. I had Ram P1 assigned to those tracks everytime it did.


    Thanks for making this awesome little unit btw!
    I've already made many things on the Machinedrum that I wouldn't have done without the MC.

    Cheers,

    JM
    • CommentAuthortIB
    • CommentTimeJan 19th 2010
     
    Hi JM, the triggering of ram p1 on M2/M3 will be the live patch doing its thing I expect... cant help with the other as not tried pattern yet. enjoy the new toy!
    •  
      CommentAuthorwesen
    • CommentTimeJan 19th 2010
     
    this is indeed weird, and I will look into what may be a reason. Is the sync still running (LED flashing) when the system gets stuck? The P1 is indeed doing what it should, as I use it mainly for retriggering the recorded sample. I think you can "mute" the livepatch firmware which is doing that in the mainscreen, and it should stop sending the P1 retriggers.
  4.  
    Hi tIB and Wesen!

    I think I've loaded the MDmonsterNew patch. So the livepatch would trigger P1 machines. That makes sense! How can I mute the livepatch firmware? by holging all four buttons (to return to the firmware selection) and then by holding button 3 (bottom right) and pressing the knob below "live patch" on the screen? or is it only in another program that we can mute? (like MDmonsterXXXX...)

    BTW, is there a version of the monster patch known to be more stable? (preferably with pitchEuclid)

    For the "stuck" bug, it may be because I unplugged the midi cables while the units where on? (to change the firmware on the MC, and then plugged the MD and MC back together without shutting down the MD). I remember doing this, but don't know if that could be what caused the MC to stop sending infos. The left LED was blinking on the MC when I pressed play on the MD, though, so the MC received the clock. I tried different things after that. But everything was ok when I went to bed yesterday, after loading PATTERNeuclid and reloading pitchEuclid after that, shuttingdown machinedrum and MC, plugging them together and power them on. If I have time, I'll test further all of this tonight and report if I had any similar problems (but this time, I'll shut down the units before plugging and unplugging).

    But just to be sure, is there a way to reset the MC to the factory default settings?

    Thanks!
    •  
      CommentAuthorwesen
    • CommentTimeJan 20th 2010
     
    Yes the stuck bug probably comes from the cables, because then it may loose the MIDI sync. You can resolve it by just pressing stop and start. The factory settings are pretty much the firmware, the only thing that is stored "outside" is the MIDI MERGE and MIDI CLOCK settings.

    For a first guess, try the START and STOP thing. The main goal in the next time is going to be debugging the existing functionality and properly documenting it. I've done a really massive amount of thinking about the direction in the next months/year, and I am writing up blog posts to explain it to the users.

    cheers, manuel
  6.  
    You mean START and STOP on the MD? I've tried that many, many times and it didn't resolve the issue. Anyway, I'll play around with the MC this week, and will report back to tell you if I have had the same problem or if everything's fine.

    Thanks for the support, it's really appreciated!

    JM
  7.  
    Ok I jammed for about an hour yesterday, with the MDmonsterNew firmware loaded in the MC. PitchEuclid was working at first and after 5 minutes stopped sending infos to the MD. I just restarted the MC and no problem for the rest of the hour.

    BUT, like you suggested to me, I muted the Live patch (and also the Arp patch), but Ram-P1 was still triggered every 2 bars. I double checked that there was no step triggered on the sequencer of the MD, and triple checked that the Live patch was really muted.

    Any ideas?
  8.  
    Oh and I don't know if it's normal, but when I upload a patch from the boatloader (on OSX 10.5, PPC), it takes like 20 seconds to recognize the elektron TM-1 user interface (it does recognize it everytime), and when I upload the patch, the progress bar does it's thing, stops at the end and stays blue even though it seems to be 100% done. The buttons below still shows "send" and "cancel". To be sure, I waited a minute to see if it was going to write "upload is finished" or something, but the bar just stays blue... So usually at this point, I click on the red "x" to close the window and assume that the patch is loaded properly.
 

1 to 8 of 8

  1.