Sorry, there's a typo in the last comment. Use this command instead:

for %a in ("*.mp4") do ffmpeg -i "%a" -c:v libx264 -preset fast -crf 23 -vf scale=320:240 -c:aa aac -b:a 80k -r 30 "converted\%~na.mp4"

THX

Oh thats nice, thank you. This will come handy for sure.

@buzz said in CRT-Pi Shader differs on Pi Zero vs. Pi 3?:

@riverstorm I set render resolution to default (video res) and video res to 720p. So they are both 720p. Looks good to me on my screen.

Thanks Buzz this worked perfect and runs the older games listed above just fine. In either 720 or 1080 with both Udb's overlays on and crt-pi shader enabled. Stock is a bit--bit sluggish at 1080 but is completely playable. Overclocked is no problem. I did not have FPS up but just more going off feel.

I also tried Udb's overlays. The 1080 overlay worked in both 720 and 1080 and fit perfect. I am guessing it's just downscaled in 720. You need to set both the group and mode to get the output set to 720. Just the mode doesn't work.

I also did not know the difference between video and output settings in the quick config as they seem like they should be the same logically thinking but video is the one to choose.

One thing that was off and didn't work correctly was Dank's custom shader configs. I used a stock 4.3 image and updated the script, retroarch core and lr-mame2003. When I ran a game it would just show me the top left corner of the game like it was really zoomed in. I am not sure if it was something as simple as a setting to get them working again.

I did get a modest overclock on the arm but decent on the gpu & sdram. The arm_freq up to 1075 (7% increase), gpu_freq (which includes the core_freq & v3d_freq) up to 525 (24% increase) and the sdram_freq up to 525 (24% increase) also.

The arm_freq is a bit modest. It is the same SoC as the Pi 1 but the manufacturing technique improved in the 4 years between releases and they were able to release it as 1,000 MHz stable whereas the Pi 1 was released as 700 MHz stable at the time. I would guess it's really pushed to it's limits already at 1000 but I see some that are getting good silicone at the top of the bell curve of variance are getting 1.2 GHz.

It's already overvolted to 6 but a simple small heatsink barely protruding through an acrylic case kept mine more than cool enough with nothing special.

A good base starting point is 1000 for arm and 500 for gpu & sdram and I worked up from there.

I did get some annoying static-ish feedback noise in Elevator Action but games like Rastan, old classics, etc. worked great.

For shaders 480 looks muddy (I prefer the solid jaggy graphics over this), 720 is acceptable but at 1080 you can clearly see a difference on a 4k TV and looks great. It might come down to performance when choosing which resolution and if using overlays and shaders.

I do like the zero but it seems like a niche market for handhelds or some special project. It's sluggish in everything from bootup, loading games, etc. compared to the 3. I think if you have room the 3 is the way to go but the zero is nice and incredibly small. Easy to velcro to the back of the TV or something. Using thin HDMI and power cables would make it easy to hide as it's quite a bit smaller then the 3 with a case.

Hi all. Just adding to this thread to mention that I was also having an issue where, when attempting to manually append a disc in Retroarch, no ROMs were appearing in my PSX ROMs folder. The above solution worked for me. This is the step-by-step for the technologically challenged (like me):

Using your computer, navigate to the "configs" folder in your RetroPie drive Go to the folder of the emulator for which your having an issue (in my case, "psx") Edit the retroarch.cfg file by right clicking it and choosing to open it in some kind of text editing program Add this line to that text file, substituting the 'psx' part for the relevant system in your case:

rgui_browser_directory = "/home/pi/RetroPie/roms/psx"

Save the file Restart your Rasberry Pi

When you go to append a disc, you should now see all of your ROM files.

@tonytoon I forgot to mention that the displays I have found are typically VGA, but many of them also have DVI ports. I found a cheap HDMI-to-DVI adapter which is the way to go. DVI cables are bulky, so this little adapter basically upgrades the display to HDMI.

Also, I un-shell them and discard the plastic bezel. This sometimes requires me to relocate adjustment buttons which has not been a problem. You end up with a screw-mountable steel bracket reinforced screen with the driver board/power intact, just not all of the branded plastic.

Hello and thanks for reply.
Yes, it's Bluetooth.

I've tried to pair it via Bluetooth pairing procedure.
It's recognized by Raspberry, but when I go to PAIR it, I got a Timeout error.

Same error I receive pairing controller with my Mac (I can pair ORIGINAL PS3 Wireless controller).

I think I'll trash out the controller and use an Xbox 360 wireless controller.

@kingrun Glad to hear it's all good now.

It's a raspberry pi 3 model B running Retropie 4.3 rpi2 rpi3. There is no error message and I am very new to Linux. I will post pics. The controller is recognized but when I try and register this happens..0_1520418277954_IMG_20180307_015618306.jpg 0_1520418330698_IMG_20180307_015804652_BURST000_COVER_TOP.jpg
I hope that helps.

@mitu hey. thanks for your help. Did not know that Linux was case sensitive. Changed all folders, and did a find and replace to all lower case in the xml and all is good! Noob at all this but I am learning alot as I go. Thanks again for the help!

I managed to change the serting of the pi to reserved ip and had no issiues "yet" if it returns ill let you guys know, i still connect to winscp via the username, if the issue returns ill use the ip of the pi on winscp as the username to see what happens...

Oh nevermind. It looks like the default setting is false anyway. Not sure why I was confused into thinking it was on by default.

# Smoothens picture with bilinear filtering. Should be disabled if using pixel shaders. video_smooth = "false"

Well, I tested it out with RetroArch framerate being displayed and it runs at a solid 59.9 to 60.0 fps. This is also after I updated my /boot/config.txt to use sdram_freq=500

Still doesn't quite look as good as when shaders are disabled but I am thinking this is about as good as its going to get.

Edit: I also sacrificed the curvature and tweaked my overlay bezel art to push it as fast as it could go with at least the zfast_standard shader for both Waku Waku 7 and Samurai Shodown 4 (the only games I have installed that demonstrate this issue to my knowledge)

@bogus Glad you got it solved.

@lostless Thanks dude for verifying ! Now back to gaming!! ;-)

@jayram1408 Swearing / personal insults on the forum as your first post. Well done.

@whistle05 you get this if you dont have an internet connection to the pi

@alturis said in EmulationStation issue with marquee.png:

Or potentially an issue with how the ComicBook theme is setting up the marquee element. Will have to look at that later tonight.

Nah looks pretty simple and straightforward to me.

<image name="md_marquee"> <pos>0.74 0.086</pos> <maxSize>0.26 0.1</maxSize> <origin>0.5 0.5</origin> </image>

Though now I am wondering if is something with the handling of the "maxSize" feature of ES that is at play here.