- Inbetween I found some hints on this page: http://bite-in.com/?p=9 for the usage of STK1160 based devices with the RPI.
- Here is one more story of success for the STK1160 based Easycap on the RPI (with the legacy easycapdriver).
Some hints for checking:
- Use a powered USB hub to conntect the STK1160 device to the RPI because Raspberry pi is not strong enough to power usb easycap directly.
- Try the -zoom option in your mplayer command.
The stk1160 driver in the kernel doesn't support (hardware-) framescaling.
from mplayers manpage:
Allow software scaling, where available. This will allow scaling with output drivers (like x11, fbdev) that do not support hardware scaling where MPlayer disables scaling by default for performance reasons.
mplayer tv:// -tv driver=v4l2:device=/dev/video0 -vf scale=400:300 -zoom
- You can try mplayer2 instead of mplayer.
Summing up all the comments below this post and some forum posts I've read about that issue, I can say that many USB video capture devices and webcams are not working at all (or only at a very low resolution) on the raspberry pi because of a rpi related USB issue.
These USB problems on the rpi are still pending and I couldn't find any report that the stk1160 device or any other Easycap device is working acceptably on the RPI.
Mainly USB webcams which are supported by the uvcvideo driver (many but not all) are working on the pi. List of pi verified USB webcams
More information about the rpi USB issue
In this thread on the raspberrypi.org forum (page 12 to 16)
In this thread on raspberrypi.stackexchange.com
success with a modified em28xx driver
more legacy information:
Easycap devices (stk1160, empia, somagic) currently are causing some problems with standard Linux disributions on the Raspberry Pi because of some RPI related USB issues.
However, enhancements are in progress.
The Easycap device registers properly like under any other Linux system (when the driver is in the kernel), but the video data transport through the RPIs USB system doesn't work.
I suppose this issue affects many other v4l2 devices plugged into the RPIs USB.
Ezequiel Garcia reported to me the following:
"The problem with the RPI is that it has a crappy USB driver and USB hardware.
When that is solved, stk1160 will work. Probably will take a long time
because synopsis USB datasheet is not public."
Note: The RPI branch on Ezequiels github https://github.com/ezequielgarcia/stk1160-standalone/tree/rpi is broken and doesn't work at all!