When you see volumes at wrong levels from playback - is this from playing back the recording from the start time ("full rewind" ) and letting the MIDI track(s) play without interruption to the end? I ask because fast forwarding skips over MIDI messages which may be changing volumes (among other things). Event chase is what is used to keep track of those messages so they are restored after changing song positions. Maybe this isn't the issue you're experiencing at all - but if it is:
https://www.yamahasynth.com/ask-a-question/program-change-in-daw-resetting-volume-on-midi-tracks

Goes into more detail.

And then if you want to stop the DAW from recording various level related messages - you could filter out the DAW's recording of CC7 altogether. I'm not sure that's what you're after even though it best answers your question as asked.

Or, alternatively, use Zone control to avoid sending the Vol/Exp from MODX in the first place. Overall it's less setup to do this on the DAW side if that's your goal - but you have options.

Reading around the posts and links above...

Is it possible that Volume is not being directly controlled by CC7 (hence the reason it can't be found and stopped). Rather.... the Volume is being influenced by some other setting... perhaps an Assign Control Offset, or other indirect configuration that alters "perceived" volume (for example Filter Cutoff, but there are actually a lot of "indirect" mechanisms on the MODX/Montage).

It's always possible. However, if you have a problem when "jumping" to positions within your MIDI recording then the issue is in some way related to events preceding the "jump" not being issued to the keyboard and thereby putting the keyboard in an invalid/wrong state for the given playback position.

A good first step is to get a handle on what is causing the behavior to begin with then work on a strategy to address.

If this is related to event chase then the same kind of problem occurs with all MIDI devices. The more event possibilities you have - the more things will get off the tracks but still the same general issue.

CC's have all been deleted (by me).

To try stop this madness, ALL of the CC communication has been scrubbed. Hence the question.

This is infuriating when editing MIDI notes.

Sometimes when looping, volume of part "resets" (much higher).

Almost always when moving the playhead back (not all the way to beginning), volume "resets" (much higher).

Have checked and eliminated all obvious possible causes of this behaviour.

This has occurred spasmodically for two years across multiple computers, operating systems and DAWS, but it is not consistent.

It feels like sometimes a value is being stored somewhere hidden, and sometimes it isn't.

Well, this kind of thing would happen on any DAW and any equipment due to the serial nature of MIDI. When you "jump" to a location in the MIDI data (skip past some MIDI data) - your device will not had all of the context that preceded and will "play" something possibly unintended.

It's easy to imagine for PC (program change) that was common in GM MIDI files. Say a GM file uses more than 16 instruments. Then one channel will have to have more than one sound - changed with a PC message.

MIDI CH 1: PC=1 (initial value) ---- intro --- later, chorus PC=50 (sound change) --- even later outro PC=100 --- later song ends

So if you call up this file - then MIDI CH1 may be initialized with PC=1. If you skip to say the last 2 measures past the start of the outro - the tune will have the wrong instrument sounding (still PC=1 because it "missed" the PC=100 event). And maybe the instrument in the outro are effects mapped to "strange" keys and sounds like garbage with the PC=1 sound. And anywhere if you do not skip to right before the PC change - then you'll possibly have the wrong PC when you skip.

This is just a "how it works" kind of thing -- and has been a Part of MIDI since the beginning of mildly complex arrangements. Certainly before combining multiple channels for a single multi-channel instrument. There are strategies to deal with this - because no one wants to have to do things in "real time" - playing from the beginning until some "skip point". Not even by cranking up the tempo to "fast forward" while still maintaining all events. DAWs and keyboards have features to manage this and one description of the solution is "event chase".

Looping is its own thing. Depends on what's doing the looping and what that loop controller feels like it should or should not do at the top of the loop. I think what you (plural) want out of the loop machine depends on any given moment. It's not one size fits all although various devices/software take one stance and stick to it (and some have options as to how to "reset" or not). I'm pretty much ignoring "looping" because that's another topic. The pattern sequencer, for example, has a stance on this. There are other threads for this and I'm taking the easy way out yielding. Plus since the focus here is a DAW - I'm (conveniently) avoiding straying.

Scrubbing CCs isn't really how I'd deal with this. If what this means is removing CCs from the MIDI track data recorded in the DAW. Maybe experimentally to try to figure things out. But I think those are all best left in to leave the playback in-tact as recorded. Of course manufacturing a shorter say 4 measure phrase that exhibits all the same problems would be easier to knock around than something more complex. Single channel ... Monophonic ... building limited CC gestures in a "controlled" fashion. Leveraging some from knowing the serial nature of MIDI and how messages spill out. I know this is probably what you're doing.

How do I stop it from occurring?

I'd explore

Go to Cubase > Preferences > MIDI > setup the items you want the program to “chase”.

https://steinberg.help/cubase_pro_artist/v9/en/cubase_nuendo/topics/playback/playback_chase_c.html
... or similar for your DAW.

Even so, event chasing isn't complete. Take Sysex.

Say near the end of the MIDI track (with all 16 channels recorded) Part 1 has all of its Part-level assignable knobs turned to 127 (full CW). And say at the beginning of the recording, all of Part 1's assignable knobs were set to 64 (the "middle" 12 o'clock position). Say right at the 15 second mark Part 2's assignable knob number 1 is turned all the way CCW to 0.

... so at the end of the playback with everything in sync and no problems Part 1 has all knobs to 127 (full CW). Then you jump to the 15.2 second position (right after Part 2's assignable knob was changed - which sends Sysex out). Assuming you chase Sysex what will happen from this jump is Sysex chasing will set Part 2's assignable knob number 1 because "chasing" will say to backup until it finds the last Sysex and send that out. What doesn't happen is Part 1's assignable knobs are not set back to 64 (as they should be) because Sysex chasing doesn't go that far back. The assumption is that the last message before the "jumped" position is good enough of a chase.

When I'm trying to figure out what's going on - I break out a MIDI monitor and take a look at what's happening on the bus. This can be complex if there's too much going on which is why constructing scaled back contrived cases for education works well.

There is nothing to stop chasing, there is nothing to further scale back.

Record a part (not in part one) with nothing but note data and perhaps sustain pedal usage.

Swap the Part out for another using the MODX/Montage controls.

Start Playback in DAW, start experimenting with Part Volume to get it to where you’d like… imagine this is about 50% (low 60’s).

Press stop in DAW… volume of this part resets to 127. Press Play in DAW, volume “resets” to something a bit less than 127.

Whatever value you set to the volume of the Part on the MODX/Montage is lost, but the little blue arrow shows you where it was set.

As I say… is there some value that’s somewhere being created or stored and then triggered by the DAW that could be doing this, from the initial recording? What is going on?

I can’t find it in any of the CC lanes/values for this Part/Track.

For an example this simple, it should “just work” and I shouldn’t need a manual and to tear my hair out, let alone a MIDI monitor. Two years of this, and many others commenting about similar volume control issues with the MODX and Montage with multiple DAWS.

What could be doing this?

How do I prevent it from happening now, in this most basic of examples, and stop it from ever happening again?

Check reset on stop in the DAW under MIDI preferences.

Stops hanging notes only.

What could be making volume (Part) control changes?

Post a small MIDI file say intended to work with "CFX Stage" (1-Part) with the issue and I'll look at it. I've got Cubase 9 up at the moment but should be fine.

Where/what is the part volume control CC that could be sent to and recorded by a DAW?

Am using Reaper, because Cubase license server has shat itself, AGAIN!