SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I've used Kino for ages to pull video from my DV camera. In Slackware64 13.1 Kino worked fine. However, since upgrading to a clean installation of Slackware64 13.37 (multilib), the preview videos are corrupted with green and pink vertical bands/stripes. DV capture still works ok and the resulting .dv file plays back just fine in mplayer, gnome-mplayer and xine. Exporting via ffmpeg seems to work ok. The corrupted preview (see attached) makes it a bit difficult to do the (very) simple editing before I create mpeg4 and mpeg2 files. I installed the same set of dependencies from Slackbuilds.org; the only difference is Slackware and Nvidia-270.41.19, so this is a bit of a conundrum. Opening video shows this:
Code:
>> Creating undo/redo buffer
> setting video preview size to 427x240
>> Starting Editor
>> Kino Common newFile
>>> Received playlist to store at position 0
>>>> Adding to end
>> Kino Common newFile
>>> Received playlist to store at position 0
>>>> Adding to end
>>> Received playlist to store at position 0
>>>> Adding to end
>> Leaving Editor
>> Left Editor
>> Starting Editor
>> Trying XVideo at 720x480
>>> XvQueryAdaptors count: 1
>>> Xv: NV17 Video Texture: ports 313 - 344
>>> formats supported: 4
>>> 0x32595559 (YUY2) packed
>>> 0x32315659 (YV12) planar
>>> 0x59565955 (UYVY) packed
>>> 0x30323449 (I420) planar
>>> 0: XV_IMAGE, 16384x16384 rate = 1/1
Any guidance is appreciated. I am exploring using cinelerra (crashes on opening any video), LiVES (wtf, interface design sucks), Kdenlive (dependency hell), and Openshot just noticed this one on SBo). I just need something simple - no bells and whistles.
Ok, I tried building kino on my current box, but was unsuccessful. Doing a bit of research on google, it appears that kino still uses v4l version 1, instead of version 2 (v4l2). Kernel developers have been notifying everyone that v4l(ver1) would be removed from the kernel tree starting on the .38 series. Sure enough, they did. So, first question, even though you are running 13.37, did you upgrade to the .38 kernel series? That would be my first guess. It would also explain why it works on kdenlive.
Nope, doesn't seem to work. Kino video preview is still corrupted. Everything else seem to work. I applied the patch (part of kino.slackbuild from SBo)
disturbed1, I tried ALL the video settings to no avail. I use Xfce 4.6.2. I get the same issue inside a virtualbox 4.0.4 vm in pure Slack64 (haven't tried Slack32 yet). What video driver are you using?
Did you build Kino with kino's ffmpeg (--enable-local-ffmpeg) or with system wide ffmpeg (--disable-local-ffmpeg). Which ever way Kino was built, I'd try the opposite .
I'd also double check that xv video out is working (mplayer -vo xv some.video), and NTSC/PAL options are set accordingly.
Thanks, disturbed1. Nothing like "talking" it out. "mplayer -vo xv some.video" works fine, as do other players, and routing it through ffmpeg. The configure option did the trick. Normally, "--disable-local-ffmpeg" is preferred, but now "--enable-local-ffmpeg" is required.
I had upgraded to ffmepg-0.7-rc1 and then to a recent git snapshot for vdpau and so forth features and bug fixes. It seems the old kino-1.3.4 can't handle anything newer than ffmpeg-0.6. To fix the video corruption issue:
downgrade the system wide ffmpeg
use "--enable-local-ffmpeg" for the internal kino-provided ffmpeg version
The drawback of (2) is that export/transcode options are limited. Fortunately, the kino-ffmpeg does does not interfere with the newer system-wide ffmpeg. Unfortunately, I now have to learn a few new tricks via the CLI or another video editing software. Sigh.
Last edited by kingbeowulf; 06-14-2011 at 10:37 PM.
Reason: stupid typo
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.