Rendering in Acid Pro 10

Brackets wrote on 3/30/2022, 2:16 AM

My question is around project rendering.
Basically it does not work. When starting, the % stays at zero, while the estimated completion time increases infinitum. I then cancel the process which then freezes the program.
Similarly ‘Real-Tim Render’ does not work either. It estimates a time far longer than the project itself, and then promptly stops when the project has finished playing. The resulting file is useless.
Please help!

Comments

Brackets wrote on 3/30/2022, 3:44 AM

Also tried 'Bypass All Audio FX' for what it's worth. Still the same result.

SP. wrote on 3/30/2022, 4:14 AM

@Brackets Does it work if you run ACID as administrator by right clicking on the program icon?

Brackets wrote on 3/30/2022, 4:26 AM

@Brackets Does it work if you run ACID as administrator by right clicking on the program icon?

No. Makes no difference unfortunately.

SP. wrote on 3/30/2022, 10:18 AM

@Brackets If it stays at zero % there is something blocking it from writing the file to your drive. Could be a firewall. Disable it temporarily.

PATIENT-X wrote on 3/30/2022, 11:49 AM

@Brackets

Hello, Welcome

I read in a post, "Try rendering with all plugins disabled to isolate which plugin is causing you an issue, if you are using plugins"

Stephen

Forum Moderator

Brackets wrote on 4/1/2022, 4:12 AM

@Brackets

Hello, Welcome

I read in a post, "Try rendering with all plugins disabled to isolate which plugin is causing you an issue, if you are using plugins"

Stephen

Forum Moderator

Yeah, I think I have have seen the same thread that you did. So that was one of the first things I tried. No dice however.

Brackets wrote on 4/1/2022, 4:17 AM

So the washup is good news / bad news.

After trying all suggestions, and a thousand random other things, it still won't let me render. Just hangs on 0%.

However, I did find an answer as to why it wasn't letting me real-time render. Basically, there was a mismatch in sample rates with the driver and the project. For some reason (using another program) the driver reset itself to a different sample rate. Once this was corrected, it seemed to work OK.

PATIENT-X wrote on 4/1/2022, 7:42 AM

@Brackets

Well at least you discovered a mismatch.

Stephen

Forum Moderator