Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?

DjDiabolik

My setup it's Pi4 4GB Labist kit.
SD Sandisk 32GB
Usually i run an update every one or two week... currently i can see it's 4.7.13.
Wrong information wrote it.. EDIT right now ~~ES 2.9.2RC~~ EmulationStation it's 2.9.6RP.

This time last night i did all the various updates... i see i have obtain about 27 Component of OS updated (like kernel and bootloader) and after that i don't know exactly how many and which cores have been updated.
i can say definitely lr-mame2003-plus infact i need to fix my roms collection whit clrmamepro :)

Anyway when i see the message of confirmation "All package as been updated" or somethings similar since the 27 system components had been updated i have made a full reboot of my Pi4.
On reboot I then played for a couple of hours... and i have and I started to notice this thing about the audio glitching/struttering about every 3 or 4 minutes on some lr-gambatte games.
It doesn't look like a drop in fps..... only the audio track seems to hesitate and sometime it seems to skip somewhere like it's cutted out some frames.

I have tryed a lot of GB roms and apparently this is append on all games...... after that i have also tryed to change the core. I have tryed some lr-fceumm and it happens here too.

Could it happen that some update has created this problem/little trouble ?

EDIT
I don't have idea if this need or not... but right now i have tryed this from SSH:

pi@retropie:~ $ sudo apt update && sudo apt full-upgrade
Get:1 http://raspbian.raspberrypi.org/raspbian buster InRelease [15.0 kB]
Hit:2 http://archive.raspberrypi.org/debian buster InRelease
Fetched 15.0 kB in 1s (16.0 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
pi@retropie:~ $

have any core libretro changed ? how can I "investigate" about it ?

dankcushions

Too investigate more or less any issue we need all the info requested in https://retropie.org.uk/forum/topic/3/read-this-first - use a particular game example, supply the verbose log, etc.

DjDiabolik

@dankcushions said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

Too investigate more or less any issue we need all the info requested in https://retropie.org.uk/forum/topic/3/read-this-first - use a particular game example, supply the verbose log, etc.

Now...... use this particular game..... problably the purpose log it's this ?

Parameters: 
Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-gambatte/gambatte_libretro.so --config /opt/retropie/configs/gb/retroarch.cfg "/home/pi/RetroPie/roms/gb/C/Catrap (USA).zip" --verbose --appendconfig /dev/shm/retroarch.cfg
[INFO] RetroArch 1.9.4 (Git c226bd8)
[INFO] === Build =======================================
[INFO] Capabilities:  NEON VFPv3 VFPv4
[INFO] Built: May 31 2021
[INFO] Version: 1.9.4
[INFO] Git: c226bd8
[INFO] =================================================
[INFO] [Input]: Found input driver: "x".
[INFO] [Core]: Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-gambatte/gambatte_libretro.so"
[INFO] [Overrides]: No core-specific overrides found at "/home/pi/.config/retroarch/config/Gambatte/Gambatte.cfg".
[INFO] [Overrides]: No content-dir-specific overrides found at "/home/pi/.config/retroarch/config/Gambatte/C.cfg".
[INFO] [Overrides]: No game-specific overrides found at "/home/pi/.config/retroarch/config/Gambatte/Catrap (USA).cfg".
[INFO] [Environ]: GET_CORE_OPTIONS_VERSION.
[INFO] [Environ]: GET_LANGUAGE: "0".
[INFO] [Environ]: RETRO_ENVIRONMENT_SET_CORE_OPTIONS_INTL.
[INFO] Core requested VFS version >= v1, providing v3
[INFO] [Remaps]: Remap directory: "/opt/retropie/configs/gb/".
[INFO] [Overrides]: Redirecting save file to "/home/pi/RetroPie/roms/gb/C/Catrap (USA).srm".
[INFO] [Overrides]: Redirecting save state to "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state".
[INFO] [Environ]: GET_LOG_INTERFACE.
[INFO] [Environ]: PERFORMANCE_LEVEL: 4.
[INFO] [CONTENT LOAD]: Loading content file: /home/pi/RetroPie/roms/gb/C/Catrap (USA).zip#Catrap (USA).gb
[INFO] Did not find a valid content patch.
[INFO] [CONTENT LOAD]: CRC32: 0xadb96150
[INFO] [Environ]: GET_CAN_DUPE: true
[INFO] [Environ]: GET_RUMBLE_INTERFACE.
[libretro INFO] Rumble environment supported.
[INFO] [Environ]: SET_INPUT_DESCRIPTORS:
[INFO] [Environ]: SET_PIXEL_FORMAT: RGB565.
[INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
[INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
[libretro INFO] [Gambatte]: Got internal game name: CATRAP.
[INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
[INFO] [Environ]: SET_MEMORY_MAPS.
[INFO]    ndx flags  ptr          offset   start    select   disconn  len      addrspace
[INFO]    001 M1A1bc 0x2284a80 00000000 0000C000 FFFFF000 00000000 00001000 
[INFO]    002 M1A1bc 0x2285a80 00000000 0000D000 FFFFF000 00000000 00001000 
[INFO]    003 M1A1bc 0x22a3218 00000000 0000FF80 FFFFFF80 00000000 00000080 
[INFO]    004 M1A1bc 0x2280a80 00000000 00008000 FFFFE000 00000000 00002000 
[INFO]    005 M1A1bc 0x22a3098 00000000 0000FE00 FFFFFFE0 00000000 000000A0 
[INFO]    006 M1A1bC 0x2278a80 00000000 00000000 FFFFC000 00000000 00004000 
[INFO]    007 M1A1bC 0x227ca80 00000000 00004000 FFFFC000 00000000 00004000 
[INFO]    008 M1A1bc 0x22a3098 00000100 0000FF00 FFFFFF80 00000000 00000080 
[INFO] [Environ]: SET_SUPPORT_ACHIEVEMENTS: yes.
[INFO] [SRAM]: Skipping SRAM load..
[INFO] Version of libretro API: 1
[INFO] Compiled against API: 1
[INFO] [Audio]: Set audio input rate to: 32917.50 Hz.
[INFO] [Video]: Video @ 1920x1080
[INFO] [Video]: Starting threaded video driver ...
[INFO] [DRM]: Found 1 connectors.
[INFO] [DRM]: Connector 0 connected: yes
[INFO] [DRM]: Connector 0 has 25 modes.
[INFO] [DRM]: Connector 0 assigned to monitor index: #1.
[INFO] [DRM]: Mode 0: (1280x720) 1280 x 720, 60.000000 Hz
[INFO] [DRM]: Mode 1: (1920x1080) 1920 x 1080, 60.000000 Hz
[INFO] [DRM]: Mode 2: (1920x1080) 1920 x 1080, 59.940201 Hz
[INFO] [DRM]: Mode 3: (1920x1080i) 1920 x 1080, 30.000000 Hz
[INFO] [DRM]: Mode 4: (1920x1080i) 1920 x 1080, 29.970100 Hz
[INFO] [DRM]: Mode 5: (1920x1080) 1920 x 1080, 50.000000 Hz
[INFO] [DRM]: Mode 6: (1920x1080i) 1920 x 1080, 25.000000 Hz
[INFO] [DRM]: Mode 7: (1920x1080) 1920 x 1080, 30.000000 Hz
[INFO] [DRM]: Mode 8: (1920x1080) 1920 x 1080, 29.970100 Hz
[INFO] [DRM]: Mode 9: (1920x1080) 1920 x 1080, 24.000000 Hz
[INFO] [DRM]: Mode 10: (1920x1080) 1920 x 1080, 23.976080 Hz
[INFO] [DRM]: Mode 11: (1360x768) 1360 x 768, 60.015163 Hz
[INFO] [DRM]: Mode 12: (1280x720) 1280 x 720, 59.940201 Hz
[INFO] [DRM]: Mode 13: (1280x720) 1280 x 720, 50.000000 Hz
[INFO] [DRM]: Mode 14: (1024x768) 1024 x 768, 60.003841 Hz
[INFO] [DRM]: Mode 15: (800x600) 800 x 600, 60.316540 Hz
[INFO] [DRM]: Mode 16: (720x576) 720 x 576, 50.000000 Hz
[INFO] [DRM]: Mode 17: (720x576i) 720 x 576, 25.000000 Hz
[INFO] [DRM]: Mode 18: (720x480) 720 x 480, 60.000000 Hz
[INFO] [DRM]: Mode 19: (720x480) 720 x 480, 59.940060 Hz
[INFO] [DRM]: Mode 20: (720x480i) 720 x 480, 30.001110 Hz
[INFO] [DRM]: Mode 21: (720x480i) 720 x 480, 29.970030 Hz
[INFO] [DRM]: Mode 22: (640x480) 640 x 480, 60.000000 Hz
[INFO] [DRM]: Mode 23: (640x480) 640 x 480, 59.940475 Hz
[INFO] [DRM]: Mode 24: (720x400) 720 x 400, 70.081665 Hz
[INFO] [GL]: Found GL context: kms
[INFO] [GL]: Detecting screen resolution 1920x1080.
[INFO] [EGL] Found EGL client version >= 1.5, trying eglGetPlatformDisplay
[INFO] [EGL]: EGL version: 1.4
[INFO] [EGL]: Current context: 0xaf23ace0.
[INFO] [KMS]: New FB: 1920x1080 (stride: 7680).
[INFO] [GL]: Vendor: Broadcom, Renderer: V3D 4.2.
[INFO] [GL]: Version: OpenGL ES 3.1 Mesa 19.3.2.
[INFO] [GL]: Using resolution 1920x1080
[INFO] [GL]: Default shader backend found: glsl.
[INFO] [Shader driver]: Using GLSL shader backend.
[WARN] [GL]: Stock GLSL shaders will be used.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GLSL]: Found GLSL vertex shader.
[INFO] [GLSL]: Found GLSL fragment shader.
[INFO] [GLSL]: Linking GLSL program.
[INFO] [GL]: Using 4 textures.
[INFO] [GL]: Loaded 1 program(s).
[INFO] [udev]: Pad #0 (/dev/input/event3) supports force feedback.
[INFO] [udev]: Pad #0 (/dev/input/event3) supports 16 force feedback effects.
[INFO] [Joypad]: Found joypad driver: "udev".
[INFO] [Font]: Using font rendering backend: stb-unicode.
[INFO] [Video]: Found display server: null
[INFO] [ALSA]: Using floating point format.
[INFO] [ALSA]: Period size: 768 frames
[INFO] [ALSA]: Buffer size: 3072 frames
[INFO] [ALSA]: Can pause: no.
[INFO] [Display]: Found display driver: "gl".
[INFO] [Font]: Using font rendering backend: stb-unicode.
[INFO] [Font]: Using font rendering backend: stb-unicode.
[INFO] [Font]: Using font rendering backend: stb-unicode.
[INFO] [Playlist]: Loading history file: [/opt/retropie/configs/gb/content_history.lpl].
[INFO] [Playlist]: Loading history file: [/opt/retropie/configs/gb/content_music_history.lpl].
[INFO] [Playlist]: Loading history file: [/opt/retropie/configs/gb/content_video_history.lpl].
[INFO] [Playlist]: Loading history file: [/opt/retropie/configs/gb/content_image_history.lpl].
[INFO] [Playlist]: Loading favorites file: [/opt/retropie/configs/gb/content_favorites.lpl].
[INFO] [KMS]: New FB: 1920x1080 (stride: 7680).
[INFO] [KMS]: New FB: 1920x1080 (stride: 7680).
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "RAM", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: Saving state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [State]: File already exists. Saving to backup buffer ...
[INFO] [State]: Loading state "/home/pi/RetroPie/roms/gb/C/Catrap (USA).state", 26888 bytes.
[INFO] [Core]: Content ran for a total of: 01 hours, 33 minutes, 43 seconds.
[INFO] [Core]: Unloading game..
[INFO] [Core]: Unloading core..
[INFO] [Core]: Unloading core symbols..
[INFO] [Core Options]: Saved core options file to "/opt/retropie/configs/all/retroarch-core-options.cfg"
[INFO] Threaded video stats: Frames pushed: 336864, Frames dropped: 154.
Plain ROM loaded.
rambanks: 0
rombanks: 2

The frames dropped 154 can it indicate something?

About another info i can provide....
Power supply it's the labist power supply. No overclock applyed or somethigs similar and apparently, during emulation, it's not yellow flash or similar appears on tv screen. it's ok ?
The image it's start from 4.7.1 from site and updated.

On first post i'm wrong information (now edit it) EmulationStation it's the version 2.9.6RP.

If it's need i can try another core whit verbose log during games..... before today i never noticed a similar issue for audio.
I have try to look on ES Audio setup..... on OMX Audio Device: it's selected BOTH. it's can be created some issue ? I try to set ALSA now but i don't have idea if i need to reboot my pi4.

EDIT nm.2
If you have some specific request like you want check some option files or somethings similar can help to understand how it's located the issue simply ask.
I can try to provide all whitout any problems.

nemo93

@djdiabolik please check that you have audio_driver = alsathread set in your retroarch.cfg (global config) and report back. Thanks!

dankcushions

@djdiabolik said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

The frames dropped 154 can it indicate something?

154 frames dropped over 1.5 hours shouldn’t be noticeable really

please supply cfg files:
/opt/retropie/configs/all/retroarch.cfg
/opt/retropie/configs/gb/retroarch.cfg

DjDiabolik

@nemo93 and @nemo93

I thinks it's ok... i can provide all both files i a moment.

I have see i can't upload directly the files here........ i can use pastebin:
This is the retroarch.cfg from "all" folder:
configs/all

And this is retroarch.cfg from "gb" folder:
config/gb

@nemo93 in "all" retroarch.cfg audio_driver it's setted as ALSA apparently. i need to change to alsathread or not ?

After that i have need to modify all cfg for every core or not ? it's normal the #include all config it's commented out ?

EDIT
Whit a verbose log.... for about 10 minutes i have tryed right now lr-handy whit "California Games (USA, Europe).zip" apparently here there's no audio issue. i have saved the runcommand.log whit verbose of this session on my windows desktop if need i can provide also this.

nemo93

@nemo93 in "all" retroarch.cfg audio_driver it's setted as ALSA apparently. i need to change to alsathread or not ?

=> correct. In your all folder, edit retroarch.cfg and then change audio_driver to alsathread and see if it's running better.

After that i have need to modify all cfg for every core or not ? it's normal the #include all config it's commented out ?

=> no. After you've made the change above no need to touch other cfg.

DjDiabolik

@nemo93 said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@nemo93 in "all" retroarch.cfg audio_driver it's setted as ALSA apparently. i need to change to alsathread or not ?

=> correct. In your all folder, edit retroarch.cfg and then change audio_driver to alsathread and see if it's running better.

After that i have need to modify all cfg for every core or not ? it's normal the #include all config it's commented out ?

=> no. After you've made the change above no need to touch other cfg.

Ok...... i thinks i need to reboot entire system to made this settings applyed.. it's right ?

Anyway right now, before I went to sleep, I was playing a little.
It seems that I have found another core where the problem with the audio seems to hesitate a little:
I was playing some gamegear games.... in almost all games I could clearly hear the audio track snap/glitch a little. apparently the emulation of the game does not seem to be affected... only the audio track.

Tomorrow i can test if i usage "alsathread" gives some positive results..

nemo93

@djdiabolik no need to reboot your system. Just launch another game to see if that makes a difference. Awaiting for your result!

dankcushions

@djdiabolik said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@nemo93 and @nemo93

I thinks it's ok... i can provide all both files i a moment.

I have see i can't upload directly the files here........ i can use pastebin:
This is the retroarch.cfg from "all" folder:
configs/all

And this is retroarch.cfg from "gb" folder:
config/gb

both of these are non-standard - they should be much shorter on default retropie. they are too large for me to effectively check them but i can't see any settings that immediately jump out as being non-optimal.

still, unless you have specific reason to be running a non-default config, i would update both retroarch and lr-gambette, and then look in those folders again for a default retroarch.cfg.rp-distfile, and then delete retroarch.cfg in the same folder and rename retroarch.cfg.rp-dist to retroarch.cfg so it replaces it.

DjDiabolik

@nemo93
mmmmm... ok.
i'm waken up right now and i have turn on my pi4 for made some test.

after entering "alsathread" i have tryed to run same "GB" games used upper for verbose log, "CATRAP (USA).zip" (if need it's a no-intro romset).
Apparently I don't see any improvements or worsening...... but i can noticed one things:
If i open Retroarch menù (Hotkey + X.... Y on my xbox360 wired controller) i can see ALSA it's again used (if i step back from RA quick menù and open the audio setting from here).

Instead if i open only RetroArch from ES Retropie Menù and follow same way for check AUDIO i can see ALSATHREAD correctly loaded.

At this point my question it's........ i need to edit all retroarch.cfg for every single core ?

@dankcushions
I do not know I have not done anything strage to create these 2 cfg.

it's a test I can do...

From retropie-setup i made an manually update for gambatte and retroarch componets.
After that i have renamed retroarch.cfg to retroarch.test on config/all
Same things whit retroarch.cfg on config/gb
After that i have renamed both rp-dist to retroarch.cfg on all and gb folder.

Now i need to try same games.... "CATRAP (USA).zip"

But anyway to do these tests guys we can change the core used... for example whit gamegear the audio thing is much more noticeable.

dankcushions

@djdiabolik said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@nemo93
mmmmm... ok.
i'm waken up right now and i have turn on my pi4 for made some test.

after entering "alsathread" i have tryed to run same "GB" games used upper for verbose log, "CATRAP (USA).zip" (if need it's a no-intro romset).
Apparently I don't see any improvements or worsening...... but i can noticed one things:
If i open Retroarch menù (Hotkey + X.... Y on my xbox360 wired controller) i can see ALSA it's again used (if i step back from RA quick menù and open the audio setting from here).

Instead if i open only RetroArch from ES Retropie Menù and follow same way for check AUDIO i can see ALSATHREAD correctly loaded.

At this point my question it's........ i need to edit all retroarch.cfg for every single core ?

only because you have these customized non-standard configs. on standard retropie you would only have to change audio_driver to alsathread in /all/retroarch.cfg and it would affect all cores

DjDiabolik

@dankcushions said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@djdiabolik said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@nemo93
mmmmm... ok.
i'm waken up right now and i have turn on my pi4 for made some test.

after entering "alsathread" i have tryed to run same "GB" games used upper for verbose log, "CATRAP (USA).zip" (if need it's a no-intro romset).
Apparently I don't see any improvements or worsening...... but i can noticed one things:
If i open Retroarch menù (Hotkey + X.... Y on my xbox360 wired controller) i can see ALSA it's again used (if i step back from RA quick menù and open the audio setting from here).

Instead if i open only RetroArch from ES Retropie Menù and follow same way for check AUDIO i can see ALSATHREAD correctly loaded.

At this point my question it's........ i need to edit all retroarch.cfg for every single core ?

only because you have these customized non-standard configs. on standard retropie you would only have to change audio_driver to alsathread in /all/retroarch.cfg and it would affect all cores

lol.. it's very strange :)

Otherwise i have made one single test whit a gamegear games:

On config/gamegear i have renamed the retroarch.cfg at .test
renamed .rp-dist to .cfg
And try to lauch some gamegear games........

Now i have the rp-dist both as default and for absurd...... I tried the same game again and the situation seems to have improved significantly.

how is it possible ?

Now try same gamegear games whit my non-standard cfg (even though I didn't create it myself...lol).

dankcushions

@djdiabolik great :)

even though I didn't create it myself

there are a number of possibilities:

you changed a setting in the retroarch menu and saved config - this will create a large config file like you've seen (and make it virtually impossible to locate any risky settings).
you deleted the files at any point - this will create a default retroarch config that is massive (like you've got) and not set up with retropie's defaults.

gb and gamegear games are pretty light for a pi4 so i don't think alsathread should make a difference, but it's still worth setting.

DjDiabolik

@dankcushions said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@djdiabolik great :)

even though I didn't create it myself

there are a number of possibilities:

you changed a setting in the retroarch menu and saved config - this will create a large config file like you've seen (and make it virtually impossible to locate any risky settings).

you deleted the files at any point - this will create a default retroarch config that is massive (like you've got) and not set up with retropie's defaults.

gb and gamegear games are pretty light for a pi4 so i don't think alsathread should make a difference, but it's still worth setting.

the second point is possible... if i remember in the pass i have deleted the retroarch.cfg on config/all for a mess up joypad/joystick configuration.

Anyway now i i put back my previous cfg (the non-standard cfg) and i have try to play the same gamegear games used as test (it's on my favorites).
the oddity is that sometimes the problem seems to be more present and sometimes less....

last night, reading other threads here in the forum, there were also rumors of any hardware problems related to the raspberry itself or even to its power supply (although I should see lightning on the screen if the power supply is damaged... or i can see the status led on board blink or somethings similar).

You speak about GB and GAMEGEAR are pretty light....... you can suggest somethings we can test better to maybe accentuate the problem ?
on my Pi4 i have gb, gamegear, snes, nes, linx, mastersystem, megadrive.... a massive retrogame collection :)

but the strange thing is that until a few days ago I had never had these problems.....

as it is so, that you can not get to the top of a problem, it takes me the grief of giving up and setting everything aside :(

DjDiabolik

@dankcushions @nemo93 sorry for double consecutive post.

I made this mainly to thank you till now :)

For today for this afternoon and tomorrow I should be a little busy and i can come back for further tests, perhaps, next Monday :)

I think to show you the "problem" it would be the best if I could make a small video example..... you thinks it's a good idea ?
I'll try to place a camera in front of the TV in my room :)

Also because I actually hope, for now, to be able to rule out hardware damage (like at raspberry board or the power supply) and the only thing i did is update my system usually i do every one or two weeks.
Maybe it's a small problem/issue (even if in theory the same problems should also be replicable by you) that will be fixed with the next updates as they are almost daily.......

Thanks again for support in this little trouble :)

dankcushions

@djdiabolik perhaps a video would help. it does sound like it might be the nebulous tearing issue as discussed here:
https://retropie.org.uk/forum/topic/26819/jittery-stuttering-graphics
do these videos seem similar to what you're seeing?

if so, the fix is here: https://retropie.org.uk/forum/topic/27632/fixing-screen-tearing-issues-on-rpi4/15?_=1623452515918

however it has some drawbacks if you use videos on your build, or certain emulators that rely on fkms features.

DjDiabolik

@dankcushions lol by a google result i had noticed the first thread you linked.

I have watched closely the three video and for absurd i don't see any problems :)
For example i have right now rewatch the "Stutter1" video... it's only about 9 seconds but where's the issue/trouble ?

Lol... My situation looks a little different......

I have a OT question... instead a using a camera put in front of my tv. It's possible for example catch the video stream from my pi4 for example registering a video on my pendrive (how i stored all my roms) ?
or anyway it is advisable to use the camera for a do a complete catch of my entire retrogame postation :)
Meanwhile, I also tried to make a request thread in that of reddit..... an user as suggest to me to check if i have the eeprom firmware updated but i thinks yes because i thinks this is updated when you make updates from retropie-setup and you choose to update OS componets right ?

dankcushions

@djdiabolik said in Pi4 - 4.7.1x after recent update audio little glitch/struttering or miss some frame on some libretro core... it's fixable ?:

@dankcushions lol by a google result i had noticed the first thread you linked.

I have watched closely the three video and for absurd i don't see any problems :)
For example i have right now rewatch the "Stutter1" video... it's only about 9 seconds but where's the issue/trouble ?

it’s probably difficult to catch on video and street fighter probably too busy to see it, but it looks like horrible tearing and stutter and happens occasionally rather than constantly. try the fix there to see if it makes a difference?

I have a OT question... instead a using a camera put in front of my tv. It's possible for example catch the video stream from my pi4 for example registering a video on my pendrive (how i stored all my roms) ?
or anyway it is advisable to use the camera for a do a complete catch of my entire retrogame postation :)

you’re overcomplicating it. just use a phone camera/camera to record it when it happens, and upload to youtube or wherever.

Meanwhile, I also tried to make a request thread in that of reddit..... an user as suggest to me to check if i have the eeprom firmware updated but i thinks yes because i thinks this is updated when you make updates from retropie-setup and you choose to update OS componets right ?

yes.

DjDiabolik

@dankcushions and @nemo93 (i cited both only because you have already partecipad in thread).

I have right now put my Android Smartphone near my TV.... you can see (partially) my Retrogames setup whit my Pi4 (remember 4GB kit in a Labist KIT buyed from amazon).

You can see i have played the same games used as example for verbose log... it's "CATRAP (USA).zip" using current (and problably latest) version of lr-gambatte.

If you can watch entire video :) After i have set my phone near my TV you can listen, clearly the audio of games..... you can see i'm stay to solve a level and at about 3minutes and 10 seconds you can clearly listen the issue i have descripted here.
You can clearly listen a very little interruption on audio tracks... and there's append about every 3 or 4 minutes. Sometime i can listen a single and little interruption and other time two or three different interruption consecutive.

As I said at the beginning ... I had never noticed such problems before a few weeks ago issues that popped up right after the update.
This last update problably it's not the main cause of the problem...... anyway now i have set audio as "alsathread" also on both retroarch.cfg (on all and on gb folder) and on the same page how i have set alsathread i see a value setted at 64 which should be relative to the audio buffer. It's the correct value 64 ??
I have look this value for any other and for all i have set this value........ it's ok ?

And.... finally.... youtube as ended to elaborate my video example...... i can share whit you.. here we go :)

EDIT number 1
I will try to add the exact timeline when it's present the issue... otherwise at about 3:11 of video.