@zing No, this isn't related. As you can see on https://wiki.recalbox.com/en/tutorials/video/crt/recalbox-on-crt-with-scart-dac the usage for system.crt.vertical_offset specified in recalbox.conf is:
" # Offset the image up (negative) or down (positive)
system.crt.vertical_offset=-2 "
This works well with negative values, but when using positive ones almost all NTSC systems fail when starting a game. It seems there's a bug in some script...
I was turning mad as most NTSC systems didn't start giving an error about missin bios or other causes, but I finally found the problem:
I'm using a crt TV via RGBPi cable and the image was shifted to the upper side of the screen. The default value on recalbox.conf for system.crt.vertical_offset is -3, so I changed it to 0 but the screen was still slightly offset, so I tried using other values (1,2,3), but then any NTSC game or system, including the 240p suite ones, doesn't start. Only PAL or portable console systems can be started. As soon as I change the value back to 0 or negative values all works fine again. I've even tried using +1, +2, +3... but it fails the same way.
Tell me if you need more information to reproduce the problem.
New unstable releases keep coming and on public repository latest commit is from February 26. Now nobody can help with development because we don't have access to the source code for the latest changes.
I'm in no way complaining of the rather slow development of Recalbox compared to other available systems, but I think keeping all development public like before would speed things up and make Recalbox a better system overall.
Hi,
During last weeks I saw new 4.1 unstable builds are being released, but since a month ago almost no new commits were submitted to public github or gitlab repositories.
Have development been migrated to private repositories? And if so, why?
I liked to have a look every morning to see the latest improvements. Anyone was able to learn how Recalbox works internally, and contribute with improvements or troubleshoot their problems and adapt it to their needs. Now it's impossible to do this if we want to be up to date with latest releases.
I think one of the main reasons for Recalbox becoming what it is today was it being public open source. I hope it stays this way for the future, not becoming a private/commercial project.
Pi3 internal Bluetooth has too much input lag for me too. It's much better if you disable Wifi on Recalbox, but still worse than my external BT dongle.
@subs Yes, I'm sure. But I'm curious to see how his solution works. Anyway, it shouldn't be too hard to deduce the schematics when it is released, as it should be using only resistors as the GPIO to SCART depicted on this forum.
He says he had to recompile some Raspberry Pi driver (¿overlay?), because the original VGA666 overlay interfered with analog audio on the Pi.
@subs Nope. I think his intention is selling it. He already ordered some PCBs with smd components. He is working on a script to make RetroPie change resolutions on the fly.
It seems the perfect solution. We will see how it all works when(if) it gets released...
Some Spanish fellows are working on a direct GPIO to SCART cable with audio. You can see the thread here: http://www.elotrolado.net/hilo_proyecto-rgb-pi-15khz-100-pixelperfect-scart-rgb-audio_2198660
