[QUOTE=kevinfishburne;41326]Also I like what tekn0 is cooking. I found this HDMI to composite converter also on the radioshack site:
Couldn’t find a similar product for S-Video, though. [/QUOTE]
I actually got both of them. The composite looks like shit in comparison to the component. The component feels very RGB’ish. The picture is sharp and crisp in comparison.
If i can somehow solve the sync issue the converter will be gold. As the pi3 is the perfect 2d 8bit/16bit box.
Thanks hunterk. Do you think it might be something that is fixable at the driver level? Or would I need to mod the hardware?
It is so close to working for only $40! 
Yeah, dunno. The first place to check would be your HDMI settings.
Did you try with custom mode like :
hdmi_cvt=768 240 60 1 0 0 0
“The one you’re probably interested in is the custom resolution config file, where you can modify the following line to set up your output resolution - it does look like you’re limited to 240p @ 60fps, but the horizontal resolution can be anything you want up to 1920x240: hdmi_cvt=768 240 60 1 0 0 0”.
@gouchi oh man, that video/description is a good find! I might have to switch my cab over to an rpi3 from my shitty old Atom board, which can’t manage full speed on PS1, CPS3, Mortal Kombat, etc.
Does anyone know how/if an rpi3 handles Killer Instinct?
[QUOTE=hunterk;41365]@gouchi oh man, that video/description is a good find! I might have to switch my cab over to an rpi3 from my shitty old Atom board, which can’t manage full speed on PS1, CPS3, Mortal Kombat, etc.
Does anyone know how/if an rpi3 handles Killer Instinct?[/QUOTE]
I am trying to test this for you now. But I am unable to get chd’s to load.
i believe i can get the chds to load in mame2003 (they need to be in ROMDIR/romname/romname.zip eg ROMDIR/kinst/kinst.zip - obviously you also need a valid game rom in the ROMDIR also) but either they’re not the right ‘version’ or CHD support is broken in that core… the game loads up with a coloured screen but gets stuck, and i think i scanned the chds and they said they were the wrong version, but i couldn’t find any others.
Yeah, I think they might only work in mame2010 and up. No worries, guys. Thanks for the effort
I get the same issue in lakka. Just a blue screen. I also tried retropie with no luck. I had my dir structure like this.
Roms/mame/kinst.zip Roms/mame/kinst/kinst.chd
I also googled around and found some threads about people saying chds dont run well. But then I see videos of people running street fighter 3 on their pi’s and I thought this was a chd.
[QUOTE=tekn0;41428]I get the same issue in lakka. Just a blue screen. I also tried retropie with no luck. I had my dir structure like this.
Roms/mame/kinst.zip Roms/mame/kinst/kinst.chd
I also googled around and found some threads about people saying chds dont run well. But then I see videos of people running street fighter 3 on their pi’s and I thought this was a chd.[/QUOTE] yeah you can run SFIII using fba-libretro (lr-fba-next in retropie) and it doesn’t need a CHD. i think a lot of games in FBA are hacked so they don’t need a CHD to run.
i’m not convinced mame2003 doesn’t support CHDs/kinst as i could never find the right versions of the CHDs according to my dat file. even the ones in my 0.78 romset were wrong, and all the chds i find online are the wrong version also.
in any case, there’s preliminary support for it in FBA latest so hopefully FBA eventually runs it fully
[QUOTE=gouchi;41357]Did you try with custom mode like :
hdmi_cvt=768 240 60 1 0 0 0
“The one you’re probably interested in is the custom resolution config file, where you can modify the following line to set up your output resolution - it does look like you’re limited to 240p @ 60fps, but the horizontal resolution can be anything you want up to 1920x240: hdmi_cvt=768 240 60 1 0 0 0”.
Source[/QUOTE]
Thanks gouchi. I am actually getting some help from the owner of that video directly. He suggested some direction that I will test as soon as I can.
If I can get this all working I will make a full video tutorial on how to set it all up for NTSC component. With all of the input lag and core patching the guys are doing in the other thread. HDMI 240p combined with their work could really create the ultimate CRT TV setup.
[QUOTE=dankcushions;41429] i’m not convinced mame2003 doesn’t support CHDs/kinst as i could never find the right versions of the CHDs according to my dat file. even the ones in my 0.78 romset were wrong, and all the chds i find online are the wrong version also.[/QUOTE] might try this again later - if anyone is interested, here’s the checksums for the kinst.chd that mame2003 is looking for: DISK_IMAGE( “kinst.chd”, 0, MD5(6d4c2f152c9a18ab3a9b05b8804306a8) SHA1(a37a2c5e52ea936a715210d237874dd573bb002f) )
[QUOTE=dankcushions;41431]might try this again later - if anyone is interested, here’s the checksums for the kinst.chd that mame2003 is looking for: DISK_IMAGE( “kinst.chd”, 0, MD5(6d4c2f152c9a18ab3a9b05b8804306a8) SHA1(a37a2c5e52ea936a715210d237874dd573bb002f) )[/QUOTE]
I believe that version of the CHD is in circulation as part of the “MAME 2003 Reference Set”
just downloaded! unfortunately it’s the same kinst.chd that i had before that doesn’t work: sha1= 77ec1dcd7d41ece81be4dd44682a1a82e27b6330 md5 = c55d552c3a698f839d32c41203213dc9
i know there are some cd5 manager programs that can change the version… might have some luck there. could be something else, dunno…
[QUOTE=dankcushions;41532]just downloaded! unfortunately it’s the same kinst.chd that i had before that doesn’t work: sha1= 77ec1dcd7d41ece81be4dd44682a1a82e27b6330 md5 = c55d552c3a698f839d32c41203213dc9
i know there are some cd5 manager programs that can change the version… might have some luck there. could be something else, dunno…[/QUOTE]
Are you looking at the checksum for the whole file, or the checksum of the disk data stored within the CHD? According to the ‘Compact History of MAME’ in the Pleasure Dome forum, CHD v3 was adopted from MAME 0.77u1 and later. I’m able to validate the kinst.chd from the MAME 2003 Reference Set as CHD v3 in chdman – it’s also showing the same sha1 that you are looking for: a37a2c5e52ea936a715210d237874dd573bb002f.
I’m validating this kinst.chd successfully with the ProgettoSNAPS DAT in ClrMamePro with all of the CRC/SHA verification options enabled as well. I think it’s the one, but I’m curious if that’s not true. Here’s my chdman output:
chdman - MAME Compressed Hunks of Data (CHD) manager 0.146 (May 21 2012)
Input file: kinst.chd
File Version: 3
Logical size: 131,076,608 bytes
Hunk Size: 4,096 bytes
Total Hunks: 32,002
Unit Size: 512 bytes
Total Units: 256,009
Compression: zlib (Deflate)
CHD size: 95,627,930 bytes
Ratio: 73.0%
SHA1: a37a2c5e52ea936a715210d237874dd573bb002f
Metadata: Tag='GDDD' Index=0 Length=34 bytes
CYLS:419,HEADS:13,SECS:47,BPS:512.
oh! well, that’s good unfortunately it doesn’t make a difference to lr-mame2003 as it still doesn’t run, even with apparently the right file. i’d be interested to know if it runs on standalone mame 0.78 (i think it’s still available on mamedev) - which would mean there’s something wrong with the core… but what?
No go on my 240p HDMI to component cable. I had originally been experimenting with 480i and the shakiness was bad. Thats why i started getting into 240p native as even though the scrolling was happening, there was zero shake. I also tried Pal resolutions and refresh rates but it was a no go. I tried many different trial and error resolutions using custom resolutions, but I was still not able to get rid of the vertical scrolling (Custom resolutions scroll doubled the speed when I could get partial sync).
The goal was do try and do what the modded wii does sending native 240p vi component, but in my case over hdmi with the pi with lakka. I just don’t know enough to solve the issue. I created like 4 forum posts on various boards and have got no answers so I guess I will return the cable. I tried soooo many hdmi_cvt settings with no luck getting the scrolling fixed. hdmi_timing settings brick my pi if they are wrong and I have to reflash every time I want to try a new one, so I stopped that game after 2 days of trying.
I did contact the cable company “Hdfury” and they said they are working on a product due next year called “RetroFury” that should solve/do what we are looking for. So I guess I will just wait until 2017 and revisit.
That’s interesting! I’ve been wondering why no companies are getting in on the retro tech. Seems like a pretty lucrative niche, judging by the framemeister market.
I agree. I also thought about contacting “hdretrovision” the makers of the highdef snes cables to suggest a potential product as they seemed to be working on their own XRBGmini.
I do wonder if lakka had the ability to switch custom resolutions in the video settings like the wii versions 1.2.2 and below had. If that would of been a work around, but I just don’t know enough about video. I’m just a very avid retro gaming enthusiast As my wii is running at 480i with a bit of shake, but once I launch retroarch and switch to like 512x240 everything including the natural scan lines lock into place.
Yeah, that stuff was Wii-specific, as I think it leverages the Wii’s hardware specially to do it.
I didn’t know hdretrovision was working on their own upscaler. Exciting times!