Blackmagic Forum

Hi,

I have not see anything about this issue, I apologize if it has already been raised and I missed it.

I am running Resolve version 17.0B build 27 on Windows. I have been working on a feature film using Resolve as an experiment to replace Pro Tools.

The issue I have is the following :

Sometimes, playback just stops. Although, if I go into the meters tab (see attached picture) it tells me that there is a peaking signal that does not go away when I stop.

I initially realized that it would happen a little while after I added a VST reverb on an aux (I tried different ones - Altiverb, Stratus and a waves one). So I have reluctantly using the Reverb that comes with the software.

I was fine for a while but it appeared again. The thing I did this time is I added a VST reverb directly on the file (no send). I tried to cache it but it still happens.

All the routing is correct.

Thanks in advance.

Hi,

I installed the newly released Resolve 17. The same issue happened again 20-30 min after inserting an instance of Exponential audio's Stratus on an aux track.

Anyone experience the same issue ?

Not experiencing this issue on macOS with Altiverb or Stratus and the other Exponential Audio plugins (both stereo and multichannel) are not exhibiting this behaviour.

The Loudness Meter level indication may just be a graphical issue as none of the other metering in your screenshot indicates the presence of signal.

Is any signal present on the physical outputs in this state?

You can't assume that because a third-party VST plugin appears to work, that it will do so consistently or reliably (artifact free or maintaining A/V sync, for example). Are any of these plugins explicitly qualified for Resolve? If not, beware. Rendering the audio is also no guarantee of performance.

Reynaud Venter wrote:Not experiencing this issue on macOS with Altiverb or Stratus and the other Exponential Audio plugins (both stereo and multichannel) are not exhibiting this behaviour.

The Loudness Meter level indication may just be a graphical issue as none of the other metering in your screenshot indicates the presence of signal.

Is any signal present on the physical outputs in this state?

Hi, thanks for the reply. No signal whatsoever coming from the physical output in this state.

Good to know that this does not seem to happen for mac users.

John Paines wrote:You can't assume that because a third-party VST plugin appears to work, that it will do so consistently or reliably (artifact free or maintaining A/V sync, for example). Are any of these plugins explicitly qualified for Resolve? If not, beware. Rendering the audio is also no guarantee of performance.

Hi John,

Thanks a lot for the reply. I could not get my hands of a list of plugins explicitly qualified for Resolve. I tried after reading some posts about relative VST compatibility.

On this forum I've not found anything specific enough.

Still having the same issue. Even with all VSTs removed. I can't seem to understand where is this coming from. If can load a backup that has no problem so it seems like it can work.

I am really desperate to find a solution. Resolve has some really cool features but I might have to start the project from scratch using Pro Tools if I don't fix it, which is a colossal waste of time.

Could my audio interface be at fault here ? I am using a RME Fireface UC- with up to date drivers.

New development, I realized that maybe it was the loudness metering causing the issue so I just went over to the edit tab. It was playing fine, then I went back to Fairlight and it was all good as well... I hope this trick works every time ! But it's still quite weird...

This is for anyone who runs into this same weird issue. The trick I found seems to be working.

If you find yourself in the situation highlighted in my previous posts with your Loudness meters stuck at a continuous 0db with no audio coming both into your masters and out of your physical outputs, click on the edit tab and hit play.

If you have audio now you can head back to the Fairlight tab and keep working.

If you do not have audio, restart the program. If you find it at the same state, then repeat the trick I mentioned before and you should be good to go.

I have sadly not been able to identify origin of the issue but at least there is some kind of a trick to fix it.

Hope this helps !

The issue keep coming randomly.

I think I (finally) figured out the issue.

I had 2 masters, one 5.1 and one stereo. I noticed that when the issue mentioned earlier occurred, my surround master still had signal coming in. By switching to it I and playing the Loudness meter went back to 0 and I had sound coming from the speakers.

I guess there is a bug - at least on my end - with the mixdown performed by Resolve. So I would suggest not running 2 separate masters and just using a third party mixdown plugin on your surround master.

I hope a fix can be found because I really enjoy being able to switch back and forth from the different masters and submixes.