You can adjust the volumes using the screen, just not with the sliders.

This is a result of local control being off in the MIDI rec quick setup option. The sliders generate midi messages, and if your DAW isn't sending those messages back then it's as if they were never moved.

Depending on your DAW, one option is to turn off "input monitoring" or the like, and enable local control on the MODX. If you don't turn off "input monitoring" or the like, however, then your notes will be doubled up and you'll hear a phasing effect from the slight delay between the initial note and its "echo".

Cheers, Brian.

What you've described is the workaround I'm using to have control of volumens.

However, how do I record those changes?

Being in "Standalone" mode (or having turned on local control) isn't helping to record these volume changes, nor to get them to be played back when the recorded MIDI on the DAW is playing back.

That's an issue with the settings in your DAW. REAPER, for example, records the CC changes by default, so it just works on playback.

Which DAW are you using?

For what you're trying to do - what is the role of the DAW? Hosting VST Instrument(s)? Hosting Instruments + Recording MODX's own MIDI (for MODX sounds too)? Or just a recorder of what MODX is playing (and you want the sliders, etc to work)?

... BTW: tutorials suggest enabling "MIDI Thru" (Cubasis's nomenclature - may vary in your DAW) on your DAW's MIDI track. This is what would be responsible for taking the MIDI messages transmitted from moving sliders and routing them back to MODX.

How to configure MODX with a DAW so the part volume controls still work whilst recording MIDI to a DAW?

Putting MODX into MIDI rec mode, the part volumes are frozen.

Anytime your Part Volumes are frozen, it means simply, you are NOT communicating with that Part.

Local Control = Off disconnects the Keyboard (including its controllers and sliders) from the Tone Generator. You must complete the Routing circuit through the DAW MIDI Track.

Think of a frozen Slider or frozen Super Knob, or frozen Assign Knob, the same as you would a Part not sounding when you play the keys... it’s because Local is Off, you must either complete the Routing through an active MIDI Track or activate Local Control (On).

When Local is Off, you must *select* a MIDI Track that is routed to the specific Part you want to sound. You know this... it is also true for Controllers including the Sliders.

In your DAW, you could *select* all the MIDI Tracks you wish to control with the Sliders. Yes, you can select multiple MIDI Tracks.
Each MIDI Track should be set to receive and echo Thru its MIDI Channel.

But there are certainly more flexible, creative, and elegant ways to record volume changes to your mix. This can vary DAW to DAW.

Since no specific DAW is mentioned, we’ll just use Cubase as an example of a world class powerful DAW.
You can record cc7 directly into the MIDI Track (old style)
However, many prefer to record this type of mix automation to its own separate Automation Lane... this gives specific advantages in how it is applied, copied, etc. you can easily cut and paste automation, you can Mute it separate from your musical performance, etc., etc., etc.

Some of these things become very important on larger projects...

You can use the MODX/MONTAGE’s DAW REMOTE layer to create your mix automation. This is far more elegant than attempting to route cc numbers. Using USB Port 2 as the Remote Control Surface communication bus, you can have a Slider for each of your DAW Tracks (both MIDI and Audio Tracks) — they show up in your MODX/MONTAGE screen named, each with a Slider.

You can use the R/W (Read/Write) function on the Cubase “Mixing Console” to document your automation moves. The Write function is used in place of RECORD.
Once you start creating your mixes this way it becomes compelling because you can easily work with your automation in the DAW.

EXTRA CREDIT
We’ll mention here that added in a recent firmware update is the ability to Overdub Controller changes in real-time. Say you did a fade in of an instrument while performing, but on playback you wish you had slowed down the fade in... you can put the Internal Sequencer in OVERDUB Record... instead of adding new notes, if you move a Controller, the sequencer will begin to reWrite (update) that controller movement... and just the controllers you engage, from the moment you engage them, replacing the previous data.