Opened 9 years ago

Closed 7 years ago

#12652 closed Bug Report - General (Won't Fix)

Navigation during editing appears to be broken.

Reported by: tom.culliton@… Owned by:
Priority: major Milestone: 0.28.2
Component: MythTV - General Version: 0.27.6
Severity: high Keywords: video editing seek navigation
Cc: Ticket locked: no

Description

Wrong frame is displayed when navigating to edit cut points. The affected videos seem to play fine and skip correctly during playback, but when trying to edit cut points it seems to get stuck displaying the wrong image.

I've tried rebuilding the seek table using both mythcommflag and mythtranscode and the data looks sane.

Change History (6)

comment:1 Changed 9 years ago by tom.culliton@…

More experimentation shows that the navigation itself appears to be OK, but it's displaying the wrong frame for some reason. it's almost like it's rendering the right thing first and then immediately rendering some other semi-random frame maybe from another end or cut point.

comment:2 Changed 9 years ago by stevegoodey@…

I've noticed this for a while but hadn't reported it, sorry. By moving backwards and forwards using keyframe skip during editing the correct frame can be briefly seen 'behind' the incorrect frame. Using this kludge I've been able to edit recordings successfully.

comment:3 Changed 8 years ago by Stuart Auchterlonie

Milestone: unknown0.28.1

comment:4 Changed 8 years ago by tom.culliton@…

Lightbulb! Video rendering method is apparently part of the problem. I was using OpenGL high quality and after switching to VAAPI normal, it's suddenly working much much better.

I'd previously seen this with a VDPAU based config on my older hardware (AMD64 CPU and an Nvidia video card) up through fixes/0.28 [v0.28-56-g5c18d3f] on my current hardware (NUC5i3RYH).

comment:5 Changed 8 years ago by Stuart Auchterlonie

Milestone: 0.28.10.28.2

Moving remaining open 0.28.1 tickets to 0.28.2

comment:6 Changed 7 years ago by Stuart Auchterlonie

Resolution: Won't Fix
Status: newclosed

Closing any remaining tickets for 0.28, if the issue persists, feel free to reopen and align to v29 or master

Note: See TracTickets for help on using tickets.