Video with artifacts on openSUSE 12.3 32bit, kernel 3.7.10 - URB packet 0, status -71 [Bit-stuff error (bad cable?)]

[tosiara]

Hi,

I have Easycap with numbered 4ch model. Built kernel modules, initialized device - no problems at all. But when capturing video using either mplayer or motion - the picture is corrupted.

When I boot Win7 32bit on the same machine and use same USB port and capture video using SuperPlayer (included by manufacturer) - no issues. Video is crisp, smooth and no artifacts.

I noticed "URB packet 0, status -71 [Bit-stuff error (bad cable?)]" in dmesg. But when tested Fedora with kernel 3.6 on the same machine - pictire is also corrupted, but no "URB" errors in dmesg

Video sample and screenshots are about to be uploaded.

Logs:

$ dmesg

[ 2071.401371] usb 1-3: new high-speed USB device number 15 using ehci_hcd

[ 2071.516634] usb 1-3: New USB device found, idVendor=1c88, idProduct=0007

[ 2071.516647] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 2071.516655] usb 1-3: Product: SM-USB 007

[ 2071.516661] usb 1-3: Manufacturer: Somagic, Inc.

[ 2071.516667] usb 1-3: SerialNumber: SMBL007

[ 2185.405852] usb 1-3: USB disconnect, device number 15

[ 2185.638900] usb 1-3: new high-speed USB device number 16 using ehci_hcd

[ 2185.754534] usb 1-3: New USB device found, idVendor=1c88, idProduct=003e

[ 2185.754555] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 2185.754563] usb 1-3: Product:  SMI Grabber Dev

[ 2185.754569] usb 1-3: Manufacturer:  Somagic, Inc.  

[ 2185.754574] usb 1-3: SerialNumber: SMIVIDEO3E9876543210

[ 2185.758931] saa7115 6-004a: saa7113 found (8f7113000000000) @ 0x94 (smi2021)

[ 2185.791213] smi2021::smi2021_usb_probe: Driver version 0.1 successfully loaded

[ 2185.799018] smi2021 1-3:1.0: V4L2 device registered as video2

[ 2186.043786] smi2021::smi2021_pcm_open: PCM device open!

[ 2186.043812] smi2021::smi2021_pcm_close: PCM device closing

[ 2186.044459] smi2021::smi2021_pcm_open: PCM device open!

[ 2186.044480] smi2021::smi2021_pcm_close: PCM device closing

[ 2189.401073] smi2021::smi2021_alloc_isoc: urbs allocated

[ 2189.411505] print_usb_err: 34 callbacks suppressed

[ 2189.411509] URB packet 0, status -71 [Bit-stuff error (bad cable?)]

[ 2189.411510] URB packet 1, status -71 [Bit-stuff error (bad cable?)]

[ 2189.449071] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.401117] smi2021::smi2021_start_streaming: Streaming started!

[ 2189.460183] URB packet 4, status -71 [Bit-stuff error (bad cable?)]

[ 2189.480172] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.550018] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.551396] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2189.566100] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2189.572448] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2189.576190] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2194.424157] print_usb_err: 262 callbacks suppressed

[ 2194.424162] URB packet 3, status -71 [Bit-stuff error (bad cable?)]

[ 2194.447993] URB packet 7, status -71 [Bit-stuff error (bad cable?)]

[ 2194.449158] URB packet 8, status -71 [Bit-stuff error (bad cable?)]

[ 2194.457838] URB packet 6, status -71 [Bit-stuff error (bad cable?)]

[ 2194.460315] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2194.494001] URB packet 4, status -71 [Bit-stuff error (bad cable?)]

[ 2194.530084] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2194.532569] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2194.533768] URB packet 0, status -71 [Bit-stuff error (bad cable?)]

[ 2194.542652] URB packet 8, status -71 [Bit-stuff error (bad cable?)]

$ mplayer tv:// -tv driver=v4l2:width=720:height=576:fps=25:outfmt=rgb24:device=/dev/video2

MPlayer dev-SVN-r35127-4.7-openSUSE Linux 12.3 (i586)-Packman (C) 2000-2012 MPlayer Team

Can't open joystick device /dev/input/js0: No such file or directory

Can't init input joystick

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 <olsch...@zpr.uni-koeln.de>

 comment: first try, more to come ;-)

Selected device: smi2021

 Capabilities:  video capture  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 = Composite; 1 = S-Video;

 Current input: 0

 Current format: UYVY

Selected input hasn't got a tuner!

v4l2: ioctl set mute failed: Invalid argument

Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory

[vdpau] Error when calling vdp_device_create_x11: 1

==========================================================================

Opening video decoder: [raw] RAW Uncompressed Video

Movie-Aspect is undefined - no prescaling applied.

VO: [xv] 720x576 => 720x576 Packed UYVY 

Selected video codec: [rawuyvy] vfm: raw (RAW UYVY)

==========================================================================

Audio: no sound

Starting playback...

V:   0.0   1/  1 ??% ??% ??,?% 0 0 

Frame too small! (2288<829440) Wrong format?

V:   0.0   3/  3 ??% ??% ??,?% 0 0 

Frame too small! (407520<829440) Wrong format?

V:   0.0 384/384 ??% ??% ??,?% 0 0 

v4l2: ioctl set mute failed: Invalid argument

v4l2: 386 frames successfully processed, -1 frames dropped.

Exiting... (Quit)

$ uname -a

Linux hostname 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) i686 athlon i386 GNU/Linux


Am I missing something? Is there a way to fix this?

Thank you

[tosiara]

Sceenshot

[Jon Arne Jørgensen]

Have you tried the userspace version of our driver?

Do you get clean video if you use it?

On Mon, Apr 1, 2013 at 12:16 PM, tosiara <tos...@gmail.com> wrote:

Sceenshot

--
You received this message because you are subscribed to the Google Groups "easycap-somagic-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easycap-somagic-...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Jonarne
http://jonarne.no

[tosiara]

When I try somagic-capture I get this error:

Failed to claim device interface: Device or resource busy
Is somagic-capture already running?

Also, I noticed that image corruptions are random. At the time I captured video - there were almost no corruption. Yesterday it happened every second all the video long. But in my captured example only 4 happened during 1 min. Please see video here: http://youtu.be/Oahou_5qc7c (note 00:25, 00:37, 00:50 and 1:00)

I tried to capture once again and couldn't reproduce at all during 5 minutes

Need to do longer test on Windows and Linux to see if my easycap is not broken somehow.

On Monday, April 1, 2013 1:38:59 PM UTC+3, Jon Arne wrote:

Have you tried the userspace version of our driver?

Do you get clean video if you use it?

On Mon, Apr 1, 2013 at 12:16 PM, tosiara <tos...@gmail.com> wrote:

Sceenshot

--

Jonarne
http://jonarne.no

[Jon Arne Jørgensen]

On Mon, Apr 1, 2013 at 1:11 PM, tosiara <tos...@gmail.com> wrote:

When I try somagic-capture I get this error:

Failed to claim device interface: Device or resource busy
Is somagic-capture already running?

You will have to rmmod the smi2021 module before testing the userspace tools.
 

Also, I noticed that image corruptions are random. At the time I captured video - there were almost no corruption. Yesterday it happened every second all the video long. But in my captured example only 4 happened during 1 min. Please see video here: http://youtu.be/Oahou_5qc7c (note 00:25, 00:37, 00:50 and 1:00)

I tried to capture once again and couldn't reproduce at all during 5 minutes

I get that kind of corruptions my self, but only at the rate you got in your video.

Most of the time I get clean video without any artifacts.

I guess it can be related to how busy the usb-bus is. I think sometimes some usb packets are dropped because the computer is to busy to handle them.

Need to do longer test on Windows and Linux to see if my easycap is not broken somehow.

Please report back if you never get this kind of artifacts with the windows driver.

 

On Monday, April 1, 2013 1:38:59 PM UTC+3, Jon Arne wrote:

Have you tried the userspace version of our driver?

Do you get clean video if you use it?

On Mon, Apr 1, 2013 at 12:16 PM, tosiara <tos...@gmail.com> wrote:

Sceenshot

--
Jonarne
http://jonarne.no

--

You received this message because you are subscribed to the Google Groups "easycap-somagic-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easycap-somagic-...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--
Jonarne
http://jonarne.no

[tosiara]

Ok, I did test on 3 laptops and now I'm puzzled...

Test 1. Old laptop HP nx6125 (USB 1.1 and 2.0). Only Linux available Video absolutely damaged
Test 2. Old laptop HP dv5-1030en (USB 2.0). WIndows Vista - black screen. Linux - better than just black screen, but still absolutely damaged video - see http://www.youtube.com/watch?v=imStcEzz-tk
Test 3. New laptop Toshiba L850-15X (USB 2.0 and 3.0). Both Windows 7 and Linux work fine (video same as already reported in previous post)

So what are Easycap requirements? USB 3.0 controller?

[Jon Arne Jørgensen]

On Mon, Apr 1, 2013 at 5:51 PM, tosiara <tos...@gmail.com> wrote:
> Ok, I did test on 3 laptops and now I'm puzzled...
>
> Test 1. Old laptop HP nx6125 (USB 1.1 and 2.0). Only Linux available Video
> absolutely damaged
> Test 2. Old laptop HP dv5-1030en (USB 2.0). WIndows Vista - black screen.
> Linux - better than just black screen, but still absolutely damaged video -
> see http://www.youtube.com/watch?v=imStcEzz-tk

Can you include the dmesg output when trying to capture video on this computer?

> Test 3. New laptop Toshiba L850-15X (USB 2.0 and 3.0). Both Windows 7 and
> Linux work fine (video same as already reported in previous post)
>
> So what are Easycap requirements? USB 3.0 controller?
>

I think I only have USB2.0 on my computer, so it should be working with USB2.0

I don't do any tests in the driver to check if the device is connected
to an USB2.0 hub, but I hope to implement that check soon.

[tosiara]

here it is:

[  222.965928] usb 1-1: USB disconnect, device number 2
[  223.199081] usb 1-1: new high-speed USB device number 5 using ehci_hcd
[  223.315112] usb 1-1: New USB device found, idVendor=1c88, idProduct=003e
[  223.315126] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[  223.315137] usb 1-1: Product:  SMI Grabber Dev
[  223.315147] usb 1-1: Manufacturer:  Somagic, Inc. 
[  223.315157] usb 1-1: SerialNumber: SMIVIDEO3E9876543210
[  288.597773] saa7115 5-004a: saa7113 found (8f7113000000000) @ 0x94 (smi2021)
[  288.623380] smi2021::smi2021_usb_probe: Driver version 0.1 successfully loaded
[  288.638362] smi2021 1-1:1.0: V4L2 device registered as video1
[  288.638406] usbcore: registered new interface driver smi2021
[  288.695246] smi2021::smi2021_pcm_open: PCM device open!
[  288.695383] smi2021::smi2021_pcm_close: PCM device closing
[  288.695510] smi2021::smi2021_pcm_open: PCM device open!
[  288.695584] smi2021::smi2021_pcm_close: PCM device closing
[  288.695717] smi2021::smi2021_pcm_open: PCM device open!
[  288.695827] smi2021::smi2021_pcm_close: PCM device closing
[  288.695958] smi2021::smi2021_pcm_open: PCM device open!
[  288.696912] smi2021::smi2021_pcm_close: PCM device closing
[  288.697404] smi2021::smi2021_pcm_open: PCM device open!
[  288.702775] smi2021::smi2021_pcm_close: PCM device closing
[  288.702929] smi2021::smi2021_pcm_open: PCM device open!
[  288.703165] smi2021::smi2021_pcm_close: PCM device closing
[  288.703292] smi2021::smi2021_pcm_open: PCM device open!
[  288.703370] smi2021::smi2021_pcm_close: PCM device closing
[  288.703507] smi2021::smi2021_pcm_open: PCM device open!
[  288.703663] smi2021::smi2021_pcm_close: PCM device closing
[  288.703795] smi2021::smi2021_pcm_open: PCM device open!
[  288.704375] smi2021::smi2021_pcm_close: PCM device closing
[  288.708630] smi2021::smi2021_pcm_open: PCM device open!
[  293.393953] smi2021::smi2021_alloc_isoc: urbs allocated
[  293.404326] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  293.405849] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  293.406969] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  293.417063] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  293.418303] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  293.418305] URB packet 9, status -71 [Bit-stuff error (bad cable?)]
[  293.394075] smi2021::smi2021_start_streaming: Streaming started!
[  293.425697] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  293.428060] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  293.429366] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  293.438208] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  293.744518] smi2021::smi2021_pcm_close: PCM device closing
[  298.408895] print_usb_err: 1790 callbacks suppressed
[  298.408902] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  298.410017] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  298.410096] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  298.411488] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  298.412655] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  298.427485] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  298.428699] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  298.428815] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  298.428865] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  298.429978] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  303.424547] print_usb_err: 1848 callbacks suppressed
[  303.424553] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  303.428193] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  303.430667] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  303.432022] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  303.437024] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  303.438171] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  303.440616] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  303.440665] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  303.440741] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  303.443114] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  308.435247] print_usb_err: 1775 callbacks suppressed
[  308.435254] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  308.437560] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  308.440155] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  308.442569] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  308.442739] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  308.450163] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  308.452520] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  308.452663] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  308.452781] URB packet 9, status -71 [Bit-stuff error (bad cable?)]
[  308.454021] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  313.444546] print_usb_err: 1670 callbacks suppressed
[  313.444553] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  313.444695] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  313.447122] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  313.459576] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  313.467111] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  313.468231] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  313.468348] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  313.473289] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  313.473367] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  313.475761] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  318.446652] print_usb_err: 1687 callbacks suppressed
[  318.446658] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  318.450342] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  318.451490] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  318.451518] URB packet 6, status -71 [Bit-stuff error (bad cable?)]
[  318.455389] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[  318.457599] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  318.457640] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  318.462672] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[  318.472652] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  318.472710] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  323.454708] print_usb_err: 1715 callbacks suppressed
[  323.454714] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[  323.454756] URB packet 7, status -71 [Bit-stuff error (bad cable?)]
[  323.454796] URB packet 9, status -71 [Bit-stuff error (bad cable?)]
[  323.458402] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  323.459509] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[  323.459613] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  323.464556] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  323.470787] URB packet 1, status -71 [Bit-stuff error (bad cable?)]
[  323.470836] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[  323.472050] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[  325.301556] smi2021::smi2021_cancel_isoc: killing 4 urbs...
[  325.309329] smi2021::smi2021_cancel_isoc: all urbs killed
[  325.309335] smi2021::smi2021_free_isoc: freeing 4 urb buffers...
[  325.309345] smi2021::smi2021_free_isoc: all urb buffers freed
[  325.309670] smi2021::smi2021_stop_streaming: Streaming stopped!

$ uname -a

Linux vista 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) i686 athlon i386 GNU/Linux 

Laptop specifications: http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01518215&tmp_task=prodinfoCategory&cc=us&dlc=en&lc=en&product=3777256

Let me know if you need anything else, I'm happy to perform additional testing

Thanks

[Jon Arne Jørgensen]

Ok, thanks.

> $ uname -a
>
> Linux vista 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013
> (82d3f21) i686 athlon i386 GNU/Linux
>
> Laptop specifications:
> http://h10025.www1.hp.com/ewfrf/wc/document?docname=c01518215&tmp_task=prodinfoCategory&cc=us&dlc=en&lc=en&product=3777256
>
> Let me know if you need anything else, I'm happy to perform additional
> testing
>

Did you test your device with the userspace application. (After
removing the smi2021 module?)

> Thanks
>
> On Monday, April 1, 2013 7:05:20 PM UTC+3, Jon Arne wrote:
>>
>> On Mon, Apr 1, 2013 at 5:51 PM, tosiara <tos...@gmail.com> wrote:
>> > Ok, I did test on 3 laptops and now I'm puzzled...
>> >
>> > Test 1. Old laptop HP nx6125 (USB 1.1 and 2.0). Only Linux available
>> > Video
>> > absolutely damaged
>> > Test 2. Old laptop HP dv5-1030en (USB 2.0). WIndows Vista - black
>> > screen.
>> > Linux - better than just black screen, but still absolutely damaged
>> > video -
>> > see http://www.youtube.com/watch?v=imStcEzz-tk
>>
>> Can you include the dmesg output when trying to capture video on this
>> computer?
>>

[tosiara]

I tried running somagic-capture on both working and non-working laptopts, and both are failing:

# somagic-capture | mplayer -vf yadif,screenshot -demuxer rawvideo -rawvideo "pal:format=uyvy:fps=25" -aspect 4:3 -

MPlayer dev-SVN-r35127-4.7-openSUSE Linux 12.3 (i586)-Packman (C) 2000-2012 MPlayer Team
Can't open joystick device /dev/input/js0: No such file or directory
Can't init input joystick
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 -.
Reading from stdin...
rawvideo file format detected.
Load subtitles in ./

Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory
[vdpau] Error when calling vdp_device_create_x11: 1

Opening video filter: [screenshot]
Opening video filter: [yadif]

==========================================================================
Opening video decoder: [raw] RAW Uncompressed Video

Could not find matching colorspace - retrying with -vf scale...
Opening video filter: [scale]
Movie-Aspect is 1.33:1 - prescaling to correct movie aspect.
[swscaler @ 0xa604460] using unscaled uyvy422 -> yuv420p special converter
VO: [xv] 720x576 => 768x576 Planar YV12

Selected video codec: [rawuyvy] vfm: raw (RAW UYVY)
==========================================================================
Audio: no sound
Starting playback...

Frame too small! (35<829440) Wrong format?
V:   0.0   1/  1 ??% ??% ??,?% 0 0

Exiting... (End of file)

[tosiara]

But why my device does not work on  USB 2.0 Windows machines?
On the package there is mentioned minimum requirement USB 2,0, but it only works on USB3 laptop
Could it be modified version? Maybe it is generating huge usb traffic?

I have tested Win7 workstation (amd quad core, usb 2.0) - it has low framerate, about 1 frame per 2 seconds. Under Linux on the same machine I get urb errors and corrupted video

I'm going also to contact manufacturer to provide support, because fully supported win machine has issue. So, let's ask for comments

Will keep you informed

[Jon Arne Jørgensen]

If you have multiple usb-ports on your windows machine, it could be
that some of the ports are USB1.0 only?

[<=K]

This looks to me like it might be a problem with mplayer. Can you verify that mplayer works for other video files from the command line?

Jeff

[tosiara]

Using mplayer I can view my built-in webcam and also I can play local files.

Command I use to view easycap (video1) and webcamera (video0):

mplayer tv:// -tv driver=v4l2:width=720:height=576:fps=25:outfmt=rgb24:device=/dev/video1

[tosiara]

I have checked mainboard specification of the workstation (ASUS - M4A78) - all ports are USB 2.0

[tosiara]

Hello,

I left motion running during this night and capturing static picture. In the morning I found that it has detected a lot of movements. Take a look, what it has detected as movements: http://yadi.sk/d/3iUiQuXa3iqSg (15MB avi) - this was a "working" laptop. Any ideas?

[tosiara]

Small update.

I noticed that mjpg-streamer streams video fine, no picture corruption. Unfortunately it has a pixel format bug which results in pink-green colors. But the fact that mplayer and mjpg-streamer are working fine. This is something wrong with motion application. Will continue investigation

[Jon Arne Jørgensen]

I just pushed an update to our git repository. It should stop the
video from flickering by dropping frames that are not complete.

Test it and report back :)

> --
> You received this message because you are subscribed to the Google Groups
> "easycap-somagic-linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to easycap-somagic-...@googlegroups.com.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>

--
Jonarne
http://jonarne.no

[tosiara]

I have just built new kernel module and tested "motion" - looks like new module resolves that issue with "crawling" frames. Great!

In dmesg there are lots of messages:

[  677.779979] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 1
[  677.779989] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 1
[  677.779999] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 1
[  677.780013] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  677.780030] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.758832] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 410400, trc_av: 285
[  704.758844] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759868] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759878] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759888] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759898] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759908] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0
[  704.759918] smi2021::smi2021_buffer_done: Dropping buffer, Buf->pos: 0, trc_av: 0

I will do more tests and leave motion running at night to see if there will be fake movements detected and report back

Thanks!

[Jon Arne Jørgensen]

The dmesg messages comes when the driver drops a partial frame.
You can disable it by building the module without the DEBUG flag (but
I'm not completely sure how to disable that flag :) ).

The easiest way to stop the messages flooding dmesg is to remove the
"smi2021_dbg()" function call on line 105 & 106 in the
"smi2021_video.c"
and rebuilding the module.

[tosiara]

Hi,

I'm back to testing and still can't overcome the initial issue:

[22450.664876] print_usb_err: 1370 callbacks suppressed
[22450.664880] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[22450.666049] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[22450.666185] URB packet 8, status -71 [Bit-stuff error (bad cable?)]
[22450.672350] URB packet 5, status -71 [Bit-stuff error (bad cable?)]
[22450.673589] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[22450.678516] URB packet 0, status -71 [Bit-stuff error (bad cable?)]
[22450.682317] URB packet 4, status -71 [Bit-stuff error (bad cable?)]
[22450.684810] URB packet 3, status -71 [Bit-stuff error (bad cable?)]
[22450.686036] URB packet 2, status -71 [Bit-stuff error (bad cable?)]
[22450.688627] URB packet 7, status -71 [Bit-stuff error (bad cable?)]

Syslog is also full of "Dropping buffer".

I have tested 3 ASUS AMD-based x86 workstations:

M5A78L-M LX, M4A78, M4A88T-M - all them have USB 2.0 ports and have same issue. I disconnect everything and only leave Easycap connected, my lsusb looks like:

# lsusb -t
/:  Bus 07.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/2p, 12M
/:  Bus 06.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/3p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/6p, 480M
    |__ Port 1: Dev 8, If 0, Class=Vendor Specific Class, Driver=smi2021, 480M

Should be enough power and bandwidth.
Meanwhile, a laptop with USB 3 works fine.

Is it a device specific hardware bug or is there any workaround to make it woking on USB 2.0 mentioned workstations?

Thanks, appreciate any feedback

[tosiara]

Just tested old Macbook (model 2006)
Works fine, video plays, smooth framerate. During 5 min playback there were only 2 messages regarding failed URB in dmesg

# lsusb -t
/:  Bus 05.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M
    |__ Port 1: Dev 3, If 2, Class=Application Specific Interface, Driver=, 12M
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
    |__ Port 2: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 2: Dev 2, If 1, Class=Human Interface Device, Driver=appletouch, 12M
    |__ Port 2: Dev 2, If 2, Class=Human Interface Device, Driver=usbhid, 12M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/8p, 480M
    |__ Port 3: Dev 9, If 0, Class=Vendor Specific Class, Driver=smi2021, 480M
    |__ Port 4: Dev 7, If 0, Class=Video, Driver=uvcvideo, 480M
    |__ Port 4: Dev 7, If 1, Class=Video, Driver=uvcvideo, 480M

I tend to beleive Easycap somehow does not like AMD's SB700 chipset, huh?

[Jon Arne Jørgensen]

Hi,
The, I've had some trouble with the "status -71 [Bit-stuff error (bad
cable?)]" errors.
I think they are caused by a bug in the driver.
I think I've fixed the bug in my latest development, but the code now
relies on a kernel from the linuxtv development tree because of some
fixes to the saa7115 driver that the driver depends on.
The code in the easycap google code repo is outdated.

I'll try to submit a new patch to the linux-media mailinglist some
time this week, and I'll try to do a writeup on the easycap page about
how to compile and test the patch.

[tosiara]

Hi,

any chances to get the magical patch?...

[Jon Arne Jørgensen]

I hope to get some patches prepared this week, and make a short
writeup on how to patch and compile the kernel.

[Jon Arne Jørgensen]

Hi All,
I've finaly gotten around to write a how-to for compiling and
installing the kernel module.

The current version of the module is on the kernel-media
patchwork/mailing-list, and can be found here:
https://patchwork.linuxtv.org/patch/20010/

The how-to is here:
http://code.google.com/p/easycap-somagic-linux/wiki/BuildingKernelModule

--
Jonarne
http://jonarne.no

[tosiara]

Cool!

The only typo I have noticed so far is:

wget --no-check-certificate https://patchwork.linuxtv.org/patch/20010/mbox/ -O test.patch

should be:

wget --no-check-certificate https://patchwork.linuxtv.org/patch/20010/mbox/ -O smi2021v3.patch

isn't it?

You received this message because you are subscribed to a topic in the Google Groups "easycap-somagic-linux" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/easycap-somagic-linux/Ay_YhrS8VfA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to easycap-somagic-...@googlegroups.com.

[Jon Arne Jørgensen]

Thanks, That is of course correct... Missed that one :)

[tosiara]

Is it possible to compile new module (and patch saa7115) for openSUSE 12.3 standard release kernel 3.7.10-1.1-desktop ?

[tosiara]

Hi Jon,

Have you also re-implemented frame drops in the new driver? I have just tested with "motion" software and looks like "crawling frames" are back again

On Wednesday, April 3, 2013 10:15:45 AM UTC+3, Jon Arne wrote:

I just pushed an update to our git repository. It should stop the
video from flickering by dropping frames that are not complete.

Test it and report back :)

On Tue, Apr 2, 2013 at 12:30 PM, tosiara <tos...@gmail.com> wrote:
> Small update.
>
> I noticed that mjpg-streamer streams video fine, no picture corruption.
> Unfortunately it has a pixel format bug which results in pink-green colors.
> But the fact that mplayer and mjpg-streamer are working fine. This is
> something wrong with motion application. Will continue investigation
>
> --
> You received this message because you are subscribed to the Google Groups
> "easycap-somagic-linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to easycap-somagic-linux+unsub...@googlegroups.com.

[Jon Arne Jørgensen]

Yes, I'm sorry.
I rewrote the driver, and forgot to add the part that keeps the frames clean.
I'll re-implement it as soon as I've got more time for development.

On Sun, Nov 3, 2013 at 5:38 PM, tosiara <tos...@gmail.com> wrote:
> Hi Jon,
>
> Have you also re-implemented frame drops in the new driver? I have just
> tested with "motion" software and looks like "crawling frames" are back
> again
>
>
> On Wednesday, April 3, 2013 10:15:45 AM UTC+3, Jon Arne wrote:
>>
>> I just pushed an update to our git repository. It should stop the
>> video from flickering by dropping frames that are not complete.
>>
>> Test it and report back :)
>>
>> On Tue, Apr 2, 2013 at 12:30 PM, tosiara <tos...@gmail.com> wrote:
>> > Small update.
>> >
>> > I noticed that mjpg-streamer streams video fine, no picture corruption.
>> > Unfortunately it has a pixel format bug which results in pink-green
>> > colors.
>> > But the fact that mplayer and mjpg-streamer are working fine. This is
>> > something wrong with motion application. Will continue investigation
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "easycap-somagic-linux" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an

>> > email to easycap-somagic-...@googlegroups.com.

>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>>
>>
>> --
>> Jonarne
>> http://jonarne.no
>

> --
> You received this message because you are subscribed to the Google Groups
> "easycap-somagic-linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to easycap-somagic-...@googlegroups.com.

[tosiara]

Hi Jon,

have you had a chance to make progress on the new version of the driver?
Especially I'm interested in the fix for "incomplete frames"

I'd like to perform some testing with the new driver so if you have any newer sources - please let us know

Thanks

>> > email to easycap-somagic-linux+unsub...@googlegroups.com.

>> > For more options, visit https://groups.google.com/groups/opt_out.
>> >
>> >
>>
>>
>>
>> --
>> Jonarne
>> http://jonarne.no
>
> --
> You received this message because you are subscribed to the Google Groups
> "easycap-somagic-linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to easycap-somagic-linux+unsub...@googlegroups.com.

[Jon Arne Jørgensen]

Hi, It's been a busy fall/winter/holidays season, so I haven't had any
time. But I'm hoping do do some coding this weekend and next week.
I got some comments from the linux-media mailinglist on my last RFC
that needs to be implemented.
I'm also planning to make the driver drop incomplete frames again, and
I guess that's what you are looking for?

I'll try to post a comment here as soon as I have some patches.

>> >> > email to easycap-somagic-...@googlegroups.com.

>> >> > For more options, visit https://groups.google.com/groups/opt_out.
>> >> >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >> Jonarne
>> >> http://jonarne.no
>> >
>> > --
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "easycap-somagic-linux" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an

>> > email to easycap-somagic-...@googlegroups.com.

>> > For more options, visit https://groups.google.com/groups/opt_out.
>>
>>
>>
>> --
>> Jonarne
>> http://jonarne.no
>
> --
> You received this message because you are subscribed to the Google Groups
> "easycap-somagic-linux" group.
> To unsubscribe from this group and stop receiving emails from it, send an

> email to easycap-somagic-...@googlegroups.com.

[tosiara]

Just update and FYI

Today I have tested old version of the driver from Google Code repo on an ARM dev board ODROID U3 which runs kernel 3.8
Compilation went fine (only needed to add #include <linux/vmalloc.h>). Loded driver and initialed also fine.

But when you open video device and want to get some video - you get same bunch of errors "status -71 (bad cable?)" and the whole USB controller stops working, that means all the devices that are connected stops working (usb wifi, usb keayboard and usb flash drive). The board continues to run, but requires reboot to restore usb functionality.

I will also try to build 3.13 kernel and test the latest driver version from v4l patchwork and post results here

HTH

On Monday, April 1, 2013 1:10:32 PM UTC+3, tosiara wrote:

Hi,

I have Easycap with numbered 4ch model. Built kernel modules, initialized device - no problems at all. But when capturing video using either mplayer or motion - the picture is corrupted.

When I boot Win7 32bit on the same machine and use same USB port and capture video using SuperPlayer (included by manufacturer) - no issues. Video is crisp, smooth and no artifacts.

I noticed "URB packet 0, status -71 [Bit-stuff error (bad cable?)]" in dmesg. But when tested Fedora with kernel 3.6 on the same machine - pictire is also corrupted, but no "URB" errors in dmesg

Video sample and screenshots are about to be uploaded.

Logs:

$ dmesg

[ 2071.401371] usb 1-3: new high-speed USB device number 15 using ehci_hcd

[ 2071.516634] usb 1-3: New USB device found, idVendor=1c88, idProduct=0007

[ 2071.516647] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 2071.516655] usb 1-3: Product: SM-USB 007

[ 2071.516661] usb 1-3: Manufacturer: Somagic, Inc.

[ 2071.516667] usb 1-3: SerialNumber: SMBL007

[ 2185.405852] usb 1-3: USB disconnect, device number 15

[ 2185.638900] usb 1-3: new high-speed USB device number 16 using ehci_hcd

[ 2185.754534] usb 1-3: New USB device found, idVendor=1c88, idProduct=003e

[ 2185.754555] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3

[ 2185.754563] usb 1-3: Product:  SMI Grabber Dev

[ 2185.754569] usb 1-3: Manufacturer:  Somagic, Inc.  

[ 2185.754574] usb 1-3: SerialNumber: SMIVIDEO3E9876543210

[ 2185.758931] saa7115 6-004a: saa7113 found (8f7113000000000) @ 0x94 (smi2021)

[ 2185.791213] smi2021::smi2021_usb_probe: Driver version 0.1 successfully loaded

[ 2185.799018] smi2021 1-3:1.0: V4L2 device registered as video2

[ 2186.043786] smi2021::smi2021_pcm_open: PCM device open!

[ 2186.043812] smi2021::smi2021_pcm_close: PCM device closing

[ 2186.044459] smi2021::smi2021_pcm_open: PCM device open!

[ 2186.044480] smi2021::smi2021_pcm_close: PCM device closing

[ 2189.401073] smi2021::smi2021_alloc_isoc: urbs allocated

[ 2189.411505] print_usb_err: 34 callbacks suppressed

[ 2189.411509] URB packet 0, status -71 [Bit-stuff error (bad cable?)]

[ 2189.411510] URB packet 1, status -71 [Bit-stuff error (bad cable?)]

[ 2189.449071] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.401117] smi2021::smi2021_start_streaming: Streaming started!

[ 2189.460183] URB packet 4, status -71 [Bit-stuff error (bad cable?)]

[ 2189.480172] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.550018] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2189.551396] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2189.566100] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2189.572448] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2189.576190] URB packet 9, status -71 [Bit-stuff error (bad cable?)]

[ 2194.424157] print_usb_err: 262 callbacks suppressed

[ 2194.424162] URB packet 3, status -71 [Bit-stuff error (bad cable?)]

[ 2194.447993] URB packet 7, status -71 [Bit-stuff error (bad cable?)]

[ 2194.449158] URB packet 8, status -71 [Bit-stuff error (bad cable?)]

[ 2194.457838] URB packet 6, status -71 [Bit-stuff error (bad cable?)]

[ 2194.460315] URB packet 5, status -71 [Bit-stuff error (bad cable?)]

[ 2194.494001] URB packet 4, status -71 [Bit-stuff error (bad cable?)]

[ 2194.530084] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2194.532569] URB packet 2, status -71 [Bit-stuff error (bad cable?)]

[ 2194.533768] URB packet 0, status -71 [Bit-stuff error (bad cable?)]

[ 2194.542652] URB packet 8, status -71 [Bit-stuff error (bad cable?)]

$ mplayer tv:// -tv driver=v4l2:width=720:height=576:fps=25:outfmt=rgb24:device=/dev/video2

MPlayer dev-SVN-r35127-4.7-openSUSE Linux 12.3 (i586)-Packman (C) 2000-2012 MPlayer Team

Can't open joystick device /dev/input/js0: No such file or directory

Can't init input joystick

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 <olsch...@zpr.uni-koeln.de>

 comment: first try, more to come ;-)

Selected device: smi2021

 Capabilities:  video capture  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 = Composite; 1 = S-Video;

 Current input: 0

 Current format: UYVY

Selected input hasn't got a tuner!

v4l2: ioctl set mute failed: Invalid argument

Failed to open VDPAU backend libvdpau_r600.so: cannot open shared object file: No such file or directory

[vdpau] Error when calling vdp_device_create_x11: 1

==========================================================================

Opening video decoder: [raw] RAW Uncompressed Video

Movie-Aspect is undefined - no prescaling applied.

VO: [xv] 720x576 => 720x576 Packed UYVY 

Selected video codec: [rawuyvy] vfm: raw (RAW UYVY)

==========================================================================

Audio: no sound

Starting playback...

V:   0.0   1/  1 ??% ??% ??,?% 0 0 

Frame too small! (2288<829440) Wrong format?

V:   0.0   3/  3 ??% ??% ??,?% 0 0 

Frame too small! (407520<829440) Wrong format?

V:   0.0 384/384 ??% ??% ??,?% 0 0 

v4l2: ioctl set mute failed: Invalid argument

v4l2: 386 frames successfully processed, -1 frames dropped.

Exiting... (Quit)

$ uname -a

Linux hostname 3.7.10-1.1-desktop #1 SMP PREEMPT Thu Feb 28 15:06:29 UTC 2013 (82d3f21) i686 athlon i386 GNU/Linux


Am I missing something? Is there a way to fix this?

Thank you

[Bartek Zdanowski]

Tosiara,

do you think that it could work with Raspberry Pi aswell/

--

You received this message because you are subscribed to the Google Groups "easycap-somagic-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to easycap-somagic-...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Pozdrawiam,
Bartek Zdanowski

Nie odpisuję zbyt długo? Napisz/zadzwoń 603 525 105!

Blog http://bartekzdanowski.blogspot.com i twitter @bartekzdanowski
Confitura 2014 - już na początku lipca! - http://confitura.pl

[tosiara]

I don't have Rpi to test, but I'm very interested if someone can perform the test and post results here

To unsubscribe from this group and stop receiving emails from it, send an email to easycap-somagic-linux+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.