DP 9.1 is here

[Killahurts]

2) Not seeing any processor change or improvement of note. (Could that be because I run all VI’s in Ve Pro and thus, DP can’t appear to benefit from efficiency improvments without running the VIs itself?)
2 b ) I will have to do an experiment to transfer VIs to DP and see if I still need VE Pro at all.

On my big template, I have a combination of VEP (same machine), V-Racks and VIs on actual tracks. VEP does most of the heavy lifting with orchestral stuff, and EW Play. I probably have around 8-10 K5 instances in DP, some MachFive and a dozen or so synths. DP's buffer is at 256 always, with VEP buffers at 2.

I installed 9.1 and went straight to work on a large project. I didn't change any parameters at all.

I have seen significant performance improvements with all these VIs. Playing them live from a controller is insane, no discernible latency at all. Even VEP hosted instruments have so little delay, as to not be aware of it while creating.

I almost never use plugins post fader, so that's not a problem for me.. and I'm sure I may run into some issues as I go, but so far this has been the best release I've ever used for my larger composing palettes.

The only thing I've noticed is that it takes quite a bit longer to save. I have autosave turned off.

[Rick Cornish]

Upgraded to both El Cap and DP 9.1 today. SFSG… definitely snappier, less beachball time.

[mhschmieder]

Performance and caching are both so good now, that I don't even notice if I change chunks and forget to disable and close all of my VI's and plug-ins (something I've done for years now).

In a way, I feel like DP 9.1 has become what Vienna Ensemble Pro was for many people, in many ways -- though of course VE Pro serves a lot of other roles besides providing better and safer memory management and encapsulation.

For performance reasons, I never got around to making much use of Virtual Racks (sorry, I'm at work so may be using the wrong terminology, but I'm talking about the feature where you define a bunch of VI's that can be shared across chunks). I rarely use that many in common between chunks anyway. When I tried that feature, I'd get too many crashes and freeze-ups.

Anyway, DP 9.1 is so slick that I no longer see any need to "work around" limitations.

[David Polich]

Performance and caching are both so good now, that I don't even notice if I change chunks and forget to disable and close all of my VI's and plug-ins (something I've done for years now).

In a way, I feel like DP 9.1 has become what Vienna Ensemble Pro was for many people, in many ways -- though of course VE Pro serves a lot of other roles besides providing better and safer memory management and encapsulation.

For performance reasons, I never got around to making much use of Virtual Racks (sorry, I'm at work so may be using the wrong terminology, but I'm talking about the feature where you define a bunch of VI's that can be shared across chunks). I rarely use that many in common between chunks anyway. When I tried that feature, I'd get too many crashes and freeze-ups.

Anyway, DP 9.1 is so slick that I no longer see any need to "work around" limitations.

I agree. So maybe the hardware insert feature isn't soup yet, not a deal killer for me because I don't really have any outboard gear I need to use within DP's environment. As for performance and latency...ohmigosh yes, I see huge improvements in these areas overall, with the exception of
"some" VI's and plugs that are long-in-the-tooth and need to be updated by their authors anyway.

If you are using VE Pro to network with other machines, I can see keeping it. If you are just using it with DP on a single machine, I'd go so far as to say it isn't needed anymore.

[bayswater]

Thanks for explaining that, Robert.

Now for a problem:

Some folks use Soundflower or Jack to get system sound back into DP. I use the digital I/O on my MacPro. I just run a light pipe from output to input, set the digital out to "use this device for sound output," and set "Built-In Digital Input" as an input in bundles. I've been doing this for years through many versions of DP and it has worked flawlessly. In 9.1, however, I'm getting some crackling after about a minute and full blown digital noise of some sort after a couple of minutes. Setting a different clock rate or clock source makes no difference. Previous versions of DP still work fine.

I don't know if this is a clock issue or some sort of buffer bug. Anyone else seeing similar problems? I'm considering holding off on sending a TechLink. I'm guessing that this soon after a new release, MOTU must be inundated with them. Maybe I'll wait for 9.1.1 and see if it's addressed. Suggestions?

Phil

I just got around to trying this out on a test partition with OS X 11.6. I loaded a six minute AIF into Quicktime player with the output set to Soundflower and recorded the playback in DP 9.1 using the Soundflower input.

First thing: My install .dmg for Soundflower was version 1.6.6b which works fine in Yosemite, and installs on El Cap but no Soundflower drivers showed up in any app or in Sound Prefs on my test partition. The Soundflower Bed was there but it wouldn't run. So maybe although SF is on your system, it no longer functions properly in El Cap (which I see you have)

I found and installed version 2.0b2 which can be located via the Rogue Amoeba site. It worked fine to make the above recording. It also has the 64 channel version of Soundflower which is handy when to run a load of channels between DP and Logic. But Soundflower Bed app is not installed.

[toodamnhip]

I have verified the snap shot automation bug with a trusted source.

Again, if user does not manually tab through or enter the data in waves and other 3rd party plugs, BEFORE hitting snap shot, snap shot will write the plug-ins default data to the sequence--which means that as soon as you hit play you lose your current settings!

Copy and paste on the fly is also verified as broken. Loading a pre set and hitting snap shot also fails unless tabbing through.
One user here found that snap shot worked on his system, but without seeing what that user is actually doing, it is hard to understand how it can work for this user when it has been a long term issue and still exists on my system as well as the systems of others. If anyone finds a work around besides manually tabbing through/ and/or re-entering all plug parameters before snap shot, please post.

In the meantime- I have gone BACK to 9.02 and it has more cpu headroom and no loop glitches

[Buckage]

I'm not sure if anyone has mentioned this on the previous pages but I noticed that the movie audio outputs can now handle multiple tracks and assign them to their own outputs. It certainly helps my work flow which is usually working with quicktime movies that have separate audio files embedded for dialog, fx and music. Should be a great time saver. No more importing movie audio into the sequence.

[MIDI Life Crisis]

I'm not sure if anyone has mentioned this on the previous pages but I noticed that the movie audio outputs can now handle multiple tracks and assign them to their own outputs. It certainly helps my work flow which is usually working with quicktime movies that have separate audio files embedded for dialog, fx and music. Should be a great time saver. No more importing movie audio into the sequence.

Cool! Thanks for letting everyone know.

[Robert Randolph]

I have verified the snap shot automation bug with a trusted source.

Again, if user does not manually tab through or enter the data in waves and other 3rd party plugs, BEFORE hitting snap shot, snap shot will write the plug-ins default data to the sequence--which means that as soon as you hit play you lose your current settings!

Copy and paste on the fly is also verified as broken. Loading a pre set and hitting snap shot also fails unless tabbing through.
One user here found that snap shot worked on his system, but without seeing what that user is actually doing, it is hard to understand how it can work for this user when it has been a long term issue and still exists on my system as well as the systems of others. If anyone finds a work around besides manually tabbing through/ and/or re-entering all plug parameters before snap shot, please post.

In the meantime- I have gone BACK to 9.02 and it has more cpu headroom and no loop glitches

Aha! I just tried in DP 9.1 this morning after reading your post and now it's not working!

I wonder what I'm doing different this time... how confusing.

[toodamnhip]

I have verified the snap shot automation bug with a trusted source.

Again, if user does not manually tab through or enter the data in waves and other 3rd party plugs, BEFORE hitting snap shot, snap shot will write the plug-ins default data to the sequence--which means that as soon as you hit play you lose your current settings!

Copy and paste on the fly is also verified as broken. Loading a pre set and hitting snap shot also fails unless tabbing through.
One user here found that snap shot worked on his system, but without seeing what that user is actually doing, it is hard to understand how it can work for this user when it has been a long term issue and still exists on my system as well as the systems of others. If anyone finds a work around besides manually tabbing through/ and/or re-entering all plug parameters before snap shot, please post.

In the meantime- I have gone BACK to 9.02 and it has more cpu headroom and no loop glitches

Aha! I just tried in DP 9.1 this morning after reading your post and now it's not working!

I wonder what I'm doing different this time... how confusing.

Well, at least the rumor that I am crazy is only 1/2 true now...
I am so happy to be back to the previous version. Dp can be so amazing. I am seriously pushing the boundaries of ANY DAW right now in 9.02- looping small sections with live MIDI, tons of vox, 17 pitch correction plug ins on BGs and using DPs pitch, and no glitching on the loops when I adjust them. Imagine a 3 sec loop and Dp is triggering tons of plugs, MIDI, VIS etc, not a glitch in 9.02. I am also running the newRaven mix board and that is a blast. 9.02 seems very tight to be cept for that automation bug. DP 9.1 glitches in a variety of situations when looping. If Dp 9.1 can get its looping this good with the new pre gen, I will come forward again. Had I seen a performance improvement in 9.1 I’d be torn, but since I didn’t, Im happy back at 9.02. (I have a feeling performance improvements are file dependent so maybe the next song I make will show such improvement). Funny thing is, I am getting better improvement on the particular song I am on, in 9.02.
I will add three things here:
1) I do have to find some time, or someone else should, to duplicate a large track made with VE Pro, but instead, pull all the same VIs into DP alone and see what kind of improvement there might be in CPU use.
2) I will also have to load some recent master mixes and see how 9.1 compares in CPU use.
3) Someone at the VE Pro forum maintains DP is aware of some issues and an update is one the way. (We all knew that anyway). Whether there is an update coming to VE Pro too or not, I haven;t heard. But I think the “ball” is in play with MOTU and Vienna most likely knowing what we are all experiencing. So I am hopeful that A- pre gen gets sorted out with looping and pedal misses etc. B-Dp fixes the long awaited snap shot automation bug. C- MOTU takes my advise and adds a button at the bottom of the plug in window that allows for “realtime". It can be placed right next to the MIDI learn button. (unless of course, pre gen is made to be so sweet that switching to live is never needed again). It also might be true that some software manufacturers have to catch up with DP and update...lol..good luck with that coordination of companies.

[labman]

I just thought of an idea that could really help things. It would be AMAZING if the plug in windows had an additional icon at the bottom, (like the MIDI learn button), to be used for turning the realtime off and on in a given plug.

YES! Superb idea. And I want it NOW

[Phil O]

Just got a response to my TechLink. The post-fader plug-in issue is a known bug and is being addressed in the next release.

Phil

[David Polich]

I have verified the snap shot automation bug with a trusted source.

Again, if user does not manually tab through or enter the data in waves and other 3rd party plugs, BEFORE hitting snap shot, snap shot will write the plug-ins default data to the sequence--which means that as soon as you hit play you lose your current settings!

Copy and paste on the fly is also verified as broken. Loading a pre set and hitting snap shot also fails unless tabbing through.
One user here found that snap shot worked on his system, but without seeing what that user is actually doing, it is hard to understand how it can work for this user when it has been a long term issue and still exists on my system as well as the systems of others. If anyone finds a work around besides manually tabbing through/ and/or re-entering all plug parameters before snap shot, please post.

In the meantime- I have gone BACK to 9.02 and it has more cpu headroom and no loop glitches

I really don't get why one would copy and paste on the fly with the transport engaged. Isn't that like changing a tire while the car is moving? It strikes me as doing something DP was never designed to do in the first place. I've never done it. In fact I've never had a need for snapshot automation, ever, and I've been a Performer user since the late 80's.

Please explain why you want snapshot automation, as opposed to simply automating plug-in or VI parameters and then editing the automation lane later as needed.

9.02 may offer more headroom for you but it is just the opposite for me...way more headroom in 9.1.

[bayswater]

Please explain why you want snapshot automation, as opposed to simply automating plug-in or VI parameters and then editing the automation lane later as needed.

I look forward to TDH's reply, but I have one that's probably a lot simpler. I get the rough mix in place, then do a snapshot at the start of the sequence to get initial values set, which can then be tweaked, scaled, etc. It might be just a bad habit formed as a workaround when, for whatever reason, I wasn't able to get DP to chase parameters or figure out what to do prior to the first written automation point, and had to manually drag that point for each parameter back to the start.

[kassonica]

Just got a response to my TechLink. The post-fader plug-in issue is a known bug and is being addressed in the next release.

Phil

that is good what is not good, is how that slipped the beta tester/s... seriously