3 Apr
2012
3 Apr
'12
2:49 a.m.
I can't find any apps that depend upon mlt. Is mlt something we want to maintain?
Darrell
3 Apr
3 Apr
7:43 p.m.
New subject: [trinity-devel] Why do we support mlt?
On 04/02/2012 09:49 PM, Darrell Anderson wrote:
I can't find any apps that depend upon mlt. Is mlt
something we want to maintain?
Darrell
mlt++ :)
MLT = Media Lovin' Toolkit
Seriously - I don't know. I just built the thing because it was part of the
GIT tree that should either be working, or fixed or nuked. A rendering engine
is a good thing as long as something uses it. IMHO, cinelerra is the only
non-liner editor to use (kino is great for rough cuts).
Since it builds, I don't see any reason to nuke it. The project is still
active:
http://www.mltframework.org/twiki/bin/view/MLT/
and seems to be fairly rich in features:
http://www.mltframework.org/twiki/bin/view/MLT/Features
The big concern would be how current is the stuff in the GIT tre. According
to the GIT tree it is version 0.2.5 WHICH WAS RELEASED IN 2007!!!
THERE HAVE BEEN --> 24 <-- RELEASES SINCE THAT TIME. If this is accurate -
the we need to either update the source to version 0.7.8, See:
http://sourceforge.net/projects/mlt/files/mlt/
Direct download:
http://downloads.sourceforge.net/project/mlt/mlt/mlt-0.7.8.tar.gz
I just built mlt 0.7.8 on tqt3 from git and it worked fine. The code should
be uploaded to git.
TDE == NO OLD CODE!!
--
David C. Rankin, J.D.,P.E.
7:45 p.m.
New subject: [trinity-devel] Why do we support mlt?
On 04/03/2012 02:43 PM, David C. Rankin wrote:
On 04/02/2012 09:49 PM, Darrell Anderson wrote:
The new mlt package is also a split package on arch:
mlt-0.7.8-1-i686.pkg.tar.xz
mlt-python-bindings-0.7.8-1-i686.pkg.tar.xz
I say update the code in GIT to current 0.7.8.
--
David C. Rankin, J.D.,P.E.
I can't find any apps that depend upon mlt.
Is mlt something we want to
maintain?
Darrell
mlt++ :)
MLT = Media Lovin' Toolkit
Seriously - I don't know. I just built the thing because it was part of the
GIT tree that should either be working, or fixed or nuked. A rendering engine
is a good thing as long as something uses it. IMHO, cinelerra is the only
non-liner editor to use (kino is great for rough cuts).
Since it builds, I don't see any reason to nuke it. The project is still active:
http://www.mltframework.org/twiki/bin/view/MLT/
and seems to be fairly rich in features:
http://www.mltframework.org/twiki/bin/view/MLT/Features
The big concern would be how current is the stuff in the GIT tre. According to
the GIT tree it is version 0.2.5 WHICH WAS RELEASED IN 2007!!!
THERE HAVE BEEN --> 24 <-- RELEASES SINCE THAT TIME. If this is accurate - the
we need to either update the source to version 0.7.8, See:
http://sourceforge.net/projects/mlt/files/mlt/
Direct download:
http://downloads.sourceforge.net/project/mlt/mlt/mlt-0.7.8.tar.gz
I just built mlt 0.7.8 on tqt3 from git and it worked fine. The code should be
uploaded to git.
TDE == NO OLD CODE!!
8 p.m.
New subject: [trinity-devel] Why do we support mlt?
> I
can't find any apps that depend upon mlt. Is mlt
something we want to
maintain?
Darrell
mlt++ :)
MLT = Media Lovin' Toolkit
Seriously - I don't know. I just built the thing GIT tree that should either be working, or fixed
or
nuked. A rendering engine
is a good thing as long as something uses it.
IMHO,
cinelerra is the only
non-liner editor to use (kino is great for rough
cuts).
Since it builds, I don't see any reason to nuke it. The
project is still
active:
http://www.mltframework.org/twiki/bin/view/MLT/
and seems to be fairly rich in features:
http://www.mltframework.org/twiki/bin/view/MLT/Features
The big concern would be how current is the stuff in
the GIT tre. According to
the GIT tree it is version 0.2.5 WHICH WAS
RELEASED IN
2007!!!
THERE HAVE BEEN --> 24 <-- RELEASES SINCE THAT
TIME. If this is accurate -
the
we need to either update the source to version
0.7.8,
See:
http://sourceforge.net/projects/mlt/files/mlt/
Direct download:
http://downloads.sourceforge.net/project/mlt/mlt/mlt-0.7.8.tar.gz
I just built mlt 0.7.8 on tqt3 from git and it worked
fine. The code should be
uploaded to git.
TDE == NO OLD CODE!!
The new mlt package is also a split package on arch:
mlt-0.7.8-1-i686.pkg.tar.xz
mlt-python-bindings-0.7.8-1-i686.pkg.tar.xz
I say update the code in GIT to current 0.7.8.
8:29 p.m.
New subject: [trinity-devel] Why do we support mlt?
On 04/03/2012 03:00 PM, Darrell Anderson wrote:
I could not build mlt 0.2.5 against TQt3 without
patching. I noticed the old version several days ago.
The challenge is this package is a continually moving target. We don't offer anything
that directly depends upon mlt/mlt++. Seems to me that anybody building other packages
needing mlt will do so through their distro and are likely to build those packages against
Qt4 or GTK.
Are you sure you built the latest mlt against TQt3 without errors? The qimage module
needs patching because qimage does not know about TQt3, only Qt3.
Darrell
Yes, I'm sure. The only qt installed in the chroot is tqt3. Here was my build
script:
makedepends=('sdl_image' 'libsamplerate' 'libdv' 'qt3'
'sox' 'libxml2' 'gtk2'
'ffmpeg' 'frei0r-plugins' 'swig' 'python2'
"jack" "ladspa")
The only depends pulled in were:
Targets (5): gavl-1.2.0-2 libdc1394-2.1.3-2 opencv-2.3.1_a-4
frei0r-plugins-1.3-3 swig-2.0.4-3
There isn't even a /usr/include/qt in the chroot...
--
David C. Rankin, J.D.,P.E.
9:33 p.m.
New subject: [trinity-devel] Why do we support mlt?
Yes, I'm sure. The only qt installed in the chroot
is tqt3.
Here was my build script:
makedepends=('sdl_image' 'libsamplerate' 'libdv' 'qt3'
'sox'
'libxml2' 'gtk2' 'ffmpeg' 'frei0r-plugins' 'swig'
'python2'
"jack" "ladspa")
The only depends pulled in were:
Targets (5): gavl-1.2.0-2 libdc1394-2.1.3-2
opencv-2.3.1_a-4 frei0r-plugins-1.3-3 swig-2.0.4-3
There isn't even a /usr/include/qt in the chroot...
Perhaps the later versions have more intelligence built into the configure process.
I still don't see why we support this package when the same is available upstream from
the distro. We don't provide anything that depends upon mlt/mlt++.
Darrell
9:41 p.m.
New subject: [trinity-devel] Why do we support mlt?
Yes, I'm
sure. The only qt installed in the chroot is tqt3.
Here was my build script:
makedepends=('sdl_image' 'libsamplerate' 'libdv' 'qt3'
'sox'
'libxml2' 'gtk2' 'ffmpeg' 'frei0r-plugins' 'swig'
'python2'
"jack" "ladspa")
The only depends pulled in were:
Targets (5): gavl-1.2.0-2 libdc1394-2.1.3-2
opencv-2.3.1_a-4 frei0r-plugins-1.3-3 swig-2.0.4-3
There isn't even a /usr/include/qt in the chroot...
Perhaps the later versions have more intelligence built into the configure
process.
I still don't see why we support this package when the same is available
upstream from the distro. We don't provide anything that depends upon
mlt/mlt++.
Darrell
4 Apr
4 Apr
3:58 a.m.
New subject: [trinity-devel] Why do we support mlt?
On 04/03/2012 04:41 PM, Timothy Pearson wrote:
As I mentioned before there were plans at one point to include kdenlive.
mlt was imported at that point due to the fact that Ubuntu dropped
official builds of it.
If the upstream mlt project uses GIT and builds as-is under tqt3, I would
suggest importing the latest upstream release as a GIT submodule to
replace the badly outdated code currently in our GIT tree.
Tim
It does, the GIT information is here:
MLT now uses the Git distributed version control system instead of the
Subversion service provided by SourceForge.
You can get the latest version of the MLT framework source code (including mlt++
and other language bindings) using:
git clone git://mltframework.org/mlt.git or git clone
http://mltframework.org/mlt.git
See: http://www.mltframework.org/twiki/bin/view/MLT/Contributing
--
David C. Rankin, J.D.,P.E.
4665
days inactive
4666
days old
7 comments
3 participants
participants (3)
-
Darrell Anderson -
David C. Rankin -
Timothy Pearson