[Tod Hopkins]

From Wikipedia and backed up elsewhere, but not by my own experience yet.

“High Speed HDMI 1.3 cables can support all HDMI 1.4 features except for the HDMI Ethernet Channel.[51][110][111]”

https://en.wikipedia.org/wiki/HDMI#Version_comparison

The follow-up logic would suggest than any decent 1.3c adapter should work for 3D if used in combination with “high speed” or 1.4 rated cables as long as you don’t push length limits. That is, it’s a bandwidth issue, not connectivity.

Have you had any luck? I’d love to hear about it as I am in the market for this box as well.

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

Convert to DVCProHD?

Are you sure it’s the codec and not drives or other issues. Do other 1080 codecs play fine? It could just be that you don’t have the horsepower for 1080.

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[Matt Campbell] “Not to keep adding to this post but why can’t you just leave the frame controls off.”

Go ahead. I’m learning a lot. I turn them on because I went to set the resize controls to “better” or even best. I’m not sure if it matters but I’m pretty sure the settings aren’t there just to make me feel better. Also gives you access to anti-aliasing and detail enhancement.

This thread inspired me to look into ways of not deinterlacing. Since you can’t go to 60p on DVD, this is not terribly relevant for this compression but might be for other applications (I do a lot of MPEG from servers). Squeeze has a “discard field” options. This works really well going from 1080i to 480i in terms of sharpness and aliasing, but you lose the temporal resolution altogether which gives it a less “smooth” feeling. TMPG has several methods, some of which seem to avoid deinterlacing but I have not tried them.

What I discovered about Compressor however, was that it was actually doing a better job of deinterlacing than I had thought. It’s tough to avoid playback transformations playing back a widescreen DVD but when I did, I discovered that many of the artifacts I was seeing were appearing in playback for one reason or another. I also want to test Compressor going from 1080i to 1080p60 to create a fully progressive intermediate for compression. This should avoid all deinterlace artifacts but may introduce scaling artifacts that are just as bad. I have not tested.

I also found that Compressor’s old deinterlace filter has a “discard field” setting that should work like the Squeeze setting. I could try that, though the Apple manual explicit maintains that the new function is “always” better than the old filter.

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[Daniel Low] “Well you obviously can’t go straight from 1080i to 480i, you have to deinterlace first. Why don’t you go straight to 480p??”

Apparently not obvious to all of us. You don’t NEED to deinterlace when scaling down from 1080i to 480i, but I realize that most scalers DO deinterlace before scaling, especially software scalers. I’m sure you are right. And in order to maintain temporal resolution, it would have to deinterlace at 1080, prior to scaling. Ouch. No wonder it takes so frigging long.

By the way, I am testing 480p, but I don’t like to lose the temporal resolution. I like 60 fields. Looks smooooooth. Upside is that going progressive does cut the compression time dramatically!

Thanks. Consider me educated!

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

Yes, resizing 1080i to 480i, MPEG2 for DVD. With deinterlace set to fast, the four minute show takes 1 hour. Set to “best” it estimates 50+ hours. I let that run for one hour and the estimate did not go down.

From what I read, the time estimates I get fit other people’s experience with this setting. It’s just that it logically should not happen when fields are set to “same as source.” I presume it’s just an oversight in the programming, but I was curious if someone knows better. I could not find anything on line. It’s not really a problem as long as you leave it at “fast” when you set to “same as source.”

Tod

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[jaime abramson] “if any of you super smart people were to tell a not-so-tech-savvy client the kinds of compressed files you’d accep”

Don’t. Handle all conversion at your end. That’s what I do. It’s the only way. You’ve already told me the client can’t handle it.

tod

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[Nat Rovit] “Please help, is there any way to download new codecs for use in Quicktime?”

Sometimes. It depends on the codec. Frequently the only proper way is to install an app that includes the codec. In this case, FCP. In other cases, the codec is available seperately (ProRes) or as an add-on (MPEG0). And I believe you can copy the codec file in the library from one machine to another, but I’m not certain about that.

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[Daniel Low] “If you are going from interlaced to interlaced, then you’d set ‘Same as source’ and ignore the deinterlace setting. Compressor only deinterlaces jobs that need it.”

Yes, that’s what the manual says, but it’s clearly not what the app does. That’s why I ask. Compressor definitely does NOT ignore that setting. If you set deinterlace to fast, fine. Set it to best and your encode times will increase 50-fold! So… why? If compressor is ignoring the setting, why do the compression times skyrocket.

tod

Tod Hopkins
Hillmann & Carr Inc.
Washington, DC

[Tod Hopkins]

[Jeremy Garchow] “The same happens to DVCPRo HD. 100mbps is the highest bit rate (1080i60), once you start getting to 720p23.98, it drops down to about 40mbps. DVCPro HD is smaller than ProRes, you will just have to trust me on that, I know it’s hard sometimes. :)”

I’m a trusting kinda guy. I know that DVCProHDpn24 (the so-called “native” framerate)is lower bitrate.

Well, duh! Here it is right on the same Apple chart. I just didn’t look for it.

Cheers,
tod

Tod Hopkins
Hillmann & Carr Inc.
todhopkins-at-hillmanncarr.com

[Tod Hopkins]

According to Apple:

1280x720p23.98 target datarate is 59mbps and 88Mbps at HQ.

1280x720p59.97 target datarate is 147Mbps and 220Mbps at HQ

Framerate makes a huge difference.

Cheers,
tod

On Oct 29, 2008, at 10:16 AM, Apple Final Cut Pro wrote:

ProRes is 145 mb/sec and ProResHQ is 220 Mb/sec, now those will get smaller depending on frame size and frame rate, but they are still larger than DVCPro HD. DVCPro HD @ 720p23.98 is about 5 MB/sec. It’s about double dv25.

Jeremy

————————————————–

Tod Hopkins
Hillmann & Carr Inc.
todhopkins-at-hillmanncarr.com