[mythtv-users] Problems with nuvexport and single episode shows

Sat Mar 20 18:37:49 UTC 2010

On 03/19/10 21:57, Gavin Hurlbut wrote:
> On Fri, Mar 19, 2010 at 4:56 AM, Dale Pontius <DEPontius at edgehp.net> wrote:
>>> mplayer -vo null -ao null -frames 0 -identify
> 
> OK, maybe try the second one with -frames 1 instead of 0?
> 
> This is what I expected to see.
> 
>> ID_AUDIO_BITRATE=384000
>> ID_AUDIO_RATE=48000
>> ID_AUDIO_NCH=2
>> ID_AUDIO_CODEC=mp3
> 
> 
>> And for the second recording:
>> ID_AUDIO_BITRATE=0
>> ID_AUDIO_RATE=0
>> ID_AUDIO_NCH=0
> 
> Nasty, it didn't re-identify like the first file.  This is what I
> expected.  With -frames 1, this may be better.  Also try adding to the
> mplayer command lines (for both):
> 
> -demuxer lavf
> 
> Did you say the second file was the same audio format as the first?
> 
For the first file:
$ mplayer -vo null -ao null -frames 1 -identify -demuxer lavf
/media/1006_20100217200000.mpg | grep ^ID
[mpeg @ 0x325f980]max_analyze_duration reached
ID_VIDEO_ID=0
ID_AUDIO_ID=1
ID_FILENAME=/media/1006_20100217200000.mpg
ID_DEMUXER=lavf
ID_VIDEO_FORMAT=MPG2
ID_VIDEO_BITRATE=6000000
ID_VIDEO_WIDTH=720
ID_VIDEO_HEIGHT=480
ID_VIDEO_FPS=29.970
ID_VIDEO_ASPECT=1.3333
ID_AUDIO_FORMAT=80
ID_AUDIO_BITRATE=384000
ID_AUDIO_RATE=48000
ID_AUDIO_NCH=2
ID_LENGTH=3597.67
ID_SEEKABLE=1
ID_CHAPTERS=0
ID_VIDEO_ASPECT=1.3333
ID_VIDEO_CODEC=mpegpes
ID_AUDIO_BITRATE=384000
ID_AUDIO_RATE=48000
ID_AUDIO_NCH=2
ID_AUDIO_CODEC=mp3
ID_EXIT=EOF

And for the second file:
$ mplayer -vo null -ao null -frames 1 -identify -demuxer lavf
/media/1006_20100303200000.mpg | grep ^ID
[mpeg @ 0x2e8a980]max_analyze_duration reached
ID_VIDEO_ID=0
ID_AUDIO_ID=1
ID_FILENAME=/media/1006_20100303200000.mpg
ID_DEMUXER=lavf
ID_VIDEO_FORMAT=MPG2
ID_VIDEO_BITRATE=6000000
ID_VIDEO_WIDTH=720
ID_VIDEO_HEIGHT=480
ID_VIDEO_FPS=29.970
ID_VIDEO_ASPECT=1.3333
ID_AUDIO_FORMAT=80
ID_AUDIO_BITRATE=384000
ID_AUDIO_RATE=32000
ID_AUDIO_NCH=2
ID_LENGTH=3598.43
ID_SEEKABLE=1
ID_CHAPTERS=0
ID_VIDEO_ASPECT=1.3333
ID_VIDEO_CODEC=mpegpes

Too many video packets in the buffer: (1787 in 33561528 bytes).
ADecoder init failed :(

Too many video packets in the buffer: (1787 in 33561528 bytes).

Too many video packets in the buffer: (1787 in 33561528 bytes).
ID_AUDIO_BITRATE=384000
ID_AUDIO_RATE=32000
ID_AUDIO_NCH=2
ID_AUDIO_CODEC=ffmp2

Too many video packets in the buffer: (1787 in 33561528 bytes).
ID_EXIT=EOF

So I guess things on that second file still aren't what you expected.
But using the "-demuxer lavf" I was able to play the video with mplayer
and get sound.  Though again I got a heck of a lot of ongoing hate-mail
like :
Too many video packets in the buffer: (1789 in 33558424 bytes).
Maybe you are playing a non-interleaved stream/file or the codec failed?
For AVI files, try to force non-interleaved mode with the -ni option.
A:  68.2 V:   9.0 A-V: 59.179 ct:  0.864   0/  0 12% 23%  2.7% 0 0

Adding the "-ni" flag as they suggested didn't change thing.

As for formats, I don't know.  Both files used the Hauppauge hvr-1600
card for capture.  However the configuration was completely dumped and
redone in-between.

Maybe this is significant...  When I first set up MythTV it was with a
bt878-based card, audio section ignored, with a short sound cable going
from the video card to my audio input.  With this card I had some audio
aliasing problems with the AC97 on one of my frontend machines, and at
some point I found the workaround being to force the sampling to
48000Hz.  Later I added a pair of hvr-1600 cards, and later still
removed the bt878 card.  When I migrated to 0.22 I had to dump the
database and do a partial restore, meaning that all configuration
information was lost.  When setting things up again on 0.22, I pretty
much accepted defaults everywhere.

So to answer, I honestly don't know about the two audio formats.  I know
they both came from an hvr-1600 capture card, but it's a versatile card
and I don't know what settings were in effect.  At this point, I don't
know that I can find out what settings were in effect, unless there is a
way to glean them from an old database dump.  I still have database
dumps from 0.21, before the migration, and can look through "before" and
"after" for specific items, if that helps.

If this suggests changes I should make in my setup now, to make things
work better in the future, I'm game for that, too.

Thanks,
Dale