Posts made by poppadum

@RadarG In the folder named megadrive (which was the name of the console in Europe)

@persichini said in [SOFT] dynquee: dynamic marquee for Recalbox:

Is there any special requirements to getting this installed and working on a Pi5?

I don't have a Pi5 to test with but it should work exactly the same as on a Pi4, as the Pi5 has two HDMI outputs.

Also what is the minimum resolution requirements for the second screen.

No particular minimum resolution as you can resize your marquee images to suit the screen you're using. If the Pi can recognise the screen it should be fine.

For testing I used an old TV with 1366x768 resolution, so if you have a spare monitor you could test with that. Most of the marquee images on the internet seem to be approx 1280x360.

@toniosj said in [SOFT] dynquee: dynamic marquee for Recalbox:

@toniosj Fixed using two graphic cards.

Ah, interesting. It's the xrandr command in /etc/X11/xinit/xinitrc that is supposed to set the screen layout. But the device names that it sees can be quite generic e.g. HDMI-A-0 and HDMI-A-1, and with two outputs of the same type on the same video card, the kernel can be a bit random when deciding which output gets which number.

There's an idea in this stackoverflow answer about using the EDID data to work out which monitor is which and a script called monitor-switch that looks potentially useful.

@toniosj On Raspberry Pi, no because the splash video is using the same framebuffer as the marquee.

On PC dynquee is started from the xinitrc when X (the graphical user interface) starts and I can't think of any way that it could start earlier.

The one way it could work is if you run dynquee on a different device to recalbox (e.g. a Pi Zero 2W), but even then you couldn't be certain that dynquee would start up faster than recalbox.

Hi @Colywobbles
I don't have either an RBGpi or RGBDual to test with but it's likely those are the reason it's not working as intended.

On a Pi 4/5 with 2 displays connected to the HDMI ports, both screens share a single framebuffer device. dynquee uses the fbv2 command to display an image on the framebuffer. This means marquee images are shown on both screens briefly when an emulator launches or exits. While a game emulator is running it writes directly to the first display so you see the game running on display 1 and the marquee image on display 2.

My guess is that the RGB devices are interfering somehow. To debug you could connect to your Recalbox via ssh and stop EmulationStation and dynquee by pasting in these commands:

es stop
/etc/init.d/S32dynquee stop

then test if you can get an image to display with
fbv2 /recalbox/share/dynquee/media/startup/startup.01.png

It could also be useful to run
ls -l /dev/fb*
and let me know what the result is.

@toniosj It's from CaisonLCD in China - model number DV190FBM.

It's a 19.1" panel with resolution 1920x360
Dimensions are 116mm(L) x 87.3mm(W) x 19mm(H)

There are now quite a few different panels available on Amazon too.

@LordIcon said in Recalbox auf NVME SSD Installieren:

Wenn ich dann aber runterfahre und die SD raus nehme sagt er im eeprom beim hochfahren er kann die NVME nicht finden. Kann mir hier jemand helfen? Oder geht Recalbox nicht "standalone" von einer NVME ohne das die SD Drinne ist?

Ich habe es nicht getestet, aber für Pi 5 soll das möglich sein. Statt das Image auf SD zu schreiben, schreib es direkt auf die NVME.

Dazu musst du möglicherweise die SSD an einen PC anschließen und den Imager benutzen, oder das Pi in PiOS booten und das Recalbox-Image auf die SSD mit dd schreiben.

Siehe auch diesen Beitrag

@daniel6984 said in [SOFT] dynquee: dynamic marquee for Recalbox:

Avec la ligne terminate_viewer = yes, il y a bien l'image des marquees que sur le crt pendant le chargement du jeux, mais rien sur l'écran lcd

Hmm

Et aussi rien sur l'écran lcd avec

viewer = /usr/bin/mpv
viewer_opts = --screen=1 --loop {file}

?

@caganimo123 said in Changing refresh rate manually?:

Can I decouple refresh rate and resolutions and pick them individually? Like 3440x1440 @60Hz

I wonder if you can set a custom mode in /boot/config.txt, something like:

hdmi_cvt=3440 1440 60 6
hdmi_group=2
hdmi_mode=87

If that doesn't work, then I would probably look at booting the Pi from a Raspberry Pi OS card and inspecting the monitor's EDID. From there you may be able to get the raw timings for a custom mode using hdmi_timings=

See

• Which values are valid for my monitor?
• hdmi_timings

@daniel6984 said in [SOFT] dynquee: dynamic marquee for Recalbox:

aucun mouvement d'image n'apparait quand ont va de droite a gauche, l'image startup reste fixe

J'ai oublié qu'il faut aussi modifier (dynquee.ini ligne 174):

terminate_viewer = yes

mais plus d'image sur le CRT

Tu vois rien sur le CRT, ni les images de marquee ni les jeux?

@daniel6984 Pour tester c'est plus facile d'accéder au cli et d'entrer

mpv --screen=2 --loop /recalbox/share/dynquee/media/startup/startup.01.png

Ou modifiez dynquee.ini lignes 169-170:

viewer = /usr/bin/mpv
viewer_opts = --screen=2 --loop {file}

@daniel6984 said in [SOFT] dynquee: dynamic marquee for Recalbox:

il a un rpi4 avec un RGB DUAL qui ce branche via les GPIO... il a voulu tester les marquees sur un écran lcd brancher en hdmi, mais les images apparaisse que sur la télévision crt

Pour le raspberry pi 4, les deux écrans HDMI partagent le framebuffer, mais il semble qu'avec un RGB Dual le framebuffer ne s'affiche que sur le CRT.

Pour Recalbox PC dynquee utilise mpv --screen=2 pour afficher les images sur l'écran 2. Pourrait-il tester si cela fonctionne avec:

mpv --screen=2 --loop <image.png>

@daniel6984 said in [SOFT] dynquee: dynamic marquee for Recalbox:

@poppadum Quand je choisis par exemple le systèmes virtuels shoot em up, il apparait bien sur le menu de navigation mais j'arrive pas a afficher le marquée, comment dois-je renommé l'image .logo.png pour qu'il apparaissent ?

Il faut nommer les fichiers <SystemId>.<quelque-chose>.png/.jpg
par exemple: actionshootemup.01.png

Liste des SystemIds pour les systèmes virtuels:

favorites
lightgun
multiplayer
action
actionplatformer
actionplatformshooter
actionfirstpersonshooter
actionshootemup
actionshootwithgun
actionfighting
actionbeatemup
actionstealth
actionbattleroyale
actionrythm
adventure
adventuretext
adventuregraphics
adventurevisualnovels
adventureinteractivemovie
adventurerealtime3d
adventuresurvivalhorror
rpg
rpgaction
rpgmmo
rpgdungeoncrawler
rpgtactical
rpgjapanese
rpgfirstpersonpartybased
simulation
simulationbuildandmanagement
simulationlife
simulationfishandhunt
simulationvehicle
simulationscifi
strategy
strategy4x
strategyartillery
strategyautobattler
strategymoba
strategyrts
strategytbs
strategytowerdefense
strategywargame
sports
sportracing
sportsimulation
sportcompetitive
sportfight
pinball
board
casual
digitalcard
puzzleandlogic
party
trivia
casino
compilation
demoscene
educative

@rliving Je crois que c'est possible. Il faut modifier le fichier de config recalbox.conf et ajouter des lignes par exemple:

apple2.ignore=1
apple2gs.ignore=1
atari2600.ignore=1
atari5200.ignore=1
atari7800.ignore=1
atari800.ignore=1
atarist.ignore=1

pour supprimer les systèmes Apple et Atari. Voir aussi https://365indies.com/recalbox-hide-systems/

Les systèmes sans jeux sont automatiquement cachés par EmulationStation. Donc si on utilise l'option de menu CACHER LES JEUX PRÉ-INSTALLÉS, seuls les systèmes sur lesquels on a ajouté des jeux seront affichés.

@leew said in [SOFT] dynquee: dynamic marquee for Recalbox:

@poppadum ok so some more playing

by un hashing this line i got the resolution to show 1920x360 but it now pushes the image to the top of the screen
framebuffer_resolution_cmd = /usr/sbin/fbset -g ${global:marquee_width} ${global:marquee_height} ${global:marquee_width} ${global:marquee_height} 16

That looks good - I get exactly the same output.

this is how a 1920x360 image is showing

Bizarre: that looks like it's taking up exactly one-third of the height which is what it would do if it thought the resolution was 1920x1080.

Could you try stopping dynquee with
/etc/init.d/S32dynquee stop
double check your framebuffer resolution with fbset
then manually displaying that image with
fbv2 path/to/your/image

You could also try with another 1920x360 image such as:
https://virginia.byf.org/wp-content/uploads/2017/03/pexels-photo-358483-1920x360.jpg

@jojo-pepette J'ai utilisé deux encodeurs de Dragonrise pour ma borne.

Pour qu'ils fonctionnent je devais connecter une bouton au connecteur "mode" et appuyez dessus une fois. Après cela, la carte encodeur a parfaitement fonctionné.

@leew said in [SOFT] dynquee: dynamic marquee for Recalbox:

@poppadum Thanks for the very detailed response and the time you have taken out of your free time to respond to me. Firstly i am a very inexperienced on the software side, but i love to learn. Unfortunately that might generate a lot more questions. I hope you don't mind and let me know if i become a pain.

No problem at all - I'll try my best to help.

I didn't know i needed to add any images, it just seemed to be working out of the box so to speak. I will look at the guide and see if i can add some images with the correct size and see if that works.

It can use scraped images as a last resort, but I always intended to use images sized roughly to my marquee screen, so I just assumed everybody else would do too.

The are some docs in English (no other languages yet but I'm happy to add them if anyone wants to translate): see the README and probably the config guide.

@leew said in [SOFT] dynquee: dynamic marquee for Recalbox:

*the pictures that should display on the marquee are shown on the main screen on and off.

On a Pi, both displays share the same framebuffer so usually the dynquee display is briefly visible on the main screen when an emulator launches or exits. A bit annoying, but we can't do much about it.

*my display is 1920x360 and i have set this up correctly

OK, that's good; just to double check, if you run the commandfbset it should confirm that the framebuffer is indeed set to 1920x360.

still has black bars top and bottom of the screen

What size of the images are you using for your marquee? 1920x360 is a common size so I suggest you start from an existing set (see e.g. the Super Pixelcade set).

To check how your images display on the marquee, stop dynquee with
/etc/init.d/S32dynquee stop
then try displaying one of your marquee images with e.g.
fbv2 /recalbox/share/dynquee/media/mame/1942.jpg (replace with a path to a marquee image).

You can experiment with the --enlarge and --ignore-aspect options, but personally I just resize all my marquee images to be 360 pixels high (my marquee is also 1920x360).

*The dynquee picture displays on the marquee for a very short time and then shows a recalbox picture with the 4 pacmen

I'm not 100% sure why that is. Make sure that in your /etc/recalbox.conf (section J) you have
system.secondminitft.enabled=0
or the line commented out.

You could also try disabling the intro video with
system.splash.length=0
(section A)

@Kaldrill There are some logs in /recalbox/share/system/logs; probably init.log is the first place to look to make sure that /etc/init.d/S50dropbear (the ssh server) is being started.

There are also logfiles in /var/log/samba (samba enables filesharing with Windows).

Also check /var/log/wpa_supplicant.log to check the wifi has connected correctly.

edit: /var/log is wiped at power off so you need to look at it while Recalbox is running; suggest connecting a keyboard and accessing the console directly.

@carqueduc I believe I have seen that before on other Linux systems. Does lsusb list the gamepad and wifi adapter when plugged in before powering on? I would also check the output of dmesg | grep usb to see if they are seen at all.

I wonder if udevadm trigger would force a rescan of usb devices?

There's also this neat idea which is to write a startup script to force the kernel to unbind then re-bind the driver from/to the relevant device IDs.