|
|
| JPT |
| Posted: Jul 13 2011, 01:00 PM |
 |
|
Member
Group: Members
Posts: 11
Member No.: 32016
Joined: 4-July 11
|
Hi,
me again.
If there was a little bit of docs on how the input filter works, I would not ask silly questions. 
This time:
MKV with H.264 and DTS-HD.
When opening in Vdub, no audio track is available.
When setting audio to external file: "The file "xyz.mkv" does not contain an audio track."
So if the matroska filter just interprets the container data, it should report "unknown type of audio track", shouldn't it?
Totally confused about handling codecs.
|
|
| ale5000 |
| Posted: Jul 13 2011, 02:55 PM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
The Matroska input plugin support a lot of types of audio but not DTS.
Since every type of video/audio is stored differently in Matroska, every thing need specific support (in a avi everything is stored in the same way).
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
| fccHandler |
| Posted: Jul 15 2011, 12:14 AM |
|
|
Administrator n00b
Group: Moderators
Posts: 3961
Member No.: 280
Joined: 13-September 02
|
| QUOTE (JPT @ Jul 13 2011, 09:00 AM) | If there was a little bit of docs on how the input filter works, I would not ask silly questions.
|
Here's the documentation: The Matroska plugin either works, or it doesn't. When it doesn't you'll just have to wait for me to fix it. 
DTS is one of those things that doesn't work, and it may never work due to lack of ACM support. (I haven't actually attempted to work with DTS yet, so that remains to be seen.) As to unsupported audio in general...
"The file ... does not contain an audio track" error comes from VirtualDub. The plugin doesn't report anything to you the user, instead it reports its findings solely to VirtualDub through the plugin API. These findings are pretty much limited to: how many streams are present and what are their properties.
As I recall the API doesn't provide any way for the plugin to give a reason for a non-fatal parsing issue, such as, I see an audio track but I don't know what it is. The plugin can only return a reason when it is a total failure, in which case VirtualDub issues a popup message and your import is aborted.
So currently there isn't any way for the plugin to tell you that it found an unsupported audio track. The only hint you get is that the expected track is not present after loading. It is of course possible for the plugin to popup its own message box to tell you of such things, but I think that would become incredibly annoying...
I am considering alternatives, such as an import log which could be viewed from File Information to give more details about any issues during file import. This would involve a good deal of time and work to implement (IF I decide to do it) so for now I won't promise anything.
--------------------
May the FOURCC be with you... |
|
| ale5000 |
| Posted: Jul 15 2011, 02:36 AM |
|
|
Advanced Member
Group: Members
Posts: 1114
Member No.: 22180
Joined: 30-September 07
|
| QUOTE (fccHandler @ Jul 15 2011, 01:14 AM) | | DTS is one of those things that doesn't work, and it may never work due to lack of ACM support. |
There is already a working DTS ACM codec (both encoding / decoding).
--------------------
New VirtualDub forum
VirtualDub AIO (All-in-One installer for VirtualDub and plugins)
Codec Toolbox RS (A tool to read/change merit of codecs and many other things)
Input plugins for VirtualDub / ACM codecs / VFW codecs |
|
