Page 2 of 3 FirstFirst 123 LastLast
Results 11 to 20 of 26

Thread: Kdenlive5 with TW

  1. #11

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by noee View Post
    Got it. Very nice, thx. The basics seem to be okay so far, though I have some source videos that are failing to import (worked fine before), so I'll try to track that down and report it if needed.
    Check that you have ffmpeg from Packman installed, i.e. the libav* packages, libavcodec56 in particular.
    I only have a crippled ffmpeg in my repo. It isn't published for Tumbleweed, but IIRC it was at the beginning for a short time.

    A zypper dup should install the one from Packman though, as I did remove the published packages (for Tumbleweed/Factory, I do keep them for 13.1/13.2 so that even people not using Packman can install my packages, with restricted codecs support).

    I see it's become a full-on KDE app now, just excellent news all the way around for KDEnlive users.
    Right, even though not too long ago everybody seemed to think kdenlive is dead...

    And I do have the stable 15.04 version now in my repo, as you probably noticed, and will follow the stable releases.

  2. #12
    Join Date
    Sep 2013
    Location
    Eastern US
    Posts
    78

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by wolfi323 View Post
    Check that you have ffmpeg from Packman installed, i.e. the libav* packages, libavcodec56 in particular.
    I only have a crippled ffmpeg in my repo. It isn't published for Tumbleweed, but IIRC it was at the beginning for a short time.
    Yeah, I run my own ffmpeg (10bit) and I just noticed that *all* of my sources are failing to import, so it must be the codec setup...This might require a little finesse.
    Quote Originally Posted by wolfi323
    And I do have the stable 15.04 version now in my repo, as you probably noticed, and will follow the stable releases.
    Yes, I did, very nice, indeed.

  3. #13

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by noee View Post
    Yeah, I run my own ffmpeg (10bit)
    Which version is that?
    I build against the latest (in Packman and Tumbleweed/Factory) 2.6.1.
    So my libmlt loads libavcodec.so.56, libavutil.so.54, and so on.

  4. #14
    Join Date
    Sep 2013
    Location
    Eastern US
    Posts
    78

    Default Re: Kdenlive5 with TW

    Source and binaries from here.

    I need 10bit. Actually, now that I think about it, perhaps we should request packman to build a 10bit version too?

  5. #15

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by noee View Post
    Source and binaries from here.
    That's a statically linked ffmpeg executable.

    But mlt/kdenlive does not run ffmpeg, it uses ffmpeg's libraries (e.g. libavcodec) to import/export files.
    If you don't have them from Packman, you probably use the crippled ones included in Tumbleweed now.

    There's no way to make mlt or kdenlive to use that static ffmpeg executable, for the clip import to kdenlive at least.

    I need 10bit. Actually, now that I think about it, perhaps we should request packman to build a 10bit version too?
    Would probably be the best idea.
    Would that be incompatible or cause problems with the current version? I have no idea what that 10bit implies...

    Or build ffmpeg (dynamically linked) yourself. You can use the openSUSE (it is included in the distribution since recently, crippled of course, but you only need to set a flag to build the full version) or Packman src.rpm and modify the build options accordingly.

  6. #16
    Join Date
    Sep 2013
    Location
    Eastern US
    Posts
    78

    Default Re: Kdenlive5 with TW

    Yes, I should've explained further...I'm using the Packman FFmpeg for import (I hope) and that static linked ver for render (you can set that in settings/config/options/ffmpeg in the MLT section).

    10bit refers to the encoder output (vs. 8bit which has been standard for years).

    Yes, that would be a good "starter" to learn to use OBS....

  7. #17

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by noee View Post
    Yes, I should've explained further...I'm using the Packman FFmpeg for import (I hope) and that static linked ver for render (you can set that in settings/config/options/ffmpeg in the MLT section).
    Well, I have never tried that, but at least the import should work then if your input files are supported by the system's ffmpeg libs.

    I haven't encountered any problems importing any video files I tried (even real video) here on 13.2 yet, with Packman's ffmpeg packages.

    So again, check that all libav* packages come from Packman, maybe run a "zypper dup --from Packman".

    10bit refers to the encoder output (vs. 8bit which has been standard for years).
    Ah, ok. So it refers to the color depth, ten "bit per color" (red, green, and blue).

    Still, the question is, is that a configurable run-time option, or does ffmpeg then use 10bits unconditionally?
    In the latter case it's probably no option to offer it on Packman...

    And is the output compatible to a non-10bit ffmpeg, i.e. can a "normal" ffmpeg read those files? I suppose yes, it sounds like you had that working before (with kdenlive/KDE4 I suppose), correct?

    Yes, that would be a good "starter" to learn to use OBS....
    Well, the problem is just that a fully blown ffmpeg is not allowed on OBS.
    You could build one in your home repo, but it might happen that you're asked to remove it again.

    Other than that, it shouldn't be too difficult. Just branch the one from multimedia:libs, openSUSE:Factory, or my repo, and add the corresponding switches to configure (I guess). What exact parameters you need for adding 10bit support I don't know though, and I don't find any that sound like that. Or is this added by a patch?

    In this particular case you'd also have to enable the build of the restricted codecs, by defining the macro BUILD_ORIG. You can either do that in the project config (ask for details if you need help), or by adding a "%define BUILD_ORIG 1" at the top of the spec file.

    PS: judging from the readme file of the tarball you linked to earlier, this 10-bit support seems to be specific to the AVC/H.264 encoder:
    Notes: ffmpeg-10bit is built with 10-bit AVC/H.264 encoding support.
    I remember that Packman enabled 10bit support for x264 some time ago, but there were problems so it got disabled again.
    I have to look that up...

  8. #18

    Default Re: Kdenlive5 with TW

    I just noticed that my libmlt actually failed to build for Factory/Tumbleweed. So the package in my repo actually has no support for ffmpeg at all, which of course explains why your import is not working...

    Sorry!
    I will fix it shortly...

    Btw, I had a look at frei0r-plugins, and Qt actually only gets pulled in via opencv. Building against my Qt5-based opencv should fix that too. I already created a patch for installing the actual plugins to a different directory...

  9. #19

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by wolfi323 View Post
    I just noticed that my libmlt actually failed to build for Factory/Tumbleweed. So the package in my repo actually has no support for ffmpeg at all, which of course explains why your import is not working...
    libmlt in my repo is now built with ffmpeg support for Factory/Tumbleweed too.
    So update your system and try again, it should work now for you.

    The problem was that OBS couldn't decide between libav and ffmpeg (both are part of the distribution now), so I had to explicitely tell which one I want.

    frei0r-plugins will still take a while, unfortunately my patch to install the plugins to a different directory is apparently not working. I have to investigate a bit more...
    So for now, my libmlt still conflicts with frei0r-plugins.

  10. #20

    Default Re: Kdenlive5 with TW

    Quote Originally Posted by wolfi323 View Post
    frei0r-plugins will still take a while, unfortunately my patch to install the plugins to a different directory is apparently not working. I have to investigate a bit more...
    So for now, my libmlt still conflicts with frei0r-plugins.
    My libmlt now only uses my new package frei0r-plugins-qt5 (built against Qt5) and ignores frei0r-plugins.
    So kdenlive5 does not crash when the latter is installed, and you can still use the frei0r-plugins.

    The problem was that I misunderstood how frei0r-plugins works. There is no library, the application (libmlt in this case) that wants to use the plugins loads them directly. So I had to patch libmlt to use the new plugin path (/usr/lib(64)/frei0r-plugins-qt5-1). (Actually I noticed now that patching it would not really have been necessary, you can specify the default path via an environment variable when building it. I probably will change that, but that has no effect on the resulting package anyway...)

    Btw, I changed all locations of the default path, so if you happened to have a custom plugin in e.g. $HOME/.frei0r-1/lib it will not be found any more (you have to move/copy it to $HOME/.frei0r-qt5-1/lib)

Page 2 of 3 FirstFirst 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •