Reproduceable: Render time 500x longer if SR is differnt

In DRS 19, if I have my audio interface set to 44.1khz samplerate and I attempt a render of a project at 48kHz, instead of taking 14 secs, the render time balloons out to 4+ hours.

This is a clear and repeatable bug. Please contact me for more details on how to reproduce. We must get this solved. The offline render process should not be engaging audio hardware.

All the best,
Dax.

Sounds like the kind of thing where the devs would benefit from the logs and a drp or dra.

It's not a crash, so I'm not sure logs are generated.

It's not a crash, so I'm not sure logs are generated.

The logs are generated when in Resolve you click Help>Create Diagnostics Log on Desktop. Those are files generated from internal MacOS logs. They contain lots of debugging information, even for cases where Resolve does not crash.

However, the most important thing is a portable replication scenario. Without that, it is often difficult to fix the problem.

All you mentioned so far is "audio interface set to 44.1 Khz and render project at 48 Khz." If it were just mixed audio sample rates, people would be hitting this every day. What is "audio interface?" Is that hardware? Does it have drivers? Is this a Mac or Windows machine? Does it happen without the audio interface hardware (whatever that is)?

Hi Joe,
Thanks for your interest.

I run a professional mastering (music) studio. I have submitted all of the information in the crash logs as it is causing crashes as well.

But for completeness, audio interface is RME UCX externally clocked via wordclock from an external clock.
(When I need to change SR, I get up, walk over to the master clock and turn the front panel knob.)

Thanks for your interest. I run a professional mastering (music) studio. I have submitted all of the information in the crash logs as it is causing crashes as well. But for completeness, audio interface is RME UCX externally clocked via wordclock from an external clock. (When I need to change SR, I get up, walk over to the master clock and turn the front panel knob.)

Resolve has always been made to run internally at 48kHz/24-bit, so if you use anything else as a source, you're going to have to go through Resolve's SRC (sample rate converter) on the way out. I've never seen it take lots more time to do something this simple, but I don't doubt you're seeing a malfunction.

What is the actual source material? What specific format is it? We generally find if we use WAV files, it's all pretty tame in terms of audio and render time. But we do make an effort to keep them all at 48kHz/24-bit, and we avoid MP3s and other kinds of compressed files whenever possible.