What happened to "run-in-real-time plug-in preference???

[Shooshie]

Yeah, Dave is the real deal, all right. He was getting ready to go out on tour with MJ when we tragically lost him. A tour like that doesn't hire wannabes.

Shoosh

[jlaudon]

Yep, I'm also getting sustain pedal weirdness as well as delayed playback form certain plugins like Play and VE Pro...

Back to 9.02 for now

[waxman]

Yep, I'm also getting sustain pedal weirdness as well as delayed playback form certain plugins like Play and VE Pro...

Back to 9.02 for now

DP 9.1 is a ho nutha ting... It defaults to pre-gen. There is no global run in real time for a good reason. Many plugs and VI's should not be run in real time. The run in real time option is per plugin and VI. There will be plugs that don't work until they are updated. Especially the ones that have built in playback engines.

I spent a lot of hours yesterday and today sussing out why I was suddenly getting crashes in BFD3 during recording. It had been working great since the DP 9.1 release. The low latency feature quickly became a can't do without. I had been in buffer 128 for weeks. Finally it was what you hear is what you get...

Since nothing had changed in BFD3 I suspected DP 9.1 had gone south. Repair permissions, reinstall both DP and BFD3. Reinstall MIDI drivers the whole 9 yards. Went to bed defeated. This morning called MOTU and Brendan joined the chase... still no fix.

I grew tired of the chase and reverted to DP 9.02 and low and behold DP 9.02 crashed also. Things that make you go Hmmm. So set up a session from scratch with a stock BFD3 Ludwig kit and DP 9.1 It all worked perfectly again... Hallelujah!!! Eventually it came down to the BFD3 Kit that had worked perfectly for many sessions somehow became corrupted. Once identified it was an easy fix.

So DP 9.1 according to MOTU has some 3rd party plugs that don't work at all but BFD3 had not been reported as a problem. This new dynamic of pre-gen is still a must have for me especially tracking drums. If there is trouble in the future it's likely going to be an issue with a plug or VI the majority. Find an alternate and if not stick to 9.02. At some point most plugs and VI's will work with 9.1. MOTU is currently working to fix the offenders.

I had a great session this afternoon that lasted hours and there was not even a hiccup. The track had meter and time changes and the drum tracking remained solid. After I became brave I jerked the wiper around to see if it would choke. Happily it is solid as a rock. So for now all my NI, Arturia, Slate Digital and UAD2 plugs and VI's work perfect and that is enough for me. Sadly for some especially those doing large VI projects for film there are probably to many variables for DP 9.1. This new technology is amazing and will be rock solid at some point. In the mean time carry on.

[Sean Kenny]

No...I'm hitting record manually, waiting a second, and then hitting a note and the pedal-on, which since the beginning of time (or at least pianos!) has triggered a sustain.

I will report the bug to MOTU, but it looks like, thanks to the last post, someone else besides me is seeing this same problem with a completely different setup.

FYI, I am seeing this with both a piano VI opened in Kontakt directly opened in DP, and also the same piano VI opened in in Kontakt in VE-Pro with the VE-Pro plug-in opened in DP.

None of this happened in 9.02, or any previous version of DP.

As I said, in previous versions of DP, I had pre-gen turned off and run-in-real-time turned on globally.

Thanks!

Had the same problem here too in a recent session using Vilabs True keys

[amplidood]

I ran back to 9.02 as fast as possible because of all the changes made to the pre-rendering system in 9.1. Rather than just make it work better, they almost completely did away with our ability to choose whether or not to use it. Unless I'm programming I don't want it, and even then the whole track buffering system has been FUBAR'd to where editing during playback is no longer a smooth experience. Plus I couldn't print or BTD without getting glitches all over the place.

Seems this one came out a bit premature.

[waxman]

I ran back to 9.02 as fast as possible because of all the changes made to the pre-rendering system in 9.1. Rather than just make it work better, they almost completely did away with our ability to choose whether or not to use it. Unless I'm programming I don't want it, and even then the whole track buffering system has been FUBAR'd to where editing during playback is no longer a smooth experience. Plus I couldn't print or BTD without getting glitches all over the place.

Seems this one came out a bit premature.

Setting "Run in real time" is available on individual plugs only. In 9.1 it's not the default preset. It's there for graphic options in the plug you want. Look for a present this Friday or next.

To run both 9.02 and 9.1 on your machine just change the name of the application of one of them.

[OldTimey]

hoping MOTU brings back "run-in-real time" option back to preferences.

i abhor "pre-gen"!

at the very least have the fixed the clicking and glitching that happens when you open up a plugin window that isn't set to "run in real time"?

[crescentoon55]

Well I've got problems with G Player and RMX in DP 9.1 They are skipping notes and are not locking into the tempo. I gave a file to motu to check out the problem. The fact is these plugins are dated and that may contribute to the problem but I would like to have more control over with pre gen in general. MOTU is going to have an update for 9.1 perhaps by next week.... I don't know whether this problem will be addressed by that time.

[Phil O]

Look for a present this Friday or next.

MOTU is going to have an update for 9.1 perhaps by next week....

Did you guys hear that from the horse's mouth? (I hope)

Phil

[monkey man]

Well, either the mouth or the other end, I'm guessing, Philly.

[crescentoon55]

Told to me by tech support last Friday....

[Phil O]

Wagers?

[Saintmatthew]

Here is the text of the new features from MOTU...

MOTU has worked hard to ensure a high level of compatibility with third party virtual instruments and effects. There may be cases where pre-generation may not work as expected with a given 3rd-party plug-in. These cases should be reported to MOTU and the plug-in vendor so that compatibility can be fully established. In the meantime, you can run the plug-in or instrument in real time.

If you would like a plug-in or virtual instrument to run in real time only while its window is open (to improve level meter timing in the plug-in window for example), go to the minimenu and choose "Run Open Instances of This Plug-in in Real Time". Close the window to return to Pre-gen mode (or uncheck the menu item). This setting applies globally to all instances of that plug-in and is saved globally.

To force a virtual instrument track into real-time operation all the time (not just when its window is open), record-enable any MIDI track that targets the instrument. To force an audio track's effects into real time, the track can either be record-enabled or monitorenabled. Alternately, the effect can be placed on an aux track, either in a chunk or a vrack, with bussing used to access the effect. Aux track effects are always rendered in real-time.

Seems like they want us to use pre-gen as a default.
Record-enabling tracks to defeat the PG would be a bit impractical for session use.
Maybe I don't understand the concept.

Is there a particular way to report these plugs? Using Tech links or a specific email?

[Prime Mover]

Oh man, I'm still on DP8, but I wouldn't want to upgrade if I couldn't disable pre-gen. I have a few plugins, G-Force Mellotron in particular, that are all kinds of bad with pre-gen enabled.

[JSmith1234567]

They really need to bring it back pronto!