Opened 11 years ago

Closed 11 years ago

#5812 closed defect (fixed)

mythtranscode only sends first frame when using cutlists

Reported by: xris Owned by: Isaac Richards
Priority: critical Milestone: 0.22
Component: mythtranscode Version: head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

After fixing the parameter issue with --fifodir, I noticed that mythtranscode seems to run forever, but with no errors. After a couple of test encodes, I've determined that when using --fifodir (and possibly other times), it only ever inserts the first frame into the buffer, despite the fact that it reports incrementing frame numbers. It does not stop when it reaches the maximum number of frames, but just keeps going on forever.

Change History (3)

comment:1 Changed 11 years ago by xris

Confirmed that this is broken after [16790].. unfortunately, so many other issues (like the aforementioned --fifodir problem) were also introduced, that it's impossible to know if [16790] specifically, or something afterward, is causing this particular problem.

comment:2 Changed 11 years ago by xris

Summary: mythtranscode only sends first frame for fifodir (used by nuvexport)mythtranscode only sends first frame when using cutlists

Just got some more info from clev in IRC... This problem affects more than just fifodir usage, and appears whenever transcoding something with a cutlist. I've confirmed that fifodir encodes work fine if the cutlist is disabled.

comment:3 Changed 11 years ago by stuartm

Resolution: fixed
Status: newclosed

(In [18809]) Fixes lossy transcoding of recordings which was broken during when the QT4 branch was merged to trunk. Thanks to xris and others for testing. Original fix from nzhook. Closes #5180, #5812

Note: See TracTickets for help on using tickets.