Unfortunately due to the rules here and the fact the system is current gen we can't post any links to where its possible to get the files which is understandable because its highly illegal! Discussing might be alright though you'll have to check with assembler.

I was looking at the manuals, it looks like you can pull hdcp free video from the system if you were so inclined.

Click to expand...

Oh damn that'd be awesome. I have an older Dell 2405FPW which happily accepts 1080i over component but damned if it'll do 1080p despite DVI accepting what amounts to 1200p. I ordered a HDMI->DVI adapter about a week ago and want to play around with it on my 360 but I'm 99% sure a PS3 won't accept this setup due to HDCP being required for more than just DVD or Blu-ray playback. Why you'd need it while playing games is beyond me other than forcing the consumer to upgrade their TV for arbitrary reasons.

Without HDCP I'm pretty sure my 2405FPW will happily accept a 1080p signal over DVI from an HDMI port.

HDCP is a "feature" that requires the I2C connection (that's present on DVI, too - it originates from VGA's DDC), and access to the pixeldata itself (which also exist on DVI). There is no reason why DVI cannot be protected.

In fact, there are both transmitters and sinks doing HDCP on DVI.

The technical difference between DVI and HDMI is the packetized transfer of audio and a few other data (colorspace information, transmitter name, ...), plus the different set of resolutions (all PC-like resolutions are "DVI resolutions" whereas all HDTV-based resolutions are "HDMI resolutions"). But most DVI sinks accept at least 480p (as it's remarkable similar to 640x480x60), and most HDMI sinks also accept DVI resolutions. Sometimes they don't announce them in their EDID. The PS3, as far as I know, doesn't output any DVI resolution. Not because it can't, but because it won't.

HDCP over analog is impossible, because the scrambling is based on the digital pixeldata.

My monitor (Dell 2405FPW) has a component, composite and s-video input and has accepted virtually everything I've thrown at it. I don't see why it wouldn't be able to handle 1080p when it's doing what amounts to 1200p and 1080p last night with my laptop.

Though I'd imagine if someone thought they should someone would implement it over composite and RF.

Click to expand...

Not technically related to HDCP, but there was a similar copy protection scheme for VHS etc which was called Macrovision. Unfortunately for the industry, VHS players were already in the wild without any Macrovision capabilities, and those players basically ignored it.

I'm not calling HDCP a good scheme, but calling Macrovision a similar scheme is really an insult.

Macrovision tries to confuse the analog VCR by inserting rogue sync signals. It's not that a VCR has to support Macrovision to become confused - at least that was the intention. However, some VCRs had better sync regeneration circuits so it would still work.

Macrovision is a serious pita. It's even more useless than HDCP, and the MV-specific registers of most, if not all video encoders are always protected with a special NDA that you have to sign - after you licensed Macrovision.

Macrovision tries to confuse the analog VCR by inserting rogue sync signals. It's not that a VCR has to support Macrovision to become confused - at least that was the intention. However, some VCRs had better sync regeneration circuits so it would still work.

Click to expand...

Thanks for the correction. I went away and had a read about it and yeah, my understanding of how it worked was totally incorrect - I assumed it'd be a Macrovision "don't copy" flag in overscan and Macrovision-compliant VHS players would detect it and scramble the signal when recording, but it's nothing like that at all. It mainly seems to work by blitzing brightness levels during overscan, which freaks out the automatic luminance detection in the recording VCR. Pretty ugly solution.