Hyperion vs. GIMX on Raspberry Pi
Posted: Thu Sep 29, 2022 2:01 pm
Hi all,
I have a weird issue running GIMX on a Raspberry Pi with a Logitech G920, connected to a PS4.
Let me start by saying that running only GIMX on either a Raspberry Pi 4 or Zero W works wonderful. So I am not per se plagued by the known USB lag issues.
However, I am trying to run Hyperion (basically a custom built Ambilight) on the same Pi. The TV picture is channeled into the Pi by a USB Video grabber. Again: running Hyperian by itself - no issue. The moment I run both, the key presses become a bit random (sometimes key presses are swallowed, sometimes randon key presses are added) and force feedback is basically completely gone. The second I stop Hyperian, the force feedback works again and it even repeats the last few seconds of missing feedback, as if it was stuck somehwere.
I have tried on my Pi 4 and on my Pi Zero W various operating systems (mainly bullseye and buster based) and various Hyperian and GIMX versions. It appears to be a conflict between GIMX and the V4L2 driver that Hyperian is using for the USB grabber.
Any idea how to tackle this? I could really need a nudge in the right direction?
Thanks a lot!
I have a weird issue running GIMX on a Raspberry Pi with a Logitech G920, connected to a PS4.
Let me start by saying that running only GIMX on either a Raspberry Pi 4 or Zero W works wonderful. So I am not per se plagued by the known USB lag issues.
However, I am trying to run Hyperion (basically a custom built Ambilight) on the same Pi. The TV picture is channeled into the Pi by a USB Video grabber. Again: running Hyperian by itself - no issue. The moment I run both, the key presses become a bit random (sometimes key presses are swallowed, sometimes randon key presses are added) and force feedback is basically completely gone. The second I stop Hyperian, the force feedback works again and it even repeats the last few seconds of missing feedback, as if it was stuck somehwere.
I have tried on my Pi 4 and on my Pi Zero W various operating systems (mainly bullseye and buster based) and various Hyperian and GIMX versions. It appears to be a conflict between GIMX and the V4L2 driver that Hyperian is using for the USB grabber.
Any idea how to tackle this? I could really need a nudge in the right direction?
Thanks a lot!