Neodev wrote:
Why are we having this "issue" ? mostly cause we are euro guys and our equipment is really different than the one you usa guys are used to have/work with.
So, what are we going to do ? listen, and think.
My own opinion about this is : the ones that have such equipment, should have no issue while doing custom cables to get the "issue" solved. Pcengines lack of rgb output, so the ones having such equipment had to mod theyr consoles and this is far much more than make a cable.
Lets put things on the table, this is an issue that gets fixed with a 8usd cable (correct me if i am wrong), not the end of the world, or something to start a drama from it.
Just relativize things. We all know the issue as today, you guys know much more than us about the custom video hardware you are using. Lets find a solution.
This statement makes no sense to me.
You sold a device claiming to be compatible with MD2 cables and outputting csync. First you mistakenly put the RGB line resistors and caps into your device, until people here explained that they are present in any on-spec MD2 cable and should be removed. Then you forgot to account for the 0.8vpp video levels of the PC Engine until people here explained how to attenuate the signal within the limitations of your design. Now it seems your csync output isn't working as it should.
All of these problems could've been easily detected by simple measurements and basic tests. If you had hooked up a scope to the RGB outputs of your device and/or the PC engine or just looked at the test screens of the 240p test suite you would've instantly seen that something was off spec and not correct. Thankfully people here pointed out these problems and their solutions before the device was shipped. If you had just tested your device with the widely used and often recommended cables of a trusted seller and hooked it up to the most widely used devices for using old consoles with modern TVs you would've noticed that csync issue as well.
So please don't insult our intelligence by claiming this is "cause we are euro guys and our equipment is really different" or a problem with our "custom video hardware" and that if we're so smart we should figure this out ourselves. This is a problem with your design & testing. That's your job.
I understand that people make mistakes and that you're a small team, but this attitude of "it's just a cable" and "there's no perfect solution" and "nobody can even notice a bit of white crush" etc. really irks me. If you made a mistake, admit to it and don't blame it on literally everything else.
And I'd very much like to correct you on the 8$ cable thing. Haven't you learned from your own cable issues? If you buy cheap random cables you get what you pay for, a poorly shielded one that may or may not have the required components in them, probably using some artifact prone sync type bleeding into audio & RGB. The shielded MD2 cables from RGC cost ~38$, and from my experience they frequently make a worthwhile difference over the basic ones (which are still far more than 8$).