Blackmagic Forum

I'm using 17b8 on linux with AMD card and I can't see any waveform in the fairlight tab.

This is what it looks like :



I can hear it and scrub through it. But that's about it.

And this is in the "Edit" tab, where it shows up properly.




(don't pay attention to the source material, just random files I found on the drive while kicking the tyres on 17b8).

I've had an issue the last few betas where a slight movement of my mouse scrolls Fairlight in a weird way where my clips are offscreen. Then a slight movement again and they're back. Anything like that happening?

smunaut wrote:I'm using 17b8 on linux with AMD card and I can't see any waveform in the fairlight tab

System spec? viewtopic.php?f=21&t=90190

Are you running RHEL or CentOS 7.3 with the BMD supplied ISO or another Linux variant with the Resolve installer from the support page?

The Resolve ISO only supports Nvidia cards and while some Linux users are successfully running with AMD cards, the issue illustrated is common with AMD drivers on Linux.

@wfolta: No, the track is there, I can see the cursor changing shape when I hover above it. Also I just noticed that if I drag the track, it appears, with the waveform ... while I am dragging it and then disappears when I let go. So it's really just drawn with the wrong alpha or the wrong color or composite mode or something ...


@Reynaud Venter:

System is running Ubuntu 20.04 with 17b8 installed using the installer.
32G RAM, Ryzen 7 3700X CPU.

Tried with both a AMD RX570 card using AMD drivers 20.45 (both GL/CL) -> Result as described above
Also tried same system with NVidia RTX2070 Super with 460.32.03 drivers -> Works as expected, both in CUDA and OpenCL mode.

smunaut wrote:Tried with both a AMD RX570 card using AMD drivers 20.45 (both GL/CL) -> Result as described above
Also tried same system with NVidia RTX2070 Super with 460.32.03 drivers -> Works as expected, both in CUDA and OpenCL mode.

Confirms that this is an AMD driver issue.

On 17b8 Windows, some video files are not showing an audio waveform in Fairlight. They also aren't showing in Edit or Cut.

However, I can hear them and in Fairlight I do see their waveform in the Audio Scroller display.

The problem files are aac stereo 44k, but have audio only encoded on the left channel.

Still have the issue in beta 9.

Is anyone else having this issue ?

Or another way : Does anyone see the waveform in fairlight when using an AMD card on Linux ?

Using 17b9 on a CentOS 8.3 install with the AMD amdgpu-pro-20.45-1188099-rhel-8.2.tar driver and an RX580 card, I see the same as your screen shot above. On the Fairlight page, the meters are working and audio is playing. But the audio track area is solid black.

One possible work around is that if you enable the Scroller option to show audio waveforms, those are working at the bottom of the page. Less than ideal, but better than nothing. But not much better, since you can only put FX on at the track level. And you can't visually adjust the clip levels.

Thanks for testing Dwaine.

At least now I know it's not something specific to my setup so hopefully it'll get fixed in a subsequent beta.

Is this similar to the fairlight blackhole issue mentioned here and fixed by h33p?

blackhole issue:
viewtopic.php?f=21&t=127060

fix:
viewtopic.php?f=21&t=56878&start=1850#p695301
https://github.com/h33p/resolve-amdocl-fix

I was actually using that mod to run DVR16 on my system. That was needed for it to run at all, so I never saw that "blackhole" in 16 since I couldn't run 16 at all without that "fix".

But with DVR17 that doesn't work at all. You need the full proprietary stack OpenGL + OpenCL, you can't get away with just the OpenCL component anymore because CL/GL interop is required.

So I just tested on DVR16 and the same issue is present there :/
That definitely used to work when I was using the OpenSource AMD drivers. (Had to switch to the official AMD ones for DVR17 to start at all).

So I suspect DVR is doing something not quite right and rely on some "implementation dependent" behavior of OpenGL that just happens to work on some driver and not others in the fairlight tab.
Given it works fine in other tabs and seems easily reproductible, it should be easy to find and fix if a dev could take a look at it ...

It's being looked into.

@Dwaine : \o/ Great, thanks for the feedback.

Still not working in both 17.0 release and the latest 17.1 released today

Correct. The issue with AMD is still in the queue.

This issue should now be fixed in the just released 17.1.1 version.

@Dwaine : I confirm the fairlight tab now shows up fine for me with AMD card/driver !

Thanks for the heads up.