Settings, Advanced, Modulation, both Velocity and Aftertouch have issues.
Issue #1:
No MIDI from Model D to Logic Pro 11.2.2 except when both Velocity and Aftertouch are set to OFF in the Advanced Modulation settings.
Issue #2:
Stand-alone or in Logic Pro 11.2.2, the 100% settings of both Velocity and Aftertouch are not editable.
Issue #3:
I’m using the AuV3 version of the plugin and both Velocity and Aftertouch have limited options when Model D is used within Logic Pro 11.2.2. For example, Aftertouch only lists: OFF or LOUDNESS within the DAW. In stand-alone mode, the Aftertouch drop-down lists: OFF, LOUDNESS, FILTER, OSCILLATOR, MOD SRC.
Has anyone found a way to use these Modulation features in the Minimoog Model D AuV3 plugin?
ADDENDUM: I did find the wrappers. My initial search came up with a site I didn’t recognize as a Moog site, so I wasn’t about to install software from an unknown site. Now I’m off to see if the VST3 wrapper works any better than the AUV3 plugin.
In my original message, it was implied I’m using the Model D plugin on a Mac when I mentioned Logic Pro 11.2.2. I should have been more clear about that up front.
PER ISSUE #1:
Using the VST3 wrapper, I now get MIDI input to the DAW when selecting SETTINGS, ADVANCED, MODULATION, VELOCITY and/or AFTERTOUCH, LOUDNESS.
PER ISSUE #2:
The 100% is still not editable in SETTINGS, ADVANCED, MODULATION, VELOCITY and AFTERTOUCH.
PER ISSUE #3:
The dropdown lists in SETTINGS, ADVANCED, MODULATION, VELOCITY and AFTERTOUCH, still don’t display all the choices shown when the Model D is run in stand-alone mode.
I need the DAW for the virtual instruments and recording capabilities, so the stand-alone mode is of no help, presently, other than to see (but not hear) what the plugin should be doing.
I would run the app out of the desktop or standalone as you call it, and then thru a virtual cable to the daw. It sounds like your issue is the mogulation is not picking up because there is some interference from the DAW taking in the MIDI. Well what are you using it for? Because if it’s just audio you want you could run the app as a standalone then pick up the audio in the DAW and just record that.
It’s what I do running the Model D externally. Of course I don’t really record the MIDI exactly but I do record it to MIDI tracks. I would think if I was going to try for the same sound again that the best way would be re route the MIDI back out to the externally kept Model D and just pick up the audio wherever I wanted it at.
Why the need to keep the app inside the actual DAW? Can’t you treat it as an external piece of hardware? I actually run my Model D thru the 3.5mm into the interface and just always keep an audio track for recording it in the DAW. Hooks up with MIDI from bluetooth really well because it’s on Apple and their bluetooth is good. I would think also that they have good sort of virtual audio ins in their OS. I don’t and haven’t used Mac but that’s what I’ve heard about it.
I’ve been using the Model D regularly for a number of years and have yet to encounter the problems you did as far as unmovable AT and Vel sliders set always to 100%. Have just upgraded my installation.
Just an idea, I don’t know if I can upload files here, but I could shoot you over a bank of presets I’ve made and you could see if the AT and Vel readings come up as they should as I have many of them set to around 10% because the AT to osc setting goes way too far when set to 100 as you I am sure know.
