RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Television sound output incompatible with my Retropie

    Scheduled Pinned Locked Moved Help and Support
    televisionsound issuesoundincompatibilityretropie
    20 Posts 3 Posters 2.2k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mituM
      mitu Global Moderator @Jiryn
      last edited by mitu

      @jiryn said in Television sound output incompatible with my Retropie:

      (I heard there is a hidden boost option in Retropie?)

      On Pi3 and older there was the config_hdmi_boost option in config.txt, but for a Pi4 I don't think it's supported anymore (see https://www.raspberrypi.org/documentation/configuration/config-txt/video.md). You can try it out and see if it makes a difference.

      What resolution are you running your system ? Is the TV running in 'game mode' ?

      JirynJ 1 Reply Last reply Reply Quote 1
      • JirynJ
        Jiryn @mitu
        last edited by Jiryn

        @mitu
        1080p, and no.
        I turned off all post-processing crap to remove as much lag as I can.
        I'll try game mode now, see if it fixes it.

        Update
        Tried game mode, didn't change a thing.
        Here's the log

        Parameters:
        Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so --config /opt/retropie/configs/fba/retroarch.cfg "/home/pi/RetroPie/roms/fba/moomesauac.zip" --verbose --appendconfig /dev/shm/retroarch.cfg
        [INFO] RetroArch 1.9.5 (Git 6738fa5)
        [INFO] === Build =======================================
        [INFO] Capabilities: NEON VFPv3 VFPv4
        [INFO] Built: Jun 21 2021
        [INFO] Version: 1.9.5
        [INFO] Git: 6738fa5
        [INFO] =================================================
        [INFO] [Input]: Found input driver: "x".
        [INFO] [Core]: Loading dynamic libretro core from: "/opt/retropie/libretrocores/lr-fbneo/fbneo_libretro.so"
        [INFO] [Overrides]: No core-specific overrides found at "/home/pi/.config/retroarch/config/FinalBurn Neo/FinalBurn Neo.cfg".
        [INFO] [Overrides]: No content-dir-specific overrides found at "/home/pi/.config/retroarch/config/FinalBurn Neo/fba.cfg".
        [INFO] [Overrides]: No game-specific overrides found at "/home/pi/.config/retroarch/config/FinalBurn Neo/moomesauac.cfg".
        [INFO] [Remaps]: Remap directory: "/opt/retropie/configs/fba/".
        [INFO] [Overrides]: Redirecting save file to "/home/pi/RetroPie/roms/fba/moomesauac.srm".
        [INFO] [Overrides]: Redirecting save state to "/home/pi/RetroPie/roms/fba/moomesauac.state".
        [INFO] [Environ]: GET_LOG_INTERFACE.
        [INFO] [Environ]: GET_MESSAGE_INTERFACE_VERSION.
        [INFO] [Environ]: SET_AUDIO_BUFFER_STATUS_CALLBACK.
        [INFO] [CONTENT LOAD]: Content loading skipped. Implementation will load it on its own.
        [INFO] [Environ]: GET_SAVE_DIRECTORY.
        [libretro INFO] Setting save dir to /home/pi/RetroPie/roms/fba/
        [INFO] [Environ]: SYSTEM_DIRECTORY: "/home/pi/RetroPie/BIOS".
        [libretro INFO] Setting system dir to /home/pi/RetroPie/BIOS
        [INFO] [Environ]: SET_CONTROLLER_INFO.
        [libretro INFO] Initialize DIP switches.
        [INFO] [Environ]: GET_CORE_OPTIONS_VERSION.
        [INFO] [Environ]: RETRO_ENVIRONMENT_SET_CORE_OPTIONS_INTL.
        [libretro INFO] [FBNeo] Searching all possible locations for romset moomesauac
        [libretro INFO] [FBNeo] No patched romset found at /home/pi/RetroPie/BIOS/fbneo/patched/moomesauac
        [libretro INFO] [FBNeo] Romset found at /home/pi/RetroPie/roms/fba/moomesauac
        [libretro INFO] [FBNeo] No romset found at /home/pi/RetroPie/BIOS/fbneo/moomesauac
        [libretro INFO] [FBNeo] No romset found at /home/pi/RetroPie/BIOS/moomesauac
        [libretro INFO] [FBNeo] Searching all possible locations for romset moomesa
        [libretro INFO] [FBNeo] No patched romset found at /home/pi/RetroPie/BIOS/fbneo/patched/moomesa
        [libretro INFO] [FBNeo] Romset found at /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] No romset found at /home/pi/RetroPie/BIOS/fbneo/moomesa
        [libretro INFO] [FBNeo] No romset found at /home/pi/RetroPie/BIOS/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x10555732 and name 151c01.q5 from archive /home/pi/RetroPie/roms/fba/moomesauac
        [libretro INFO] [FBNeo] Using ROM with known crc 0x52ae87b0 and name 151uac02.q6 from archive /home/pi/RetroPie/roms/fba/moomesauac
        [libretro INFO] [FBNeo] Using ROM with known crc 0xa5cb137a and name moomesauac.nv from archive /home/pi/RetroPie/roms/fba/moomesauac
        [libretro INFO] [FBNeo] Using ROM with known crc 0xc896d3ea and name 151a03.t5 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x3b24706a and name 151a04.t6 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0xcde247fc and name 151a07.f5 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0xbc616249 and name 151a05.t8 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x38dbcac1 and name 151a06.t10 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x376c64f1 and name 151a10.b8 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0xe7f49225 and name 151a11.a8 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x4978555f and name 151a12.b10 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x4771f525 and name 151a13.a10 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] Using ROM with known crc 0x962251d7 and name 151a08.b6 from archive /home/pi/RetroPie/roms/fba/moomesa
        [libretro INFO] [FBNeo] No missing files, proceeding
        [libretro INFO] [FBNeo] Samplerate set to 48000
        [libretro INFO] [FBNeo] Applied dipswitches from core options
        [libretro INFO] [FBNeo] Initialized driver for moomesauac
        [libretro INFO] [FBNeo] Adjusted audio buffer to match driver's refresh rate (60.000000 Hz)
        [libretro INFO] [Cheevos] System RAM set to 0xaa691088, size is 241699
        [INFO] [Environ]: SET_ROTATION: 0
        [INFO] [Environ]: SET_PIXEL_FORMAT: XRGB8888.
        [libretro INFO] [FBNeo] Driver moomesauac was successfully started : game's full name is Wild West C.O.W.-Boys of Moo Mesa (ver UAC)
        [INFO] [SRAM]: Skipping SRAM load..
        [INFO] Version of libretro API: 1
        [INFO] Compiled against API: 1
        [INFO] [Audio]: Set audio input rate to: 48000.00 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 39 modes.
        [INFO] [DRM]: Connector 0 assigned to monitor index: #1.
        [INFO] [DRM]: Mode 0: (3840x2160) 3840 x 2160, 30.000000 Hz
        [INFO] [DRM]: Mode 1: (4096x2160) 4096 x 2160, 30.000000 Hz
        [INFO] [DRM]: Mode 2: (4096x2160) 4096 x 2160, 29.970001 Hz
        [INFO] [DRM]: Mode 3: (4096x2160) 4096 x 2160, 25.000000 Hz
        [INFO] [DRM]: Mode 4: (4096x2160) 4096 x 2160, 24.000000 Hz
        [INFO] [DRM]: Mode 5: (4096x2160) 4096 x 2160, 23.976000 Hz
        [INFO] [DRM]: Mode 6: (3840x2160) 3840 x 2160, 29.970001 Hz
        [INFO] [DRM]: Mode 7: (3840x2160) 3840 x 2160, 25.000000 Hz
        [INFO] [DRM]: Mode 8: (3840x2160) 3840 x 2160, 24.000000 Hz
        [INFO] [DRM]: Mode 9: (3840x2160) 3840 x 2160, 23.976000 Hz
        [INFO] [DRM]: Mode 10: (1920x1080) 1920 x 1080, 60.000000 Hz
        [INFO] [DRM]: Mode 11: (1920x1080) 1920 x 1080, 59.940201 Hz
        [INFO] [DRM]: Mode 12: (1920x1080i) 1920 x 1080, 30.000000 Hz
        [INFO] [DRM]: Mode 13: (1920x1080i) 1920 x 1080, 29.970100 Hz
        [INFO] [DRM]: Mode 14: (1920x1080) 1920 x 1080, 50.000000 Hz
        [INFO] [DRM]: Mode 15: (1920x1080) 1920 x 1080, 30.000000 Hz
        [INFO] [DRM]: Mode 16: (1920x1080) 1920 x 1080, 29.970100 Hz
        [INFO] [DRM]: Mode 17: (1920x1080) 1920 x 1080, 25.000000 Hz
        [INFO] [DRM]: Mode 18: (1920x1080) 1920 x 1080, 24.000000 Hz
        [INFO] [DRM]: Mode 19: (1920x1080) 1920 x 1080, 23.976080 Hz
        [INFO] [DRM]: Mode 20: (1280x720) 1280 x 720, 60.000000 Hz
        [INFO] [DRM]: Mode 21: (1280x720) 1280 x 720, 59.940201 Hz
        [INFO] [DRM]: Mode 22: (1280x720) 1280 x 720, 50.000000 Hz
        [INFO] [DRM]: Mode 23: (1024x768) 1024 x 768, 75.028580 Hz
        [INFO] [DRM]: Mode 24: (1024x768) 1024 x 768, 70.069359 Hz
        [INFO] [DRM]: Mode 25: (1024x768) 1024 x 768, 60.003841 Hz
        [INFO] [DRM]: Mode 26: (800x600) 800 x 600, 75.000000 Hz
        [INFO] [DRM]: Mode 27: (800x600) 800 x 600, 72.187569 Hz
        [INFO] [DRM]: Mode 28: (800x600) 800 x 600, 60.316540 Hz
        [INFO] [DRM]: Mode 29: (720x576) 720 x 576, 50.000000 Hz
        [INFO] [DRM]: Mode 30: (720x576i) 720 x 576, 25.000000 Hz
        [INFO] [DRM]: Mode 31: (720x480) 720 x 480, 60.000000 Hz
        [INFO] [DRM]: Mode 32: (720x480) 720 x 480, 59.940060 Hz
        [INFO] [DRM]: Mode 33: (720x480i) 720 x 480, 30.001110 Hz
        [INFO] [DRM]: Mode 34: (720x480i) 720 x 480, 29.970030 Hz
        [INFO] [DRM]: Mode 35: (640x480) 640 x 480, 75.000000 Hz
        [INFO] [DRM]: Mode 36: (640x480) 640 x 480, 60.000000 Hz
        [INFO] [DRM]: Mode 37: (640x480) 640 x 480, 59.940475 Hz
        [INFO] [DRM]: Mode 38: (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: 0xa783b0a8.
        [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] [Shaders]: Configuration file shader set to .
        [INFO] [Shaders]: Configuration file shader set to .
        [INFO] [Shaders]: Configuration file shader set to .
        [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).
        [WARN] [udev]: Couldn't open any keyboard, mouse or touchpad. Are permissions set correctly for /dev/input/event*?
        [INFO] [udev]: Pad #0 (/dev/input/event0) supports force feedback.
        [INFO] [udev]: Pad #0 (/dev/input/event0) supports 16 force feedback effects.
        [INFO] [Joypad]: Found joypad driver: "udev".
        [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] [Environ]: SET_SUBSYSTEM_INFO.
        [libretro INFO] [FBNeo] Unknown device type for port 0, forcing "Classic" instead
        [libretro INFO] [FBNeo] Unknown device type for port 1, forcing "Classic" instead
        [libretro INFO] [FBNeo] Unknown device type for port 2, forcing "Classic" instead
        [libretro INFO] [FBNeo] Unknown device type for port 3, forcing "Classic" instead
        [INFO] [Playlist]: Loading history file: [/opt/retropie/configs/fba/content_history.lpl].
        [INFO] [Playlist]: Loading history file: [/opt/retropie/configs/fba/content_music_history.lpl].
        [INFO] [Playlist]: Loading history file: [/opt/retropie/configs/fba/content_video_history.lpl].
        [INFO] [Playlist]: Loading history file: [/opt/retropie/configs/fba/content_image_history.lpl].
        [INFO] [Playlist]: Loading favorites file: [/opt/retropie/configs/fba/content_favorites.lpl].
        [INFO] [Playlist]: Written to playlist file: /opt/retropie/configs/fba/content_history.lpl
        [INFO] [Environ]: SET_INPUT_DESCRIPTORS:
        [INFO] [KMS]: New FB: 1920x1080 (stride: 7680).
        [INFO] [KMS]: New FB: 1920x1080 (stride: 7680).
        [INFO] [Core]: Content ran for a total of: 00 hours, 02 minutes, 34 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: 9295, Frames dropped: 1.

        1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator
          last edited by

          Can you try adding hdmi_safe=1 to config.txt and see the audio is cut ? It will change your resolution also, but for the sake of the test, just run with it temporarily.

          JirynJ 2 Replies Last reply Reply Quote 1
          • JirynJ
            Jiryn @mitu
            last edited by Jiryn

            @mitu
            It say "Pemission Denied?"
            f0d3dfd0-e389-42b2-b3aa-6e1f83b5da07-image.png

            fcc48038-441b-4b90-a8ba-632638a0f29a-image.png

            (Sorry kinda new to the editing)

            1 Reply Last reply Reply Quote 0
            • JirynJ
              Jiryn @mitu
              last edited by Jiryn

              @mitu
              Got it edited, the sound issue persists. (Figured out how to edit remotely through command line)
              It's only in the emulators like MAME, FBNEO, and now even the GBA.

              I enabled the "Force HDMI instead of DVI" to test it, since it references sound compatibility in monitors, and it also did nothing.

              JirynJ 1 Reply Last reply Reply Quote 0
              • JirynJ
                Jiryn @Jiryn
                last edited by Jiryn

                @dankcushions @mitu
                The answer has been found, and there is nothing I can do about it for now.
                Back in May/June Vizio released a firmware patch that screwed up all their middle/high end TVs across the board.
                What I am experiencing is a very small portion of the issues the firmware caused.

                They posted a notice on various sites saying they'd fix it... but it's been a month and nothing has happened, they've gone silent.

                https://www.reddit.com/r/VIZIO_Official/comments/o0juho/tv_firmware_update_to_1201817/

                1 Reply Last reply Reply Quote 0
                • JirynJ
                  Jiryn
                  last edited by

                  HUGE UPDATE AND I HOPE SOMEONE READS THIS!
                  @dankcushions @mitu (Sorry you guys were helping so much!!!)

                  I went and bought a brand new TV
                  a 2021 LG 55" NanoCell 4K UHD Smart LED HDR TV - 55NANO75

                  The sound issues persist.
                  The sound cuts out regularly on most games, and extremely frequently with Jurassic Park (mame2010), which was my originally complaint.

                  I once again tried it on my older TVs and it worked without an issue or sound cutting out.
                  So it has to do something with modern sound hardware and the PI.

                  The LG detects the pi as PCM.

                  dankcushionsD 1 Reply Last reply Reply Quote 0
                  • dankcushionsD
                    dankcushions Global Moderator @Jiryn
                    last edited by

                    @jiryn
                    i have an lg 4k OLED which works fine so i am sure it’s an issue with your specific hardware, cables or configuration. i would start from the beginning again - ideally with a fresh default image, and then all the usual stuff like a verbose log, the config.txt, and so on.

                    mame2010 is not a recommend emulator, and i don’t use it, so i would replicate the issue with something far more generic like a game on a console system that your pi can be guaranteed to emulate well, at full speed. sound dropping out is a classic symptom of a game that pushes the hardware too much.

                    JirynJ 1 Reply Last reply Reply Quote 0
                    • JirynJ
                      Jiryn @dankcushions
                      last edited by Jiryn

                      @dankcushions
                      That's what I'm getting at is weird though.

                      The sound doesn't drop or hitch at all on a 4 of the 6 TVs in my house hold.
                      It runs perfectly, even Jurassic Park.

                      Even when captured through my system capture card, the sound is perfect.
                      Yet the signal to the TV still cuts out (See original post of the side by side Jurassic park videos)

                      This problem has been cropping up in everything on the PI. Mame 2003, FBNeo, Neo Geo, 32X, Virtual Boy, etc etc.

                      A Fresh Install is the only thing I've not tried, but why would it work perfectly for 4 of 6 TVs?

                      Once again, this is how it sounds on those TVs and on my stream
                      Mame 2010

                      This is how it sounds on the LG Nanocell and Vizio M55-E0

                      dankcushionsD 1 Reply Last reply Reply Quote 0
                      • dankcushionsD
                        dankcushions Global Moderator @Jiryn
                        last edited by dankcushions

                        @jiryn it’s all i can suggest. removing all extraneous factors. in addition to the default image and basic game, also not going via an micro hdmi converter, no hdmi capture devices or audio devices devices in the chain, a name brand cable, and so on.

                        my suspicion is your cable or something in between your pi4 and the tv is interfering with the signal. as to why it works with other tvs - either the setup isn’t identical or older hdmi versions are less sensitive.

                        JirynJ 1 Reply Last reply Reply Quote 1
                        • JirynJ
                          Jiryn @dankcushions
                          last edited by

                          @dankcushions said in Television sound output incompatible with my Retropie:

                          @jiryn it’s all i can suggest. removing all extraneous factors. in addition to the default image and basic game, also not going via an micro hdmi converter, no hdmi capture devices or audio devices devices in the chain, a name brand cable, and so on.

                          my suspicion is your cable or something in between your pi4 and the tv is interfering with the signal. as to why it works with other tvs - either the setup isn’t identical or older hdmi versions are less sensitive.

                          As I said, I connected it directly to both TVs that it's not working on and had the same issue.
                          The cables I am using are the Blue Rigger HDMI - Micro HDMI, and the Monoprice HDMI to Micro HDMI
                          I am not using an adapter of any sort.

                          dankcushionsD 1 Reply Last reply Reply Quote 0
                          • dankcushionsD
                            dankcushions Global Moderator @Jiryn
                            last edited by

                            @jiryn ok, well like i said, the other steps (default image, trivial game, etc) are what i would do to diagnose the issue. good luck

                            JirynJ 2 Replies Last reply Reply Quote 1
                            • JirynJ
                              Jiryn @dankcushions
                              last edited by

                              @dankcushions

                              Yep! Doing a fresh install and transfer of games as we speak.
                              The reason I use Jurassic Park as the benchmark is because it always fails at the same time if the sound is going to cut out.. unlike the other games which are random and patchy.

                              Right now the system works on a Vizio E370VL, Vizio M471J-A2, Vizio V505-G9 (2019 model), and a 32 inch Samsung
                              It doesn't work on a Vizio M55-E0 (2017 Model) and an LG Nanocell 55NANO75

                              Thank you for your help all the way!
                              I just want to squash this issue..

                              1 Reply Last reply Reply Quote 0
                              • JirynJ
                                Jiryn @dankcushions
                                last edited by Jiryn

                                @dankcushions
                                Everything is reinstalled, but how do I set the resolution to 1080p 60hz?

                                When I enter Raspberry config, everything is TINY and I can't read it on 4k, and my streaming software only supports up to 1080/60.

                                I got to Raspi-config -> Display Options -> Resolution
                                But all it does is blink and come back

                                mituM 1 Reply Last reply Reply Quote 0
                                • mituM
                                  mitu Global Moderator @Jiryn
                                  last edited by

                                  @jiryn https://retropie.org.uk/docs/Pi4/#issues-using-a-4k-tv

                                  JirynJ 1 Reply Last reply Reply Quote 1
                                  • JirynJ
                                    Jiryn @mitu
                                    last edited by Jiryn

                                    @mitu @dankcushions
                                    It is working perfectly now thank you!
                                    Your suggestion in the 4k post helped a lot!
                                    Even Jurassic Park!

                                    The only (minor) issues are
                                    #1. whenever I load anything it says
                                    "lul0: Volume Control ::inut() -Failed To Find Mixer Element!"

                                    #2. I forgot how to make them perfectly full screen as I had before.

                                    Spoke too soon, something is really messing up FBneo.
                                    Fixed the mixer by making it HDMI

                                    I am also randomly losing controller connection on a wired controller. When I updated Retropie Setup.

                                    When I tell Retroarch to reset defaults, I lose all controller access.

                                    --
                                    Final edit, got the sound working again.
                                    Oddly it's related to something I did with the video output on FB Neo that caused the sound issues, by setting it back to default it works perfectly.

                                    It was something in the scaling and video options causing the LG and Vizio sound to screw up
                                    It began to happen with FBNeo as I began to screw with Integer and ratio... when I set it back to default (core) it worked perfect again. No clue why it affected the sound on those TVs.

                                    dankcushionsD 1 Reply Last reply Reply Quote 0
                                    • dankcushionsD
                                      dankcushions Global Moderator @Jiryn
                                      last edited by

                                      @jiryn we only get email notifications for your first version of the first version of your post, FYI.

                                      When I tell Retroarch to reset defaults, I lose all controller access.

                                      yeah don’t do this. retroarch defaults are not retropie defaults and will not work.

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post

                                      Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                                      Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.