MPC 3.4 Beta 3 - Bug Reports & Feedback Here

cocosushi wrote:agreed - but then you don't have to buy them?

It was a joke about the "free" OS not really being free.

sduck wrote:Still no time signatures besides 4/4. Major problem Akai is going to have to address eventually.

I'm not convinced it will get addressed. At least not soon. I would have said tempo automation was also a major issue and that didn't get addressed until 3.0.

Didn't someone already mentioned that it's already in the code? Or did I red it elsewhere.. I am 100% sure odds will be there

Legotron wrote:Didn't someone already mentioned that it's already in the code? Or did I red it elsewhere.. I am 100% sure odds will be there

I don't think so, I think you are referring to event track mutes, I believe these were in the code and had been temporarily removed, but no public mention of time signatures so far. But they are aware that it's an issue for many people.

Just upgraded to the latest beta, purchased and activated Air Delay Pro. Everytime I'm trying to add the effect, my MPC One+ crushes.

Just to clear up some confusion over the new 'Drum pads as stems' feature compared to 'explode tracks' and 'separate tracks'.

First it's worth noting that the term 'stems' is being used incorrectly, normally it's used to refer to a mixdown of an entire group of related tracks, such as the drum stem (a stereo mixdown which contains the hat, kick, snare and cymbals). A better word to use when referring to individual track exports is 'multis' or 'multitracks' - Conan explains this all better here: https://www.youtube.com/watch?v=9o9MsuWAvmg

'explode track' is fundamentally the same functionality as found in mpc2. So if you have a DRUM track with say, kick, hat and snare, you hit the pencil in MAIN and choose 'Explode Track'. This mutes the current track and gives you 3 new DRUM tracks, one for each pad. The difference compared to MPC2 is that, as we cannot have the same program on multiple tracks, it puts just the kick pad on the kick track and so on. It also puts pads in the same mute group on the same exploded track (e.g. open & closed hat).

The 'Separate tracks' feature in the 'Save > audio mixdown' screen (previously called 'Explode tracks') is referring to creating individual multi files for each track in the current sequence, so can work in tandem with 'explode track' above.

With the new 'Drum pads as stems' feature you can select your original sequencer track containing a mix of kick, hat, snare, go to 'Save > Drum pads as stems' and you'll get 3 multi files (kick, snare, hat etc),it will ignore all other tracks in your current sequence. So it's effectively a way of avoiding ever having to 'explode' the original sequencer track

It’s nice of them to reintroduce normal track mute functionality as a ‘new feature’… but now that they have incorporated it again, it would be nice if using the solo in the track mute page had the same functionality, with the other tracks playing through to the end of whatever sample they were on when the solo is activated. Much more natural. The fact you can now do multiple solos is great for live work, you can build up a track, then solo and rebuild the track differently, but the hard audio muting of the other tracks decreases its usefulness.

I'm on MPC One, the track group function on the Track Mute Screen seems to be mostly broken. Q-Links are very unresponsive. Selecting a track group for one pad/track also affects some or all of the other ones. I can't make much sense of it.

H-Mann wrote:I'm on MPC One, the track group function on the Track Mute Screen seems to be mostly broken. Q-Links are very unresponsive. Selecting a track group for one pad/track also affects some or all of the other ones. I can't make much sense of it.

Same here. Total erratic behavior.

Akai is taking us as hostages for an emotional rollercoaster for some and for others simply as free IT/QA beta testers. Ridiculous. This can't ev3n be called a beta it is a pre-beta.

Marcus123 wrote:Akai is taking us as hostages for an emotional rollercoaster for some and for others simply as free IT/QA beta testers. Ridiculous. This can't ev3n be called a beta it is a pre-beta.

Then don't use the beta and stick with the official release. No one is taking you hostage, stop being so dramatic.

In the past lot's of people have said Akai should do public betas, so here we are. Clearly they can do some things better, no doubt they'll improve the processes over time. The fact is without this 'pre-beta' we couldn't have pressured them into bringing back proper track mutes, and they at least know how many people are against the loss of assignable programs. Fingers crossed we'll see plenty more improvements before it goes to final release.

So, people willing to be free beta testers and help shape the future, enjoy the ride. It's not for everyone though, but that's what 2.15.1 is for.

MPC-Tutor wrote:

Marcus123 wrote:Akai is taking us as hostages for an emotional rollercoaster for some and for others simply as free IT/QA beta testers. Ridiculous. This can't ev3n be called a beta it is a pre-beta.

Then don't use the beta and stick with the official release. No one is taking you hostage, stop being so dramatic.

In the past lot's of people have said Akai should do public betas, so here we are. Clearly they can do some things better, no doubt they'll improve the processes over time. The fact is without this 'pre-beta' we couldn't have pressured them into bringing back proper track mutes, and they at least know how many people are against the loss of assignable programs. Fingers crossed we'll see plenty more improvements before it goes to final release.

So, people willing to be free beta testers and help shape the future, enjoy the ride. It's not for everyone though, but that's what 2.15.1 is for.

Yeah. I should have dropped a smiley or two cause I was half-joking All good. I prefer to stick with Beta because I am new to MPC.

Still, I think they are treating their loyal customers not so good. Take something from you, have you beg for it, then give it back... lol. Belongs to a soap opera I would say.

Because let's be honest, they are taking away things from it that were there before (this in my books equals to reducing features) e.g. time signature, clips, etc. and the ones structural they are NOT gonna change them no matter how hard users shout. Or does someone expect they will trash the whole development and start from scratch? They could share a roadmap at least.

As said, all good. I am taking this with humor as I don't have any attachment to the brand nor to 2.15 workflow. I am a new spectator.

Cheers!! And thanks for the wondeful forum btw

FreeBeat wrangles with the arranger - filmed in real time with no cuts nor shortcuts, hence giving an honest impression of what working with the arranger is like, which looks great to me !

As I suspected, named locators and loops make the one-sequence workflow very usable... For production. Live MPC is certainly another matter.

Hi everyone,
There is something I still don't understand with this Beta software. The tracks are common to all the sequences, but the data that is recorded on the tracks seem to be attached to the sequence. If I record something on track 1 in sequence A, the data recorded in that same track 1 will not appear if I move to sequence B. So, if I record something else on track 1 in sequence B, it won't overwrite the data in sequence A.
I am still a bit lost with this new organization... Can anyone shed some light on this? Meanwhile, I am going to watch a few more videos about MPC Beta 3 and see if I can understand more eventually.

FlashTheDog wrote:Hi everyone,
There is something I still don't understand with this Beta software. The tracks are common to all the sequences, but the data that is recorded on the tracks seem to be attached to the sequence. If I record something on track 1 in sequence A, the data recorded in that same track 1 will not appear if I move to sequence B. So, if I record something else on track 1 in sequence B, it won't overwrite the data in sequence A.
I am still a bit lost with this new organization... Can anyone shed some light on this? Meanwhile, I am going to watch a few more videos about MPC Beta 3 and see if I can understand more eventually.

I'm not sure what you're confused about. Are you trying to reference a pattern in sequence A from sequence B, like in Ableton? MPC cannot do that.