Moog Music Forum

hey guys

i created a M4L device to control the sub phatty.

i'm keen to hear your feedback on the device, so pls post up any suggestions

EDIT: check the later posts for latest version - removed old version

i'm using live 9.0.4 with Max 6.1 on OSX

KNOWN ISSUES
- when in shift mode amplifier attack sends midi cc28 instead of cc104. this will hopefully be addressed in a future version of the subphatty firmware.
- keyboard octave responds to midi cc89, but does not send out any midi cc data when changed via the buttons on the panel. this will hopefully be addressed in a future version of the subphatty firmware.
- the M4L device is unable to receive preset information when you press a preset button or "activate panel". the subphatty only sends presets as SYSEX data, not midi CC data at the moment. this will hopefully be addressed in a future version of the subphatty firmware.

I LOVE IT. Thanks for your work.

Please keep doing it. It will be awesome if you add more under-the-hood functions.

And, it might be great if PUSH can handle parameters. I can do that now, but it is not orderly arranged.

Thanks man again.

robml wrote: - the M4L device is unable to receive preset information when you press a preset button or "activate panel". the subphatty only sends presets as SYSEX data, not midi CC data at the moment. this will hopefully be addressed in a future version of the subphatty firmware.

Just for you, Rob.

New firmware, v1.3.3:
http://www.moogconnect.net/downloads/su ... _1_3_3.syx

To trigger sending all parameter values, send CC# 99 value 0, followed by CC#6 value 127.

bandmasta wrote: And, it might be great if PUSH can handle parameters. I can do that now, but it is not orderly arranged.

at the moment the various bits and pieces under the hood dont have proper variable names. i will sort it out before it comes out of beta.

cheers

Amos wrote:Just for you, Rob.

New firmware, v1.3.3:
http://www.moogconnect.net/downloads/su ... _1_3_3.syx

To trigger sending all parameter values, send CC# 99 value 0, followed by CC#6 value 127.

awesome! thanks amos

cheers

hey guys

here is beta 0.23
EDIT: removed old version, check latest posts for latest version

NEW FEATURES
"Get Current Parameters" button.

KNOWN PROBLEMS
Amos, would it be possible to add all the midi variables to be sent out? At the moment i am receiving 32 midi messages upon the trigger. It leaves off filter cutoff and a bunch of others. If we could get all of the documented midi cc values being sent out that would be fantastic! .

cheers

robml wrote: KNOWN PROBLEMS
Amos, would it be possible to add all the midi variables to be sent out? At the moment i am receiving 32 midi messages upon the trigger. It leaves off filter cutoff and a bunch of others. If we could get all of the documented midi cc values being sent out that would be fantastic! .

yeah, oops. It was supposed to be all the parameters. I didn't test very carefully; just saw that a bunch of data was coming out, declared victory and went home for the day.

try this version, seems to do the trick:
http://www.moogconnect.net/downloads/su ... _1_3_4.syx

cheers!

new firmware works good.(1.3.4)

If I ask you one more favor, it would be "get current parameters" for shift mode also.

It works well for the main panel, but I don't think it makes any changes for the shift mode.

Thanks for the awesome M4L.

edit) ooops. It is working... SORRY. NEVER MIND. Your M4L is amazing.

EDIT) I have a question. Why do I have to click "BLOCK MIDI IN" first in order to listen to the sound of Phatty?
Without clicking and re-clicking it, I cannot play any sound.

bandmasta wrote:Why do I have to click "BLOCK MIDI IN" first in order to listen to the sound of Phatty?
Without clicking and re-clicking it, I cannot play any sound.

that doesn't happen to me. i have updated it to version 0.24 with a solution that may fix it for you. pls let me know if it works for you.
edit: check latest posts for latest version

cheers

Amos wrote:yeah, oops. It was supposed to be all the parameters. I didn't test very carefully; just saw that a bunch of data was coming out, declared victory and went home for the day.

haha. thats awesome amos, thanks so much for all your time and helping out to make this M4L device truly usable tool

it was great to see all the knobs change so you can easily see all your current preset parameters.

will spend some time playing with it making some music and hopefully finalise it soon.

cheers

Everything is good now. Thanks.

I love your device.

bandmasta wrote:Everything is good now. Thanks.

I love your device.

no problem.

glad you like it

cheers

HI.

I have a question because Ableton is new to me.

I mapped few knobs from your Max device to Macro.

When I click the "Get Current Parameters", mapped knobs does not change. Is it normal?

Only un-mapped knobs responds to the "Get current parameters".

Thanks.

Amos wrote:

robml wrote: - the M4L device is unable to receive preset information when you press a preset button or "activate panel". the subphatty only sends presets as SYSEX data, not midi CC data at the moment. this will hopefully be addressed in a future version of the subphatty firmware.

Just for you, Rob.

New firmware, v1.3.3:
http://www.moogconnect.net/downloads/su ... _1_3_3.syx

To trigger sending all parameter values, send CC# 99 value 0, followed by CC#6 value 127.

Amos, please implement this behaviour for Minitaur FW too.

bandmasta wrote:HI.

I have a question because Ableton is new to me.

I mapped few knobs from your Max device to Macro.

When I click the "Get Current Parameters", mapped knobs does not change. Is it normal?

Only un-mapped knobs responds to the "Get current parameters".

Thanks.

when you map an ableton live knob to a macro, the macro then overrides all other controls over that ableton live knob. so its not only the "get current parameters" button that wont work for macro mapped ableton live knobs, you also wont be able to control that ableton live knob with the physcial knobs on the sub phatty. its just the way ableton live works. the macro is either controlling the ableton live knob or its not, there is no middle ground.

cheers