UAD-1 v4.7.1 and SONAR and Sound Forge and err=3

[erlijohn]

They have fixed the munching problem on my SONAR 6 setup, but introduced a lot of pops and cracks in my export-mixdowns. And the err=3 trouble are still present in Sound Forge v9.

 

[Emusic1]

They have fixed the munching problem on my SONAR 6 setup, but introduced a lot of pops and cracks in my export-mixdowns. And the err=3 trouble are still present in Sound Forge v9.

Bummer, I was just thinking of trying out 4.7.1 after experiencing the err=3 in Cubase with 4.7.0 drivers and having to revert back to 4.6..

thanks for the heads up... really hope they get this fixed for real next time..

 

[imdrecordings]

They have fixed the munching problem on my SONAR 6 setup, but introduced a lot of pops and cracks in my export-mixdowns. And the err=3 trouble are still present in Sound Forge v9.

What are your buffer settings?
Are you doing real time bounces?

 

[WWANDERSEN]

Same problem for me in Sonar 5.2. With the \"Sonar compatibility mode\" checked, CPU munching seems to be reduced, but I can't do a mixdown/export/bounce/freeze because of extremely bad stuttering and pops. I mean REALLY bad....unusable.

Uncheck the \"Sonar\" mode, then I can mixdown. But with it unchecked, I get random dropouts, pops and stuttering when playing the project in Sonar.

There are others over in the Cakewalk Sonar forum experiencing this with 4.7.1 and Sonar. Looks like UA will need a 4.7.2 update quick.

 

[billybk1]

Uncheck the "Sonar" mode, then I can mixdown. But with it unchecked, I get random dropouts, pops and stuttering when playing the project in Sonar.

I can also confirm the gapping issue in rendered files with the SONAR mode enabled. I believe UA added the SONAR Compatibility Mode to specifically deal with the native CPU munching during playback. Native CPU munching is not an issue when doing an export of a project. So the modus operandi should be:

1) For those experiencing the native CPU munch, during playback, keep the SONAR Compatibility Mode enabled

2) When rendering, simply disable this option, from the UAD-1 Performance Meter.

It only takes a moment to change the option. If you are mixing and want to do a quick render, just deselect the option, from the UAD-1 PM, after you stop playback and then go tho the SONAR Export dialog. After the render simply re-enable the option and continue mixing. You never have to close SONAR or the project.

I suppose UA should have put in the 4.7.1 readme, that the new SONAR Compatibility Mode is to be used during playback/mixing to alleviate native CPU munching just to avoid any confusion.

I am just thankful there is now a way to finally get rid of the native CPU munching when playing/mixing a project. This is something I have been asking for since 2003, when I got my first UAD-1 card and SONAR 2.2 was current version. Better late than never I guess.

 

[granted]

For those wondering about 4.7.1 - It fixed my err=3 issues in Ableton Live 6.0.7 and Cubase Studio 4.0.3.
I don't use Sonar.

But I now get \"err=3\" messages in Sony Sound Forge 9c. Dang.

 

[SteveD]

My munching issues are slight but still there as the mixing session progresses. Still, I rarely need to do anything about it.

I have never had any pops or crackles on my system when mixing, bouncing, or exporting with UAD-1 cards. *None*. Never needed to disable fastbounce. So reliable, I don't even need to check bounces unless they're finals going to a Mastering engineer or a duplication plant.

However, I haven't been able to use any UAD-1 update since 4.5:

____________________________________________________________

The installer sees the hardware, finds the drivers, and installs them properly. They just don't work. Won't communicate with the hardware.

I tried to install 4.6 and had the same \"Unable to communicate with UAD hardware\" problem so I reinstalled 4.5 with no problem at all.

I was hoping to see if 4.7 would correct the occasional munching I'm seeing on my system... but I guess I'm forever stuck at v4.5.

It's shame too... 'cause I was ready to end my boycott on all new UAD-1 plugins once all compatibility issues with SONAR were resolved.

I've got 3 cards in a 7 slot Magma (ribbon cable) with a 4th card on it's way. I know some will advise me to try them without the Magma. I will. When I have the time. Such a hassle.

Oh well. Back to v4.5. I'll spend my money on something else. :|

BTW... I'm not alone:

Search on \"Unable to Communicate\"

 

[erlijohn]

Another possible way to solve problems

I'm running an P4 3Gz HT pros on SONAR 6.2.1 with one UAD-1 card with v4.7.1. All CPU munching is gone, but I have had trouble with gaps when exporting and freezing tracks when Fast bounce is turned on. I got severe pops and cracks with the new SONAR compatible mode running in UAD-1.
Well: Here is what I did:
1. I turned off multiprocessing in SONAR.
2. I turned on SONAR compatible mode in UAD-1.
3. I turned on Fast bounce when I mixed down.
The result: Not a single glitch.

Just to let you know about my experiences.

 

[Matt Hepworth]

What are your buffer settings?
Are you doing real time bounces?

Unfortunately, SONAR doesn't do real time bouncing.

On a small project fast bounce is fairly fast and unchecking fast bounce goes roughly real time.

On any of the projects I work on fast bounce goes a little slower than real time and unchecking fast bounce means a 15 minute render.

Real time would sure be nice.

 

[ranchdip]

I usually don't see much difference in \"fast bounce\" and normal. I don't \"Fast Bounce\" anymore in Sonar. I fixed all of my rendering issues (skips, pops, etc.) by disabling \"Fast Bounce\" in Sonar.

 

[Matt Hepworth]

With my pretty modern dual core and such, my Fast Bounce runs about 4 minutes per song. Unchecking it is 12-15 minutes. I push my system hard regularly.

 

[ranchdip]

I could be wrong but I think it has nothing to do with the CPU usage in your computer but what CPU usage you are on your UAD's. With my 4 UAD-1's in my magma running 80-90% UAD-1 CPU usage and 20% on my computer I have to deselect \"Fast bounce\" to keep from getting the occasional skips.

 

[Matt Hepworth]

I don't have that problem, but I've seen plenty of reports from people who do, yes, regardless of CPU.

I assumed that your \"I usually don't see much difference in \"fast bounce\" and normal.\" was referring to time of bounce, but you must have been referring to quality of bounce.

 

[ranchdip]

Well, I was actually talking about time. I guess I've never sat down and timed it. I'm usually walking away from the computer for a few min's while it's rendering.

 

[SteveD]

Okay... Finally fixed this bugger.

UA FINALLY responded to a phone call from LAST WEEK and left a message indicating I needed two registry fix files. But rather than LISTEN to my original voice mail and just send the necessary fix files to me... the message indicated I needed to call them back. RIGHT. Week-end... they're closed... no support.

I saw a fellow UAD-1 user post that he had received these files from UA... so I sent him a note asking if he'd share. He did. Problem's fixed.

Now I can report... just like many others here... that the UAD-1/SONAR-CPU-Munching bug is squashed. I can also confirm that multi-processor bounces and exports are full of G-A-P-S. One click of the Multi-processor check box in SONAR to turn it off before bounces cures it.

I'm sure UA will patch that.

Until then... it's really really close to PERFECT!

4 cards in a Magma here.

 

[Eddie Macarthur]

my uad1 now gives error and crash (plus corrupted graphics) with soundforge 9 also...
Ed

 

[NuSkoolTone]

Funny, I used to NEVER have this issue in Nuendo. Now occasionally I DO!

In UA's defense my DAW did have a hiccup while I was multitasking this past week and hasn't been as stable since.