Saving in Host issues.

So tonight I created a full project in mpc ren,in studio one latest version. I saved the s1 project, then later when reloading the s1 project, the mpc data was long gone..

It's like as if I never recorded anything on the mpc. Being that any other vst that sequences, saves within a daw, I figured the mpc would do the same thing..

wrong, the project in the mpc software must be saved itself, before saving the daw project, or all data is missing??


I know I've done this 100 times before without saving the project, so what happened tonight?

Is this a 1.5 issue?

I had a similar problem in Logic using the Essentials software. I haven't tried the mpc software. Might try just for kicks.

But it didn't matter what I recorded in the essentials instance, the data would be gone when I reloaded my logic project.

I would think that a DAW save would save everything. But check the manual too. The essentials software explicitly requires that you save in the plugin too. Not sure about the ren / studio software. Not near my computer to check. Although one forum member using protools reported that he didn't have to save in the plugin.

Anyway, not really being helpful I suppose. At least letting you know your problem isn't unique. And possibly could be a 1.5 issue. I assume essentials was based on the 1.5 code base.

From my experience, when using another production software as a plugin inside a host DAW, you always have to save the project in both. When I was using Reason, I always saved the Reason project separately as it had to be loaded when coming back to it later. The plugin would just load a blank rack when opening my Pro Tools session. Then I go into the Reason plugin and load the project file that goes with my Pro Tools session.

DJ Hellfire wrote:From my experience, when using another production software as a plugin inside a host DAW, you always have to save the project in both. When I was using Reason, I always saved the Reason project separately as it had to be loaded when coming back to it later. The plugin would just load a blank rack when opening my Pro Tools session. Then I go into the Reason plugin and load the project file that goes with my Pro Tools session.

This is interesting. I've never used Reason, so maybe I'm expecting something that isn't reality. In Logic Pro, no matter what plugin I've used, I've never had to save in the plugin and in the DAW. But from what you're describing, other production software works similar.

Though I don't fully understand why a dual save should be necessary, I suppose it's related to production software and not plugin instruments. Heck I don't know.

Eyalc wrote:

DJ Hellfire wrote:From my experience, when using another production software as a plugin inside a host DAW, you always have to save the project in both. When I was using Reason, I always saved the Reason project separately as it had to be loaded when coming back to it later. The plugin would just load a blank rack when opening my Pro Tools session. Then I go into the Reason plugin and load the project file that goes with my Pro Tools session.

This is interesting. I've never used Reason, so maybe I'm expecting something that isn't reality. In Logic Pro, no matter what plugin I've used, I've never had to save in the plugin and in the DAW. But from what you're describing, other production software works similar.

Though I don't fully understand why a dual save should be necessary, I suppose it's related to production software and not plugin instruments. Heck I don't know.

I believe the difference is the type of plugin. Reason and MPC are other complete applications. With plugins that are just instruments or effects, it's different.

No reason is a rewire app, mpc is vst so it should function in the same manner. Like I said it's worked before, so this just shows how unpredictable the software is

bobbybland wrote:No reason is a rewire app, mpc is vst so it should function in the same manner. Like I said it's worked before, so this just shows how unpredictable the software is

Yeah, but they are still full applications that you are inserting! Maybe they are supposed to save, I don't know. I've never not saved within Reason or MPC when using them in Pro Tools!

Well I know the essentials docs say to save in both places. So wouldn't be surprised if it's mandatory in the mpc software as well. Though I still believe that it's not behaving the same across hosts, which I think could be the real issue. JAh said he didn't have to save in protools when using essentials, but I did. And even when I did it seemed to be unpredictable.

I'm just holding out hope to see more virtual outs in the flagship software. That would make things so much easier for me to use it as a plugin. Not being selfish... Lol

weird, I reloaded the project and it did load the mpc project. It's weird, like it has a mind of it's own, it says something like mpc state etc.. I'm assuming it remembers the state of it's last settings, well sometimes it doesn't.


For what it's worth the dev's should probably have a look at this behavior, in studio one.

In all the DAWS. A least the major ones. They seem to operate differently. When they should be air tight consistent.

You guys should be saving anyway. No way I would trust this type of thing to a DAW. Even lately, I've been saving my entire Kontakt rack separately in my MPC projects. I just save the rack files right in the same folder as my project. That way if it ever decides to forget what my patch settings were, I can easily recall them. Takes an extra two seconds, but losing work is depressing!

Eyalc wrote:Well I know the essentials docs say to save in both places.

If the doc states you should save in both places and you don't then it is user error...

YEs IT saves it as mpcrenstates...

Sometimes though, I;ll use a template, (track templates in reaper) and it will use the last saved directory of a project instead of the new one. (even though i create the new project directory for reaper project and save it) So i have to use save as (in mpc sof) instead of just save..

It would be a good fr to save all mpc ren vst project contents to daw user specified project directory when you save on daw... imo...

I'll spend some time to day creating MPC projects in Logic and Pro Tools and report back what I find.

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!