|
|||||||||
|
Thread Tools | Search this Thread |
January 4th, 2007, 09:14 AM | #16 |
Convergent Design
Join Date: Apr 2005
Location: Colorado Springs, CO
Posts: 869
|
I can absolutly assure you that the HDMI output from a "live camera" has never been compressed. MPEG2 compression adds anywhere from 15 to 30 frames of additional latency to the signal. We see this latency when an HDV camera is connected to our HD-Connect SI box, which does HDV -> HD-SDI conversion. There is an undeniable delay of the video and audio signal (about 1 second). However, when we use our HD-Connect MI (HDMI -> HD-SDI) converter there is no perceptible delay in the audio and video.
Furthermore, if the HDMI output from a "live camera" was indeed compressed, then the camcorder would need to perform both a compression and decompression process simultaneously. This would add even more latency and further increase the power consumption (always a concern for battery powered devices). So, the HDMI output from a live camera has indeed never seen a compression, just like the HD-SDI ouput from the Canon (in live mode). Sony likely has a number of marketing reasons to not advertize or promote this capability. Mike Schell
__________________
Mike Schell Convergent Design |
January 4th, 2007, 10:41 AM | #17 | |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Quote:
From another perspective, how do you explain that Sony confirmed that their single chip range of cameras, the HC3, UX1 and SR1 output compressed HDMI signals @ 25 Mbps? That there is no way to switch from a 1.485 Gbps stream to a 25 Mbps stream? This means that you can only use HDMI live and not afterwards. How do you explain the fact that the HDMI connection is TV compatible, but the TV HDMI input is limited to 25 Mbps and the camera has no way of switching between the two different signal streams? How do you explain, from Sony's perspective, the price difference between the XDCAM-HD 330 and 350 due to HD-SDI (and some other differences), the relatively high price of the Canon H1 with HD-SDI, the price differential between the Canon A1 and G1 with HD-SDI and a long list of possible other examples? If you are correct, Sony is definitely embarked on a route that can be designated as a price fighter. That is a new one for me. Also, for the first time in their existence, they act mute in promotional terms. Sorry, I just don't buy it without confirmation from Sony. Mike, please do not consider this a (personal) attack. Just expressing my doubts. It might be worthwhile to check whether a HD-SDI signal from a camera (H1, G1, 350 or similar) converted to HDMI can be directly displayed on TV during live recording, and repeat that for HDMI. I assume (hopefully I'm wrong) HDMI is no problem, but the HD-SDI data rate is just too much for the TV and chokes on it. Just in the lucky case that I find a 4.2 liter V8 under the hood of the car sold as a 2.0 liter 4 cylinder, that nobody told me about, I consider the start of 2007 very, very good. Last edited by Harm Millaard; January 4th, 2007 at 11:54 AM. |
|
January 4th, 2007, 11:34 AM | #18 |
Barry Wan Kenobi
Join Date: Jul 2003
Location: North Carolina
Posts: 3,863
|
Not sure why you think this is so breakthrough of a feature -- every HD camera on the market outputs uncompressed high-def through at least analog component outputs; the XHG1 and XLH1 do so through genuine HD-SDI, and the tiny little Sony HC3 and the AVC-HD cameras from Sony and Panasonic all output uncompressed digital HD through their HDMI ports.
It's a great feature, sure, but it's not like it's a) hidden, or b) unique to the V1U. The HC3 brought uncompressed HDMI output to the market almost a year ago. |
January 4th, 2007, 11:42 AM | #19 | |
Barry Wan Kenobi
Join Date: Jul 2003
Location: North Carolina
Posts: 3,863
|
Quote:
The only way they could be outputting the 25mbps signal would be if they uncompressed it to full uncompressed before transmitting, and you'd know that real quickly on an HDV camcorder because you'd see a 1/2-second lag between action in front of the lens and when that action shows up on the monitor. HDV has to buffer 1/2 second of footage before it can compress a GOP, so HDV output is always delayed by a minimum of 1/2 second (shorter GOPs can reduce that time, but Sony always uses 1/2-second GOPs). So -- if someone were to report that the HDMI monitoring on their Sony camcorder was lagging 1/2 second behind reality, then yes that would be an indication that the HDMI output was perhaps being compressed to HDV, and then uncompressed and output over HDMI. But AFAIK there is no lag, which would in and of itself be proof positive that the HDMI output has not undergone 25mbps HDV compression. |
|
January 4th, 2007, 12:13 PM | #20 | |
Trustee
Join Date: Aug 2006
Location: Rotterdam, Netherlands
Posts: 1,832
|
Quote:
|
|
January 4th, 2007, 12:35 PM | #21 |
Convergent Design
Join Date: Apr 2005
Location: Colorado Springs, CO
Posts: 869
|
Hi Harm-
This is also not a personal attack, but I don't think you have a clear understanding of HDMI. May I suggest that you visit hdmi.org and also download a copy of our white paper: "HDMI in HDV and AVCHD camcorders". Firstoff, HDMI only supports uncompressed video, not 25 Mbps compressed video. Camcorders and decks use an MPEG2 decoder chip to decompress the (25 Mbps) HDV or AVCHD video/audio before it is output on the HDMI port (this assumes playback from a tape, DVD or hard drive). In the case of live capture, the video stream out the HDMI port has never been compressed. Our HDMI white paper, available from the Convergent Design web site, shows the video/audio dataflow through the camcorder/deck. This diagram should help everyone better understand how the video and audio are processed. I can't comment on the marketing reasons behind adding HDMI output to camcorders and decks. I do know it works and produces excellent quality video/audio. Yes, 2007 will indeed be a very very good year. Mike Schell Convergent Design
__________________
Mike Schell Convergent Design |
January 4th, 2007, 04:29 PM | #22 | |
Regular Crew
Join Date: Oct 2005
Location: San Jose, CA
Posts: 141
|
lots of good responses to the initial line of questions. i'll just add this...
Quote:
|
|
January 4th, 2007, 05:21 PM | #23 | |
Barry Wan Kenobi
Join Date: Jul 2003
Location: North Carolina
Posts: 3,863
|
Quote:
|
|
January 4th, 2007, 09:01 PM | #24 |
Regular Crew
Join Date: Aug 2006
Location: Currently on the move!
Posts: 33
|
Great answers! - More questions...
As usual, a thread full of useful replies!
Some more questions though that I am really hoping for an answer to: 1) If you want to capture live using the HDMI but without using RAID, which is the best way to go, for bluescreen work? Is there a way to keep full 4.2.2 without using DVCPROHD and thus scaling down the image? And if there is such a way, what are it's potential drawbacks? 2) How about this Gefen adaptor? Feed component and sound, export HDMI. Does it work? What are the loses? Or what could be the loses? (I mean, technically, is there a lot of ways to convert component to HDMI?) 3) Thomas: You mention in your post that "if you have a progressive frame sitting inside of a 1080i stream then you end up with chroma jaggies because the chroma samples may not line up exactly with the luma samples because they alternate every other line." From what I gathered you are discussing the V1's recording of progressive signal on tape. How about the signal of say A1's 24f from component? From what I understand, A1's component signal is always interlaced - therefore another "progressive frame sitting inside of a 1080i stream." Would that mean that this signal would suffer from the same problems (in reference always to bluescreen work). Given Mike's point that component's signal is exactly the same as SDI, I guess bluescreening with H1 -> 24F -> SDI would give the same results (and problems, IF any). 4) Finaly, one thing I really don't understand: How come the sensors of these cameras capture 4.2.2 and not 4.4.4? I really cannot understand what these sensors "see"! I thought sensors "see" all the colour spectrum and AFTER they capture that, then their signal is processed and encoded to whatever codec is to be used. Andromeda plug in for the DVX claims a full 4.4.4 capture out of the sensor. How come these HD sensors, made so many years after DVX, capture only 4.2.2? Please excuse my ignorance! I just cannot understand how this works! Thanks a lot, Thanasis |
January 4th, 2007, 10:03 PM | #25 | |
Trustee
Join Date: Mar 2004
Location: Milwaukee, WI
Posts: 1,719
|
Quote:
|
|
January 5th, 2007, 02:37 AM | #26 | ||||||||||
Regular Crew
Join Date: Jan 2006
Location: Vancouver, BC
Posts: 62
|
Hey everyone thanks for contributing to this humble thread. Some of the points you guys have brought up raised a few questions for me.
Quote:
Quote:
Quote:
Quote:
Quote:
Quote:
The diagram at the sony V1U site http://bssc.sel.sony.com/Broadcastan...U/devices.html seems to contradict this as it shows the component out AFTER the image has been converted to 1440x1080. Wouldn't this contradict what you're saying about component data stream being the same as HDMI? Unfortunately this diagram doesn't label where HDMI out is in the chain. The bottom line HDMI question here seems to be, as I know this is still a confusing subject for a lot of people on the net, what do the following resolution size do the following cameras output through HDMI? Sony V1U Sony HC3 Sony SR1 Sony UX1 Quote:
Quote:
Quote:
Quote:
|
||||||||||
January 5th, 2007, 08:21 AM | #27 | |
Major Player
Join Date: Feb 2004
Location: Philadelphia, PA, USA
Posts: 548
|
Quote:
The Green channel should be virtually white for a green screen, so using a dark subject provides lots of high-detail contrast to work with, resulting in a better starting point even for color difference and vector based keyers like Keylight and Primatte. If you put a bright subject in front of a green screen, though, there's little-to-no contrast in the green channel to work with. Your color keying operations end up being based on the blocky data in Red & Blue. This is why it's helpful to use a bluescreen for bright subjects. The green channel for a blue screen is almost black, so the bright subject provides lots of high-detail contrast in the green channel, again helping your keyer independant of color compression. You'll still be battling artifacts from the lens, sensor, A->D converter noise, and post processing like in-camera sharpening (which is why my instinct favors the idea of using the A1 vs a consumer targeted hand-cam) but by setting up your scene this way, color compression itself becomes less of a factor in calculating your compositing keys. |
|
January 5th, 2007, 11:51 AM | #28 | |
Convergent Design
Join Date: Apr 2005
Location: Colorado Springs, CO
Posts: 869
|
Quote:
The compressed HDV/AVCHD video is 1440 x 1080, but is automatically resized to 1920x1080 before being output to the HDMI port or to the analog component encoder. HDMI does not support a 1440x1080 video format. Using our HD-Connect MI box we can get either 1080i, 720p or 480i/576i out of the HC3 camcorder. While we have not tested these modes on the other camcorders, we are fairly certain they all perform in a similar manner. Note that the HC3 does not list 720p as an output option, but we have found a technique to coax this output from the camcorder. Ultimately, I think the analog connections will disappear completely and we'll move to serial digital formats like HDMI and HD/SD-SDI. They include both the video and audio and offer no degredation of the signal (no A/D and D/A conversions). They also can be less expensive to implement. Connections are also simplified (only one cable). I am working on an update to our HDMI white paper with a compatibility chart for playback of Sony, Canon and JVC tapes in the variious camcorder and decks. Bottom line, HDMI offers far more playback options compared to 1394. The Sony M25 deck, for example, can playback JVC 720p30 tapes through HDMI, but not through 1394.
__________________
Mike Schell Convergent Design |
|
January 5th, 2007, 03:27 PM | #29 | |
Trustee
Join Date: Aug 2003
Location: Vancouver BC Canada
Posts: 1,315
|
Quote:
__________________
Damnit Jim, I'm a film maker not a sysytems tech. |
|
January 5th, 2007, 08:25 PM | #30 | |
Regular Crew
Join Date: Jan 2006
Location: Vancouver, BC
Posts: 62
|
Quote:
|
|
| ||||||
|
|