General MIDI editing workflows

2»

Comments

  • D-One
    D-One Moderator Posts: 3,479 mod
    edited April 16

    Dang.. @theviirus we replied at the same time... :D

    1: Sending midi program change on every pattern cycle leads to drop outs occasionally when a preset that is still sounding is called up a second time...cutting off the previous note. Any edit youve made to a sound gets reset on pattern play or loop. This also does weird things to programs with their own clock (e.g. arps) and can lead to dropped notes, stuck notes, muted voices, timing issues.

    Oh, I see. Thats a fair bit to digest and I appreciate the explanation! Wouldn't triggering it with double stop also cause the same problem of resetting the sound tho?


    2: Double tap stop is not a custom feature in my opinion. In almost every other midi or digital audio environment I've used since 2000, double tapping stop: returns song position to zero

    I am aware and agree, to the point I hacked my maschine to do just that.

    (Only possible in controller Mode since I don't have access to the M+ internal eMMC and/or there's no known way to modify the SW on the M+, yet.)

    Anyway, I was not aware Double Stop did all that other stuff you mentioned on other platforms tho, that's certainly interesting. I gotta think about this for a bit... I do feel like a discussion like this which is rare around here should have its own thread instead of being, well... offtopic.

  • theviirus
    theviirus Member Posts: 12 Member
    edited April 16

    You can, with a Macro, but for that you gotta set it up on the computer first, then save a template I guess....

    I have macros for my SH01A and Virus Snow for patch selection using msb/lsb, and program change,... and I thought this would be the end of this but the macros don't send or update these messages on project load. Thats where Tetsuneko's lock state trick comes into play. Set one for zeros on those parameters, and another for the parameters you want...toggle between them to manually send these program change messages.

    Wouldn't triggering it with double stop also cause the same problem of resetting the sound tho?

    Not really. Resetting the sound is expected on double pressing stop and not really concerning...because you're returning to zero and resetting what you are doing. If you want to save your sound, you probably are going to do this before double pressing stop. The issue I was describing is that sending a program change while playback is still active is something that can be done but hardware devices respond to it in different ways. My SH01A will likely just chop off a note but my Virus Snow (lets say, responding to midi program change on four channels) will likely drop notes, run off sync if any effects or arpeggiators are active, and audio might drop out because it likely takes a little longer to initially load a preset (or four at a time).

    I think in terms of a delay effects, its called spill; where feedback wont immediately cut out if you bypass it but not every hardware device that makes sound or processes sound has options for "spill". Synths especially don't do this.

    Triggering a midi program change on pattern play, even if only conditionally to trigger the first time the pattern plays but not on repeat, is still linking that action to the beginning of playback...which isn't always a smooth time to do that. Midi program changes are best sent at project load (and re-sent at double stop or return to zero if necessary) but not right at playback or on restart.

    I do feel like a discussion like this which is rare around here should have its own thread instead of being, well... offtopic.

    I definitely dont think this is off topic at all and all of the responses to this have been with sincere effort. The Maschine is very MPC informed and even the MPC60 has midi program change functionality. (Page 105 of the MPC60 user manual.)

    [edit: added clarification why the midi macros don't solve this problem]

  • D-One
    D-One Moderator Posts: 3,479 mod
    edited April 17

    I see, that was very informative, thanks for taking the time. A dedicated thread would help others facing the same challenges find it, discusses and possibly get some attention.. Up to you if you rather let this info be here where it might get buried under tons of other unrelated comments and/or closed eventually.

This discussion has been closed.
Back To Top