Replies: 13 comments
-
|
Here is a h264 relevant excerpt from our overall Encoding Strategy discussion #14: This currently looks to specify 7 separate h264 alias's (you can think of these as seperate buckets processed video files). By splitting into 7 separate alias's, we avoid attempting encode all possible types of candidate videos into a single alias. NOT that there is anything wrong with the first example, as we are simply experimenting with different ideas to aid in lowering storage space WITHOUT compromising on direct play available for all scenarios. By going for a 'Candidates Only' alias for each hardware driven criteria, we might be able to avoid constantly remuxing candidate videos from vfo-source. On the other hand, by allow for 'Possible Transforms Only' alias's too for each hardware driven scenario, we are aiming to ensure, WHEN a candidate video A: Does not meet the hardware driven criteria & B: is objectively of 'higher quality' than the given hardware driven criteria; the given candidate video will be able to exist in this alias. SO, we are attempting to:
Take note, this particular encoding strategy is not considering any changes to audio other than the usual stripping down to stream 0 & stream 1 for vfo-source (i.e. always just deal with a single video stream and a single audio stream before encoding or remuxing to an alias). Let's now try to mock up a new vfo_config.conf file that specifies these 7 aliases exactly. We can then compare this vfo_config.conf with the single 'queen' alias vfo_config.conf example from the first post. It might be the case that both are feasible strategies and it is down to the encoder what their portfolio/encoding goals are, particularly when thinking about things like streaming distribution/file access/end-user use cases etc. |
Beta Was this translation helpful? Give feedback.
-
defined config task list: LION - (co) - done defined ffmpeg commands task list: LION - in progress - (requires SKIP feature) |
Beta Was this translation helpful? Give feedback.
-
|
Lion alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Shark alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Mouse alias: Is the video codec allowed to be h264? YES DONE -------- We cannot 'transform' candidates below minimum resolution, (this would be considered upscaling), so we must skip. /* file is already an exact match of alias critera, so just use ffmpeg to remux */ For transform candidates where their res is above criteria max. Some candidates may fall within res, but are on the lower end of the criteria res AND requires transforming, in those case we watch for specific scenario res so to encode at a higher quality (crf) at the lower end of resolutions. /* when candidate video file is between exactly 241p and 479p */ For this alias, we are doing our best to CATCH ALL candidate's in the scenarios above |
Beta Was this translation helpful? Give feedback.
-
|
Tiger alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Bear alias: |
Beta Was this translation helpful? Give feedback.
-
|
Wolf alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Ox alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Frog alias: |
Beta Was this translation helpful? Give feedback.
-
|
Robin alias: Is the video codec allowed to be h264? YES In all other scenarios, is the candidate video file skipped? YES |
Beta Was this translation helpful? Give feedback.
-
|
Bat alias: |
Beta Was this translation helpful? Give feedback.
-
|
_Ending this discussion as I've just realised that I don't need to encode to h264 for decoding incompatibilities. Instead I can decode more modern codecs on any streaming device really, I just need to now consider the hardware limitations of that particular device. However this is still a good discussion to piggy back off of for reference/scaffolding vfo_config.conf files in future._ EDIT: never mind again! Looks like there ARE devices that can ONLY decode x264. Good news though is that AV1 appears to support all devices that CAN decode HEVC? Need to verify this, but so far this seems to be the case. This confirms that it is essential to have a library of x264 video content for clients on such devices. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This space is centred around h264 alias's and ffmpeg commands.
Starting point:
As we can see, this is a pretty busy alias as we are forcing the alias to accomodate video candidates both WITH and WITHOUT valid color space information.
Perhaps there is a better way of coping with this by introducing multiple alias's first. Then we can more easily dive in to establishing the best possible command for a given candidate videos portfolio.
Beta Was this translation helpful? Give feedback.
All reactions