Add <VideoExclude> Option to Transcoding

[Former user]

Currently there is no way to explicitly skip the transcoding of explicit codec combinations that will play natively and transcode the rest by default.

Currently a codec combo will skip transcoding only after all matches are tested and the combo drops thru without a match.

My Samsung will play H264/AAC.flv files natively but any other combination of codecs will fail. So currently I must define all the codecs that will NOT play with Match statements in order to have h264/aac.flv files play natively, and even then if I fail to define an unplayable codec with a Match option, if I get a video with that codec it will fail to play rather than be transcoded.

All of this could be avoided with the availability of a <VideoExclude> option which if matched would "drop thru" immediately and skip the following transcoding rules .

The following example would play h264/aac.flv files natively and transcode all other flv codec combinations, and make the profile much simpler.

{{{ <Transcoding> <VideoExclude> <Matches container="flv" vCodec="h264" aCodec="aac"/> </VideoExclude> <Video targetContainer="mpegts" targetVCodec="mpeg2video" targetACodec="ac3"> <Matches container="flv"/> </Video> </Transcoding> }}}

[Former user]

I need to expand this to include the requirement that the "drop thru" effect of this exclude option would be limited to the <Transcoding> section and that the <Online Transcoding> section would continue to be applied. Hence for example, if avc/aac.flv videos which play natively on Samsung were excluded from local transcoding as above , they would still remux to avc/aac.ts according to the online transcoding rule, but all other .flv combinations would be transcoded as stated above for both local and on-line sources. The proposal #444 to change the online transcoding behavior would further simplify the profiles..

[Petr Nejedly]

this would make current profiles confusing and might break everything