• Audio Issues HDMI

    Help and Support
    2
    0 Votes
    2 Posts
    212 Views
    mituM

    @fredthelifeguard said in Audio Issues HDMI:

    Built From: Image found on Raspberry Pi SD Card Imager

    Which image are we talking about - RetroPie or RaspiOS Did you install any additional drivers or run additional scripts for the PiCade hat to work ?
    Please post your /boot/config.txt file.

  • 0 Votes
    15 Posts
    1k Views
    L

    Hi @mitu, I keep digging and find strange stuff, look at this...

    pi@retrocade:~$ sudo amixer scontrols Simple mixer control 'HDMI',0 pi@retrocade:~$ amixer scontrols Simple mixer control 'Master',0 Simple mixer control 'Capture',0
  • 0 Votes
    5 Posts
    578 Views
    mituM

    @ezra84 Not sure what error are you seeing. You should have deleted just the site from where you downloaded the image, not the rest. The post is ok now.

  • Adjust BGM volume? (mpg123)

    Help and Support
    2
    0 Votes
    2 Posts
    521 Views
    RapidEdwin08R

    @retropie start with a specific % volume

    mpg123 -f "32768" # Volume % "100"
    mpg123 -f "29484" # Volume % "90 "
    mpg123 -f "26208" # Volume % "80 "
    mpg123 -f "22932" # Volume % "70 "
    mpg123 -f "19656" # Volume % "60 "
    mpg123 -f "16380" # Volume % "50 "
    mpg123 -f "13104" # Volume % "40 "
    mpg123 -f "9828" # Volume % "30 "
    mpg123 -f "6552" # Volume % "20 "
    mpg123 -f "3276" # Volume % "10 "
    mpg123 -f "1638" # Volume % "5 "

  • 0 Votes
    3 Posts
    913 Views
    m2306M

    @Clyde Thanks. And for anyone following up this question I was easily able to add audio volume control (via hotkey + D-pad up/down) to the config file mentioned earlier. Like this: input_volume_up_axis = ”” inside the quotation marks I copied the number for the up axis, which was -1 in my config file.

  • 0 Votes
    9 Posts
    2k Views
    LolonoisL

    @blackjackpsp good to see you have found a workaround as solution. If you think this topic can be marked as solved please do adapt the subject of your inititial post (e.g. replace [HELP] with [Solved]).
    If you want you may add Triggerhappy as additional label.

    Cheers

  • 0 Votes
    4 Posts
    516 Views
    J

    Your suggestion worked great! Thanks!

    Jim

  • 0 Votes
    1 Posts
    555 Views
    No one has replied
  • Volume Control Command

    Help and Support
    3
    0 Votes
    3 Posts
    2k Views
    AndresA

    I'm pretty shure Triggerhappy is running, because if it was not running it wouldn't have worked for the shut down hotkey.
    I found the "name" of the buttons by using the "thd --dump /dev/input/event*" command in the post you recommendet and created a .cfg:

    BTN_BASE3 1 /usr/bin/amixer sset PCM,0 2dB-
    BTN_BASE4 1 /usr/bin/amixer sset PCM,0 2dB+

    The buttons are connected via USB to the Raspberry and work great with the commands configured in emulationstation. The Speakers are plugged in to the 3,5mm klinke output of the pi.

  • control volume with controller?

    Help and Support
    4
    0 Votes
    4 Posts
    2k Views
    chipsnblipC

    i added the following lines to my controller autoconfig file:

    (/opt/retropie/configs/all/retroarch/autoconfig/<controller>.cfg)

    input_volume_up_btn = "h0up" input_volume_down_btn = "h0down"

    then <hotkey>+Up/Down on the D-pad becomes volume control for all libretro emulators. not sure about kodi though.

  • 0 Votes
    2 Posts
    1k Views
    edmaul69E

    @MadRikXIV if you remove the mic chip and capacitor on the original board you could rewire that volume slider on the board to be used

  • Changing default volume setting from 77%

    Help and Support
    6
    1 Votes
    6 Posts
    4k Views
    P

    That worked. Cheers.

  • 0 Votes
    2 Posts
    2k Views
    S

    I found the solution in: Audio issue with latest version of RetroPie.

    For those who want to know, the solution was to add this to the config.txt file in /boot:

    dtparam=audio=on

    Sorry for wasting any time!

  • Volume control on HATARI for Atari St

    Help and Support
    1
    0 Votes
    1 Posts
    655 Views
    No one has replied
  • 0 Votes
    2 Posts
    2k Views
    Z

    @cif140
    I've set this up using the buttons on a logitec s-150 usb sound card+amp+speakers. To the pi, it registers as two devices a sound card, and a HID keyboard.
    Anyways, I used triggerhappy (or its deamon: thd) to listen to specific keypresses (it has a mode to just show the presses it detects, so you can find out easily depending on your HW).
    This then triggers one of three scripts for volume up, down or mute toggle.
    These scripts first perform the alsa command, then play a sound to reflect the current sound volume.

    This all starts at system startup, and is completely independent from RetroArch.

    I can post the scripts if you're interested, and when I'm back at a proper computer.

  • 0 Votes
    1 Posts
    1k Views
    No one has replied
  • 0 Votes
    9 Posts
    3k Views
    markyh444M

    @darksarcasm Sorry dude, must've skim read that bit (character flaw of mine). Have you tried a different button combo instead of using 10 in both in case it is conflicting?

  • 0 Votes
    2 Posts
    1k Views
    obsidianspiderO

    I modified my Mausberry script to change the display on my TFT to show that the Pi is shutting down. That said, I've seen other python implementations to try to do the same thing. Most seemed to be less "foolproof" than the Mausberry method, so I didn't use python to manage the shutdown. I'm still quite a hack at this, I'm still cleaning things up, and I'm sure my code is messy, but this is my modified switch.sh

    #!/bin/bash #this is the GPIO pin connected to the lead on switch labeled OUT GPIOpin1=18 #this is the GPIO pin connected to the lead on switch labeled IN GPIOpin2=17 echo "$GPIOpin1" > /sys/class/gpio/export echo "in" > /sys/class/gpio/gpio$GPIOpin1/direction echo "$GPIOpin2" > /sys/class/gpio/export echo "out" > /sys/class/gpio/gpio$GPIOpin2/direction echo "1" > /sys/class/gpio/gpio$GPIOpin2/value while [ 1 = 1 ]; do power=$(cat /sys/class/gpio/gpio$GPIOpin1/value) if [ $power = 0 ]; then sleep 1 else #load image sudo python /home/pi/Adafruit_Python_ILI9341/examples/imageparam2.py "/home/pi/Adafruit_Python_ILI9341/examples/powering-off.png" sudo poweroff fi done

    The Mausberry script is pretty inefficient if you want to monitor buttons as it's constantly polling. From my research the "wait for edge" method is less processor intensive. This is my "reset button" python script that controls the backlight on my secondary TFT. My code may be messy, but I noticed less CPU load when using this method compared to the Mausberry method.

    #!/usr/bin/python import RPi.GPIO as GPIO import time # set up BCM GPIO numbering GPIO.setmode(GPIO.BCM) # turn off warnings GPIO.setwarnings(False) # tell the script that we're going to output data on GPIO 23 GPIO.setup(23,GPIO.OUT) # tell the script we're going to use GPIO 27 for input and act as a pull up resistor GPIO.setup(27, GPIO.IN, pull_up_down=GPIO.PUD_UP) # the default state of the light is on light = 1 # run this unless there's an exception try: # Turn ON Backlight by default GPIO.output(23,GPIO.HIGH) # do this forever while True: # use interrupt to wait for button to be pressed GPIO.wait_for_edge(27, GPIO.FALLING) # if the light is on, turn the light off if light == 1: #Turn OFF Backlight GPIO.output(23,GPIO.LOW) #change the state of the light variable so the script knows the light is off light = 0 # if the light is off, turn the light on elif light == 0: # Turn ON Backlight GPIO.output(23,GPIO.HIGH) #change the state of the light variable so the script knows the light is on light = 1 # wait a little while to account for bounce in the button time.sleep(0.2) # keep running unless you Ctrl+C to break out of it except KeyboardInterrupt: # reset the GPIO pins used in this program GPIO.cleanup()
  • Low Base Volume

    Help and Support
    4
    0 Votes
    4 Posts
    2k Views
    BuZzB

    you can mark threads topics as "solved" under topic tools btw. I will do that now.

  • Single GPIO button

    Help and Support
    11
    0 Votes
    11 Posts
    4k Views
    S

    @tehswiftone said in Single GPIO button:

    Add this inside of your controllers config, don't forget to replace button with a proper button ID. This will be similar to exiting an emulator, you will use select + button to use it. So don't worry about it taking up a button on your controller.

    input_volume_down_btn = "button"
    input_volume_up_btn = "button"

    I have mine setup to use Up and Down on the D-pad. Just change the "btn" to "axis".

    input_volume_down_axis = "+1"
    input_volume_up_axis = "-1"