[
https://issues.apache.org/jira/browse/TIKA-590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12988741#comment-12988741
]
Nick Burch commented on TIKA-590:
---------------------------------
TikaInputStream can help with the case of needing to do multiple passes over
the stream.
For the libvlc vs java case, you'd probably want something like:
* A libvlc powered movie parser (mixture of java and native code)
* A pure java "switching" parser - eg will use the normal java parser if
ParserExtraWorkLevel is none or limited, and will use the vlc one for FULL
assuming it loads ok
You could then choose to use the switching+vlc one or not by including / not
including the jar
> Create facility for deeper introspection of media files
> -------------------------------------------------------
>
> Key: TIKA-590
> URL: https://issues.apache.org/jira/browse/TIKA-590
> Project: Tika
> Issue Type: Wish
> Components: metadata
> Reporter: Andre-John Mas
>
> This feature would allow applications to dig deeper into files to define
> meta-data that is not presented as a tag in the file. For example a file that
> has no duration information could with a little more work provide this
> missing information. The idea is to let the API user make a difference
> between data that is quick to retrieve and data that is slower to retrieve
> because of the extra processing needed to get that information.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
