October 1, 2022 at 12:47 PM #55121
Thanks for trying.October 1, 2022 at 3:56 PM #55125
I have ordered a retro tink scart which plays the pc engine with no drop outs. It’s not quite as sharp but the plug and play nature suits me better than the OSSC. Thanks for you help.October 4, 2022 at 9:58 AM #55176
Out of interest which PC engine was it exactly?October 10, 2022 at 7:59 AM #55251kamonegiParticipant
I tried PC-ENGINE(White)+Super CD-ROM, PC-ENGINE(CoreGrafx)+Super CD-ROM. It’s same problem.
And I take singnal from EXT port like this
It’s better than use composite as Csync. But also lose sync.October 10, 2022 at 8:29 AM #55252
Thanks Kamonegi, I was thinking of importing another PC Engine to test, I won’t now you are having the same issue. The one I was using was an original white Pc Engine.October 10, 2022 at 9:47 AM #55254
No issues here on my Supergrafx with Super SD system 3. I think I’ve another PC Engine in storage I’ll try though.November 10, 2022 at 11:56 PM #55712
I had some rare occasions of picture dropout on my white pce which has an rgb amp that I contructed myself and has been serving me well all these years. Its based on an old schematic and its supposed to be specifficly designed for the pce. It has 4 amps, 3 for the rgb and a slightly different one for the sync and it is comprised of a transistor (each), resistors and capacitors. The pce is on an IFU-30 with a cdrom2 but I get the RGB from the PCE and the stereo sound from the two RCAs of the IFU.
In my case, using the default settings of the OSSC (v1.6, fw 0.9a) and 2x upscale, I would rarely get a dropout for a second and the picture would come back. When I say rarely I mean that you could complete a game (Dynastic hero which is long for example) and it would happen once or twice throughout.
Fidling with pre and post coast and increasing HSync tolerance didn’t solve it. Neither the Sync LPF which is by default at 2.5Mhz.
I noticed that when turning on the OSSC and after the PCE, the OSSC would lock at 60.28Hz. If after that I turned off the OSSC and then back on, it would lock on 60.05Hz or 59.98Hz (OSSC LCD screen). Others have reported these same frequencies when using a PCE with the OSSC.
There hasn’t been one time that I would get a picture dropout when the OSSC is locked at 59.98Hz (I haven’t tried at 60.05Hz yet but I suspect the case will be the same). I’m talking finishing Dracula X and Star Parodia and not having a single dropout.
Also to mention that when my OSSC locks on a frequency, it doesn’t change on it’s own, its stable.
I suspect that the OSSC doesn’t detect the frequency of the sync signal correctly on console power up and this definitely seems to be responsible for even these rare dropouts.
I mean, I know the PCE doesn’t output 60.28Hz, thats for sure. It should be around 59.89Hz or 59.83Hz depending on the software (Voultar). It is known to fluctuate.
One other thing that I noticed and please if someone knows please tell me… The LCD may show 60.28Hz (or what have you) but if I press “info” on the remote the window that appears on screen says “FPGA 59.82Hz” among other things. Should these two be different? Could the 59.82Hz be the output of the OSSC and not the input and thats why they differ?November 15, 2022 at 10:59 AM #55813
I think it’s just the case that OSSCs reporting of the Hz isn’t always terribly accurate.November 15, 2022 at 11:40 AM #55817
Well yes but that isn’t a problem. My DUO and DUO-R start at 60.28Hz and stay there (there’s no re-sync to another frequency).
The white I have on the other hand, begins at 68.28 and later on it loses sync for a second and re syncs at 60.05Hz. And some times later on it does it again but resyncs on 60.05 again.
Well I redid the mod on this white yesterday…. placed the amp (4 channel) on another spot and not on the oscillator that was initially, and also taped the R G B and Sync signals from the cpu chip and not the expansion port that was initially.
Played for an hour yesterday and remained at the initial 60.28Hz. We will see….
November 15, 2022 at 7:32 PM #55821marqsParticipant
- This reply was modified 2 weeks, 5 days ago by GTSS.
The frequency shown on the screen is based on status readback from video ADC which is not always accurate. Once ADC has been configured for the source, accurate refresh rate can be calculated via FPGA and is shown when ‘info’ is pressed. If you suspect the problem is related to resyncing to different frequency, you can try freezing mode detection by opening the load profile prompt via remote hotkey and leaving it there.November 16, 2022 at 9:16 AM #55827
- You must be logged in to reply to this topic.