Hi,

I just installed Kdenlive on my macbook, running OS x 10.10.2. I am facing few issues while adding a title clip.

1. On the title window, 'Ok' button is always disabled. Only 'Cancel' is enabled. So I can't add a title clip.
2. When I click on colour section, the colour selection screen doesn't appear.

Has anyone else faced these issues?

I'd appreciate your help.

Thanks

The user base for the mac ports version is not very large. I don't think the kdenlive developers really support the MacOS version as such. I don't like your chances of anyone knowing the solution to this here. I could be wrong.

You might have better luck on this forum http://mac-os-forge.2317878.n4.nabble.c ... ts-f3.html - maybe.

Hello,
It appears other users recently faced Title Clip problems on Linux too.
Which MLT version do you run (0.9.2 release or 0.9.3+ development snapshots)?
Is MLT built with QImage and title modules?

Thanks for the response.

MLT is 0.9.2.

How can I find out if MLT is built with QImage and title modules?

I ran these commands that I found on the forum. There are no such files in my local or lib directory.
ls -la /usr/local/lib/libmlt*
ls -la /usr/lib/libmlt*

I just installed Kdenlive on my Mac OS X 10.10.1 also and have the exact same problem as @saligo365. The mlt version I get from MacPort is 0.9.2 with kdenlive at 0.9.10.

The "Config Wizard" in Kdenlive (Settings > Run Config Wizard) confirms that DV, QImage and Title modules are missing from the MLT engine. How do I go about installing these three missing modules?

Any help is appreciated. Thanks.

So the problem is in MacPort packaging, its build script may have missed a Qt dependency or a MLT module name change. Do you have a contact for who is maintaining this port, where to report bug? Else I can ask on the list...

This might be the place to raise this
https://trac.macports.org/browser/trunk ... e/Portfile

hi vpinon, did you get anywhere with this?

i try to installed the old version of mlt to salve this problom. it works. mlt @0.9.0_0

FYI, here is the MacPorts bug ticket for tracking this. It has been fixed now.
https://trac.macports.org/ticket/46798