MOTUnation.com

Michael Canavan wrote:That's really great it came out today!
One thing I'm curious about is if the new improved time stretching will be applied to Beat Detection??? That's not mentioned but it should be easy enough to figure out whether it has or not as it would likely be able to be switched between new and old.

I won't be able to instal and check until later this evening, if anyone wants to poke around and see what's going on there that would be cool!

Beat Detection hasn't changed but the time stretch used for any tempo changes is now done with ZTX.

Dave

HCMarkus wrote:

Michael Canavan wrote:

bayswater wrote: Maybe not completely but I'm seeing no effect at all.

BTW: Where do you see something other than bypass?

Sorry not near a computer right now, but the only place I know where you can disable a plug in or track is in the mixer window...

Disable track using round blue button in Tracks Window.

Correct, you can disable a track in the Track window. You can also disable a track in the drop down menu at the bottom of the channel strip in the Mixer.

But, we're not taking about disabling a track. We're talking about disabling a plugin. The Effects performance window shows the CPU load from an Effect, not a Track or Channel Strip.

As per the manual, you "disable" a plugin, you bypass it in the Effect Window, or in the Insert slot in the Mixer, suggesting that disabling and bypassing are the same thing in DP. I don't see anywhere else to disable a plugin that isn't the same action as bypassing it.

Back to my original question, shouldn't we see some sort of reduction in CPU when a plugin is bypassed?

bayswater wrote: Back to my original question, shouldn't we see some sort of reduction in CPU when a plugin is bypassed?

No. And the reason is that you need to be able to bypass and unbypass a plug-in on the fly - with automation for example. In order to do that the plug-in has to be in line and running.

The only way to completely bypass a plug-in is to disable the track (ENA button) or set the output of the track to none.

Dave

Just messing about with the time scaling, which is what's most important to me about DP 9.5, since I spend a lot of time fitting music to film....

I took one piece that the Mont Alto Motion Picture Orchestra recorded last June (Andante Pathetique, by Gaston Borch), and scaled it using the <Region: Scale Time> command to 85% and 110% of the original, which is about as extreme as you can take a classical string sound without it getting really weird in the vibrato speed.

Links to the results as mp4 files are at the end of this post.

This is a multi-track recording (two stereo tracks for room and piano, plus four mono instrument tracks for violin, clarinet, trumpet, and cello), and it is spliced together from a number of takes so you're hearing a bunch of soundbites with crossfades. There is some volume automation, and a touch of reverb added to the "Master" mix.

The first thing I noticed after scaling is that the cross-fades were all removed. Since this was just a test, I used control-F to recreate the cross-fades, but a couple of them still failed (you can hear it occasionally as a sudden, short dropout in either of the scaled takes). On the screen, those fades are drawn in very dark color showing that there was not enough "overlap" between the two sound bites to create a fade. So DP must clip the underlying soundbite to whatever "shows on top," at least sometimes. I'll always want do a "merge sound bites" before trying this in a real project.

The volume automation seems to be scaled in tandem with the soundbites.

The issues I have are mostly with the violin vibrato sounding unnaturally fast at 85%, which no algorithm can fix. So, I'm very happy with the added functionality, except for the cross-fade issue.

Previous to this, scaling in DP would give me weird fluttery sounds and low thumps that made the audio unusable (I've put an example of that below too), so I had to do a complicated round trip through MachFive's IRCAM algorithm to do this kind of scaling well. Thanks, Motu! This will save me a lot of time.

Andante Pathetique 100%: https://www.dropbox.com/s/rn04rp0d16ha6 ... 0.mp4?dl=0

Andante Pathetique 85%:
https://www.dropbox.com/s/kfodw18mnzi4n ... 5.mp4?dl=0

Andante Pathetique, 110%
https://www.dropbox.com/s/rn04rp0d16ha6 ... 0.mp4?dl=0

As a comparison, this is what it sounds like if I use <Region: Scale Time> in DP 9.13 to scale the Andante Pathetique to 85% (this clip is shortened, who wants to listen to more than a few seconds of this):
https://www.dropbox.com/s/tjd98k2qw1jcw ... 5.mp4?dl=0

On my way to download right now...

GREAT news. Thanks MOTU!

magicd wrote:

bayswater wrote: Back to my original question, shouldn't we see some sort of reduction in CPU when a plugin is bypassed?

No. And the reason is that you need to be able to bypass and unbypass a plug-in on the fly - with automation for example. In order to do that the plug-in has to be in line and running.

The only way to completely bypass a plug-in is to disable the track (ENA button) or set the output of the track to none.

Dave

All of this, which is no different in any DAW is the reason people want VST3, but of course plug ins could have huge issues with giving cpu back when resting etc. I would guess this is why most DAWs don't support VST3 and why there are still plug ins that don't either. I'm curious as to whether AU can do this now and whether any developers have implemented it in their plug ins?

magicd wrote:

bayswater wrote: Back to my original question, shouldn't we see some sort of reduction in CPU when a plugin is bypassed?

No. And the reason is that you need to be able to bypass and unbypass a plug-in on the fly - with automation for example. In order to do that the plug-in has to be in line and running.

The only way to completely bypass a plug-in is to disable the track (ENA button) or set the output of the track to none.

Dave

Thanks.

I'm running DP 9.5 on both Mac and Windows. I opened (a copy of) my latest project on the windows box and got right back to work. No issues. Haven't tried out the mac side yet. Thanks for a great update. Love the Effects Performance insights.
Rip

dix wrote:One really cool thing, that I don't think is documented, is that you can launch any plugin or VI in the sequence right from the Effects Performance window. Very handy!

Stating the obvious after exploring this tip, clicking on a plug-in name in the Effect Performance list opens that plug-in window. A new plug-in can can be selected from the plug-in selection menu. Very cool!

Nice!
I don't show up for a couple of weeks, and now I read this GREAT news!

I haven't seen any mention about the handling of VIs. Do we have now a global option to run them in real time by default, or that hasn't changed?

Do we have now a global option to run them in real time by default, or that hasn't changed?

No change. No global run-plugins-real-time setting.

magicd wrote:Hey everyone, please allow me to clear this up. That link is a draft page that we haven't officially published. I'm not sure how it was found. However, there is a DP update on the way soon and I will let all of you know when it's live at motu.com/download. So please stay tuned!

Dave

Question Magic Man.....

When we get the 9.5 update, should we also check other updates like MOTU audio installers and MIDI etc, or does 9.5 update audio and MIDI drivers to latest versions?

Thanks, looking forward to no longer using iZotope RX for pitch and time work..we’ll see....

Great question! I wouldn't have thunk to do that...

Audio & MIDI installers updated July 31, 2017.

Lazy me...
Has anyone compared the new time/pitch to Melodyne 4 ?
esp. the ability to do it with multiple tracks ?
Thanks and best regards

Klaus

Klaus wrote:Lazy me...
Has anyone compared the new time/pitch to Melodyne 4 ?
esp. the ability to do it with multiple tracks ?

I don't have Melodyne, but DP 9.5 does work with a selection of multiple tracks, though it loses cross-fades (see my post above).