[mythtv-users] Glitches in firewire capture from DCT-6200

Thu Dec 29 21:23:22 EST 2005

On Wednesday 28 December 2005 21:38, Alex Brekken wrote:
> I'm using the analog output (composite jack) on my soundcard to go straight
> into my stereo receiver.  My master backend/frontend machine is an AMD
> Sempron 2300.  Here's the output from mplayer::
>
> root at localhost home]# mplayer -vo xv
> 1005_20051218123000_2005121813 0000.nuv
> MPlayer 1.0pre7-3.4.3 (C) 2000-2005 MPlayer Team
> CPU: Advanced Micro Devices Athlon MP/XP Thoroughbred (Family: 6,
> Stepping: 1)
> Detected cache-line size is 64 bytes
> CPUflags:  MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 0
>
>
> Opening joystick device /dev/input/js0
> Can't open joystick device /dev/input/js0 : No such file or directory
> Can't init input joystick
> Setting up LIRC support...
> mplayer: could not open config files /root/.lircrc and /etc/lircrc
> mplayer: No such file or directory
> Failed to read LIRC config file ~/.lircrc.
> You will not be able to use your remote control.
> Playing 1005_20051218123000_20051218130000.nuv.
> TS file format detected.
> DEMUX OPEN, AUDIO_ID: -1, VIDEO_ID: -1, SUBTITLE_ID: -1,
> PROBING UP TO 2000000, PROG: 0
> VIDEO MPEG2(pid=2304)AUDIO A52(pid=2305) NO SUBS (yet)!  PROGRAM N. 1
> Opened TS demuxer, audio: 2000(pid 2305), video: 10000002(pid
> 2304)...POS=5640
> VIDEO:  MPEG2  528x480  (aspect 2)  29.970 fps  5500.0 kbps (687.5
> kbyte/s)
> ==========================================================================
> Opening audio decoder: [liba52] AC3 decoding with liba52
> Using SSE optimized IMDCT transform
> AC3: 2.0 (stereo)  48000 Hz  192.0 kbit/s
> Using MMX optimized resampler
> AUDIO: 48000 Hz, 2 ch, s16le, 192.0 kbit/12.50% (ratio: 24000->192000)
> Selected audio codec: [a52] afm:liba52 (AC3-liba52)
> ==========================================================================
> vo: X11 running at 1024x768 with depth 24 and 32 bpp (":0.0" => local
> display)
> ==========================================================================
> Opening video decoder: [mpegpes] MPEG 1/2 Video passthrough
> VDec: vo config request - 528 x 480 (preferred csp: Mpeg PES)
> Could not find matching colorspace - retrying with -vf scale...
> Opening video filter: [scale]
> The selected video_out device is incompatible with this codec.
> VDecoder init failed :(
> Opening video decoder: [libmpeg2] MPEG 1/2 Video decoder
> libmpeg2-v0.4.0b
> Selected video codec: [mpeg12] vfm:libmpeg2 (MPEG-1 or 2 (libmpeg2))
> ==========================================================================
> Checking audio filter chain for 48000Hz/2ch/s16le ->
> 48000Hz/2ch/s16le...
> AF_pre: 48000Hz/2ch/s16le
> alsa-init: 1 soundcard found, using: default
> alsa: 48000 Hz/2 channels/4 bpf/65536 bytes buffer/Signed 16 bit Little
> Endian
> AO: [alsa] 48000Hz 2ch s16le (2 bps)
> Building audio filter chain for 48000Hz/2ch/s16le ->
> 48000Hz/2ch/s16le...
> Starting playback...
> VDec: vo config request - 528 x 480 (preferred csp: Planar YV12)
> VDec: using Planar YV12 as output csp (no 0)
> Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
> VO: [xv] 528x480 => 640x480 Planar YV12
> alsa-space: xrun of at least 0.128 msecs. resetting stream% ??,?% 1 0
> A:12534.8 V:12534.9 A-V: -0.052 ct: -0.657 409/397  8%  1%  0.9% 15 0
> demux_mpg: 24000/1001fps progressive NTSC content detected, switching
> framerate.
> A:12535.6 V:12535.6 A-V:  0.046 ct: -0.624 427/415  8%  1%  0.9% 15 0
> demux_mpg: 30000/1001fps NTSC content detected, switching framerate.
> Warning! FPS changed 23.976 -> 29.970  (-5.994000) [4]  1%  0.9% 15 0
> A:12536.9 V:12537.0 A-V: -0.057 ct: -0.571 469/454  8%  1%  0.9% 15 0
> demux_mpg: 24000/1001fps progressive NTSC content detected, switching
> framerate.
>
> On 12/24/05, Steve Adeff <adeffs at gmail.com> wrote:
> > On Friday 23 December 2005 17:08, Alex Brekken wrote:
> > > Playing it back through mplayer looks pretty good - I didn't see any
> > > faults.  THEN, I actually re-named the file to overwrite an existing
> >
> > show
> >
> > > saved on my master machine.  This way I could playback the show through
> > > myth, to make the simulation as accurate as possible I guess.  Anyway,
> >
> > when
> >
> > > viewing the show through Myth, it DOES have the same slo-mo effect as
> > > it does when playing it back via the slave backend.  So that completely
> >
> > rules
> >
> > > out the network as a possible failing point.
> > >
> > > Weird...  As I stated before, I have no problem playing back recordings
> > > made via my PVR-250.  One thing I did notice, the codec I'm using for
> > > PVR-250 recordings is DVD-special2.  I believe Firewire recordings are
> >
> > TS.
> >
> > > Could this be it??  I wouldn't think so since then everyone would
> >
> > probably
> >
> > > have the same problem.
> > >
> > > On 12/18/05, Steve Adeff <adeffs at gmail.com> wrote:
> > > > On Sunday 18 December 2005 08:31, Alex Brekken wrote:
> > > > > Steve, I'd like to try that (copying the .nuv file over to the
> > > > > other
> > > >
> > > > Myth
> > > >
> > > > > box and playing locally from it's own hard drive) but I'm not
> >
> > exactly
> >
> > > > sure
> > > >
> > > > > of the best way to do that...  Are you suggesting to add entries
> >
> > into
> >
> > > > the
> > > >
> > > > > database, etc, and playing it within Myth, - or just manually
> >
> > playing
> >
> > > > > it using mplayer?
> > > >
> > > > just manually play it with mplayer. Lets see if the recording of the
> > > > firewire
> > > > signal is working ok before we blame that. Since you don't get
> > > > typical mpeg
> > > > breakup my theory is your capture is working fine, its one of the
> >
> > steps
> >
> > > > in your playback chain that is causing the issue.
> >
> > can you paste the stream info for the firewire captures from mplayer's
> > output?
> > are you using the analog output of your soundcard or passing the digital
> > audio through to a receiver? whats the cpu/speed of your system?
> >

I don't see why Myth is showing a slo-mo effect. Do you have Myth set to sync 
to audio n the settings? Unless a dev chimes in, I'd say open a support 
ticket.

-- 
Steve