MPC Essentials as a plugin - the good, and some needs

Sorry for the length ahead of time...

Okay, so I spent some time digging into this today. Have to say that there is definitely some potential here, but a few things are really puzzling me about the implementation and execution of actually using it as a plugin. None of this really applied to using the software standalone. I won't be using it that way, so haven't even tried to run it that way.

I'm using Logic Pro X as the host, and am starting with a 20 track, 13 sequence song composed in the MPC Software (I use a MPC Studio). So my goal is load 20 instances of Essentials, so that I can completely mix the song in Logic. For those of you unfamiliar with my complaints about the MPC Software, it's that there aren't enough virtual outs. I was thinking that Essentials could potentially compensate and allow similar capability.

So here's my list of the good and the needs of using it in this fashion. Btw, intentionally not saying "bad", as I don't believe anything is bad - just in need of some attention from Akai.

Good:
1. In each Essentials instance I loaded the MPC project. As the FAQs say, I was presented with a pick list for me to specify which track of the project I wanted to load in the Essentials instance. Definitely cool (but more on this in the not so good).

2. On a macbook pro, 8gb ram, I was able to load 20 Essentials instances in Logic, and map each one to the appropriate track, and play it with no memory issues. Each track is not jam-packed with activity, so maybe this helped. If it were 20 dense tracks, not sure if it would perform the same or not.

3. Each Essentials instance could be set for Song Mode, allowing the whole track to play using the Logic transport. This worked really well.

4. As expected, I was able to apply my Logic-based plugins for dynamics, effects, etc. Great to have this mix control from the DAW.

So now the needs, as in, this just needs an enhancement...

Needs
1. When loading an instance of Essentials I navigated to my MPC project. As I mentioned above, I can select the track to load for the Essentials instance. The problem with this is that I you have to select which track to load for each sequence in the project. Remember, I have 13 sequences in this project. In my projects, I use sequencing for song parts, so everyone track in each sequence has the same instrument. So for each Essentials instances, I have to select the track to load 13 times. Multiply that by 20 tracks, and that's a LOT of mouse clicks. I could always merge my sequences into one long sequence, but I shouldn't have to do that. ENHANCEMENT REQUEST - allow me to select once, and click a checkbox that applies that selection for all remaining sequences for that track.

2. I have mute groups across tracks - think of it this way - track 1 is a hihat, track 2 is an open hihat. Mute groups ensure they cut each other off. These mute groups didn't work across Essentials instances. The workaround would be to ensure all mute group sounds are on the same track. But that's not always realistic. ENHANCEMENT REQUEST - allow mute groups to work across instances.

3. Each Essentials instance loads every sample that the original project used. Even though I didn't experience memory issues, does this cause each Essentials instance to be unnecessarily "heavy"? ENHANCEMENT REQUEST - only load the samples that are needed for that instances. Again, architecture, not sure if this is possible.

4. Per the manual, you have to save your work in the Essentials plugin, as well as in the host software. I tried that a couple times... set one Essentials instance, saved from the plugin, saved from Logic, quit Logic, reloaded, everything worked fine. Added a second Essentials instance, saved in Essentials, saved in Logic, quit, reopened, and only the first track played. The second Essentials instance was present on the track, but nothing loaded in it. Perhaps it was user error, and I'll do more experimenting tonight.

All in all, promising. But still no replacement for more virtual outs in the flagship software!

I haven't tried the essential software yet, but that's surely a great review!

Must have been sleep......is the Essentials software available for download yet?

JAH wrote:Must have been sleep......is the Essentials software available for download yet?

Yep, http://www.akaipro.com/essentials

Eyalc wrote:All in all, promising. But still no replacement for more virtual outs in the flagship software!

^^^^^ THIS! ^^^^^

Regardless, great write up Eyalc and thank you.

You're welcome.

And just to revisit the needs,#1 and #4, after more time spent last night.

#1 - this one has proven quite annoying. The only way to reasonably use it is to convert to one sequence. But that's not how I work. This definitely needs an enhancement for it to be useful. I'm surprised no one caught this during beta testing - clearly no one tried to do what I'm doing. LOL. A fix for this would probably take less than an hour and maybe 10 lines of code (if the design was good). So if this was caught, I have to imagine it would have been improved with a quickness. And yes, I'm a software developer too. Until then, I can't see myself going through an hour of set up each time I want to mix a track (some of my stuff is 30 tracks, 15 sequences). Might as well export to audio - which is not always desirable either.

#4, for some reason, I can't get this to work reliably / consistently. I've tried different save orders (save in plugin, save in Logic; or save in Logic, save in plugin). This morning I realized I never thought about it, but perhaps the save always have to be done from within the FIRST Essentials instance. I had been saving from the current instance open. Guess I'll try that later today. But my question is this... When I load other plugins that load samples, I only have to save from Logic... why do I even HAVE to save in the Essentials instance??? So my ENHANCEMENT REQUEST - redesign so that I only have to save from my DAW, and every plugin instance is recalled automatically, including samples loaded, when I reopen the DAW project. Having to save in two places is counter-intuitive to using as a plugin in a DAW.

My updated feeling is that this wasn't designed to use as a plugin from the ground up, which isn't unexpected. But somewhere along the way that capability was added, but requires work arounds to accomplish the basics (#4). I can imagine its usefulness as a standalone, but as a plugin, it's not quite there yet.

^ yeah, at that point you might as well use battery or some similar thing.

im surprised the files that need to be loaded and the ability to load those files can not be done by the vst wrapper.

thanks for the review. I was thinking of getting the element but I think i might just go for the Studio instead. If using the element with a DAW is going to require me to write tracks in a linear fashion then i don't see the point. I want to work with chaining pattern sequences together. Am correct to think that the element does not allow this when using it with a DAW?? I am trying to understand if each instance can be sequenced in song mode via the mpc software.

Thanks in advance

In Pro Tools 10, I only need to save the Pro Tools 10 project. Upon reloading, the MPC Essentials plugin loads up on all 6 tracks I used to include the samples within the plugin.

As far as Loop based and Linear recording in DAWs...you are not forced either way...you are only limited by your imagination and creativity. In A DAW, you can easily create multiple 4-8 bar loops and later rearrange them as you see fit.

My suggestion would be to get the Studio. If I'm understanding correctly...

Studio = use MPC or Essentials software

Element = use Essentials software

The only way to unlock the flagship software is with a Studio or Ren. So getting the Studio is more $, but you can use either software.

Regarding linear sequences, it does allow chaining together sequences. My only gripe is that I have to select the same track to load for each sequence. I get it if your track order is mixed between sequences, but I can't imagine anyone working that way if it's all one song. Multiple songs strung together as a sequence - sure, makes sense. So, logically, if you use sequences as sections of one song (ie, a MPC project is one song), your track order would be the same between sequences, but you still have to select the track to load for each sequence in your project. Just a time consuming process that is unnecessary.

But once loaded, put Essentials in Song mode, and the entire song plays fine from the DAW. Hope this helps.

JAH wrote:In Pro Tools 10, I only need to save the Pro Tools 10 project. Upon reloading, the MPC Essentials plugin loads up on all 6 tracks I used to include the samples within the plugin.

Interesting, because even the Essentials docs say you have to save in the plugin as well.

I tried again in Logic. Loaded a couple instances of Essentials. Saved my Logic project, quit, reopened, and nothing was saved in the Essentials instances.

Not sure what else to do. Will have to table Essentials and move on to some tasks that make $$$.

Eyalc wrote:My suggestion would be to get the Studio. If I'm understanding correctly...

Studio = use MPC or Essentials software

Element = use Essentials software

The only way to unlock the flagship software is with a Studio or Ren. So getting the Studio is more $, but you can use either software.

Regarding linear sequences, it does allow chaining together sequences. My only gripe is that I have to select the same track to load for each sequence. I get it if your track order is mixed between sequences, but I can't imagine anyone working that way. So, logically, your track order would be the same between sequences, but yet you still have to select the track to load for each sequence in your project. Just a time consuming process that is unnecessary.

But once loaded, put Essentials in Song mode, and the entire song plays fine from the DAW. Hope this helps.

Thanks. my problem is that i want to use two vst intruments for my songs. If i use Essentials with Logic pro, i guess i would need two instances open in Logic. Now I am just wondering if i can make 4 sequences just with the two mpc instances seemlessly in sync together? I hope my question makes sense. I am tryin to save money by getting essentials but if its gonna be a headache then i will just save for the Studio.

Thanks again

Have to admit, not entirely following...

But you can open as many instances as you want.

And regarding what you're describing, if I'm understanding, yes, I think you'd be able to accomplish what you need.

Still recommend getting the studio over the element though, then you'll have access to both. But $$$ - I get it. Do what you can. But saving for the Studio will give you more flexibility.

But I don't think either are particularly well-suited for plugin mode honestly. Though they are functional. My .02

Eyalc wrote:Have to admit, not entirely following...

But you can open as many instances as you want.

And regarding what you're describing, if I'm understanding, yes, I think you'd be able to accomplish what you need.

Still recommend getting the studio over the element though, then you'll have access to both. But $$$ - I get it. Do what you can. But saving for the Studio will give you more flexibility.

But I don't think either are particularly well-suited for plugin mode honestly. Though they are functional. My .02

does it not wok well when using vst intruments on a track in the mpc software?

Eyalc wrote:

JAH wrote:In Pro Tools 10, I only need to save the Pro Tools 10 project. Upon reloading, the MPC Essentials plugin loads up on all 6 tracks I used to include the samples within the plugin.

Interesting, because even the Essentials docs say you have to save in the plugin as well.

I tried again in Logic. Loaded a couple instances of Essentials. Saved my Logic project, quit, reopened, and nothing was saved in the Essentials instances.

Not sure what else to do. Will have to table Essentials and move on to some tasks that make $$$.

Probably because it will work better in some DAWs more than others...and following the doc will ensure it loads perfectly across all DAWs. But it does work flawlessly with Pro Tools 10. I wouldn't want to use the plugin if I had to go through multiple steps to save.