Silencing VLC Messages in Background?

stonewind

Hello! I am running a Raspberry Pi 3B, Retropie Buster image. Everything is operating as expected. My one annoyance is a background error from VLC that is visible before games launch.
The errors are exactly as described here and are only apparent when video snap previews play for games:

"@roslof said in Good news regarding tearing and low EmulationStation performance on Pi 4:

@akamming said in Good news regarding tearing and low EmulationStation performance on Pi 4:
I noticed some errors on the console. Haven't noticed them before. The only change i lately did was the move to 5.4 using the kms driver. So i think it is related.
mmal: mmal_vc_component_create: failed to create component 'vc.ril.hvs' (1:ENOMEM) 
mmal: mmal_component_create_core: could not create component 'vc.ril.hvs' (1)
All works fine, dos anyone know what they mean and how to fix (or how they can be supressed, alle seems to work fine...)?
@akamming I just started tinkering with KMS and my console also displays these errors each time a video snap plays (using VLC). Like you, I'm having no visual/audio issues, but these errors appear on the console. The Interwebs were not much help. Were you ever able to find a solution?"

My question is - is there a way to hide vlc output text to the terminal with a "dev/null" command, and if so, where would you put this?

mitu

@stonewind said in Silencing VLC Messages in Background?:

My question is - is there a way to hide vlc output text to the terminal with a "dev/null" command, and if so, where would you put this?

No, sincevlc is not run as a command by EmulationStation, but as an embedded library so there's no redirection to /dev/null available. The error comes from other library used by vlc and not from vlc itself - see this issue:

The mmal errors are caused by the code seeing if it can set up HVS for fullscreen output (which it can't under KMS) and come from the userland libraries. It is arguable that VLC should know it is doomed before trying - I'll look into that.

stonewind

@mitu Thanks!

Zlutz

Hi guys!
Sorry to resurrect the old thread, but have you found the solution for this?
I fixed the aggravating intermediate screen tearing problem by switching from fkms to kms, but now I'm having those errors... I know they're not that big of a deal, but they really poke my eyes.

...I had massive tearing even with Vsync ON and double buffering - and I don't like tripple buffering because of input delay.
Switching from fkms to kms fixed it and all the games are much more responsive right now!