Branch: refs/heads/opengl
Home: https://github.com/mltframework/mlt
Commit: 4048b438b5e8f449f3207926973e08f67969af4d
https://github.com/mltframework/mlt/commit/4048b438b5e8f449f3207926973e08f67969af4d
Author: Dan Dennedy
Date: 2012-12-26 (Wed, 26 Dec 2012)
Changed paths:
Branch: refs/heads/master
Home: https://github.com/mltframework/mlt
Commit: f5eaf76631b6ca68867d384b1df074dccb353c65
https://github.com/mltframework/mlt/commit/f5eaf76631b6ca68867d384b1df074dccb353c65
Author: Niv Sardi
Date: 2012-12-26 (Wed, 26 Dec 2012)
Changed paths:
Thanks a lot for providing the requested information.
It is working fine with pango.
On Wed, Dec 26, 2012 at 10:18 AM, Brian Matherly wrote:
> >It works based on number of characters in the text.
>
> >When I use geometry as 0/0:50%x100%:100, it does not place text at
> 0(zero'th) pixel if the
Hi,
As reported in Kdenlive issue 2841 (1), there is a problem with alsa devices
in the avformat producer.
I can reproduce the problem in shotcut, so the problem is probably in MLT but
I am not sure where.
The problem happens when you want to use another device than "default".
Let's say for e
On Tue, Dec 25, 2012 at 8:48 PM, Brian Matherly wrote:
>>It works based on number of characters in the text.
>
>>When I use geometry as 0/0:50%x100%:100, it does not place text at
>>0(zero'th) pixel if the
>>* text has less number of characters (say 4 characters)
>>* text alignment is ri
On Wed, Dec 26, 2012 at 6:01 AM, j-b-m wrote:
> Hi,
>
> As reported in Kdenlive issue 2841 (1), there is a problem with alsa devices
> in the avformat producer.
>
> I can reproduce the problem in shotcut, so the problem is probably in MLT but
> I am not sure where.
>
> The problem happens when you
