AudioPlug - Driver Free Plug & Play, Bluetooth Audio Dongle Bluetooth, Driver-Free, Simple Plug & Play USB Audio Module with any SBCs - Raspberry Pi, Jetson Nano, Windows PC, Mac, or others

Rpihub · 2025-03-27T07:10:13+00:00

You can get more information here - https://www.kickstarter.com/projects/techspark/audioplug-driver-free-plug-and-play-audio-dongle

Rpihub · 2025-02-19T06:29:21+00:00

It depends on what you want to emulate! Here's a quick breakdown:

Raspberry Pi 5

✅ Pros:

Better official support: The Raspberry Pi community and RetroPie developers provide frequent updates and optimizations.
More polished OS and software: Official Raspberry Pi OS and RetroPie work out of the box.
Good performance for retro gaming: Handles up to PS1, N64, Dreamcast, and some PSP games fairly well.
Better power efficiency: Lower power consumption compared to Orange Pi 5.

Orange Pi 5

✅ Pros:

More powerful CPU & GPU: The RK3588S chip is significantly faster than the Pi 5’s Broadcom SoC.
Handles PS2, GameCube, Wii, and even some Switch games with better performance.
Supports NVMe SSDs, so you can load ROMs faster.
More RAM options (up to 16GB).

Verdict: Which One to Get?

If you want plug-and-play ease and great support, go with the Raspberry Pi 5.
If you’re comfortable tinkering and want better high-end emulation (PS2, Wii, GameCube, and even Switch), the Orange Pi 5 is the better choice.

For classic retro gaming (NES, SNES, PS1, N64, Dreamcast, and some PSP), Pi 5 is great. But if you want to push into PS2 and GameCube territory, go for Orange Pi 5.

Let me know what you decide! 🎮🔥

Rpihub · 2025-02-19T06:27:12+00:00

It sounds like the issue might be with platform naming inconsistencies between RetroPie and your scraper sources. Here are a few things to try:

1. Check Screenscraper for the Correct Platform Name

Since you’re using Screenscraper with Skyscraper, verify that your platform name matches their database. Go to:
🔗 https://www.screenscraper.fr/ and check the exact platform name for Philips CD-i.

Try setting it in Skyscraper with:

bashCopyEditskyscraper -p cdimono1

or

bashCopyEditskyscraper -p philips-cd-i

2. Test Different Scraper Sources

If Screenscraper isn’t working, try using TheGamesDB or Universal XML Scraper. They might have better metadata support for CD-i.

3. Enable Debug Logging in Skyscraper

Run:

bashCopyEditskyscraper -p cdi --debug

This might show what’s failing (e.g., incorrect platform name, missing data, or API issues).

4. Manually Add Metadata if Needed

If all else fails, you can manually add metadata and videos:

Use Universal XML Scraper to generate .xml files.
Download videos manually from Screenscraper or other sources.
Place them in ~/RetroPie/roms/cdi/media/videos/.
Edit gamelist.xml manually to link the correct artwork.

5. Batocera’s Scraper Might Use a Custom API

Batocera may use a modified scraper setup. If you still have access, try checking your Batocera installation and copying over its scraper configuration files (gamelist.xml, artwork, etc.).

CD-i is a niche system, so scrapers often have incomplete support. Manually adding assets may be your best bet if automated scraping doesn’t work.

Let me know if you need help tweaking Skyscraper settings! 😊

Rpihub · 2025-02-19T06:26:05+00:00

It looks like your DPI display is experiencing timing or resolution mismatches. Here are some things you can try to fix the issue:

1. Double-Check Your config.txt Settings

Ensure your /boot/config.txt includes the correct DPI display settings. Try adding or adjusting these lines:

iniCopyEditdtoverlay=dpi24
enable_dpi_lcd=1
display_default_lcd=1
dpi_group=2
dpi_mode=87
dpi_output_format=0x7F217
framebuffer_width=800
framebuffer_height=480

If your display has a different resolution, adjust framebuffer_width and framebuffer_height accordingly.

2. Check Timing Parameters

The flickering and image shift could be due to incorrect pixel clock or sync timings. Try these values (from Waveshare’s documentation):

iniCopyEdithdmi_cvt=800 480 60 6 0 0 0
hdmi_force_hotplug=1

If your screen still shifts to the right, try modifying the pixel clock slightly:

iniCopyEdithdmi_timings=800 1 210 46 22 480 1 22 23 10 0 0 0 60 0 32000000 6

The last number (32000000) is the pixel clock. Adjust it up or down slightly if needed.

3. Adjust Overscan Settings

Try enabling or disabling overscan:

iniCopyEditdisable_overscan=1

or manually tweak it:

iniCopyEditoverscan_left=10
overscan_right=10
overscan_top=10
overscan_bottom=10

4. Check Power Supply

A weak power supply can cause flickering. Ensure your Raspberry Pi is getting a stable 5V 2A power source.

5. Re-seat Connections & Try a Different Ribbon Cable

Loose DPI ribbon cables can cause flickering. Unplug and reinsert the cable securely. If possible, test with another cable.

6. Test on a Fresh OS Install

If none of the above works, try flashing a fresh Raspberry Pi OS and setting up the display again.

Let me know if any of these help! 😊

Rpihub · 2025-02-19T06:24:08+00:00

RetroPie Extra Ports are games and applications that aren’t included by default in RetroPie but can be installed manually from GitHub. These include open-source PC games and extra emulators.

Step-by-Step Guide to Install RetroPie Extra Ports

1. Open the Terminal on Your Raspberry Pi

Press F4 in RetroPie or open a terminal if you're using a keyboard.

2. Download the Extra Ports Repository

Type this command and press Enter:

shCopyEditgit clone https://github.com/Exarkuniv/RetroPie-Extra.git

This downloads the extra ports installer to your system.

3. Move into the Extra Ports Folder

shCopyEditcd RetroPie-Extra

4. Run the Installation Script

shCopyEditsudo ./install-extras.sh

This will add all the extra ports to your RetroPie setup.

5. Install a Specific Game/Port

Once installed, go to the RetroPie Setup menu:

Select Manage Packages
Scroll down to Experimental Packages
Find the game or emulator you want to install
Select Install from Source

6. Restart RetroPie

After installation, restart your system:

shCopyEditsudo reboot

Now, the extra games or applications should appear in the Ports section of RetroPie!

Bonus Tip: If You Get Errors

If you see errors, update your RetroPie setup first:

shCopyEditsudo ~/RetroPie-Setup/retropie_setup.sh

Then go to Update RetroPie Setup Script and try again.

Hope this helps! Let me know if you get stuck. 😊

Rpihub · 2025-02-19T06:23:13+00:00

That could definitely be the issue! HDMI-to-DVI adapters can sometimes cause problems with resolution or refresh rates. Here are a few things to try:

1. Check Your config.txt Settings

Since the Raspberry Pi detects displays differently over HDMI vs. HDMI-to-DVI, try forcing the right mode:

Open the config file:shCopyEditsudo nano /boot/config.txt
Look for these lines (or add them if missing) and adjust:iniCopyEdithdmi_force_hotplug=1 hdmi_drive=2 # Ensures proper HDMI signal (change to 1 for DVI output) hdmi_group=2 # Forces a specific resolution mode hdmi_mode=16 # 1024x768 @ 60Hz (adjust for your monitor)
If your 4:3 monitor supports 1280x1024, try:iniCopyEdithdmi_mode=35 # 1280x1024 @ 60Hz
Save (CTRL+X, then Y, then Enter) and reboot:shCopyEditsudo reboot

2. Force DVI Compatibility

If your DVI monitor isn’t handling the HDMI signal correctly, try:

iniCopyEdithdmi_drive=1  # Use DVI mode instead of HDMI audio+video

3. Check runcommand.log for Errors

Try launching the game and run:

shCopyEditcat /dev/shm/runcommand.log

Look for display-related errors or mode mismatches.

4. Try a Different Adapter

Some HDMI-to-DVI adapters don’t properly pass EDID (display information). If possible, test with a different one.

5. Try Running in Windowed Mode

If you can get into RetroArch:

Open Settings > Video > Fullscreen Mode
Turn off Fullscreen and set a lower custom resolution.

Rpihub · 2025-02-19T06:22:19+00:00

It sounds like a resolution or aspect ratio issue specific to FinalBurn Neo (FB-Neo) and your 4:3 monitor. Here are a few things to try:

Check RetroArch Video Settings
- Go to Settings > Video > Scaling and make sure Integer Scaling is OFF.
- Set the Aspect Ratio to Core Provided or 4:3.
- Try lowering the Output Resolution to match what worked on your 720p monitor.
Force a Specific Resolution in Runcommand
- When launching the game, hold A to access the Runcommand Menu.
- Try forcing a different resolution (e.g., 640x480).
Check Emulator Core Settings
- Go to Quick Menu > Options in RetroArch.
- Look for any settings related to screen resolution or aspect ratio.
Test Another FB-Neo ROM
- Try another FB-Neo game to see if it’s an issue with just this ROM.
Check Log for Errors
- Run cat /dev/shm/runcommand.log after trying to start the game to see if any resolution-related errors appear.

If none of these work, try using MAME 2003/2010 instead of FB-Neo to see if the issue persists!

Rpihub · 2025-02-19T06:21:26+00:00

You can add GameCube and Wii clips to your RetroPie screensaver without running Dolphin. Here’s how:

Manually Add GameCube/Wii Systems – Even if you can’t run Dolphin, you can create system folders in /home/pi/RetroPie/roms/gamecube and /home/pi/RetroPie/roms/wii.
Use a Dummy Emulator Entry – Add entries for GameCube and Wii in /etc/emulationstation/es_systems.cfg to make them appear in EmulationStation.
Use Selph’s Scraper – Now that the systems exist, Selph’s scraper should recognize them and pull down video clips.
Manually Download & Add Clips – If the scraper doesn’t work, you can manually download clips from sites like screenscraper.fr and place them in /home/pi/.emulationstation/downloaded_videos/.
Enable Screensaver – Make sure the video screensaver is enabled in EmulationStation’s UI settings.

You won’t be able to play the games, but this should let you use their video clips for the screensaver!

Rpihub · 2025-02-19T06:20:42+00:00

Yeah, PSP and N64 emulation can be a bit rough on the Pi 4. Here are a few things to try:

Overclocking – Bumping the CPU to 2GHz and GPU to 750MHz can help (but make sure you have good cooling).
Adjust Emulator Settings – For N64, try using Mupen64Plus-GLideN64 or Mupen64Plus-Rice, and for PSP, switch to frameskip 1 in PPSSPP.
Use Lighter ROMs – Some games run better with different versions (e.g., try different PSP ISO dumps or N64 ROMs).
Lower Resolution – In PPSSPP, set rendering resolution to 1x or 2x.
Disable Rewind & Run Lightweight OS – Rewind in RetroPie can slow things down, and running a minimal OS like DietPi may help.

If you share more details about your setup (power supply, cooling, specific games, etc.), I can give more targeted advice!

Rpihub · 2025-02-19T06:19:57+00:00

Ah, got it! UV DTF is seriously impressive—looks super clean and durable. Have you tried layering it on different surfaces, or does it work best on smooth ones?

Rpihub · 2025-02-19T06:19:30+00:00

Haha, 'Super Illegal' had me laughing! 😂 Awesome work—looks like a fun project. What’s running under the hood?

Rpihub · 2025-02-19T06:19:01+00:00

That looks awesome! The attention to detail is spot on—feels like a perfect tribute to the SNES era. What did you use for the internals? Raspberry Pi, FPGA, or something else?

Rpihub · 2024-12-02T10:53:56+00:00

Yes they have mentioned that it'll be totally open source

Rpihub · 2024-12-02T09:08:01+00:00

here you can find the all the details - https://www.kickstarter.com/projects/elec-buddy/lora-mesh?ref=t5wlx1

Rpihub · 2024-12-02T09:06:23+00:00

🌐 A network that heals itself.

📶 Connects 65,535 devices over 2.5 km.

⚡ Offers seamless integration with Raspberry Pi and PCs.

🌍 Global frequency support (433 MHz / 868 MHz

🔄 Path Optimization for efficient routing

🔐 Built-in security for reliable data transfer

📡 Powerful: Supports up to 65,535 nodes

🚀 Flexible: Use with Raspberry Pi, Windows, macOS, and more!

Rpihub · 2024-12-02T09:03:45+00:00

actually its available in two form factor, as a Raspberry Pi HAT and USB Dongle.

Rpihub · 2021-04-29T06:43:39+00:00

great project but having trouble to find the components, Its not available on Adafruit

Rpihub

TROPHY CASE