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

    Amiberry 3.3 / RPi 4 slow

    Scheduled Pinned Locked Moved Help and Support
    amiberryraspberry pi 4slow gameschoppy audio
    64 Posts 9 Posters 9.7k 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.
    • quicksilverQ
      quicksilver @gordonfreemanjr
      last edited by quicksilver

      @gordonfreemanjr the solution @mitu suggested to limit the maximum resolution doesnt work by itself on my vizio tv either for some reason (it should work but I have learned my vizio has some weird quirks)

      What worked for me was also setting this in my config.txt

      hdmi_ignore_edid=0xa5000080
      
      G 2 Replies Last reply Reply Quote 1
      • G
        gordonfreemanjr @quicksilver
        last edited by

        @quicksilver Thx. Was that the only additional line or have you included the one @mitu proposed as well?

        RPi 4 4GB
        Retropie v 4.7.1

        quicksilverQ 1 Reply Last reply Reply Quote 0
        • quicksilverQ
          quicksilver @gordonfreemanjr
          last edited by

          @gordonfreemanjr That setting plus mitu's works for me.

          1 Reply Last reply Reply Quote 0
          • G
            gordonfreemanjr @quicksilver
            last edited by

            @quicksilver IT WORKS.

            This is the only combination of settings that did it for me. Both need to be active at the same time. Now, when I press the HOME remote button to inspect the resolution, it's 1080p / 60 - and it shows in the emulation speed. For the first time ever, Amiberry works at full speed.

            This is the gamechanger for me.

            @quicksilver @mitu Thank you both for your help. It's been a long topic and couple days, but this is it. It works.

            Thank you!

            So, to sum up. The final working combination to fix the resoution for the RPi4/Samsung Smart TV combo:

            [hdmi:0]
            hdmi_max_pixel_freq=200000000
            [hdmi:1]
            hdmi_max_pixel_freq=200000000
            hdmi_ignore_edid=0xa5000080
            

            RPi 4 4GB
            Retropie v 4.7.1

            mituM S 2 Replies Last reply Reply Quote 1
            • mituM
              mitu Global Moderator @gordonfreemanjr
              last edited by mitu

              @gordonfreemanjr Well, glad you sorted it out.

              I'm wondering if the TV's EDID is not broken and/or lying about the TV's capabilities. Can you get the EDID contents from the TV with

              tvservice -d myTV.edid
              base64 myTV.edid
              

              then post the output of the last command.

              G 1 Reply Last reply Reply Quote 0
              • G
                gordonfreemanjr @mitu
                last edited by gordonfreemanjr

                @mitu Sure. If you don't mind, I'll just attach the .edid file itself. My Ubuntu is unable to open in correctly.
                https://we.tl/t-VITH1B471s

                That’s how it appears on the screen though:
                https://ibb.co/wKk2p4L

                RPi 4 4GB
                Retropie v 4.7.1

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

                  @gordonfreemanjr said in Amiberry 3.3 / RPi 4 slow:

                  @mitu Sure. If you don't mind, I'll just attach the .edid file itself. My Ubuntu is unable to open in correctly.

                  It's a small binary file which isn't meant to be seen as a text file. You need a program to decode it - like edid-decode- , and see the details.

                  I don't see anything out of the ordinary here, apart from the 4k video modes being filtered out (probably because of the configuration).

                  G 1 Reply Last reply Reply Quote 0
                  • G
                    gordonfreemanjr @mitu
                    last edited by gordonfreemanjr

                    @mitu @quicksilver Our case has made it to Amiberry FAQ:

                    https://github.com/midwan/amiberry/wiki/FAQ

                    RPi 4 4GB
                    Retropie v 4.7.1

                    1 Reply Last reply Reply Quote 1
                    • S
                      slimbrick @gordonfreemanjr
                      last edited by slimbrick

                      [EDIT: I fixed my issue, so I tried to delete the post but it wouldn't let me]

                      BuZzB 1 Reply Last reply Reply Quote 0
                      • BuZzB
                        BuZz administrators @slimbrick
                        last edited by

                        @slimbrick it would be more useful imho to leave your post and reply with your fix.

                        To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

                        S 1 Reply Last reply Reply Quote 1
                        • S
                          slimbrick @BuZz
                          last edited by slimbrick

                          @buzz
                          You have a good point.

                          I had a very similar problem to this thread. I replaced my Pi 3 retropie with a Pi 4 and retropie was behaving in a jittery fashion with Emulation Station and the games weren't smooth. I also have a 4K Samsung Smart TV as did the original poster. Although I wasn't using Amiberry, I was using mame, daphne, and jzintv and I figured the same solution that @gordonfreemanjr used would work for me. So I added the five lines to my /boot/config.txt file that he listed in his "IT WORKS" post but lo-and-behold it did not work for me. tvservice -s was still showing a 4K connection when I expected 1080p.

                          My solution was simple with a twist. Starting from the stock config.txt, I uncommented and modified the following:

                          hdmi_group:0=1
                          hdmi_mode:0=16
                          

                          It was necessary for me to add the :0 to get it to work. Now there are no jitters, the motion is smooth, and tvservice -s reports a 1080p connection.

                          1 Reply Last reply Reply Quote 1
                          • 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.