Opened 3 years ago
Closed 3 years ago
Last modified 3 years ago
#13169 closed Bug Report - General (fixed)
video playback profile format codec selection field
Reported by: | Owned by: | Peter Bennett | |
---|---|---|---|
Priority: | minor | Milestone: | 29.1 |
Component: | MythTV - Video Playback | Version: | Master Head |
Severity: | low | Keywords: | video format codec |
Cc: | Ticket locked: | no |
Description
v30-Pre-198-g6646748 added support to use video format (codec) & resolution to control video playback profile.
This only seems to work iff one keyword (h264) is used. If any other text is added before or after 'h264' then this profile fails for h264.
I've tried comma-space & space only delimiting. All fail.
Is the intention to allow multiple keywords ? I assume valid keywords are h264, mpeg2video, mpeg1video, vc1, wmv3 & mpeg4 or similar. All I'm trying to do is set NOT(h265) or NOT(hevc).
Workaround is to setup a profile for each video codec format.
Change History (8)
comment:1 Changed 3 years ago by
Owner: | changed from JYA to Peter Bennett |
---|---|
Status: | new → assigned |
comment:2 Changed 3 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:4 Changed 3 years ago by
Space separated is the correct way to enter them. This commit fixes the bug.
comment:5 Changed 3 years ago by
Milestone: | needs_triage → 29.1 |
---|
comment:6 Changed 3 years ago by
Fantastic work. The additional options for video decoder filters are comma separated, why does this have to be different? Is there any chance the video format/codec could contain a space? i.e. hevc (main) etc. Thanks.
comment:7 Changed 3 years ago by
You can see a full list by running
ffmpeg -codecs
There are none with spaces, they sometimes have underscores.
comment:8 Changed 3 years ago by
Owner: | changed from Peter Bennett to Peter Bennett |
---|
In 310ae2aa8afb8a55a8a365e4ce1621ef4337718e/mythtv: