Support and discussion for all of Akai’s modern standalone MPCs including the MPC X / X SE, MPC Live 1, 2 & 3, MPC One / One+, MPC Key 37/61.
User avatar
By antic604 Thu Jul 30, 2020 7:17 am
When you're talking about "volume" do you mean MIDI track volume or Pragram track volume? I understand those are different things and if you plan on transitioning between sequences you should probably consider which one is it that you want to change. I learned - don't have my MPC yet :D - that when using Sequences in Song Mode MPC will continue using the Program that was on given track in 1st Sequence throughout the song.
User avatar
By Lampdog Sun Aug 02, 2020 5:36 pm
I have MPC X, if you want to, send me that project google drive/dropbox and I can troubleshoot with you.

Nothing wrong with your english, lol.
User avatar
By DeaDeus Wed Aug 05, 2020 2:42 pm
This normal behaviour - I am using the MPCX also in standalone only. Or the whole settings should be sent via MIDI dump - I am not aware that any hardware is doing so at the start of a track. It would most likely end anyway in MIDI jutter....

To overcome this issue you need to record the volume setting in your MPC.
Still, the fader WILL jump as soon as you touch it if you do not have an endless turn knob sensing the current setting or an auto-fader doing the same on your MIDI device.
Luckily, at least that is my experience, is the MPCX not sending this information again and again if the sequence loops - it used to to this, or it would reset every time when it restarts the sequence. I am running the latest update 2.8.1.

Maybe this helps a little.
User avatar
By Lampdog Wed Aug 05, 2020 5:40 pm
DeaDeus wrote:This normal behaviour - I am using the MPCX also in standalone only. Or the whole settings should be sent via MIDI dump - I am not aware that any hardware is doing so at the start of a track. It would most likely end anyway in MIDI jutter....

To overcome this issue you need to record the volume setting in your MPC.
Still, the fader WILL jump as soon as you touch it if you do not have an endless turn knob sensing the current setting or an auto-fader doing the same on your MIDI device.
Luckily, at least that is my experience, is the MPCX not sending this information again and again if the sequence loops - it used to to this, or it would reset every time when it restarts the sequence. I am running the latest update 2.8.1.

Maybe this helps a little.


This is EXACTLY the case, it's normal midi default behavior.
By idk973 Sun Aug 09, 2020 3:06 pm
Can Def live with this behavior, but I would like to have the possibility to "reset" the volume. If I compose with external midi gears, I have to record my track wathever the monitoring is set (in, auto, merge) but have to disable it if I mess with the different volume midi tracks. If like you say I record the volume into the mpcx, it set per sequences and can do roller-coaster levels from a sequence to another and no ability to avoid this. Even if I overdub the volume to 127 like lampdog suggest me, then my sequence will be go to 127 whatever I change the volume on my ext gear. The program volume does keep the level trough all the sequences. Not the midi.
User avatar
By Lampdog Sun Aug 09, 2020 4:18 pm
I have faders on my Kronos default configured for control surface maybe just like yours. I’ll try again.

I know EXACTLY what you did now!

You recorded both sequences at different faders volumes. You previously recorded them. Set both volumes on both sequences where you want. Do an overdub on that track, press stop after 1 second. Your volume is now recorded onto that track.

When you record you are also recording that volume setting, this is normal. If your volume is set before recording it’s not an automation and doesn’t show up as an automationin list edit.

It’s the ext midi volume we have been talking about this whole time. When playing back and moving through sequences that program midi volume page doesn’t actively update, you have to change pages and go back to see the volume change.

Solution, change your volume, record the volume setting simply by overdubbing for a 1 sec.

I just recreated your vid on my kronos faders, using 2 sequences, I changed volume on one of the sequences and recorded. I played both and yes, it happened just like your vid. It’s realtime vs recorded volume on the same fader. The fader will do whatever you tell it in realtime, it’s not permanent to track unless you record it. Seq always plays back at whatever level you recorded it at.
By idk973 Sun Aug 09, 2020 5:07 pm
This is it, but my wish is to change a volume midi sequence and that volume is set to all the sequences. Whatever where I'm changing it, just like a pad or program volume. Ex : my track 1 midi is recorded with a piano sound. Track 2 midi channel 2 I record a bass sound. Do a verse sequence, a chorus sequence and find my bass too loud. Move the midi fader let's say to 60, and wish my bass will be set to 60 in all the sequences. Are we agree we speak about the same thing?
User avatar
By Lampdog Sun Aug 09, 2020 7:13 pm
Initialized my kronos and x to hardware defaults and I changed nothing else.

Start new project.
Create a sequence using ext mid.
Copy that 1st sequence to 2nd seq.
On 2nd seq use ext fader to change midi volume before recording/overeub.
Stop playback.

Play through both sequences to see if volume changes.
I just did this and my volume between seqs stayed the same wherever I left the fader.

It works as you expected it to work.
By Plex Mon Aug 10, 2020 10:49 am
Bug 1: I found out that the MPC records volume information and doesn‘t show in the list editor but when I open the list editor from the piano roll editor they are all there and I can delete them.

Bug 2: MPC records volume data although I‘m not in recording mode.

I‘m still on 2.8 maybe 2.81 heals these bugs.
By idk973 Mon Aug 10, 2020 12:07 pm
Plex wrote:Bug 1: I found out that the MPC records volume information and doesn‘t show in the list editor but when I open the list editor from the piano roll editor they are all there and I can delete them.

Bug 2: MPC records volume data although I‘m not in recording mode.

I‘m still on 2.8 maybe 2.81 heals these bugs.

Yep, my only way to not record the volume information is to record my midi with monitoring off (and stay in local mode on, on the midi gear)
By himster Mon Dec 21, 2020 4:03 pm
I know this thread is old, but I thought I'd chime in. I use a Launchcontrol XL. Instead of mapping to programs, I map to submixes. Submixes also have inserts, and sends that I also map. This is saved in my default set with a couple of programs for drums etc. Then what I do is route audio from programs, or pads to the the submixes. My general approach is Sub1 - Kicks, Sub2 - Snares & Claps, Sub3 - Hats & shakers, Sub4- Percussion, Sub5 is Bass, and Subs 6-8 for other stuff.

This serves two purposes - it allows me to quickly route any audio out any mix. And I don't have to midi map every time I make a new program. So I can have long sets and never really worry about mapping.