Artifacts on video by selecting ‘Open capture device ...’

[glvlc]

Hi, to view video from a 2018 Eachine ROTG01 FPV device I go to ‘Open capture device ...’ and then choose these settings:

1) Capture mode = DirectShow
2) Video device name = USB2.0 PC CAMERA
3) Audio device = from Default to None

The first time I make the above selections, the image on the screen shows noise and artefacts visible in the images below.



In order to display the device video output correctly, I have to repeat the selection of the above-mentioned settings for a second time each time.

The problem occurs on different versions of Windows 10 and does not occur with the ‘Camera’ app included with Windows 10.

Does anyone have any idea what this might be due to ?

[Lotesdelere]

Please open Tools -> Messages (set Verbosity to 2) before you start the playback, keep the messages window open during the whole process and then paste the full resulting log here or on Pastebin.com or on Justpaste.it if it's too long.

[glvlc]

This is the log generated when the problem occurs.

[Rémi Denis-Courmont]

Are the artifacts permanent or only at the beginning? Initial artefacts can often be caused by buffering problems.

But if they are permanent but only on first open, it is likely a bug in the device driver with little recourse from VLC side

[glvlc]

Are the artifacts permanent or only at the beginning? Initial artefacts can often be caused by buffering problems.

The artefacts are permanent, they only disappear when I close and then re-open VLC for the second time.

But if they are permanent but only on first open, it is likely a bug in the device driver with little recourse from VLC side

Then, shouldn't the problem also occur with the ‘Camera’ app included in Windows 10 ?

[Rémi Denis-Courmont]

VLC is doing the exact same with different results... The stateful part is the device driver, so that's where the bug ought to be.

[glvlc]

Maybe someone who has a recent version of the Eachine ROTG01 FPV device (mine is from 2018) can do some tests and post the results here to see if the problem occurs even with new devices with updated firmware.