Opened 14 years ago
Closed 13 years ago
#4026 closed defect (invalid)
Default playback group for XvMC does not invclude 1080I/P
Reported by: | anonymous | Owned by: | danielk |
---|---|---|---|
Priority: | minor | Milestone: | 0.21 |
Component: | mythtv | Version: | head |
Severity: | low | Keywords: | |
Cc: | Ticket locked: | no |
Description
The default playback groups include profiles for up to 720P but not 1080. The playback will result in not using Chromakey for 1080I.
Change History (3)
comment:1 Changed 14 years ago by
comment:2 Changed 13 years ago by
Milestone: | unknown → 0.21 |
---|---|
Owner: | changed from Isaac Richards to danielk |
Status: | new → assigned |
Version: | unknown → head |
comment:3 Changed 13 years ago by
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
The CPU+ profile is an example that mixes hardware + software rendering methods. The CPU-- example is a better starting point for you.
Note: See
TracTickets for help on using
tickets.
I noticed this last night. Because of it, it was somehow defaulting to opengl rendering on the CPU+ playback profile (made no sense to me).
Anyway, I increased the first option in the profile to say anything <=1920x1088 and that fixed it.
I do think this probably should be fixed upstream, as right now it's limited to 720 content and doesn't take into account 1080 content without defaulting to some other option. I don't understand how/where/why mine defaulted to opengl rendering, but from the -v playback logs it looked like this:
Once I increased the maximum resolution, it did what I wanted it to do which was use standard ffmpeg decoding without xvmc/opengl - using xv-blit. I've got to admit, the new playback profiles is cool, but there's a slight learning curve and I've still learning.
Again, like I said - maybe the default should be changed to accommodate 1080i signals. Of course, the rules that say >0x0 should cover it too... but that's more of a fallback.