• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
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

ROMS have blue tint/no audio

Scheduled Pinned Locked Moved Help and Support
romscolor wrongno audiocolor blue
7 Posts 4 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.
  • S
    seanonalawn
    last edited by 24 Oct 2016, 16:42

    Hi everyone,

    I have a raspberry pi 3 setup with I believe the most recent version of retropie. I have everything set up and running; however, whenever I launch a ROM, the colors are off as they have a blue tint. In searching the web for a solution, the problem might be that the retropie resolution is 768p when it should be 720p. I'm still trying to understand how to operate the terminal line, so when I find a resolution I only get about halfway through before getting stuck. I haven't been able to find much help online, so if there's someone that could help I would appreciate it.

    I'm also having a problem where the audio is not playing.

    Thanks!

    E 1 Reply Last reply 24 Oct 2016, 20:28 Reply Quote 0
    • E
      edmaul69 @seanonalawn
      last edited by edmaul69 24 Oct 2016, 20:28

      @seanonalawn this site has all the info you need for this stuff.
      http://elinux.org/RPiconfig#Video_mode_options
      In your case open up /boot/config.txt and change the hdmi drive and hdmi mode lines to this. Remove the hashtags if they are in the line:

      hdmi_drive=2
      hdmi_mode=4
      

      Hdmi mode 4 is for ntsc 720p @ 60hz. If your video is different that site has a whole list of the modes. Hdmi drive 2 should fix your audio. Not sure about the blue tint though

      1 Reply Last reply Reply Quote 0
      • S
        seanonalawn
        last edited by 24 Oct 2016, 21:21

        Thanks for the help, this is what I saw when I did a google search. I saw that I'm supposed to do that under "sudo nano /boot/config.txt". When I typed that in about 60 lines of code came up and confused me. Do you think I type in the config.txt and then just type in the hdmi group/mode text? Or should I disregard the config.txt and just type in the hdmi group/mode text in the terminal? Again, I have a hard time understanding the terminal and am just barely starting to understand it. I hope what I just wrote makes sense.

        O 1 Reply Last reply 24 Oct 2016, 21:26 Reply Quote 0
        • O
          obsidianspider @seanonalawn
          last edited by obsidianspider 24 Oct 2016, 21:26

          @seanonalawn You have to modify the contents of the config.txt file. When you say sudo nano /boot/config.txt you're telling Linux to run the program nano (a text editor) as a super user (that's what sudo does) and you're telling it to open the file/boot/config.txt. You need sudo privileges to modify that file.

          Source: I fart around with Linux just enough to break things.

          📷 @obsidianspider

          1 Reply Last reply Reply Quote 0
          • S
            seanonalawn
            last edited by 25 Oct 2016, 13:17

            Thanks for the help, I'm going to try your suggestions and let you know how it turns out.

            1 Reply Last reply Reply Quote 0
            • B
              backstander
              last edited by 25 Oct 2016, 13:32

              @seanonalawn
              Also after you are in the Nano text editor, you can press Ctrl + W to do a search so you can find where hdmi_drive and hdmi_mode is so you can make the changes. Then when you're finished editing, press Ctrl + X and it will ask if you want to save it and you press Y and then enter when it's asking for a name. Then just reboot RetroPie.

              1 Reply Last reply Reply Quote 0
              • S
                seanonalawn
                last edited by 28 Oct 2016, 13:18

                Just an update, I fixed the issue and now it's running beautifully. It turns out I was following the directions correctly, but I had no idea I had to remove the #. If I hadn't asked, I wouldn't have known so thank you guys for all your help!

                1 Reply Last reply Reply Quote 2
                4 out of 7
                • First post
                  4/7
                  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.

                  This community forum collects and processes your personal information.
                  consent.not_received