Opened 19 years ago

Closed 18 years ago

#3083 closed defect (fixed)

livetv flickering images (works ok if watched with mplayer)

Reported by: primijos@… Owned by: Isaac Richards
Priority: minor Milestone: unknown
Component: mythtv Version: 0.20
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Hi,

I'm having some trobules watching some channels of my DVB-T stick.

Most channels work ok, but I have some of them (30% of the channels) that present the following problems/symptoms:

  • Each x seconds, the image "flickers", as is a photogram was inserted in the stream (out of order) for tenths of second
  • If I open the EPG while watching one of those channels, the little PIP on the top right corner of the screen grows in height, overlapping the EPG (I believe -not sure- that this "growth" is produced at the same time that the flickering appears)
  • The same mpg stream that mythbackend saves works ok with mplayer (no flickering at all)

In the following URLs you can find a cut of the MPEG stream that produces the error (8MB), the logs for mythfrontend (level=important,general), the logs for mplayer (just in case they help, MPLAYER_VERBOSE=1) and a picture of what happens with the EPG (notice the dark square under the PIP... that appears with the flickering and, I force the redraw of that areea (moving the selector square to that position), it is overwriten again and again...)

Any hint/workaround will be welcome. I'll glad to provide you with any other information, streams, logs, whatever you need to fix this.

The URLs (located at http://www.etilikos.org/mythtv ):

MpegStream mythfronted_log Mplayer_log EPGPicture

Change History (5)

comment:1 by primijos@…, 19 years ago

Sorry, URLs are not valid, the files for the bug investigation are now located here:

http://personales.ya.com/joseo/mythtv/

Sorry... I've found that my domain has expired and I'm trying to migrate it to another provider, but I believe that it will take a 60-days battle to make my current provider release my domain :(

comment:2 by stuartm, 18 years ago

Status: newinfoneeded_new

Does this problem still occur with trunk? There have been a couple of ffmpeg resyncs since the ticket was opened.

comment:3 by anonymous, 18 years ago

The problem seems to be solved, maybe it was some problem with the emitter ¿? Or maybe some update of my linux system... thanks anyway

comment:4 by stuartm, 18 years ago

Status: infoneeded_newnew

comment:5 by stuartm, 18 years ago

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.