Opened 11 years ago

Closed 10 years ago

#6098 closed patch (fixed)

channel changes don't show on frontend until buffer catches up

Reported by: Zach C <uid000@…> Owned by: Isaac Richards
Priority: minor Milestone: 0.22
Component: mythtv Version: head
Severity: medium Keywords: channel change LiveTV
Cc: Ticket locked: no

Description

If there is some amount of buffer in LiveTV, say after pausing for 10 seconds, then it takes that amount of time (10 seconds) to see video from the new channel after a channel change.

However long LiveTV was paused before changing channel is how long it takes to see the channel change. The channel change is executed immediately on the backend, however.

MythTV Version : 19620 MythTV Branch : trunk Library API : 0.22.20090108-1 Network Protocol : 43 QT Version : 4.4.3 Options compiled in:

linux debug using_oss using_alsa using_arts using_backend using_directfb using_dvb using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtwebkit using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmc_vld using_xvmcw using_bindings_perl using_bindings_python using_opengl using_ffmpeg_threads using_live using_mheg

Attachments (1)

livetv_delayed_channel_change_fix.diff (455 bytes) - added by Shane Shrybman 10 years ago.

Download all attachments as: .zip

Change History (3)

comment:1 Changed 10 years ago by Shane Shrybman

Milestone: unknown0.22
Type: defectpatch

The attached patch should resolve this problem.

The livetv ClearSwitch?() call at the end of NuppelVideoPlayer::ClearAfterSeek?(..) was clearing the NeedsToSwitch/NeedsToJump? state before the switch could actually occur.

Changed 10 years ago by Shane Shrybman

comment:2 Changed 10 years ago by shane

Resolution: fixed
Status: newclosed

(In [20169]) The livetv ClearSwitch?() call at the end of NVP::ClearAfterSeek?() was clearing the tvchain NeedsToSwitch/NeedsToJump? state before the switch could actually occur. Fixes #6098

Note: See TracTickets for help on using tickets.