[mythtv] Mythtranscode .mpg => .mpg not .mpg => .nuv

[Geoffrey Hausheer]

On 11/6/05, Cory Papenfuss wrote:
>         Still hanging on my file.  Here's the last bit of debug=4:
> Id:1:  0:23:02.100 V:2602264 6159 A:611499 3915
> AUD: pts: 124391160
> Id:1:  0:23:02.124 V:2602264 6159 A:610923 3871
> AUD: pts: 124393320
> Id:1:  0:23:02.148 V:2602264 6159 A:610347 3827
> AUD: pts: 124395480
> Id:1:  0:23:02.172 V:2602264 6159 A:609771
>
>         ... Sitting right here.............^
This doesn't make sense.  Did you pipe the result to a log file or
less?  There is no way it could stop printing at the middle of a line
(that I can think of), so the real ending point is probably buffered. 
Try rerunning without reditrecting the output.  At this point the
ringbuffers are nowhere near full, so it is almost certainly has
nothing to do with the multiplexer, or the threading code.  I wouldn't
be surprised if the last line is something like 'Building P-Frame...'
You didn't say how you started it either.  Are you using '-t', or not?
 You should try it both ways.

Running through gdb would be very helpful as well, and is very easy:
gdb --args ./mpeg2fix -i infile.nuv -o out.mpg -t
then type 'run'
when it hangs, hit ctrl-c and type:
thread apply all bt

send me that, plus the previous 20 lines of output, and I'll have a
much better idea what is going on.

> Opening ../sync.nuv
> STATE: 4 (8097f4f) W: 704 H: 480 P: 900900 0:0:0.0 T:0 F: 2
>
> STATE: 4 (80887d9) W: 704 H: 480 P: 900900 T:3 F: 2
>
> 16022 -178 3003 0
> V: 16200 A: 16200 delta: 0
> V-queue: 1 A-queue: 0
> Delta: 0.000000ms
Looks ok to me.  Looks like it is from a PVR250 (or equivalent)

>         ... and the end of the output of mpegparse:
> PTS: 124399622
> --pos: 0x2c712014 AUx-HEADER (c0) len: 2028 (header bytes: 8)
> Audio frame: 576 bytes
> Audio frame: 576 bytes
> Audio frame: 576 bytes
> pos: 0x2c71280e PAC-HEADER t-base: 124395373 t-ext: 214 (1382.170819) mux:
...
Looks fine to me.  This PTS is < what you sent before (124399622-16200
< 124395480) which reinforces my thought that this is purely a decoder
issue, and isn't thread related.

Thanks for your response,
.Geoff