Opened 20 years ago
Last modified 11 years ago
#287 closed enhancement
XvMC decoding, MPEG2 stream recognized as MPEG1 — at Version 4
| Reported by: | Owned by: | danielk | |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.19 |
| Component: | mythtv | Version: | head |
| Severity: | low | Keywords: | XvMC MPEG1 MPEG2 |
| Cc: | Ticket locked: | no |
Description (last modified by )
Whenever a XvMC is used, it sometimes works and sometimes it does not, I have found that when the same DVB-C (ts) stream is recognized as MPEG1 the XvMC-hardware decoding does not work ( AVFD: Stream #0, has id 0x33 codec id MPEG1VIDEO, type Video at 0x0x82a95a0 ), but when the same stream is recognized as MPEG2 everything works.( AVFD: Stream #0, has id 0x215 codec id MPEG2VIDEO, type Video at 0x0x827e940 )
Debug output attached.
Change History (7)
comment:1 by , 20 years ago
| Description: | modified (diff) |
|---|---|
| Owner: | changed from to |
| Priority: | critical → minor |
| Status: | new → assigned |
comment:2 by , 20 years ago
| Milestone: | → 0.19 |
|---|---|
| Severity: | medium → low |
| Type: | defect → enhancement |
comment:3 by , 20 years ago
But why the stream is sometimes recognized as MPEG1 and sometimes MPEG2. This happens on all of my channels. That's a little wierd if it's a broadcasters problem..
by , 20 years ago
| Attachment: | mpeg1-hack.patch added |
|---|
Note:
See TracTickets
for help on using tickets.
It looks like the transmitter is marking an MPEG-2 stream as a MPEG-1 stream, since libav can handle MPEG-1 in the MPEG-2 decoder it should be easy to work around this problem with the channel. I just want to check if this will break libmpeg first.
But you should notify the engineers at that broadcaster of their problem.