Saving in Host issues.

And to top it off, it's at version 1.5, and they still haven't found a way to drag n drop, tracks,pads, to the host for easy bounce downs, which would obviously be the answer to bouncing tracks down.

Akai you really need to get a better team in place.

bobbybland wrote:And to top it off, it's at version 1.5, and they still haven't found a way to drag n drop, tracks,pads, to the host for easy bounce downs, which would obviously be the answer to bouncing tracks down.

Akai you really need to get a better team in place.

bobbybland wrote:Poor coding, vs NI's Maschine for example. I've never had 1 saving issue in any host using Maschine.

This again just shows how un-ready for prime time they are. Akai needs to really understand the vst spec they are dealing with, losing projects is no fun.

I shouldn't have to save in two places period, seriously it's shit like this that makes me wanna just sell the thing off, and remove anything Akai from my studio.

Beta testers my ass!

Are you even sure that the MPC Software is even the problem and not Pro Tools? Because since you're only saving in Pro Tools, Pro Tools is what needs to remember the plugin configuration state and settings, I would think, just like with any other plugin! If you're not saving within the MPC application, then it's not up to the MPC plugin to remember your settings, again, I would think!

I'm using presonus studio one and no issues with the host saving any other vst settings, such as geist, motu bpm, maschine, etc.

bobbybland wrote:I'm using presonus studio one and no issues with the host saving any other vst settings, such as geist, motu bpm, maschine, etc.

But do you think it's possible that S1 could have some incompatibility with the MPC app? Afterall, S1 is what is supposed to be what's remembering your MPC settings. If you aren't saving in the MPC app, how can you expect the app itself to remember anything?

It's not S1, as I mentioned, all other vstis,bpm,geist,guru,maschine, that sequence have no issues within this host. It's that the mpc software, whatever the "mpc state" memory thing is, is not working as it should, and akai is aware of it. To me it's not properly coded. The settings you last leave in a vst, then save under the host, with all other apps, retain the correct settings..

With the mpc, it does not. This is an mpc software issue under the vstspec,which is not coded alike the above named vsti's, but it should work like them. If it's working correctly, this is just poor coding, or someone got lazy, the user shoouldn't have to save it twice!

I wouldn't be surprised if protools is the only host that the plugin works reliably in, given that LE was supposed to be included in the flagship package, if I'm remembering correctly. Most of the testing probably occurred there. But hosts aren't incompatible with plugins. It's the other way around. That's the basic host / plugin "contract". Hosts say "if you want your plugin to function correctly, here is the specification that you have to meet". That's why it's tough to make a plugin that works in all hosts. You could potentially have a separate specification for each host that you have to adhere to.

Each host functions a bit differently, but either way, from a software design perspective, it all points to the plugin. Save events, load events, etc are called by the host, and the plugin has to be designed to respond to those events accordingly. This to me, looks like the mpc software isn't responding to those events correctly across all hosts.

My question that akai can answer, what hosts has the flagship and essentials software been certified for? Certification is a common software vendor task when their product relies on, or uses another product to function.

bobbybland wrote:With the mpc, it does not. This is an mpc software issue under the vstspec,which is not coded alike the above named vsti's, but it should work like them. If it's working correctly, this is just poor coding, or someone got lazy, the user shoouldn't have to save it twice!

We must have been posting at the same time. ^^^^ this.

Eyalc wrote:
Each host functions a bit differently, but either way, from a software design perspective, it all points to the plugin. Save events, load events, etc are called by the host, and the plugin has to be designed to respond to those events accordingly. This to me, looks like the mpc software isn't responding to those events correctly across all hosts.

My question that akai can answer, what hosts has the flagship and essentials software been certified for? Certification is a common software vendor task when their product relies on, or uses another product to function.

Exactly, and this is the reason I mentioned the idea of a public beta,a year or so ago in order to get the issues within the daw ironed out. I guess I'll mess with the element software to see if it suffers from the same issue, but Akai is aware of this issue, and it's very unprofessional imo. Akai you guys want the N.I. money,then serve your customers with proper bug fixes before anything else, before you launch a new product fix the ones your pushing!

Essentials doesn't work well either. I tried, when it was first released, to use it in Logic Pro X. I bailed on it, because I refuse to use a plugin that I have to save in, and also save in the host. And when I did save, I couldn't get it to function consistently - at least not that I could figure out.

As I've been saying, I don't think the MPC software, or Essentials was designed from the core to function as a plugin. Or either they didn't test thoroughly. Seems that it was an afterthought, at least for DAWs other than ProTools. Hence, my other gripe, why it was released with only 8 stereo virtual outs. If used as a plugin, for full productions, way more than 8 virtual outs are needed for it to be useful. There are other gripes as well - that's just mine.

Anyway, I haven't used either as a plugin, and won't until they get these things addressed.

Thanks for the heads up,that'll save me the headache from even testing it. I'm in agreement with you, I think Akai is lost on alot of the workflow users want when using it in a daw.

Hopefully they can start pushing out some quality updates,much faster then their current scheme. I'd rather have 15 smaller consistent updates then one big one and have to wait 3 or 4 months at a time.

Again thnx