MPC Renaissance & MPC Software OS 1.0 Bug Reports

masada2502 wrote:

im i the only person with these errors?

IMAKEMADBEATS wrote:
Jah,
What do I change in the preferences to keep it from recording before it's suppose to?

masada2502 wrote:Im use the vsts that came with the ren

IMAKEMADBEATS wrote:I went to preferences, clicked on sequencer, unselected "record pad aftertouch events" and the software instantly crashed. Here are the error codes..

http://imakemadbeats.com/mpccrashcode4.rtf

Did a little testing. If I reopen the software, preferences, unselect "record pad aftertouch events"...then try to load a sound to a pad, it crashes. Every time.

If i add a sound to a pad first, then try to unselect that in preferences, it crashes as soon as I hit "Ok"

The error codes above are for this problem.

JAH wrote:

IMAKEMADBEATS wrote:I went to preferences, clicked on sequencer, unselected "record pad aftertouch events" and the software instantly crashed. Here are the error codes..

http://imakemadbeats.com/mpccrashcode4.rtf

Did a little testing. If I reopen the software, preferences, unselect "record pad aftertouch events"...then try to load a sound to a pad, it crashes. Every time.

If i add a sound to a pad first, then try to unselect that in preferences, it crashes as soon as I hit "Ok"

The error codes above are for this problem.

I see. What other options are in the Sequencer menu?

JAH wrote:

switch18 wrote:

switch18 wrote:I think I found a bug in the Preferences "Audio Section". I am able to select my Allen & Heath ZED 16 (Firewire) channel as an AUDIO Output. However, I am trying to make channels 15-16 (stereo pair) my Output Channels. I use these 2 channels as my main Output channels for everything coming out of my Mac.

When clicking on the Audio Test The signal does output on channels 15-16 as I wanted (all channels still selected), but will not play sequences at all. Nor, trigger audio from the samples on pads.

After some Q/A and frustration, I was able to get channels 1-2 on A&H ZED 16 as an Output for the MPC. All 16 channels are still selected on Preferences still, but sound is only coming out of channels 1-2. Weird.

As it stands, you are absolutely not able to de-select the other channels, and or just select channels 15-16 (stereo) as an Output.

I think I should be able to route the output to whatever channel I should want on my mixer. Kinda frustrating as I use channels 1-2, as post EQ's sends for 2 of my synthesizers.

So, I took some of the advice on here and upgraded my OS to Lion. However, the problem still persist. I am still not able to de-select channels on my A&H mixer within the MPC References section. When clicking on the test button I am getting a test tone on channels 1-2 & 15-16 now. However, audio from the MPC Ren is only transmitting on channels 1-2.

Tutor, I don't know that you will be able to reproduce the same problems. Unless you have an A&H, but this is clearly not right. For now I will settle for sound on channels 1-2. However, this is not ideal.

Did you read my post on how to configure an audio interface on the Ren? I am using an Universal Audio Apollo interface (firewire) and all available channels are available.

JAH wrote:

IMAKEMADBEATS wrote:If you tap any pad CLEARLY during the metranome click in before recording has started, that pad will record at the very beginning when it actually starts to record. For example, if I Rec+Start, and say between the first count in click and the second (theres a total of 4) i tap my snare pad to make sure its the right one...after 4...when it actually starts recording, the snare will be recorded as if it was hit right upon the start of actually recording.

I dont think this is supposed to be this way. its definitely not like that on the 2000xl. Anyone else notice this?

**Update** - This is not a bug. The recording of notes during count-in is a feature of the Ren. It is in Cubase 6 and I believe an older MPC but can't recall exactly. I believe there was an option to turn it on/off but not in OS1. Will suggest as a feature request to turn it Off/On for those users that don't like this behavior.

masada2502 wrote:

im i the only person with these errors?

JAH wrote:

masada2502 wrote:

im i the only person with these errors?

Confirmed. This is more of a limitation of the software and your computer than a bug. The MPC Ren is a 32 bit app. Adding too many plugins will eventually produce this issue. The number of plugins added to produce this problem is system and OS dependent.

dryad-66 wrote:
f its a limitation of your comp and software then its a limitation of the ren.Just sayin.Maybe not a bug but will come across as one.And of course we will see a stack more of these 'limitations' as time goes on ...facepalm... Its the nature of constant variable parameters in comps and sw.........Glad im not responsible for updating the OS

JAH wrote:

wakko1999 wrote:Issue 2 - Strange behavior with programs when moving from track to track on hardware

Not a bug.
The MPC Ren is weird in this regard but it is actually designed to perform this way. When you navigate to an empty track, it will use the settings of the last track you were on.

So if the last track was a MIDI track, going to an EMPTY track and it will me assigned to MIDI. If you have Program 'Bad Ass Drums" on a track and then move to an EMPTY track.....''Bad Ass Drums' are ready to record on that track. The only difference is for Plugin tracks that are assigned an actual plugin. If you move to an EMPTY track after a plugin track, the default will be an MPC program. Having plugins automatically assigned would cause serious issues.

This 'feature' is believed to provide a faster workflow when you record methodically from one track to another. If you jump around (skipping tracks), that it can look confusing.

ISSUE 1
Deleting empty pgm field while Inst field set to plugin crashes program

Steps to reproduce:
a) on hardware, set a tracks 'Inst' field to 'plugin'
b) on hardware, in pgm field select a plugin
c) (optional, will crash wether this is done or not) record some midi notes
d) select the plugin name in the pgm field and press the 'window' button on the hardware
e) press delete, then' do it' to delete the plug in
f) while still in the pgm field, press the window button again, delete and 'do it'
g) program will crash
***note i stumbled on this while using the ren. this obviously is not a set of steps i would normally be doing, but inadvertantly doing the above sequence will take the progrsm down. i would think if the pgm field was empty then either the window button would not activate or at least the delete option would not appear so the exception could not be triggered.

wakko1999 wrote:came across these glitches that are reproducible (at least on mine so far). all are while trying to use the hardware exclusively...first, the particulars:

Osx 10.7.4, 8gb ram, dual quad Macpro tower, MPC 1.0 software


ISSUE 2
Clearing a track from hardware results in 'Inst' field being set to 'mpc' while 'Pgm' field remains set to a plugin. Also, because of this, multiple instances of a plugin end up being created after each time a track is cleared. Prior instances are also unusable.

Steps to reproduce
A) create a track with a plugin instrument
b) (optional) record some midi data on the track
c) on the hardware, navigate to the track name, press the window button and select 'clear' and then 'do it'. The track will now show 'MPC' in the 'Inst' field, yet the 'PGM' field will still have the plugin active.
d) record some midi data. You will be able to hear the sounds from the plug in.
e) try to playback the midi data and you will now not hear the plugin because the midi data is actually routed to the MPC engine despite the plugin being displayed as the current program.
f) on the hardware, switch the 'INSt' field to plugin. the 'PGM' field will now go empty.
g) navigate to the PGM field and turn the jog wheel to select the same plugin instrument. observe the only option available will be 'duplicate'. select that option and another instance of the plugin will be created (observe that in the software under the project files you will see "plugin name-2")
h) in the software, click the plugin drop down for the track and attempt to select the original instance of the plugin and it will only create another instance of the plugin.

****note creating another instance of the plugin is not a problem in itself and I understand the need to instantiate another instance if creating a plugin on another track. The actual 'bug' or glitch is in steps a-c with regard to Inst showng MPC while PGM was still had the plugin active. I included steps d-h to illustrate the workflow implications. The problem above is that each time a track is cleared the user is ultimately forced to create a new instance for that track even though a plugin was already allocated to that track. The prior instances cannot be used and when you try (as was done above) it just creates yet another instance. I came across this because I had at one point 19 instances of a plugin sitting in the program list when looking at the software and I really only had that particular plugin used on one track...

Not sure what the correct behavior is supposed to be when a track clear is done on the Ren (meaning are only midi notes cleared or are both the Inst and Pgm fields supposed to be reset to default, etc..) but the current mismatch between the Inst showing MPC and the PGM being set to the plugin is a problem...