@weissnix4711 said in HDMI CEC Remote support, seems there but not working:

Hey, sorry for bumping this old thread, but could I get an update on this?

There hasn't been any new code added for CEC support.

@mitu Gotcha. Thanks so much.

@retropieuser555 Hopefully you see this, but I was able to fix it by going into /home/pi/.config/AM2R/config.ini and changing:

[Screen] Fullscreen="1.000000"

to

Fullscreen="0.000000"`

@mitu I feel so dumb I am so sorry to bother you. It worked turns out it was wring problem like you said.

Thank you for everything though

I'm a bit confused. If you're using the Pi4 image provided on retropie.org.uk/download, there's no additional installation to be done - RetroPie is already installed and the system should boot to EmulationStation.

How are you installing RetroPie ? Is a Raspberry Pi OS image from raspberrypi.org working on the device ?

@punx45 , I'm about to go almost the same way myself, wiring up buttons from my genuine arcade machine. I'm planning to use the grounding instead of the plus feed (Raspberry's GPIO's should trigger fine on three state i.e. either open circuit going high to feed voltage OR going low to GND).

However, my thought was also a prevention from involentary multi triggering but not by H/W support, we do have plenty of computer power at hand; have a look at this article Physical computing with Raspberry Pi. Some simple sleep timers should do it.

@mitu They don't work at all. :(

I ran through the install instructions posted on the main page twice to be sure. Fresh RetroPie install on a 32GB card, updated everything RetroPie then right to the shutdown scripts. No go. So I did it again with a fresh install with no updates. Still no go. I also used Putty so I could copy and paste the commands with no chance of incorrectly typing them in.

The former dev said he hasn't touched them in over 16 months.

EDIT for added info

@redmarsbluemoon Cheers dude will keep trying thanks and I know the feeling of not having enough time...

@alegasalv Is the gpu_mem actually using the 512mb though? I found that enabling the 'hdmi_enable_4kp60' overrides the setting, as running 'free' in the terminal was showing less than 512 being used. It's only meant to boost the stock gpu memory by 50mb's...or so I've read.

I have mine set at:

force_turbo=1
over_voltage=8
arm_freq=2147
gpu_freq=750
gpu_mem=512

Needed to force_turbo in order to go above gpu_freq=550 though, tested by running 'vcgencmd measure_clock core' to confirm. Also, 'vcgencmd measure_clock arm' for the cpu.

edit: Forgot to mention...if raising the gpu_mem, then using the raspi-config gui to modify anything, it will automatically hash out the hdmi_enable_4kp60 on you...or at least it does for me. I guess it's anything over a certain value.

edit2: Sorry...also forgot to mention that in order to use the gpu_mem=512, you need to enable cma=512 as well. The kernel crashes on me otherwise.

dtoverlay=vc4-fkms-v3d,cma=512

@mitu I updated the setup script and Wolf4sdl, and all is good. I can once again hear enemies shout "mein leben". Thanks again for the help!

I made some progress and figured I would share some updates in the event that anyone runs into this issue. I found a Youtube tutorial to utilize Xroar for Coco Emulation on the PC. I had no installed the disk11.rom or the extbas11.rom. Based on the Retropie doc file, only the bas13.rom is mentioned so it might be worth a minor update.

Here is the Youtube video for reference if anyone would like.

I also ran into some issues with everything being in black and white but with some searching Ctrl-A resolved the issue.

Hopefully this helps someone down the road if they run into this.

@xu-xiaolan omg I actually got it working, tyvm @mitu or I would've been very confused xd, I cloned the github, went to configs and allowed the safe hdmi option then I switched the HDMI port from 1 to 0 (right to left) if anyones wondering how i did it

@clyde

Thanks, yea I did try that as well as "joystick order" in the Configuration Editor. I believe both of these set:

6a766ae2-7b8d-4ccc-9ea0-57399168c6c3-image.png input_player1_joypad_index = "0"
input_player2_joypad_index = "1"In the retroarch.cfg file.

I decided to just install Raspbian, which I had working on my monitor before, and install RetroPie as an app over top of Raspbian

@mitu yes! I was subscribed to help & support
I was looking in my settings, did realise there was a setting on the category page.
Thank you for your help. 👍

Please add some info about your setup, as detailed in https://retropie.org.uk/forum/topic/3/read-this-first.

Did you run a scrape before trying to generate the gamelist ? Do you have any amiga data (art/text) in your cache ?

You should talk to the vendor of the board - maybe they have a way to check for faulty wiring ? Looking at the documentation for the board, it looks like it's using GPIONext and that should detect any GPIO inputs easily.

Put this in your /usr/local/bin folder and make it executable with chmod +x <filename>. Run it from your video folder. Your video files will not be overwritten. New files are saved to ./converted; to use them, you must move or copy one level up to replace the original files. Repeat for each system.

You may need to install ffmpeg first with sudo apt update && sudo apt install ffmpeg.

#! /bin/bash # Script provided by Clyde mkdir -p converted # create the folder "converted" if it doesn't exist for f in *.mp4 # process all videos in the current directory do echo "$(pwd)/$f" # show the processed file's name c=$(ffprobe "$f" 2>&1 | grep -c yuv444p) # (-c)ount no. of "444p" if [ "$c" -gt 0 ] # if 444p is present, then # convert to 420p ffmpeg -i "$f" -y -pix_fmt yuv420p -strict experimental converted/"$f" fi done

[bump]

No one else? This problem persists for me regardless of what device I hook it up to. Originally it was hdmi audio but I now have it hooked up via the audio jack into an amplifier in my bartop and the same thing still happens.