MFM2: Seperate feedback for each channel?
- KVRAF
- 6208 posts since 25 Dec, 2004
Hi there, just bought the MFM2, and as there is no manual (and i'm possibly blind), i thought i'd ask if there were any way of adjusting the delay feedback of each channel seperately?
All i see is the one big 'master' feedback knob at the top...
Simon
All i see is the one big 'master' feedback knob at the top...
Simon
sketches... http://soundcloud.com/onesnzeros
some artists i support... https://bandcamp.com/spectraselecta
some artists i support... https://bandcamp.com/spectraselecta
- u-he
- 30248 posts since 8 Aug, 2002 from Berlin
Click on the top of the center circle, where it says "Four mono"... in the drop down menu select "User Matrix". There you have feedback for each line into itself - and into every other line. That's basically the thing that's in MFM1, but MFM2 has those simplified matrices for quick'n'dirty delay creation...
- KVRAF
- Topic Starter
- 6208 posts since 25 Dec, 2004
...you're a champion Urs!
This is a very powerful unit, scratching the surface is proving to be an enlightening experience! Feedback indeed!
One thing though, when i use the plugin 'wrapped' with my Novation ReMOTE Zero SL (in Automap Mode), i cant map the delay sync times and almost anything that has a dropdown box...
One thing is for sure, learning MFM2 to a MIDI controller brings HOURS of fun!
Thanks Again!!
Simon
This is a very powerful unit, scratching the surface is proving to be an enlightening experience! Feedback indeed!
One thing though, when i use the plugin 'wrapped' with my Novation ReMOTE Zero SL (in Automap Mode), i cant map the delay sync times and almost anything that has a dropdown box...
One thing is for sure, learning MFM2 to a MIDI controller brings HOURS of fun!
Thanks Again!!
Simon
sketches... http://soundcloud.com/onesnzeros
some artists i support... https://bandcamp.com/spectraselecta
some artists i support... https://bandcamp.com/spectraselecta
- u-he
- 30248 posts since 8 Aug, 2002 from Berlin
Thanks Simon!
Actually, I've started to not make all parameters available for automation in my plugins because there are just too many... you can still MidiLearn them to normal Midi Control Changes though...
Have fun,
Urs
Actually, I've started to not make all parameters available for automation in my plugins because there are just too many... you can still MidiLearn them to normal Midi Control Changes though...
Have fun,
-
- KVRian
- 864 posts since 4 Apr, 2001 from Finland
Urs, would you have to do much manual work for that?
I believe that these context-sesitive controller mapping things (such as Novation Automap and Cakewalks ACT) need that the parameters are automatable.
They are really handy because they automatically recall correct mapping for whichever plugin is selected.
Ratio is(are) the parameter I think is not automatable in MFM2 and would be really useful to automate for drastic changes in sound.
I believe that these context-sesitive controller mapping things (such as Novation Automap and Cakewalks ACT) need that the parameters are automatable.
They are really handy because they automatically recall correct mapping for whichever plugin is selected.
Ratio is(are) the parameter I think is not automatable in MFM2 and would be really useful to automate for drastic changes in sound.
- KVRAF
- Topic Starter
- 6208 posts since 25 Dec, 2004
^
Amen
Amen
sketches... http://soundcloud.com/onesnzeros
some artists i support... https://bandcamp.com/spectraselecta
some artists i support... https://bandcamp.com/spectraselecta
-
- KVRAF
- 2752 posts since 15 Apr, 2004 from Capital City, UK
Urs, I can understand why the above lads want the old automation in MFM2, though my needs aren't as urgent. Would you consider (at this late stage of production) a cross between the Performance pads from Zebra2 and the PluginParameters from PlogueVST?
128 parameters made available to the host, which can be assigned to any MFM2 parameter via a 'patch' panel.
Yeah, I know, I should have mentioned it earlier.. Is it particularly unfeasible?
128 parameters made available to the host, which can be assigned to any MFM2 parameter via a 'patch' panel.
Yeah, I know, I should have mentioned it earlier.. Is it particularly unfeasible?
