2010-11-25, 12:00
spiff Wrote:you know that anssi is a team member right?You devil!
gnif Wrote:I got the new receiver today, very nice unit but wont be able to do anything for at-least a couple of days as I am out of town. Very excited to get things started, will be nice to finally have TrueHD support and DTS-MA working as they have been missing for a long time now.
danconti Wrote:hey,
i did all of the hd audio work in boxee. on my todo list is making a backport for xbmc, but since you guys are forking it's probably easier if i help where needed. i can check back here or you can get in touch with me, dan at boxee dot tv
one note - we didn't implement eac3 bitstream. on the box it's handled for us by the platform sdk, and on the desktop we don't have it. but i can certainly help out with dts-hd and truehd.
cheers
danconti Wrote:hey,
i did all of the hd audio work in boxee. on my todo list is making a backport for xbmc, but since you guys are forking it's probably easier if i help where needed. i can check back here or you can get in touch with me, dan at boxee dot tv
one note - we didn't implement eac3 bitstream. on the box it's handled for us by the platform sdk, and on the desktop we don't have it. but i can certainly help out with dts-hd and truehd.
cheers
furii Wrote:i'm curious though. will adding the hd audio support to the AE branch allow for xbmc to differentiate between dts-hd and standard dts tracks in the ui? currently a dts-hd track in the mkv container still shows up as being a regular dts track. i assume that is just because there is not dts-hd support as of yet.DTS-HD is just normal DTS with some extra data in the end, so it is a bit tricky to differentiate them. HD audio passthrough in AE will need to differentiate them, but we probably want a solution for the UI that does not depend on passthrough
Anssi Wrote:DTS-HD is just normal DTS with some extra data in the end, so it is a bit tricky to differentiate them. HD audio passthrough in AE will need to differentiate them, but we probably want a solution for the UI that does not depend on passthrough
I guess this could be added as some extra check for a DTS-HD signature at the DTS stream when probing the streams. However, this is not dependant or related to the AE branch, AFAICS.
Also, there is the issue if we should show the stream as DTS-HD in the UI if we are only going to decode the DTS core part (which is done when HD passthrough is not in use), and the stream information (channel count, sample rate) is really the information from the DTS core, not DTS-HD... So it is, as usual, not simple at all
Anssi Wrote:[*]Windows support is possible (MSDN), but this of course requires a Windows developer to do it (which I am not)
[/LIST]
Anssi Wrote:For the record, and as a summary:
- Windows support is possible (MSDN), but this of course requires a Windows developer to do it (which I am not)
Anssi Wrote:For the record, and as a summary:
- We know how to make E-AC-3 / DTS-HD / TrueHD bitstreaming work on Linux, and it is planned to implement this in AudioEngine (I've also confirmed the bitstream syntax with danconti).
- Windows support is possible (MSDN), but this of course requires a Windows developer to do it (which I am not)
E-AC-3 should work (at least on Linux) on all cards that have 192kHz stereo support, which is probably everyone except ATI cards (see below).
Support status of DTS-HD / TrueHD (from a driver/hw standpoint; not yet in XBMC):Note that the NVIDIA information above is mostly gathered from the relevant nvnews.net and Phoronix threads. I could be wrong on the other entries as well, as this hasn't been very widely tested at this point (for example, no actual Intel testers).
- NVIDIA GeForce 200 series works partially (I believe it is slightly buggy and it depends on the A/V receiver if it works or not), but on *Linux only*; the 200 series is not supported on Windows at all
- NVIDIA GeForce 400 series works
- ATI cards do not work on Linux; they seem to have a non-standard interface for anything else than 48kHz stereo audio, some information from AMD about that will be needed to get it working (or some serious trial-and-error by someone who has such a card )
- ATI cards work on Windows, but I don't know which ones have bitstreaming support
- INTEL HDMI graphics chipsets that should work, at least on Linux: IbexPeak (0x80862804), CougarPoint
- INTEL HDMI graphics chipsets that have no hw support: Cantiga, Eaglelake
- INTEL HDMI graphics chipsets that I don't know about: Bearlake, IbexPeak (0x80860054), Crestline
You can check DTS-HD/TrueHD support on Linux by checking for "HBR" text in "Pincap" line in /proc/asound/cardX/codec#Y. For actually testing it, you can see the above threads (or just wait for XBMC to get support :p).
Anssi Wrote:E-AC-3 should work (at least on Linux) on all cards that have 192kHz stereo support, which is probably everyone except ATI cards (see below).Actually, this is enough for less-than-6.144-Mbps DTS-HD streams as well. I.e. e.g. GF9400 / ION cards can do that. (I tested with one full-length sample, and it never peaked above 6.144 Mbps)
danconti Wrote:note that there is no rule that the dts and dts-hd packets come in pairs at the start of the stream (i have seen some where we get 4-5 dts packets before seeing a dts-hd one).Does there exist a sample showing this?