Freezing UAD plugs with Logic Pro 7

[Disobedient]

Sorry, maybe this has been covered before, but the search function keeps timing out.

So, how´s the freezing? Fast or slow? Can I freeze as many tracks as I want to?

Thanks.

 

[UAJames]

Freezing tracks will take longer with the more DSP intense UAD-1 plugins, and everything will freeze properly, however, the outstanding issue in Logic is that it will not unload the DSP from the card once the track has been frozen (it will for any other native plugins/instruments though). So at this time it won't free up any UAD-1 resources, but you can still use it to free up CPU from some of those bigger virtual instruments or native plugins. Emagic/Apple knows of the problem, but there is no official ETA on when this will be fixed.

 

[macaroni]

So, it doesn't release the CPU resources on the UAD-1, but does it cut down on the Mac CPU resources, re sending and receiving UAD-1 signals?

 

[UAJames]

Right, the plugin is sitting there idle (like if you were to bypass it in Logic) but the DSP (UAD-1 CPU) resources are not released, so you will still see the load in the UAD-1 Meter. Everything else operates as usual.

 

[Disobedient]

What the? Dammit! This issue is enough for me to abandon the Logic sequencer.
What about Cubase SX2/ SX3? Does the unloading of DSP when freezing work there?

Thanks James!

 

[UAJames]

I belive it does, although I have not tested it specifically so I can not say *for sure*.
Can anyone with SX2/SX3 confirm that it unloads the UAD-1 DSP load (resources) from the card after a track is frozen?

 

[Disobedient]

Come on ya, I know I´m hideous but plz help me out... I luv ya´ll...

 

[jmejia]

haven't tried this yet, but a simple workaround under logic 7 would be freezing the track as usual, saving your preset somewhere useful (sub folder of your project probably?) and removing the plugin from the track when playing back. i can't think of any reason this wouldn't work, and free up 100% of the dsp you were using for the track in question.

 

[Ashermusic]

haven't tried this yet, but a simple workaround under logic 7 would be freezing the track as usual, saving your preset somewhere useful (sub folder of your project probably?) and removing the plugin from the track when playing back. i can't think of any reason this wouldn't work, and free up 100% of the dsp you were using for the track in question.

Well, I can. You cannot alter or remove any plug-ins on a frozen track which is why it is called "frozen". The solution in Logic 7, which was not available in previous versions, is to use under "Export" the "Track as Audio File" command which creates a permanent audio file to add to your Arrange page and then you can remove the track with its plug-ins.

Unfortunatley the simple fact is that in generaal presently with Logic your workflow will be better if you wait until the mixing stage rather than the compositional stage to utilize the UAD-1 plug-ins.

 

[UAJames]

Asher is correct. In Logic 7 (and Logic 6) when you freeze a track, you can no longer alter (this includes removing and instantiating) plugins or audio instruments, unless you un-freeze the track. A nice paradox don't you think

 

[akisd28]

What about Cubase SX2/ SX3? Does the unloading of DSP when freezing work there?

In Nuendo/SX3 it works with the UAD plugs. It doesn't work for the Powercore ones, though. :evil:

 

[UAJames]

Yeah, the PoCo never releases DSP from the card. Thanks for the info on SX 3/Nunedo (3?).

 

[akisd28]

Yeah, the PoCo never releases DSP from the card.

Does this have to do with the way the Powercore system is designed? Anything to do with the fixed point processing?

Thanks for the info on SX 3/Nunedo (3?).

Yes, Nuendo 3.

 

[UAJames]

Yeah, the PoCo never releases DSP from the card.

Does this have to do with the way the Powercore system is designed? Anything to do with the fixed point processing?

Thanks for the info on SX 3/Nunedo (3?).

Yes, Nuendo 3.

I don't think specifically with the fixed-point architecture, but more-so with the design of the 56k (Motorolla) chips. If my memory serves correctly, this is the same way ProTools cards function, even when the plug is bypass, it's still showing load on the chips.

Thanks for the clarification on Nuendo 3.

 

[J]

UAD Logic Freezing and Delay Compensation

Sorry to rehash this old topic but I have a problem, need help.

Due to the fact that Logic Delay Compensation doesn't work with MIDI tracks!!!! :x I have resorted back to the old UAD Track Adv and Delay Comp method of compensation.

However I have noticed that freezing tracks that have a track adv plugin seems to mess with the timing!!!! Is this just me?!? Does anyone out there have a solution?

 

[xist2005]

From the latest webzine:
\"For a while now, Logic users have not had the benefit of UAD-1 plug-ins releasing their DSP resources when they are bypassed, or when they are \"frozen\" through Logic's Freeze function. We have been working with Emagic on this issue, and as of Logic V. 7.1 and UAD-1 V. 3.9, Logic users will now be able to release the DSP of UAD-1 plug-ins when they are bypassed or frozen.\"

Is this a Tiger-only feature of it will work also on 10.3.9 & L7.1?

 

[J]

From the latest webzine:
"For a while now, Logic users have not had the benefit of UAD-1 plug-ins releasing their DSP resources when they are bypassed, or when they are "frozen" through Logic's Freeze function. We have been working with Emagic on this issue, and as of Logic V. 7.1 and UAD-1 V. 3.9, Logic users will now be able to release the DSP of UAD-1 plug-ins when they are bypassed or frozen."

Is this a Tiger-only feature of it will work also on 10.3.9 & L7.1?

Thanks xist2005. I got that webzine but the issue I have at the moment is that the timing is affected, not that the DSP resources aren't released!!

I'm just trying to get everything to run in sync. It's cool before I freeze tracks, but when I do the timing goes all screwy!!! :roll: But only when there is a Track Adv plug on the track! This is not supposed to happen! Surely!!

 

[nathandevore]

freeze problem not fixed in 3.9?

I had the understanding from the webzine article that in 3.9, the DSP from the UAD-1 would be realeased in addition to the CPU's processing when a track was frozen in Logic 7.1. I was even hoping that this would be a workaround for the AMD 8131 issue. James is now saying though that there is no ETA for fixing this problem. Am I reading the webzine article wrong?
-nathan

 

[UAJames]

When UAD v3.9 comes out, you can freeze tracks (as well as bypass UAD-1 plugins) with Logic 7.1 and have their DSP resources (as well as an host CPU when they are running) released. This is a feature added in 3.9, so if you freeze with 3.8 no resources are released.

to J,
How do you have the midi track setup? If you have midi regions on a virtual instrument track (this is the only way I am aware that you can freeze midi tracks) there should be no problems with delay compensation (ie. you shouldn't have to use track advance.

 

[J]

to J,
How do you have the midi track setup? If you have midi regions on a virtual instrument track (this is the only way I am aware that you can freeze midi tracks) there should be no problems with delay compensation (ie. you shouldn't have to use track advance.

Thanks UAJames. My post may not have been clear. My problem exists when runnung real MIDI instruments (JV2080 Korg MS2000 etc.) alongside both virtual instruments and audio tracks.

The Trk Adv-Del Comp combo works fine, until I decide to freeze a track(Audio) with a Trk Adv plug in the chain. The TIMING screws up!!! I know that it won't release dsp power yet. That I can live with until 3.9. However the timing is crucial to the music.

I am NOT trying to freeze MIDI tracks (How stoopid would that be!?) only trying to run them alongside my Audio and my Virtual instuments. In time!

Thanks for your help.

J