October 28, 2017 at 10:08 AM #16497
I haven’t tried older firmware…Can older firmware work with version 1.6?
Have you tried to connect via dvi to dvi?October 28, 2017 at 10:17 AM #16498
Yea, I have a 1.5 with installed audio HDMI which came with 0.76a-aud, no difference. And I’ve tried DVI TX mode today, still random drops.October 28, 2017 at 11:50 AM #16500
So you hav3 tried older firmware and there is no difference?
A 240p related issue is a very serious one.October 31, 2017 at 5:51 AM #16588
Did some testing today. Without modifying my setup, OSSC freshly rested a full day, I ran CPS2 didn’t cause any sync drop with OSSC (30 minutes), full game of MVC1 and Puzzle Fighter. I switched my SuperGun to the CPS3, I got sync drops at random every few to 5 minutes. I switched back to CPS2 MVC1, and I got sync drops every few to 5 minutes. The OSSC was on the entire time when I was switching. Couldn’t replicate the ‘no drop’ behavior when the OSSC first turned on.
I held the OSSC at the bottom and it felt really warm and I went to turn it on. I wonder if it’s load and temperature dependent when it’s starts randomly dropping systems with odd frequencies.October 31, 2017 at 12:18 PM #16600
No there are no thermal issues.
Instead of enjoying playing, I do tests every night. I do today again but I am sick and tired.
I will post with new evidenceOctober 31, 2017 at 11:59 PM #16639marqsParticipant
I’ve not used CPS2 much with OSSC after I started the dedicated digital AV interface project for it, but I don’t recall any sync drops. It’s true that the analog frontend IC in OSSC is sensitive to any sync variations, but if the issues only occur with Extron on the chain, then it leads to suspect that it may have some problem as well, or somehow contributes to grounding-related noise.November 1, 2017 at 1:36 PM #16666
My OSSC died yesterday! I played CPS3 and CPS for 2 hours with one total sync drop. Then it lost signal and it’s little screen started flashing.
I have mailed Bucko and waiting for his responseNovember 1, 2017 at 6:25 PM #16678
PVM line out end Extron line out make sync drops frequent enough to unplayable. But even with just the supergun connected and nothing else in the circuit, sync drops occur once in a while. But maybe it is my OSSC unit. I can’t tell since I only have one OSSC to test. I put 0,5 meter very high quality scart cable and sync drops were rarer yesterday. I don’t want to go back to analog display any more.
Unfortunately my OSSC unit is dead or something similar as I‘m afraid. I hope it can be repaired for me.
ThanksNovember 1, 2017 at 9:16 PM #16679BuckoA51Keymaster
Been working flat out toady I’ll get to your RMA now.November 1, 2017 at 11:01 PM #16691
Did it happen with the Extron or with?November 2, 2017 at 12:00 AM #16695
If you mean if OSSC died because of the Extron, no. It was a faulty unit from the beginning I suppose. Maybe a cold joint.
Playing CPS, CPS2, CPS3 through Extron to the BVM plays flawlessly without sync drops. OSSC was so sensitive, maybe to ground related noise as Marqs said. I am looking forward to try the new unit. If it will be sensitive too then I will have it playing arcade pcbs straight connected from the supergun to OSSC and a short scart cable. I will find a way to have OSSC hooked up through Extron only for the consoles. No sync drops with the following consoles and Extron as far as I have tested.
Mega drive 2 Jpn
PC Engine Duo R
N64 RGB Jpn
GameCube RGB Pal
I would also like to inform that Wii looks better connected to OSSC using high quality PACKAPUNCH RGB cable rather than official Nintendo Component. Component maybe 480p but image looks dark and greenish. RGB is 480i but colors are vibrant and very alive. Not greenish. Difference is obvious. I bought tha RGB cable recently and I haven’t seen Super Mario Galaxy so colorful. Test was in widescreen mode.November 2, 2017 at 12:05 AM #16698marqsParticipant
One thing I remember from testing arcade boards is that the digitizer chip randomly reported completely incorrect line counts / timings (even when its output was perfectly stable), triggering OSSC to change processing mode until I added some filtering logic. I’m not sure if this could be related to the same issue, but it can be easily checked by temporarily freezing OSSC’s mode detection logic. Once sync is stable, the easiest method to do that is pressing profile load hotkey on remote but not select any. There OSSC polls for user input and does not query the digitizer chip on (potentially false) mode changes.November 2, 2017 at 12:13 AM #16699
Thank you Marqs.
Unfortunately I can’t try that now but
user darkstrider2 can try it and let us know. It is quite easy to do it as you describe it. He only needs to press button “10+” on the far down corner of the remote and leave it there.November 2, 2017 at 12:56 AM #16701
Ok, I’ll test tonight and let you know. So I just turn on OSSC and press the “10+” button, then turn on CPS2? That’s it?November 2, 2017 at 12:59 AM #16702
You turn on OSSC then CPS2 and when you have stable sync you press the button of profile loading 10+. You leave it there waiting for a profile.
Let us know
- You must be logged in to reply to this topic.