Comma separated lists in profiles
Posted: Wed Sep 18, 2013 12:59 amA thought - would the use of comma separated lists for aCodec make for simpler profiles. For example, when trying to transcode all unsupported audio for a container type:
I think this makes the profiles simpler and more readable, and easier to include other audio types - but I understand it adds overhead to the code that parses the profile (am hoping that as the code already exists for say the vFourCC attribute it might be easy to do for these attributes).
I also thought this principle might then also be applied to vCodec and even container level eg. from the XBox profile:
could simplify to:
Hope this makes sense - your thoughts? Do you think it adds anything to the readability and understanding of profiles (ps the existing scheme is still supported under this model, so no need to re-write existing profiles unless you want to) or is it too complex and not worth doing (the existing scheme ain't broke...)??
could be simplified to:
I think this makes the profiles simpler and more readable, and easier to include other audio types - but I understand it adds overhead to the code that parses the profile (am hoping that as the code already exists for say the vFourCC attribute it might be easy to do for these attributes).
I also thought this principle might then also be applied to vCodec and even container level eg. from the XBox profile:
- Code:
<Matches container="matroska" />
<Matches container="mpeg" />
<Matches container="mpegts" />
<Matches container="mpegvideo" />
<Matches container="avi" vCodec="h264" />
<Matches container="avi" vCodec="msmpeg4" />
<Matches container="avi" vCodec="wmv2" />
<Matches container="avi" vCodec="dvvideo" />
<Matches container="mp4" vCodec="dvvideo" />
<Matches container="wtv" />
<Matches container="ogg" />
<Matches container="3gp" />
<Matches container="flv" />
<Matches container="rm" />
My concern with doing this for all three attributes though is you could end up with something like:
which isn't readable at all (however I think even if allowed, this can be still be avoided by convention ie. by convention you only use comma separated lists on the far right attribute when in container, vCodec, aCodec order). This scheme must also be used with caution if other matching attributes are included (eg. if profile, levelgreaterthan, vFourCC, etc are included - you could still combine aCodec's but not vCodec's).
Hope this makes sense - your thoughts? Do you think it adds anything to the readability and understanding of profiles (ps the existing scheme is still supported under this model, so no need to re-write existing profiles unless you want to) or is it too complex and not worth doing (the existing scheme ain't broke...)??