PlayStation FFmpeg Recording causes Seg Fault in RetroPie 4.0.2 (Recording Megadrive, VCS, etc still fine)

dankcushions

@RetroResolution that xmb menu is quite old now but is nice looking. it shouldn't be the default as retropie has the menu_driver set to rgui in the /all/retroarch.cfg, no? i don't know as i've been intentionally using the xmb driver for ages.

and yeah i would say your guides aren't out of date as i imagine retropie will keep using the rgui (old menu) as it's lighter on resources (although on an rpi3 i don't see any difference in game).

meleu

@dankcushions I took a look at the configure_retroarch function and there's no default setting to video_driver. I think it would be useful to set it to rgui.

RetroResolution

@dankcushions thanks for the insight - that menu being different really threw me this morning, and given the problems with recording I just assumed it was new. Glad my other guides can be left as-is!

dankcushions

@meleu you're right! hmm, interesting. perhaps the xmb will in fact be the default from now on :) i just asked in the retroarch IRC channel and apparently it's defaulted differently on different systems, so who knows when it changed.

like i said, it's fine on the pi3 but not sure about pi2 and 1.

meleu

@dankcushions said in PlayStation FFmpeg Recording causes Seg Fault in RetroPie 4.0.2 (Recording Megadrive, VCS, etc still fine):

perhaps the xmb will in fact be the default from now on

It's a bad idea for Android phones. The xmb doesn't accept input from the touchscreen...

meleu

@RetroResolution can you please paste here the output of this command:

grep video_driver /opt/retropie/configs/all/retroarch.cfg

I'm curious if it is really the default or if somehow it is explicitly xmb.

RetroResolution

@meleu hi,

the video block is as follows:

#### Video

# Video driver to use. "gl", "xvideo", "sdl"
# video_driver = "gl"

All commented out...

dankcushions

@RetroResolution @meleu i think you want the menu_driver block :)

meleu

ooops! Indeed! I mean menu_driver

@RetroResolution

grep menu_driver /opt/retropie/configs/all/retroarch.cfg

RetroResolution

@meleu hi,

I'll try to get this for you soon; having some issues since switching out sd cards a couple of times earlier today to do testing - a kernel panic on boot, and then after a few more reboot tests a 'fixing recursive fault but reboot is needed' message.

I had a kernel panic on 5th July after removing the sd to make a backup image and the re-inserting it (not on the first boot though). Oddly enough, on my Pi 2 (with the older sprung-loaded sd slot, not the Pi 3 friction slot) I'd sometimes have to re-insert the card a couple of times for it to be recognised. I have used a number of different sd cards over the last year or so.

Anyway, I'll try and get that information to you soon.

meleu

I tested on a friend's raspi3 (I don't have one) and, indeed, RetroArch defaults menu_driver to xmb on raspi3. In other words, the menu_driver line is commented and when I invoke the menu with select+x it shows this screen:

xmb

herb_fargus

@meleu I was unaware it even functioned on the pi. I can't even get it to run on my pc. (As an aside the blank squares are due to the lack of the assets folder)

meleu

@herb_fargus to avoid this confusion I've just made a PR to explicitly use rgui as the menu_driver.
https://github.com/RetroPie/RetroPie-Setup/pull/1674