http://forum.handbrake.fr/viewtopic.php?f=5&t=10327

I have reviewed the IRC logs and forums (both public and private messages) since before the original Turbo.264 shipped and cannot find a single instance where any employee of your company reached out to the HandBrake team via any means (public message, private message, e-mail, you name it). If you have information to the contrary, please share it.

That having been said, as you are no doubt very well aware, there is not a thing the HandBrake team can do to integrate with your solution because we did not write the existing encoder either. As stated in the very response you referenced, your integration point needs to be with libx264, not HandBrake, and I am unaware of any efforts on Elgato’s part to reach out to the x264 development team.

Since HandBrake, like x264, strongly prides itself on being a multiplatform solution, I suspect x264 integration will be dicey-to-snowball’s-chance-in-hell, but I do not wish to speak for the x264 team and am only offering conjecture on this. Public comment from the x264 team on the Turbo.264 product was, shall we say, less than positive.

Long story short, as you no doubt read in the HandBrake forums, if Elgato can get some sort of technology integration with x264 accomplished (which will likely require the coding burden for this to be on the Elgato team if it happens at all), HandBrake will reap the benefits “for free” since we use libx264. And if there isn’t, there’s not a thing HandBrake can do about it.

Regards,

Rodney

I’m hoping that two-pass is enabled in the new HD product… or, if not, that it’s coming soon. Anyone here know about this?

Thanks.

a conversion to h264 by default will have an AAC2.0 output. from what i gather that’s Apple’s preferred flavour of h264.

but if the source was AC3 ‘Dolby Digital’ encoded (5.1 or even 2.0) that will be included as a secondary track too, and if present, played in preference to the AAC (on an AppleTV. Quicktime on a full Mac appears to behave differently, will still only play the AAC2.0 – anyone know why?).

my question stemmed from months of confusion/frustration after Apple changed the way AppleTV plays back files with only AC3 tracks. previously it would, despite ther ‘recommendation’ that its primary soundtrack be AAC. then a firmware update 6 months ago enforced the need for AAC, with AC3 as an option if present alongside AAC. AC3-only files will play silently .

Thanks for answering techydude’s question, but what about mine?

“If the input file(s) have AC3 5.1 audio, does the Turbo.264 just pass it through untouched? DigMo’s post implies it is converted to AAC.

Also, it would be nice to see support for MKV as an output container format along with VC-1/MP4.”

You implied that converting to AppleTV keeps 5.1 AC3 audio intact; is that true in general? (I don’t have an AppleTV – would prefer to convert to VC-1/MP4 or, more preferably, MKV)

i ordered my eyeTV Diversity w/ eyeTV v3 + IceTV EPG subscription from IceTV.com.au last night.

now i can go hunting a good price on the turbo264HD :p

thanks heaps to DigMo & Elgato for an excellent eye-to-eye exchange here (pardon the pun .

Normal MPEG-2 Transport Stream files should be read by Turbo.264 HD without problem.

And again, very happy to see Elgato engaging those replying to this review.

P.S. I really appreciate Elgato engaging with questions at this level, it’s refreshing and reassuring!