MPC Renaissance and MPC Studio v1.3 & 1.31 Bug Reports

When in plugin mode in PT 10.3, The MPC Software wont let any plugin, VST or Insert, take the forefront/focus. It will pull them up behind the software. The only way to use them is to move the software left or right to access the plugin.

MBP 10.6.8 PT 10 8gb ram v1.3

My Omnishere worked flawless on 1.2 now im having crazy issues. Its seems to take forever to load a patch and sometimes the patch sound isnt even there. Anyone experiencing this?

Hi

Unfortunately the MPC Ren VST plugin is still completely unusable for me in my DAW. Here are my system specs:

CPU: i7 2600K
GPU: Radeon HD 6970
RME HDSPe PCIe firmware rev 20
RME Hamerfall ASIO driver 332
OS: Windows 7 x64
MPC Software 1.3.0
Cubase 7.0.2 x64

The standalone version of the MPC software seems to function as expected, but if I try and use the MPC VST plugin within my DAW (which is essentially the only way I want to use this MPC) then first the MPC plugin will crash and eventually VST bridge and Cubase itself will crash.

All I need to do to reproduce this is the following:

1) Create an empty new project in Cubase 7.0.2
2) Add the MPC as a VST instrument
3) Open the MPC VST and browse to samples
4) Start adding samples to pads by dragging them over

Then eventually (usually after adding only a few samples) the UI of the MPC VST will either go completely white and unresponsive (see screen shot below), or will not update - i.e. you cannot manipulate anything within the MPC's VST UI - you cannot select different samples or manipulate any of the parameters within the UI:



When this happens, the instance of the MPC VST loaded will never return to normal, even if I close and re-open it it will remain in this 'crashed' state. Sometimes I am able to disable the VST completely and reload another instance of the MPC VST, but it will crash in the same way as soon as I repeat the above.

The problem also occurs if I simply try and load previously saved MPC presets in the VST version within my DAW that were created in the standalone version of the MPC software. Sometimes I will get a more serious crash with VST Bridge that is caused by the MPC.dll. This crash seems to seriously affect VST Bridge as the process completely hangs and even after Cubase crashes, I have to force the actual process to quit. When this happens I get the following error:



I was really looking forward to version 1.3 as I was hoping to finally be able to use my new MPC Ren, but it seems there are still fundamental problems with the VST in my scenario. Any ideas or suggestions greatly appreciated.

Cheers

Edit: BTW, contrary to another post in this thread, I am able to adjust the size of my MPC VST window in Cubase 7 just fine before it crashes.

foge1 wrote:OSX10.7.4
Macbook Pro
REN1.3

Next bug in keygroup sampling.

Go to the LFO mod page.

Qlinks have the wrong display names when adjusting parameters.

E.g. Qlink three is the LFOMOD when adjusting qlink 3 parameter display shows Q3:Sample Play =100

Wheel>LFO function doesn't seem to work. Checked my modwheel in Logic its working so not sure whats going on there.

LFO>PAN q-link does nothing, software knob works though.

G

G[/quote]
#7 is the issue you were having with keygroups. Do you have this problem when creating a key group program within the Ren instead of loading a key group program?

Come on Jah u r the Beta tester. I will write it out again for you.

Try this create a keygroup program with say 3 key groups , add samples to them. Now exit that program go to the main window choose a different track different program. Now return to your keygroup program set the edit mode to All as it will have defaulted back to a single key group. Now change the filter type etc.
It only happens on a single keygroup, you have to select a single keygroup and then return to ALL again for ALL to work. It is exactly as I showed and wrote about everytime you return to a keygroup program selecting the ALL edit does not work the first time you choose it.

I can't believe that if you have have created and edited any keygroup programs that you wouldn't have noticed this. Please spend some time beta testing the keygroup sampling section and report all bugs to akai.

Also in the keygroup
As I stated "Wheel>LFO function doesn't seem to work. Checked my modwheel in Logic its working so not sure whats going on there. "

Does the Wheel>LFO work for u Jah ? have u tested it? this is not a qlink issue neither the software control or the hardware q-link works for me, how about for u?

Investigate further What happens if u try recording MOD WHeel data on a Keygroup track JAH Hmmmm??
Check it out for yourself.

Now try the AFT>FLT knob i.e. the aftertouch control knob ??
WHat do you notice Hmmmm?

Let me know how u get on.

G

foge1 wrote:Come on Jah u r the Beta tester. I will write it out again for you.

More accurately.....I am an MPC user the helps test in my spare time. I go through these posts as a service to the MPC community and don't get paid a dime. If you want any issue addressed, you can report it directly to Akai (whom will ask you the same questions) or you can report it here, all in one post with as many details as possible (no detail is insignificant). It is helpful if you only write one bug per post. Writing a step-by-step guide to reproducing the bug is easier to follow then a paragraph.

By the way....I don't use keygroup programs. They are too limiting and creating them is cumbersome. I use plugin samplers instead.

i don t know which this is a bug
some time
sequence does not copy gridnotes
and there is no mute function in this copyed pattern

windows 8
32 and 64 bit
hp desktop 3,3ghz i3 prozessor
4gb ram

InspectahEX wrote:when I load a plug in instrument like sample tank for example, the gui of the vst is all whited out, all i can see is the window outline. I have to click on the mpc software window and bring it to the foreground, and move it out of the way to see my plug in window.

osx 10.8 ml

I get this same issue with sample tank. The GUI is whit clicking in it a cpl times makes it come back.

2011 Macbook Pro 15 2.3 GHz Quad Core i7
Windows 7 Professional x64
4GB RAM
Renaissance

I cannot trigger pad A4 externally.
I have Roland TD-3 V-Drums plugged in via MIDI cable to the Ren.

Toggling through midi notes on the V-Drum brain, the notes do not even chromatically step through the pads.....Its is a very strange mapping, for example midi note 36 will trigger Pad A2 for example (not sure if thats actually true, just an example) and then midi note 37, will trigger pad A6, and then 38 will tragger pad A5 or something.
It makes absolutely no sense, and this has been going on since 1.0
Now in 1.3 however, i cannot find any way to trigger pad A4 via the V-Drums.

Subby32 wrote:It makes absolutely no sense, and this has been going on since 1.0

Absolutely agree with you, that´s a big non-sense... I guess " It´s how Note Mapping is designed " and " It works as designed " . On any keyboard the notes are not nicely mapped. On my Xboard, same issue. Limitation ? Sure...

I didn´t understand why they didn´t respect a scale like :

C0-> Pad A1 , C1 -> Pad A12 , C2 -> Pad B8 etc... And chromatically organized within the octaves.

All software samplers are logical, but not the REN ^^

BUG:
1. Load vsti Analog Factory on track.
2. Set Master Volume of Analog factory to .50 or halfway
3.Press record on mpc then play to engage recording..
4. Watch the Volume on Analog Factory shoot up to 1.00 or full volume..

= Worthless, Useless, can't make music with this tool, when it's filled with bugs, note your current beta team sucks ass!

BOOMBAPXL wrote:-Emu Emulator X VSTi & Voxengo Span VST Plug-In (latest version) crashes the software.

-----------
Win7 32bit
4GB Ram
Core2Duo

Can confirm this as well after testing with my pc.

bobbybland wrote:Watch the Volume on Analog Factory shoot up to 1.00 or full volume..

Sounds like an automation point is at the beginning of the track... Weird...

Why isn't there a seperate topic for windows vs Apple OS? This can help with the confusion on what works on what system. All of these bugs should be address on their own platform thread. All of the major systems (AVID, MAUDIO, etc) do this. Nothing will be fixed if the programmers have to sift through this one little thread. They are going to miss most of the stuff.

Bug?
When working with samples, adjusting start end points, the qlinks sometimes don't work and sometimes the start or end head jumps all the way to the other when only touching a qlink. What a mess I wrote
MPC Studio
Macbook 8gb ram Mountain lion

comtox wrote:

Subby32 wrote:It makes absolutely no sense, and this has been going on since 1.0

Absolutely agree with you, that´s a big non-sense... I guess " It´s how Note Mapping is designed " and " It works as designed " . On any keyboard the notes are not nicely mapped. On my Xboard, same issue. Limitation ? Sure...

I didn´t understand why they didn´t respect a scale like :

C0-> Pad A1 , C1 -> Pad A12 , C2 -> Pad B8 etc... And chromatically organized within the octaves.

All software samplers are logical, but not the REN ^^

The Ren's Pads are laid out in General MIDI format.....other MPCs as well. The only difference is that you can't change Pad to Note number assignment easily.

If you open up a Ren program file with a text editor, you should be able to change Pad Note Number Assignment.