jellyfin-media-player
jellyfin-media-player copied to clipboard
Client is grabbing input from my Saitek Throttle
Client is grabbing input from my Saitek Throttle and have to disable it in device manager to properly play movies without it seeking by itself.
I thought there was some new 'Controls' section to disable 'gamepad' support but I cannot see it anywhere except when i connect to server with web interface.
There is a configuration folder where you can edit the input maps. You can also delete the jmpInputPlugin.js
from the extension directory to disable input mapping.
Alright, sounds like a decent workaround.
Still not sure why the web client has a 'Controls' section where you can disable 'gamepad support' (aka joystick) but in the client this isn't possible through UI. I'm not sure why this is even enabled by default to begin with on a personal computer in desktop mode.
I think this should be off by default as plenty of people have game controllers hooked to their PC.
Thanks for the response though.
Edit: I removed the file (First renamed which didn't work either) and my saitek throttle is still affecting seeking by itself.
I had a similar issue, a temporary fix is adding window.navigator.getGamepads = null;
to the end of nativeshell.js which prevents jellyfin-web from accessing the controller. Stupid but it works.
That seems to suggest that the jellyfin-web implementation is the problem. Honestly the two likely conflict…
It is from jellyfin-web, that's why removing jmpInputPlugin.js doesn't help. As soon as 10.8 is out with the option to disable gamepads it should be fixed. Pretty sure he is running the 10.8 alpha which is why he has that option in the browser.
I should make a dev build with that new web client. I think you could actually drop it in with some simple config changes.
It is from jellyfin-web, that's why removing jmpInputPlugin.js doesn't help. As soon as 10.8 is out with the option to disable gamepads it should be fixed. Pretty sure he is running the 10.8 alpha which is why he has that option in the browser.
Yea the server runs alpha 10.8.
I guess I'll wait for this to get fixed in the client as well then.