@bobbyblan, Danny, Airyck, TyBordelo & dorsey

I remember reading that all you guys use the MPC Ren plug-in inside Presonus Studio 1...

I'm a recent convert and have hit a brick wall. Can any one help out??

I get the error message ''MPC Already Running. You already have MPC running in this host. You can only run once instance of MPC at a time.''

One of Studio 1's features is to have multiple songs loaded and inserted into a mastering project. Problem is, I can't have the MPC plug-in loaded in more than one song at a time. I just get the red triangle message. I've tried deactivating the MPC plug from the other songs but I still get the message. Essentially if I load 2 songs, I can only use the Ren Plug-in in one of them, no matter what I do

Just wandering how you guys work around this...

PS-Is there a short cut in Studio One to bring up the Plug-in GUI?? I can't find it in the key commands menu. I need a quick way to show/hide the MPC plug-in.

Thanks

i get this message also. don't know if there is a workaround. why do you want to use 2 beats the same time?
i open the plugin with the button of the vst track, don't know if there is a shortcut?

I want to make use of the Projects feature. It works best if I have a bunch of tracks loaded. I can see the potential in using it but not if I can't have the MPC on more than one song:(

I was hoping there would be a work around too... maybe one of the other S1 users I mentioned has a solution??

thinking about this i guess its technical not possible to do it because you can only load one beat inside the mpc. i think you should ask pete via twitter about this issue, maybe they make it possible in 1.4

Yeh I guess but I won't hold my breath. They have a loooong list if things I'm sure they intend to address first.

I just assumed that when you load one song it would deactivate the mpc plug-in link from the other...

At least that seems to me to be the most logical..

I made a template in studio one that i load up, with vst plugins already loaded inside studio ones mixer but since 1 month it started crashing some of this plugins when loading, then i have to turn the mpc off and on or reload the template to get it working. this has definitly to do with the mpc plugin/audio engine, i hope they fix it soon.
do you have this issues too when loading a beat with vst plugins?

the only way your gonna do this is to convert instrument to audio which would be better
all round for mastering your projects because of the cpu use
you cant run more than one mpc plugin on any of the other daws as far as i know

just convert the instrument to audio tracks
all those plugins are eating the cpu you want that in tip top shape when mastering your
tracks.

I dont think its possible, but I never load more than one song without closing the last since my projects are large.

You can just click on the little keyboard looking symbol to the right of the mpc instrument track and it will bring up the editor, not sure it they have a key command for that , but im running mine under jbridge in 64 bit mode so it maybe different.

cool tip, if you insert a blank midi region on the mpc instrument track and name it, then drag it into the browser ( should make a folder for all your stuff to organize it first) it will make a clip of the mpc session( even with multi outs and fx sends) and if you want to drag it back into another session it will bring it back with multi out sends and fx just as it was..... good for making complex drum sequences for songs to start ideas

The Mpc Ren is coded completely wrong in this regard, if you ask me. It remains open when loading a new project,whereas it should shut down.To be able to create a new instance.

Studio One unlike many other daws,is able to load multiple songs at once,(meaning keeping active projects open to edit and tweak until your desired results occur) but since the ren,has no option to allow for 2nd or 3rd instances, it will fail in this regard.

Not a studio one issue,but yet a Akai mpc ren issue.

Your ahead of the game though with S1, the most slept on daw. Mind you I have all the usual suspects,and they aren't even close.

peace

TonyBordelo wrote:do you have this issues too when loading a beat with vst plugins?

To be honest, I'm just starting out using the MPC plug with Studio 1 so I cant really comment on this.

Danny wrote:
just convert the instrument to audio tracks

I tried this and disabled the MPC plug-in but I still got the error when switching song. I even removed it from the first song and still couldn't get it to open in the second!

dorsey wrote:You can just click on the little keyboard looking symbol to the right of the mpc instrument track and it will bring up the editor..

cool tip, if you insert a blank midi region on the mpc instrument track and name it, then drag it into the browser ( should make a folder for all your stuff to organize it first) it will make a clip of the mpc session( even with multi outs and fx sends) and if you want to drag it back into another session it will bring it back with multi out sends and fx just as it was..... good for making complex drum sequences for songs to start ideas

I'm aware of how to open/close the GUI from the DAW but I used to use Cubase and you could assign a key command to almost anything. I use to hit the space bar to open/close my virtual instruments. Looks like I can't do it in S1 just yet.

Thanks for the workflow tips, I'l bare that in mind. Still getting to grips with S1 at the moment.

bobbybland wrote:The Mpc Ren is coded completely wrong in this regard, if you ask me. It remains open when loading a new project,whereas it should shut down.To be able to create a new instance.
....Not a studio one issue,but yet a Akai mpc ren issue.

Your ahead of the game though with S1, the most slept on daw...

Yeh I agree. Just when I thought I'd found my perfect Ren host I come across this. I'm also a lil annoyed I can't resize the MPC plug in S1 like you can in Ableton or Logic. Apparently that's a Studio one issue tho (according to Akai anyway).

I was hesitant at first about S1 but the more I got into it, the more I agree it's a slept on DAW. It's fairly new too so I'm hoping it's just getting started:)

Thanks for the replys!