Problems automating the program based filter

Not sure if this is a bug or not so I made a topic instead of posting to the bugs thread.

I’ve got a drum program loaded up with some slices on each pad, already used the effect slots up but need to do a filter sweep for the first 16 bars, so I’m using the program level filters. I’ve selected the relevant pads via the multiple menu, and it’s working, I can play the pattern while sweeping the filter and it sounds as it should, and selecting a filter type affects all the selected pads too. But the damn thing won’t record as automation for some reason (I guess it would actually be 12 automations, one for each pad used).

So the question is, what am I doing wrong? Or is it a bug? Hoping some of you veterans may have some insight into this, maybe I’m expecting too much though it seems it should work.

Are you in automation write mode(right way)? Or are you trying to record automation by pressing the record button(wrong way)? Sounds like it would be easier using a plug-in on a submix channel anyways.

Yeah, I’m enabling the write mode to record the automation but it won’t actually write. I did think about using a submix channel but apparently they can’t be automated either. I guess what I’m trying to do is a rare use case though, I’m sure I’ll find another way round it.

Thanks for the input

enzyme wrote:Yeah, I’m enabling the write mode to record the automation but it won’t actually write. I did think about using a submix channel but apparently they can’t be automated either. I guess what I’m trying to do is a rare use case though, I’m sure I’ll find another way round it.

Thanks for the input

i swear i just did what your talking about the other day. Recorded filter sweep automation in the program level. Do you have data already there? I think that's what tripped me up.

Go to the grid view, expand the bottom panel thingy by tapping that little down arrow so your velocity info comes up. On the left if you double tap it will show the list of all the options you can view that have possible info. mine had an option for something like "prog:filter".

There will be a list of all the info you can see. If you tap on the "prog:filter" option (if its available) it will show what the filter levels over time are. I think my problem was there was already shit recorded there accidentally at like 78% and i kept trying to record the filter being around 58% so it didnt work. The solution was to tap the trash icon on the bottom left and delete the automation info for the filter. Now go thru those steps to record it you did before, making sure the automation icon is red etc

idk if i explained that well. I suck at typing my thoughts

You’ve explained it perfectly fine! I have already tried all that stuff though, I have a feeling that the auto write can only do one pad at a time (in my case, I’m trying to write to 12 pads at once).

I’ll dig a bit deeper today but I think maybe it’s not possible. Thanks for the input though!

It is not possible to use edit zone multi or all to record a filter sweep on all drums in a drum program at the same time.

Once again, the Force gives you options, the Force has macros so you could use macros to record several automations at the same time, or just use submixes with a filter effect on it and record that automation on the submix itself, the MPC line cannot do any of that.

I don't think there is even a way to copy paste automations from one drum sound to other drum sounds on the same track.

You can do automate a filter effect on the track itself but you need to free an effect slot.

The only work around would involve using a keygroup program instead of a drum program, and use a midi track to automate the after touch then send that information to the keygroup program controller mod aft>filter, the drum program doesn't have a controller mod.

So the MPC would need to either be able to automate multiple drums in the drum program at the same time, or get macro and submix automations like in the Force, or give the drum program and the keygroup program a proper modulation matrix, which is to this day shockingly basic.

Others have identified to problem but not the solution.

The problem is that you can't automate mutiple pads simultaneously.

The solution is to add a filter effect on the program itself (not the individual pads, not a submix) and to automate that.

"It is not possible to use edit zone multi or all to record a filter sweep on all drums in a drum program at the same time."

this part is true.. when it comes to the q-links..
but you CAN use an external midi controller to midi-learn one knob/fader to multiple pads and it will record all automations at once.

though.. in the time it takes to map all those learns... you could also just bounce all the pads you want to filter sweep down to a single sample instead.

jamos wrote:Others have identified to problem but not the solution.

The problem is that you can't automate mutiple pads simultaneously.

The solution is to add a filter effect on the program itself (not the individual pads, not a submix) and to automate that.

If you read the OP, you'll notice that they said that all the 4 effect slots are already taken, so this isn't the solution to the OP's problem either.

already used the effect slots up but need to do a filter sweep

AKAI really needs to bring the MPC sequencer up to the level of the Force sequencer, there is no justifications for these differences (submix/return/master automations), especially when MPC Software (the alleged DAW) has the same limitations.

Thanks for all the input guys! There are some clear limitations in the mpc but I don’t care so long as there is a way to get the job done, the workflows good. (a proper mod matrix for the sampler would be great though, amongst other things). I’ve tried again today and found I can only automate one pad at a time. There’s an issue with using a track filter plugin, and that’s because on/off for the fx slot can’t be automated, and all the filter plugins colour the sound slightly even at default settings, plus, I’ve already used up the slots in this case.

But there’s a rough and ready solution, I just recorded the first 16 bars of drums then put that sample on a pad to be automated. Actually, I’m not sure why I didn’t already do that, I’ve had to do it before but forgot

Yes! There Multiple Workarounds for every situation on the MPC. We have to understand that the Standalone MPC is NOT a full fledged DAW. Sh*t even the Software isn't Full Fledged

I’ve only ever used the software to make keygroup programs, but yeah the full blown DAW experience isn’t to be found with the mpc. The lines are definitely blurring though.

Again, thanks to everyone for the input, I wasn’t sure if it was a bug or a limitation

No worries, it’s a weird use case, doesn’t seem to have been thought about by the developers.