Pinnacle and Dazzle
in [UK Linux]
|
Prev: Permission Denied On USB Hard Drive
Next: The Linux experience - ugly, bad, and good - Re: Random Hesitations: The new threat to windummy productivity in the office
From: Davey on 22 Apr 2010 12:56 On Mon, 19 Apr 2010 13:38:01 +0100, Paul Martin wrote: > In article <hqgkes$hsa$1(a)n102.xanadu-bbs.net>, > Davey wrote: > >> The only output I see is a pair of tiny loudspeakers built in to the >> keyboard, and they are supposed to be muted if a headset is plugged in. But >> I can try that. >> What else can there be? This is a laptop, I'm not doing any physical >> digging! > > eg: > $ cat /proc/asound/cards > 0 [I82801DBICH4 ]: ICH4 - Intel 82801DB-ICH4 > Intel 82801DB-ICH4 with AD1981B at irq 11 > 1 [Modem ]: ICH-MODEM - Intel 82801DB-ICH4 Modem > Intel 82801DB-ICH4 Modem at irq 11 > 5 [ThinkPadEC ]: ThinkPad EC - ThinkPad Console Audio Control > ThinkPad Console Audio Control at EC reg 0x30, fw 1RHT71WW-3.04 > > Also, giving us a copy of the commandline you're using to run mplayer > might be helpful. Paul, I'm updating this thread in the other branch, stated by Andy Furniss. If you are still interested, please follow it there. Thanks. -- Davey.
From: Davey on 22 Apr 2010 13:35 On Thu, 22 Apr 2010 12:54:47 -0400, Davey wrote: > On Mon, 19 Apr 2010 20:09:35 +0100, Andy Furniss wrote: > >> Davey wrote: >> >>> [36475.333748] em28xx #0: V4L2 device registered as /dev/video0 and >>> /dev/vbi0 >>> [36475.333766] em28xx #0: Found Pinnacle Dazzle DVC 90/DVC 100 >>> [36475.333832] em28xx audio device (2304:021a): interface 1, class 1 >>> [36475.333885] em28xx audio device (2304:021a): interface 2, class 1 >>> [36475.333965] usbcore: registered new interface driver em28xx >>> [36475.642569] usbcore: registered new interface driver snd-usb-audio >>> >>> Any help understanding that lot much appreciated. But it seems to be happy >>> that there is a Dazzle out there. Tonight, the picture is a lot less jerky, >>> even on VLC. But still no sound! >> >> I have never used usb audio, but guessing from the blog example I would try >> >> mplayer tv:// -tv >> driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 >> >> I see you have two audio devices so also try with ...:adevice=/dev/dsp2 >> >> Also run alsamixer and make sure "DVC 100" (if it exists) is unmuted and >> turned up while testing. >> >>> I see the AC97 audio in there. Maybe that's where the trouble is, isn't >>> that a Windows driver? >> >> AC97 is a standard for sound so that is OK. > > Progress! > > I can now get video and sound, although the volume is low, but it is there. > Your command line worked, using /dsp2 crashed it, /dsp1 is fine. > The Alsamixer gives me control using PCM, if I run the 'alsamixer -c 1' > command I just get a three-line header with little info. > The mplayer just quit, and won't restart, so I'll reboot and let it run > undisturbed for a while. > But we have Progress! > More later. Thanks to all. The first time, the picture was good and stable, and in colour. The second time after reboot, it's really unstable, and it quit after a couple of minutes, and after it crashed, it keeps repeating: 'Error reading audio, No such device.' Back to the drawing board. The terminal showed: "david(a)david-laptop:~$ mplayer tv:// -tv driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team CPU: Mobile Intel(R) Pentium(R) 4 CPU 3.06GHz (Family: 15, Model: 2, Stepping: 9) CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing tv://. TV file format detected. Selected driver: v4l2 name: Video 4 Linux 2 input author: Martin Olschewski <olschewski(a)zpr.uni-koeln.de> comment: first try, more to come ;-) Selected device: Pinnacle Dazzle DVC 90/DVC 100 Capabilites: video capture audio read/write streaming supported norms: 0 = NTSC; 1 = NTSC-M; 2 = NTSC-M-JP; 3 = NTSC-M-KR; 4 = NTSC-443; 5 = PAL; 6 = PAL-BG; 7 = PAL-H; 8 = PAL-I; 9 = PAL-DK; 10 = PAL-M; 11 = PAL-N; 12 = PAL-Nc; 13 = PAL-60; 14 = SECAM; 15 = SECAM-B; 16 = SECAM-G; 17 = SECAM-H; 18 = SECAM-DK; 19 = SECAM-L; 20 = SECAM-Lc; inputs: 0 = Composite1; 1 = S-Video; Current input: 0 Current format: YUYV Selected input hasn't got a tuner! xscreensaver_disable: Could not find XScreenSaver window. GNOME screensaver disabled ========================================================================== Opening video decoder: [raw] RAW Uncompressed Video VDec: vo config request - 640 x 480 (preferred colorspace: Packed YUY2) VDec: using Packed YUY2 as output csp (no 0) Movie-Aspect is undefined - no prescaling applied. VO: [xv] 640x480 => 640x480 Packed YUY2 Selected video codec: [rawyuy2] vfm: raw (RAW YUY2) ========================================================================== ========================================================================== Forced audio codec: mad Opening audio decoder: [pcm] Uncompressed PCM audio decoder AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio: 192000->192000) Selected audio codec: [pcm] afm: pcm (Uncompressed PCM) ========================================================================== AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample) Starting playback... No bind found for key 'MOUSE_BTN0'. 0.2% 0 0 No bind found for key 'MOUSE_BTN0'. 0.2% 1 0 " ------------------------------------ And relaunching it from a fresh terminal gave: "david(a)david-laptop:~$ mplayer tv:// -tv driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team CPU: Mobile Intel(R) Pentium(R) 4 CPU 3.06GHz (Family: 15, Model: 2, Stepping: 9) CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 Compiled with runtime CPU detection. mplayer: could not connect to socket mplayer: No such file or directory Failed to open LIRC support. You will not be able to use your remote control. Playing tv://. TV file format detected. Selected driver: v4l2 name: Video 4 Linux 2 input author: Martin Olschewski <olschewski(a)zpr.uni-koeln.de> comment: first try, more to come ;-) v4l2: unable to open '/dev/video0': No such file or directory v4l2: ioctl set mute failed: Bad file descriptor v4l2: 0 frames successfully processed, 0 frames dropped. Exiting... (End of file)" ---------------------------------------------------------- Hmm. -- Davey.
From: Davey on 22 Apr 2010 13:47 On Thu, 22 Apr 2010 13:35:02 -0400, Davey wrote: > On Thu, 22 Apr 2010 12:54:47 -0400, Davey wrote: > >> On Mon, 19 Apr 2010 20:09:35 +0100, Andy Furniss wrote: >> >>> Davey wrote: >>> >>>> [36475.333748] em28xx #0: V4L2 device registered as /dev/video0 and >>>> /dev/vbi0 >>>> [36475.333766] em28xx #0: Found Pinnacle Dazzle DVC 90/DVC 100 >>>> [36475.333832] em28xx audio device (2304:021a): interface 1, class 1 >>>> [36475.333885] em28xx audio device (2304:021a): interface 2, class 1 >>>> [36475.333965] usbcore: registered new interface driver em28xx >>>> [36475.642569] usbcore: registered new interface driver snd-usb-audio >>>> >>>> Any help understanding that lot much appreciated. But it seems to be happy >>>> that there is a Dazzle out there. Tonight, the picture is a lot less jerky, >>>> even on VLC. But still no sound! >>> >>> I have never used usb audio, but guessing from the blog example I would try >>> >>> mplayer tv:// -tv >>> driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 >>> >>> I see you have two audio devices so also try with ...:adevice=/dev/dsp2 >>> >>> Also run alsamixer and make sure "DVC 100" (if it exists) is unmuted and >>> turned up while testing. >>> >>>> I see the AC97 audio in there. Maybe that's where the trouble is, isn't >>>> that a Windows driver? >>> >>> AC97 is a standard for sound so that is OK. >> >> Progress! >> >> I can now get video and sound, although the volume is low, but it is there. >> Your command line worked, using /dsp2 crashed it, /dsp1 is fine. >> The Alsamixer gives me control using PCM, if I run the 'alsamixer -c 1' >> command I just get a three-line header with little info. >> The mplayer just quit, and won't restart, so I'll reboot and let it run >> undisturbed for a while. >> But we have Progress! >> More later. Thanks to all. > > The first time, the picture was good and stable, and in colour. The second > time after reboot, it's really unstable, and it quit after a couple of > minutes, and after it crashed, it keeps repeating: > 'Error reading audio, No such device.' > Back to the drawing board. > > The terminal showed: > > "david(a)david-laptop:~$ mplayer tv:// -tv > driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 > MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team > CPU: Mobile Intel(R) Pentium(R) 4 CPU 3.06GHz (Family: 15, Model: 2, > Stepping: 9) > CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 > Compiled with runtime CPU detection. > mplayer: could not connect to socket > mplayer: No such file or directory > Failed to open LIRC support. You will not be able to use your remote > control. > > Playing tv://. > TV file format detected. > Selected driver: v4l2 > name: Video 4 Linux 2 input > author: Martin Olschewski <olschewski(a)zpr.uni-koeln.de> > comment: first try, more to come ;-) > Selected device: Pinnacle Dazzle DVC 90/DVC 100 > Capabilites: video capture audio read/write streaming > supported norms: 0 = NTSC; 1 = NTSC-M; 2 = NTSC-M-JP; 3 = NTSC-M-KR; 4 = > NTSC-443; 5 = PAL; 6 = PAL-BG; 7 = PAL-H; 8 = PAL-I; 9 = PAL-DK; 10 = > PAL-M; 11 = PAL-N; 12 = PAL-Nc; 13 = PAL-60; 14 = SECAM; 15 = SECAM-B; 16 = > SECAM-G; 17 = SECAM-H; 18 = SECAM-DK; 19 = SECAM-L; 20 = SECAM-Lc; > inputs: 0 = Composite1; 1 = S-Video; > Current input: 0 > Current format: YUYV > Selected input hasn't got a tuner! > xscreensaver_disable: Could not find XScreenSaver window. > GNOME screensaver disabled > ========================================================================== > Opening video decoder: [raw] RAW Uncompressed Video > VDec: vo config request - 640 x 480 (preferred colorspace: Packed YUY2) > VDec: using Packed YUY2 as output csp (no 0) > Movie-Aspect is undefined - no prescaling applied. > VO: [xv] 640x480 => 640x480 Packed YUY2 > Selected video codec: [rawyuy2] vfm: raw (RAW YUY2) > ========================================================================== > ========================================================================== > Forced audio codec: mad > Opening audio decoder: [pcm] Uncompressed PCM audio decoder > AUDIO: 48000 Hz, 2 ch, s16le, 1536.0 kbit/100.00% (ratio: 192000->192000) > Selected audio codec: [pcm] afm: pcm (Uncompressed PCM) > ========================================================================== > AO: [pulse] 48000Hz 2ch s16le (2 bytes per sample) > Starting playback... > No bind found for key 'MOUSE_BTN0'. 0.2% 0 0 > No bind found for key 'MOUSE_BTN0'. 0.2% 1 0 " > ------------------------------------ > And relaunching it from a fresh terminal gave: > > "david(a)david-laptop:~$ mplayer tv:// -tv > driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 > MPlayer 1.0rc2-4.3.3 (C) 2000-2007 MPlayer Team > CPU: Mobile Intel(R) Pentium(R) 4 CPU 3.06GHz (Family: 15, Model: 2, > Stepping: 9) > CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1 > Compiled with runtime CPU detection. > mplayer: could not connect to socket > mplayer: No such file or directory > Failed to open LIRC support. You will not be able to use your remote > control. > > Playing tv://. > TV file format detected. > Selected driver: v4l2 > name: Video 4 Linux 2 input > author: Martin Olschewski <olschewski(a)zpr.uni-koeln.de> > comment: first try, more to come ;-) > v4l2: unable to open '/dev/video0': No such file or directory > v4l2: ioctl set mute failed: Bad file descriptor > v4l2: 0 frames successfully processed, 0 frames dropped. > > > Exiting... (End of file)" > ---------------------------------------------------------- > Hmm. Ran it again, and watched. When it quit, this is the message. The A: and V: values had gone from 0, as had the 3208/3208 refs. Now to find out what it all means, and what to do about it. Again, any help most welcome, I am a "Stranger in a Strange Land" here. "A: 107.6 V: 107.6 A-V: 0.003 ct: 0.086 3208/3208 0% 8% 0.8% 10 0 0.75x video buffer full - dropping frame". This repeated ad infinitum, with increasing values, until I killed it. -- Davey.
From: Andy Furniss on 22 Apr 2010 18:40 Davey wrote: > Ran it again, and watched. When it quit, this is the message. The A: and V: > values had gone from 0, as had the 3208/3208 refs. Now to find out what it > all means, and what to do about it. Again, any help most welcome, I am a > "Stranger in a Strange Land" here. > > "A: 107.6 V: 107.6 A-V: 0.003 ct: 0.086 3208/3208 0% 8% 0.8% 10 0 > 0.75x > video buffer full - dropping frame". > > This repeated ad infinitum, with increasing values, until I killed it. The mplayer output was useful as I now know the video format is yuy2, which should get hardware acceleration. I wish I knew why it isn't working properly, though - so some more things to try. Make sure the video is playing before you start mplayer. Try using an extra option called buffersize like - mplayer tv:// -tv driver=v4l2:norm=NTSC:buffersize=64:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 Try using alsa for sound - mplayer tv:// -tv driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:alsa:adevice=hw.1 Try using textured video rather than overlay. mplayer -vo xv:adaptor=1 tv:// -tv driver=v4l2:norm=NTSC:buffersize=64:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 Of course you can mix the extra options eg if alsa sound works try with buffersize=64 and -vo xv:adaptor=1 as well etc. When testing leave running top -b | grep Cpu in another terminal and see how much spare Cpu you have (id)
From: Davey on 23 Apr 2010 11:51
Andy, some comments in line. On Thu, 22 Apr 2010 23:40:46 +0100, Andy Furniss wrote: > Davey wrote: > >> Ran it again, and watched. When it quit, this is the message. The A: and V: >> values had gone from 0, as had the 3208/3208 refs. Now to find out what it >> all means, and what to do about it. Again, any help most welcome, I am a >> "Stranger in a Strange Land" here. >> >> "A: 107.6 V: 107.6 A-V: 0.003 ct: 0.086 3208/3208 0% 8% 0.8% 10 0 >> 0.75x >> video buffer full - dropping frame". >> >> This repeated ad infinitum, with increasing values, until I killed it. > > The mplayer output was useful as I now know the video format is yuy2, > which should get hardware acceleration. > That's good. > I wish I knew why it isn't working properly, though - so some more > things to try. > > Make sure the video is playing before you start mplayer. > Actually, I'm just for now using the TV-out bypassing the tape, so as long as the player is turned on, I have A-V output. > Try using an extra option called buffersize like - > > mplayer tv:// -tv > driver=v4l2:norm=NTSC:buffersize=64:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 > After some more digging yesterday, I already have that in my list of things to try. > Try using alsa for sound - > > mplayer tv:// -tv > driver=v4l2:norm=NTSC:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:alsa:adevice=hw.1 > I will do, but the alsamixer does already control the volume, now I know how to get the right GUI on display. But here is no harm in trying it as part of the command line, per your suggestion. > Try using textured video rather than overlay. > > mplayer -vo xv:adaptor=1 tv:// -tv > driver=v4l2:norm=NTSC:buffersize=64:device=/dev/video0:audiorate=48000:immediatemode=0:forceaudio:adevice=/dev/dsp1 > Will try that. > Of course you can mix the extra options eg if alsa sound works > try with buffersize=64 and -vo xv:adaptor=1 as well etc. > > When testing leave running > > top -b | grep Cpu > > in another terminal and see how much spare Cpu you have (id) Thanks. The last time that I ran the Dazzle, it went on for a good long time, only stopping when I did something else on the PC, which suggests the CPU got overloaded. If it works ok on the basis of "that's all it will do at one time", I can live with that. If I (we!) can get this to the point where it plays locally just fine, then the next stage will be to get it to stream either to an .iso file, or to a USB DVD-writer. I am prepared to accept that a second busy USB connection might be too much to handle, so I have been trying to find how to stream the signals to a .iso file, but I got lost in the mplayer man document, my eyes glazed over! Again, any hints welcome. Going back into the forums yesterday confirmed my original thoughts of others' experiences, either it worked out of the box, or was a huge pain in the behind and still didn't produce sound. Well, we're over that hump! I have also tried the Dazzle on an 8.04 Pentium 3 machine, with WinXP running under Sun virtualbox, but it doesn't recognise the Dazzle, so it won't run the capture program, since it thinks there's nothing there. I came back to this 9.04 machine, which at least is partially working. Thanks again. -- Davey. |