got my answer here

https://wiki.recalbox.com/en/tutorials/system/access/folders-and-ssh-commands

merci pour ton retour.

@paradadf said in USB CEC Adapter not creating ttyACM device:

@timmerman thanks for debugging it! The changes have been merged to master.

Great! Thanks @paradadf for your work.

Thanks for your answer @dh04000 !
But Recalbox seems to recognize it as a "Twin USB Joystick". If I plug the two blue adapters I have, RecalBox recognizes 4 controllers... If I map the buttons on the controller plugged in the 2nd USB port, Recalbox configures the 3rd controller. So that all seems logical. The issue seems somewhere else.

Not quite finished but this config might be of help for anyone stumbling upon this topic:

After adding n64.configfile=dummy to recalbox.conf to avoid configgen to generate the button mapping, you can copy this configuration into /recalbox/share/system/configs/mupen64/InputAutoCfg.ini:

[USB GamePad USB GamePad] plugged = True plugin = 2 AnalogDeadzone = 2096,2096 AnalogPeak = 21912,21912 Mempak switch = Rumblepak switch = mouse = False A Button = button(1) B Button = button(2) C Button D = axis(2+) C Button L = axis(3+) C Button R = axis(3-) C Button U = axis(2-) DPad D = hat(0 Down) DPad L = hat(0 Left) DPad R = hat(0 Right) DPad U = hat(0 Up) L Trig = button(6) R Trig = button(7) Start = button(8) Z Trig = button(9) X Axis = axis(0-,0+) Y Axis = axis(1-,1+)

I need to dig deeper into the AnalogDeadZone and AnalogPeak to find the best way to get the proper values.

Do not forget to delete the garbage characters on /recalbox/share/system/.emulationstation/es_input.cfg

(.emulationstation is a hidden directory!)

I‘ll share a proper mapping for it as soon as I can.

@alcartur ok, i.ve been searching a little more, it's gonna be much more complex than just adding a device id in an existing driver (which is what i had hoped so far ...)

@substring Merci pour ta réponse, mais je me suis mal fait comprendre je pense. Quand l'image de l'émulateur "déborde" de l'overlay, il faut diminuer l'image de l'émulateur pour qu'elle rentre dans l'overlay, on est d'accord.
Sauf que quand je rentre dans le menu de retroarch pour adapter justement l'image de l'émulateur à l'overlay, celui ci (l'overlay) disparaît, et il est alors difficile de centrer/déporter/étirer l'image puisqu'on ne voit pas l'overlay lorsqu'on est dans le menu retroarch.

D’où ma question: comment voir les limites de l'overlay quand on est dans le menu Retroarch?

Ma phrase est un peu lourde dans sa construction mais je souhaitais éclaircir le plus possible mon problème.

@moengel

Guten Abend und danke für die Rückmeldung.
Das Thema kannst du selber schließen, siehe meine Signatur 😉

Schönes Restwochenende