Let us know, Fudoh! I might give it a try this weekend if I can find some spare time..fafangus wrote:Fudoh is on his wayjuji82 wrote:Did anybody try OSSC - Crystalio II combo ? I cannot find some spare time to test this..

Let us know, Fudoh! I might give it a try this weekend if I can find some spare time..fafangus wrote:Fudoh is on his wayjuji82 wrote:Did anybody try OSSC - Crystalio II combo ? I cannot find some spare time to test this..
Something is definitely not right there, even with the SNES you should see something. Are you sure you haven't accidentally enabled and saved line triple mode?Samsung ks8000, ks8500, ks9000, ks9500 = shows initial 480p "gray" square, but once RGBS input is selected it fails top display an image. Sony 840d had the same results.
Scheduled improvementsmarqs wrote:Updated wikipage with link to DIY kit instructions and added fw changelog and roadmap.
BuckoA51 wrote:Something is definitely not right there, even with the SNES you should see something. Are you sure you haven't accidentally enabled and saved line triple mode?Samsung ks8000, ks8500, ks9000, ks9500 = shows initial 480p "gray" square, but once RGBS input is selected it fails top display an image. Sony 840d had the same results.
Might need a larger FPGA then, or at least the memory structure rewrite. Or maybe marqs said earlier it was kind of out of the scope of the project, dunno.Guspaz wrote:If I'm figuring right, that would require you to buffer roughly 11% of the scanlines on the input, so you'd need a ~27 scanline buffer, I think?
Instead of another IC, just more memory (bigger FPGA and possibly external SRAM) should be enough to implement OSD.lui wrote:Marqs, what type of IC would be required to have an OSD with the OSSC?marqs wrote:.
I'm presuming something along the lines of http://pdf1.alldatasheet.com/datasheet- ... 90096.html
Yes, it's not realistic with current HW.bobrocks95 wrote:Might need a larger FPGA then, or at least the memory structure rewrite. Or maybe marqs said earlier it was kind of out of the scope of the project, dunno.Guspaz wrote:If I'm figuring right, that would require you to buffer roughly 11% of the scanlines on the input, so you'd need a ~27 scanline buffer, I think?
The test pattern was mainly meant for DIY kit builders since it easily reveals if some IC pins are not soldered down correctly. It has some other uses too (highlights overcsan area and shows if limited/full-range is configured incorrectly) so I left it there as is. A nicer looking background with instructions would need memory - currently the pattern is generated by just logic elements.akumajo wrote:cosmetic suggestion :
change ossc default background to something sexier (logo, copyright, etc) and maybe with basic instructions ?*
*(Press 1 for SCART / Press 2 for COMPONENT / Press 3 for SCART)
Strikers1945guy wrote:"Do we....eat chicken balls?!"
The cable I am using is the same one as the DVDO Edge and that worked perfectly. The other 50 pro I had before had the same problem too though I am sure that one was actually faulty. Maybe for whatever reason my amp doesn't like the signal, though again, no issues with the Edge.@BuckoA51: just noticed your new 50 Pro + OSSC article, one thing different for me is that I have absolutely no issues with analogue audio integration > HDMI.
I used to though, but all problems were gone after switching to a more modern HDMI cable (was using an old non-high-speed before) and using a perfectly fine SinPro power brick (original one started acting).
I wouldn't mind if you copied the OSD code from GCVideo, but IIRC your project is in Verilog and mine is in VHDL... If a low-resolution text screen is good enough (it was for me), two or three M9K blocks should be sufficient: One for the font (128 chars) and one or two as video RAM.marqs wrote:Instead of another IC, just more memory (bigger FPGA and possibly external SRAM) should be enough to implement OSD.
Mine is like 1€, still no problems, maybe it's on the amp side yeah...BuckoA51 wrote:2 channel analogue audio shouldn't need an uprated cable anyway...
Strikers1945guy wrote:"Do we....eat chicken balls?!"
Are there any additional settings you need for the 256px optimized mode for SNES? When I select it with both my SFC consoles the red led on the OSSC lights up and my monitor loses the picture. It comes back every couple seconds for a split second, but nothing stable. My SC-500N1 capture card will continue to display the picture, but the colors are inverted most of the time. Sometimes it jumps back to normal colors for a brief moment.marqs wrote:The current optimal linetriple parameters are chosen for NES/SNES (256x240) and PSX 320-column mode (320x240). Until I manage to include sampling clock tweak option in the fw, those modes won't necessarily be good/compatible with other consoles. As for desync, does OSSC red LED light up or does your display just lose the picture for a moment?
Are you mooving from Winterfell ? XPCan't do that soon anyway I'm moving in a few days, gotta box all that junk.
ZellSF did.fafangus wrote:Anyone here tested the beast with a vp50 (not pro) ?
Yeah I'm out of innocent people to kill, going to invade another fresh castle (just moving to a new house ^^ can't wait to reinstall the machines and resume testing)fafangus wrote:Are you mooving from Winterfell ? XP
Strikers1945guy wrote:"Do we....eat chicken balls?!"
Mixing VHDL and Verilog modules should work, although it might make sense to modify HDL and write it in Verilog instead. Memory is really tight at the moment, but 2-3 M9Ks are not that much. Maybe I should add OSD on the roadmap and start thinking about implementation alternatives.Unseen wrote:I wouldn't mind if you copied the OSD code from GCVideo, but IIRC your project is in Verilog and mine is in VHDL... If a low-resolution text screen is good enough (it was for me), two or three M9K blocks should be sufficient: One for the font (128 chars) and one or two as video RAM.
Compatibility of 256px optimized mode is not that great at the momemt, especially with SNES that has uneven sync. There are a couple things on my list to try out to improve the mode so that it would work with more displays and without losing phase setting every time the mode is selected. Inverted colors are SC-500N1's fault though, and not related to OSSC. I tried generating s matching modeline for my SC-512N1 using PC and color inversion problem was also shown there.blizzz wrote:Are there any additional settings you need for the 256px optimized mode for SNES? When I select it with both my SFC consoles the red led on the OSSC lights up and my monitor loses the picture. It comes back every couple seconds for a split second, but nothing stable. My SC-500N1 capture card will continue to display the picture, but the colors are inverted most of the time. Sometimes it jumps back to normal colors for a brief moment.
lol I kept forgetting to mention this. Can't remember how many times I've gone to check the OP for info without thinking. It's definitely appreciated.marqs wrote:Updated first post to point new people to relevant places. Should have done that already before the thread went over 50 pages but better late than never...
Did you use it to mix analogue audio into the hdmi? Bucko seemed to have problems with that and the vp50 pro...ZellSF wrote:
Really liking the DVDO VP50 + OSSC combo btw. Perfect in everything (except the minor color range issue).
On my test setup, I have it set to use analog audio from the Sega Genesis and digital audio from the PlayStation 2. Both convert fine to HDMI. Though that's not a function I actually plan to use once I get everything set up properly.RocketBelt wrote:Did you use it to mix analogue audio into the hdmi? Bucko seemed to have problems with that and the vp50 pro...ZellSF wrote:
Really liking the DVDO VP50 + OSSC combo btw. Perfect in everything (except the minor color range issue).