v1.7 bug reports

AyePee wrote:
Does cubase not get the midi when in controller mode? have you tried going up octaves to around bank D that's usually where the program is on a keyboard which when controller mode is activated the mpc is acting as so if you have your sounds on bank A in pgm but then go to midi mode it will be a few banks up if you play from bank A you won't hear or get anything from your pgm

you can confirm its sending a signal by controlling a vst and staying at bank A the note will be like -2 octaves or something

Id much rather a midi profile like the mpd and mpk series & maschine have that way you can activate it without needing the mpc software loaded by a simple key switch like it does now it would just not need the software loaded up

SimonInAustralia wrote:
Is that a bug, or something that has not been implemented due to differences in MIDI routing out of plugin mode from the RTAS version of the plugin vs the VST and AU versions of the plugin?

The 'DAW" MIDI output is available in the AU MPC Software plugin, it just doesn't seem to go into Logic in the same was it does in Pro Tools. That seems like a bug to me.

It is impossible to play pads for midi note input, MPC software as sound module and DAW as sequencer. This means bypassing MPC sequencer.

Make this simple experience:

- Don't load MPC as plugin. Create midi track into DAW. Put MPC as Midi IN. Play pads: You can input notes on your midi track. Great but you can't hear Ren's sound.

- Create Instrument track using MPC as your instrument. You play pads, hear MPC sounds and record inside MPC sequencer as you expect. But instantaneously, your first midi track stops receiving midi from your MPC.

Using a midi keyboard, you can still record midi notes into DAW and hear MPC sound. But this completely kills the purpose of having pads.

For now, using Renaissance as an instrument inside a DAW results to have a DAW within a DAW.

DJPureLogic wrote:When I attempt to mute, or unmute a channel strip for a sound in a copied sequence, it effects all other sequences on that project in 1.7. It's driving me insane. Any advice?

Program strips are global. So what you do in in sequence to a program will reflect in all sequences that use that program. Want different behavior then you have to duplicate the program.

DJ Hellfire wrote:

DJPureLogic wrote:When I attempt to mute, or unmute a channel strip for a sound in a copied sequence, it effects all other sequences on that project in 1.7. It's driving me insane. Any advice?

Program strips are global. So what you do in in sequence to a program will reflect in all sequences that use that program. Want different behavior then you have to duplicate the program.

in 1.6 it worked like a charm. I'd copy a sequence, add a few more tracks, building it up into a song like normal. With 1.7, if I copy the 1st sequence, and add a few tracks, and it mirrors that to the 1st sequence. Never had an issues with the past few updates. What gives...?

Its loading crazy amounts of copied programs if I load an older 1.6 project into 1.7....
Looks like
Program 001-S3-T2
Program 001-S3-T3
Program 001-S3-T4........and so on...Dont know why but by creating all the copied sounds and plugs it spikes the CPU.

in kontakt, if i scan to the next preset with in the instrument konakt guy closes. contact is still loaded but you need to bring it up again to continue to edit..

and i can't delete program 001 if you do it reappears as last track.

1. When you click the stop button twice to stop a sequence and kill all sounds playing (ie long samples) the unit goes to shiat and freezes, jumps jiggy, crashes, etc. This is a must fix for me because i am a sampler and i cant wait around for long samples to play out while stopping and starting a beat multiple times during creation.

2. some 1.6 sequences just do not play all of the assigned pad samples (kicks, snares, etc) even though it shows the sound properly assigned to the pad. i have checked the routing and all and no luck. will not even play assigned sound even if u hit the pad even though it says that the sound in loaded and on the sequencer i can see the actual marks on the sequencer steps

3. sequence play back is choppy. have checked all settings. nothing out of place. freezing randomly. created new sequence file just to see if conversion issue. same problems. if you stop a sequence it freezes for 15-20 secs while making noise the whole time then unfreezes.

unusable without these things being fixed to me so im bak to 1.6 until fixed and i got a feeling that may be a while with as long as we waiting this time. beyond frustrated. waited all this time for this.

Sidebar Rant
Individual VST Program settings (patch volume, etc) should not be global. It should be per sequence unless you are directly copying the same sequence to make a song. or it at least should have to option to do both ways. Yea thats how midi basically worked but that just does not make any sense in todays cpu based in the box environment.

Not sure if this is an MPC bug or an OS issue or a UAD issue, but any settings I make in UAD plugins are not saved - when I load up a previously saved file they are all reset to default. Other AU plugins (on a Mac) do keep their settings. Anyone else see this?

DJ Hellfire wrote:

jigdagod wrote:Not sure if it's a bug or not, but I can't change any of my volume faders and pan knobs with the scroll wheel on my mouse anymore. It works inside the plugins, but the software

This was intentionally removed in favor of being able to scroll the mixer without accidentally changing faders and pans when using track pads, which was extremely annoying.

Cool. Just making sure I'm not going crazy. I used it because it was there, but I'm cool without it.

akaipete wrote:There will be a 1.7.1 release shortly.

We are listening. Some things reported here have been fixed already in the next release.

Not a bug, but could this be fixed as well in that release?
Make all dB/fader volume levels font bigger, bold, and a color that can be seen.

using locate: start/end on the hardware during playback can cause stuttering audio that can take up to 10 seconds to resolve, and once for me the software completely locked up. I use this feature a lot to move between sequences quicker during playback ie i'll navigate to the next sequence i want to tweak on the lcd screen in main mode and hit locate: end to act as a 'sudden' jump to the sequence lined up. Had no problems doing this with 1.6.

Using both MPC 32/64 bit apps. My CPU% n the MPC app is matching my UAD DSP% or a little less than the UAD% in the Control Panel. I didn't have this issue with 1.6. All my UAD processes were used with my UAD DSP not in the MPC app. I'm also getting an error message of device code -26 from only using 4 UAD plugins in MPC 32 app when I can normally use more than that when I mix in Pro Tools. I don't mix in the Ren software as of yet. I was just testing it out for a user who was experience other issues and I couldn't reproduce his issues, but stumbled on this.

Windows 7 64-bit
3.50GHz - i7-4770K CPU
16 GB Ram

Spoff77 wrote:Not sure if this is an MPC bug or an OS issue or a UAD issue, but any settings I make in UAD plugins are not saved - when I load up a previously saved file they are all reset to default. Other AU plugins (on a Mac) do keep their settings. Anyone else see this?

I have the same issue...If I set a UAD plugin and load that project up later it is always set as its default.

KASZ247 wrote:Its loading crazy amounts of copied programs if I load an older 1.6 project into 1.7....
Looks like
Program 001-S3-T2
Program 001-S3-T3
Program 001-S3-T4........and so on...Dont know why but by creating all the copied sounds and plugs it spikes the CPU.

This is actually as designed. It's not actually creating any more plugins than you originally had in the program. They are just being moved from tracks to program channels. The amount of plugins that you get are the amount of plugins you actually put there on your own. I explain this here: viewtopic.php?p=1657650#p1657650

Don't know if anyone mentioned this, or if it's considered a bug in regards to track explode. It's useful, until you explode the wrong track. When you undo, it removes all of the events and un-mutes the original track you exploded, but it leaves all the tracks it created behind. If the project was saved you can just reopen it if you hadn't done anything else, otherwise you have to clear all the extra tracks it made manually. This should happen automatically when you press undo.

I have Win 8

Against my better judgment I decided to upgrade last night. I tried to load a few projects, A few 1.6 projects fully load but crash as soon as I hit play.

Never had that happen....

Going back to 1.6

Also, what file does this " project backup copy go too"?

Anyone know?