I do alot of video processing in kdenlive, and am getting ready to instal #! on the desktop.
I'm curious about other peoples experience with kdenlive on #!, or just any video editing in general.
I know that K apps can sometimes be buggy in GTK...
and there goes Windoze.
Not necessarily buggy but huge with a ton of KDE libraries. But should run without problems.
Though for us minimalists I would consider something else.
Just as an example what is on offer:
I've used it on #! and it's worked pretty well. First, you might just want to make sure that suggested packages aren't considered dependencies in your package manager so you don't pull in the entire KDE desktop- but you might have to track down other packages though that's still better than pulling in the desktop. Also make sure you install the frei0r-plugins package since if I recall right it's not actually listed as a dependency so won't get pulled in.
I still do most editing in Windows and transcodes or up/downconverts in Linux, but I've done a bit of lightweight editing in Openshot and LiVES. LiVES converts everything to an image sequence on import (which could be good or bad depending on what you want) but I've found it helpful for recovering damaged or otherwise difficult video by copying out the cache folder in the LiVES temp directory while it's running to import the image sequence into whichever editor I'm using (usually Vegas).
I don't do actual editing with Kino, but I like it better than Kdenlive for DV captures.
My Statler box is totally down right now so I don't have it available for reference (and I don't know which version of #! you're running), but in general if you haven't worked with the Debian Multimedia repository yet you'll want to get familiar with that (there should be a good info on that in the forums via search). If you use the Multimedia repository I'd suggest using just that for both editing applications and media players to keep it clean. And once you've got everything set up to your liking I'd recommend locking versions since there might be conflicts between the main Debian repository and Multimedia with regards to both applications and codecs which could cause a problem at an update.
Hope that helps!
(Edit- the Debian Multimedia repository has moved, see vrkalak's post here on how to enable it)
Last edited by chillicampari (2012-05-15 02:03:41)
Apart from one problem with VLC that I had once, the Multimedia repo works perfectly. I would not lock it, especially if you want fixes and updates that chimes into that repo for the apps you install from there.
Normally they are made to run fine under Stable.
Though, I have the experience that it is better to add first the Multimedia repo and then install things like VLC etc.
It's really dependent on what you need to use it for. I don't like one update making multiple applications wonky so I'll lock and freeze versions when I'm happy with the video apps (though at the time I originally started using #! for some video work Statler was still Testing where updates were still rolling in, which is why I was wondering which version the OP is using).
Edit- I should clarify, specific versions of specific things (not the entire system) so you don't roll up on something like libavcodec(*) on an update without checking first to see if anyone is having problems before taking it. Then, if it looks good to go, unlock and go for it. But as a default state and if it's Testing, I like playing it safe. Like you mentioned, Stable really shouldn't have those issues at this point.
Last edited by chillicampari (2012-05-15 02:51:09)