Hello,
I just bought the mf-104m. I am extremely happy, the sound is great, huge possibilities… I can’s stop playing with!
Therefore I have two issues:
The first is that I do not understand what is MSB-LSB and How can we send that value with a standard midi device.
The second issue is a real problem. When I send tap tempo with a midi device, there are often sharp artifacts that are created. I feel that the device sends close subseqent CC#114, which creates this. I experienced the problem with two device: axiom pro 25 and a pedal FCB1010.
On the 104M, you use the MSB (CC#12) whether 7-bit (values 0..127) or 14-bit (0..16383). The Midi standard dictates that there is a 32 offset between so despite the fact that you are configuring #12 for use, if your DAW or keyboard is set for 14 bit, it will automatically know to send the rest of the message to LSB. Have a look here http://www.midi.org/techspecs/midimessages.php and scroll down to Table 3 for more information.
Worthwhile to add that on the 104M, the range switch is a ‘hard’ switch and the full range of CC for the TIME parameter applies to each separately (if you want to set a maximum [normal] delay value, 127 (or 16384) won’t do it unless the panel switch is toggled or you toggle CC#86 appropriately.) See explanation below for ‘lo fi’ aka not the ‘normal’
Answer to your second question is as follows.
When the TIME CC’s or TIME knob on the panel are used, the range of the BBD clocking will only stay within the normal audio range. But if you use Midi clock, or if you Tap (via CC) a TIME, you will descend into the land of low-fi. (also via Midi note on). In the Midi clock use case, it really MUST provide this functionality otherwise it wouldn’t exactly be sync. It’s really useful that Moog Engineers implemented it in this fashion; but if you are striving for highest quality delay sounds, you must be aware.
Your next question might be “why Tap Tempo ‘A’ and Tap Tempo ‘B’” and the answer is that some Midi devices, in particular some of the ‘stomp box’ foot pedals (and even the MP-201 in the proper configuration), will send a 0 for switch up and a 64 for switch down. So stepping on the button/switch might send 64,0,64,0,64,0 in the case of 3 taps.
Other devices (my Novation SL 25 MK2 for instance) only sends the desired byte when pressed. So I would use CC#114; tapping 3 times would yield whatever value I configured so 16,16,16 (if that was configured). The manual says “any value” so the 104M doesn’t care.
Great question… having just bought some Moog gear recently I have been doing some serious reading about MIDI over the past 5-6 weeks, but just could not find it written anywhere to satisfy my pedantic curiousity like this…
Thanks a lot for the answer.
I understand a bit more about the msb lsb-but I must search by myself before asking more specific questions.
About the tap tempo, my artifact problem is not resolved by switching to CC # 125. Is it because of lo-fi problem (ie msb-lsb)?
To clarify I recorded my problem: 4 tap tempo: 1 and 2 with the mf switch, 3 and 4 with a midi switch.