From: Jason T. <ta...@ur...> - 2010-09-15 15:45:15
|
Hi Mike, On Tue, 2010-09-14 at 17:51 -0400, Mike Pelley wrote: > I'm new to the list, and just joined to make this request. I was > writing a python script to convert MKV video files to > iPad/iPod/PS3/360 compatible MP4 files and discovered kaa.metadata. > It's much nicer than parsing the output of mkvinfo - thanks! Happy to see kaa.metadata is working well for you. The matroska parser is certainly one of the most full featured parsers in the library, mainly because it's among the best spec'd and sanest containers. :) Although, is parsing the output of mkvinfo an option for your use-case? I didn't know mkvinfo would dump codec private data. > machine to expose it (see diff below). This seems like a simple way > to allow clients of the API to access this data without adding support > for parsing the private data directly (which is different for each > video codec). I'd also suggest that the variable name be changed from > "codec_private_id" to "codec_private", but I wanted to keep my changes > minimal. I could imagine other scenarios where having access to the profile and level would be useful. I might want to expose these as video track attributes. Would you mind sharing the code you're using to parse this out? > Hopefully you'll find this useful and incorporate it into > kaa.metadata, so my script can be run by others someday. Yes, I've meanwhile added 'codec_private' as core attributes for video and audio tracks, which is initialized to None when not present, or a string of bytes when it is. Thanks for the submission! Cheers, Jason. |