More MIDI MuRF improvements - you tell me how it should be

How should the MuRF handle MIDI Sync when you toggle from Bypass to Active?

  • Option 1 - don’t change anything about pattern sync while in bypass
  • Option 2 - keep locked on the beat but restart pattern at step 1 when toggle to Active
  • Option 3 - stay in MIDI clock sync but set a new downbeat the moment you switch to Active
0 voters

Hello again,

I am putting the finishing touches on a new firmware for MF-105M MIDI MuRF.

One thing I noticed is that if you are synchronized to MIDI clock and you put the pedal in Bypass,
when you come back from Bypass to Active mode there is a stutter in the clock sync.

This is easy to fix - in fact, I have fixed it. But there are several valid things the MuRF could do in this situation. I’d like to ask the user community (you, dear Reader) what would be best.

Basically there are three options:

1.) Keep pattern exactly in sync while in Bypass, so when you return to Active mode the pattern is on exactly the beat at exactly the pattern step it would have been if you had never gone into Bypass mode.
Essentially this is like slamming the mix to 100% dry, without any effect on pattern sync in the process.

2.) Keep pattern steps exactly on the same beat, but re-start the pattern on step 1 any time you switch from Bypass back to Active mode. This way the pattern never falls off-beat, and if you come out of Bypass a little early or late it won’t affect the rhythm – however, you re-start the pattern to the beginning on the next beat after switching to Active mode. This is a little bit like what happens on the MuRF when you are not in MIDI sync – any time you switch from Bypass to Active while on the internal clock, it restarts beat one of the pattern.

3.) Resynchronize everything the instant you switch from Bypass to Active (“set a new downbeat”) – this option is the most similar to how the MuRF behaves when not in MIDI Sync. The moment you switch into Active mode, you set the downbeat of pattern step one and everything is synchronized to that moment. This is also how MIDI Sync behaves when you have played any of the filters using MIDI notes, thus stopping the pattern clock, and you then press F above Middle C (Midi note 65) to restart the pattern. What happens then is that the very next MIDI clock received becomes “the downbeat,” and clock sync resumes counting from that moment.

The advantage to option 3 is that it creates a unified behavior; any time you switch from Bypass to Active you are setting a new downbeat at exactly that moment. Also, you can redefine the groove on the fly by using Bypass to change the phase of the pattern (relative to the rest of your arrangement). The disadvantage is that this could be too much power – it requires the player to punch out of bypass at exactly the moment they mean to, or it could throw off the groove.

Option 1 is the easiest to use live, because you can toggle in and out of Bypass all you want and it has no effect at all on pattern sync; if it was right to begin with, it stays right. But this is also the most limiting behavior, because if the timing isn’t right to begin with, you can’t fix it by hitting Bypass and then punching back in on the beat. With simplicity you have limitations.

So, what’ll it be? I understand it’s not the same to read about these options as it is to try them yourself, but I think the above descriptions sum it up pretty accurately.

If any MIDI MuRF users have access to a Windows computer (beta firmware updater is windows only) and want to try this stuff for yourselves, please let me know and I’ll be glad to send you an update.

Thanks very much,

Amos

#1 is a perfect application of K. I. S. S. :slight_smile:

When I come back it’s going to be tracking exactly the way it was when I left it.

Amos,
I voted 2 because I feel like it would give the user more control over the pattern. Ive found myself on the Voyager wishing that I had more control over things that were free running when they were not being heard. I’m a big fan of being able to have complete sweeps rather than jumping in where you have no idea where the sweep will be in relation to the up or down beat of the song. You might have a particular part of the sweep going on where theres a down beat and then if you went with your option 1, you might jump in and that part of the sweep is now on the up beat and it will throw off the continuity. I think this would be most relevant if you programmed your own pattern and wanted certain things happening at a certain time. Do you follow?


I can also say that its very hard to make a decision like this that is set in stone, only to find out down the road that you needed it to be a different way.


Eric

Thanks for asking.

Option 1: I usually have a mixer handy and can achieve that buy just dropping and bring back up the signal out of the murf

The other 2 add funtionality. If I’m understanding correctly, both options 2 and 3 can be achieved by animating the murf with an external sequencer. I have not got deep enough into my murf to start experimenting with external sequencing.

Anyone on here try animating their murf externally? I was thinking of just writing sequences to animate, instead of reprogramming the murf. It would be more predicable to use live, but I would loose the ability to program more random patterns like the factory prime length sequence.

Option 3 could be tough to work with live. I can see it making a simple task difficult. :unamused:

Amos, do what you like. This is a 3 way tie and even if 1 more person votes and breaks the tie, most voters won’t be happy. Democracy is an inefficient way to run a country away :smiley:

OK, cool – thanks everyone for your input. I went with option number one after extensive testing, because it was the most fun.
It’s the only option where you could be completely faced in a club and fall on the Bypass switch at a random moment without messing up the groove.
Both of the other options put a bit too much uncertainty into the process, such that you really have to “perform” a bypass-switching maneuver and get it right in order to keep the groove alive.
So, no worries + rock solid sync = fun.

Also, you can already obtain the functionality of both options 2 and 3, using MIDI notes.
If you already have a pattern in MIDI Sync and you play the F above middle C (MIDI note 65) then the pattern will restart on the next clock step.
If you play any of the Triggered or Sustained Filter MIDI notes (48-60 or 72-84) this stops the pattern, and if you then play MIDI note 65 it will snap back to MIDI sync with a new downbeat set at the instant you played the note.

So, everybody can be happy with this, I think.

Plus it means that the update is complete – a bit more testing and I will release a final version into the wild.

Cheers!

-Amos

I hate to be a nuisance, but it has been more than a month since this message. Any guess as to when the update will be available?