Dan Weatherill wrote:
looks like you don't have g++ installed. I'm a suse user and on my
system the necessary package is called gcc-c++, on ubuntu I think it's
just g++
For your configuration pleasure:
http://lab.dyne.org/cinelerra/Gutsy
___
Cineler
Craig Lawson wrote:
Try:
Format = MS-AVI or Quicktime for Linux
Audio = Twos complement, 16 bit linear
Video = MPEG-4, quantization = 5, fixed quantization
Thanks Craig. I used to use render to Quicktime for Linux, but recent
use has produced videos where the colours are mixed up :(
I almost never look at comp.lang.python, but a quick scan revealed this:
I've put up an initial pre-alpha release of DVEdit - a highly pythonic
free/opensource framework for scripted video editing and production.
http://www.freenet.org.nz/dvedit
It's in very early stages, mainly pr
Cehteh, you asked me to do:
git push git://git.pipapo.org/cinelerra3/mob master:heads/refs/mcarter
But it didn't work :(
I can push from my clone of the mob repo back to your copy of the mob repo, but
I cannot push my clone of your ct branch to your copy of the mob repo. This
makes sense, be
I made a small doc change to cine 3. I was trying to push it to mob, but
no joy :(
If memory serves, I first did:
cloned git://git.pipapo.org/cinelerra3/ct
git checkout -b mcarter
Hack hack hack
git commit README
git push git://git.pipapo.org/cinelerra3/ct mcarter:mob
But I get:
fatal: The remot
Christian Thaeter wrote:
This will be done better in cin3, using extern libs if possible, try to
avoid to patch common libs,
I'm wondering to what extent you think extern libs might help (hopefully
the answer is "a lot"). I'm presuming that Cinelerra grew up in a world
where there was a paucity
Johannes Sixt wrote:
My favorite workflow actually is that we abandon svn altogether. But I don't
know how our packagers can deal with such a situation.
The main advantage I see to Git is that anyone can clone a repo and get
their own personal checkin. I can't find the article, but some people
Christian Thaeter wrote:
Well you likely can't imagine how much kernel patches and repositories
are all around and will never be merged :) .. same with git itself, when
you look at the Mailinglist you see a lot of proprosals which are
abadoned, thats the way free software works when it is under
Christian Thaeter wrote:
mark carter wrote:
For cinelerra things are little different:
If you mean HV by upstream,
Primarily I meant CV - I was assuming (very dodgy assumption, I know)
that HV and CV perform a cross-merge, on the basis that it's all good stuff.
thats sadly tru
Christian Thaeter wrote:
some personal opinions...
A list of things which I would make me happy:
* More people contributing to the project.
* Help coding already planned and important things
* Send patches (git mob?) which fix existing issues.
Looking at Cinelerra, I'm amazed at how Lin
Johannes Sixt wrote:
Are these available from a git repo, eg. from CT's mob repo?
(http://www.pipapo.org/gitweb/cinelerra/mob)
Also, please don't publish a patch series that contains fixup patches, like
the last one where you say that you decide to reshuffle the .gitignore
entries to sub-dire
/Makefile.am
@@ -0,0 +1,21 @@
+# A good source for reference on how I (mark carter) cobbled this
+# file together is to look at
+# http://sources.redhat.com/automake/automake.html#Texinfo
+
+# On Gutsy, I would expect info files to be installed in
+# /usr/share/info
+
+
+
+info_TEXINFOS
I attach some patches which should improve the lot of people using git
repos. I've basically added some things to .gitignore files so that you
don't get useless alarms all the time.
>From 432539d20679c1f06e2e626b5d48fc87991c8150 Mon Sep 17 00:00:00 2001
From: Mark Carter <[EMAIL
My bad. I forgot to actually mention the wretched location for the patch.
You can get it from here:
http://www.luncarty.me.uk/cinelerra.htm
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cineler
Hey guys, I tried attaching a patch for Ficl earlier on, but it was too
big for the moderator's liking. It's a 337k patch which uncompresses to
about 2.2M. The patch is big because it has a lot of code in it -
basically Ficl with some mods by me.
I've created a patch for Cinelerra which you ca
A recent message noted problems with the build process on Gutsy.
Take a look at:
http://lab.dyne.org/cinelerra/Gutsy
Hopefully it will resolve all your issues.
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinu
I excitedly installed Gutsy on my computer this morning. One of the
first things I did was attempt a build of Cinelerra. It's getting
easier!
I created a wiki entry here:
http://lab.dyne.org/cinelerra/Gutsy
I hope that people will be pleasantly surprised at the ease.
From: Bradley A. Hare <[EMAIL PROTECTED]>
>Working minimal functionality that can be maintained. I might be
> wrong, others
> seem to have been more successful at this than I have,
I just want to use Cinelerra for more casual amateur use, rather than
professional.
I've found Cinelerra rather
I notice that Cinelerra has a directory for libmpeg3. It is giving me
compilation problems - and Googling around, I don't seem to be the only one. So
my question is: what's it doing there, can't we just get rid of it and use the
latest version from our repos?
__
I think youz guys are getting a bit bogged down in the argument. My point about
the switching wasn't about them being time-critical (the check_sig() functions
are going to be taking up most of the time anyway), but that the code was a bit
of a mess and a more elegant solution was available, and
> I would worry about the architecture of the thing first. Right
> now the code extremely tangled with many opportunities for
> non-deterministic behavior. I assume that's why everyone is arguing
> about a re-write. My own opinion is that a re-design is
> needed first.
HV is undoubtedly a
From: Martin Ellison <[EMAIL PROTECTED]>
> Hopefully, you just need FICL running in its own thread.
You guys really like your threads, n'est pas? I have a feeling that they'll be
too hard for me to understand, though. I like to approach things from the angle
of simplicity and debuggability. I
Nah ;)
Suppose you wanted to define an "interface" - I think C++ calls them pure
virtual classes.
Well, in that case, work out what functions are required, then create a table
of vectors. In file.C, for example, if it doesn't know the file format, it does
a whole lot of specialised check_sig(
Not to mention the fact that threads scare me bigtime. From what I've heard,
I'm right to be scared.
A separate window is a logical idea, with an "eval on enter" handler. Don't
forget, though, that you can't guarantee how long a word takes to execute. It
could load other files, and conceivably
ICL (Forth Inspired Command Language) is a way to script your
Cinelerra programs. It was introduced in August 2007 by Mark Carter -
and as at that date, very little support for the internals of
Cinelerra is available. It does, however, incorporate a full Forth
programming language lightly adapted from th
don't say /etc, that's far far too
straightforward ;) ).
- Original Message
From: Stefan de Konink <[EMAIL PROTECTED]>
To: cinelerra@skolelinux.no
Sent: Friday, 24 August, 2007 1:25:24 PM
Subject: Re: [CinCVS] Some of my thoughts on scripting
On Fri, 24 Aug 2007, Mark Car
;[EMAIL PROTECTED]>
To: cinelerra@skolelinux.no
Sent: Friday, 24 August, 2007 9:37:05 AM
Subject: Re: [CinCVS] Some of my thoughts on scripting
On Fri, 2007-08-24 at 08:15 +, Mark Carter wrote:
> Nah ;)
>
> C++ couples functions and data, C decouples them. And decoupling
> rocks
Nah ;)
C++ couples functions and data, C decouples them. And decoupling rocks. At
least that's what the adverts say.
Also - and I've seen this before on a different project - if you're doing
something like handling different classes of say, file readers, in C++ you have
to resort to a lot of s
Well, I've been thinking about my scripting idea further. I've decided to
experiment with ECL, too - Embedded Common Lisp. What's the big idea? Well, ECL
provides a FFI. So, I could interface ECL with Cinelerra. But it goes further
than that in 2 ways:
* the FFI that you use with ECL could be co
Sorry to bother you cehteh, but I've changed my public RSA key, so now I can't
log into your server. I don't have a record of your email address, so if you
could send it, I can email it to you.
Sorry for any inconvenience caused.
arated.
Nice stuff. I imagine this 'libcinelerra' will be of great help if
someone were to experiment with new GUI concepts at some point in
the future. I haven't been following the discussion on IRC, but in
my opinion this seems also like a prime example for the new
scripting
Hi there cehteh. I had downloaded your ct branch a couple of weeks ago.
I thought I'd give it another investigation. When I try to do a make
from the top level dir, I get
ar cru libcinelerradata.a ./cinelerra/data/theme.o
ar: ./cinelerra/data/theme.o: No such file or directory
:(
On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote:
>
> Could you explain this more? svn allows branching, so why not just
> create as many development branches as required and work there?
git allows a project to be forked easily, whereas svn is geared towards
central command. svn requires
On Thu, 2007-08-16 at 16:37 +0800, Martin Ellison wrote:
>
> Could you explain this more? svn allows branching, so why not just
> create as many development branches as required and work there?
>
> I do not know git, so could you please explain what git has over svn?
> (Not intended as an attack
On Wed, 2007-08-15 at 19:36 +0200, Christian Thaeter wrote:
> 2) Stop using SVN
I just saw a YouTube vid by Linus who is talking about git:
http://uk.youtube.com/watch?v=4XpnKHJAok8
> Even if commit access is generously handled to people who ask, it's
> still a big blocker as I explained earlier
From: Christian Thaeter [EMAIL PROTECTED]
> The SVN was declared to be following HV and staying mergeable, hence I
> started my 'ct' branch where developers can work without this brakeshoe.
If I understand correctly:
* Cinelerra-CV is the ct branch, and the ct branch is considered "stable"
* Ubu
I think this is a good idea, and one that I intend to have a go on. No
promises, of course. After playing for a little while, I realised that it was
going to be trickier than I first thought. Looking at flip - the simplest
plugin - one sees that one has to worry about threads, and whether one is
One of my fears about cinelerra is that there are a lot of git code branches
out there, each doing its own thang, and I wonder how much good effort will
ultimately be effectively wasted. Looking at
http://www.pipapo.org/pipawiki/Cinelerra/GitBranches
is enough to make most people's head swim at w
> i am a bit pissed about any system and written
> http://www.pipapo.org/pipawiki/BuildingSoftware ,
Your comment made me think of Lisp, and how it already has a packaging system.
I'm no Lisper, though. Whenever I've tried to use it, I generally think, "oh
hell, why don't I just do it in Python
l /could/ bring Cinelerra down.
- Original Message
From: David McNab <[EMAIL PROTECTED]>
To: cinelerra@skolelinux.no
Sent: Monday, 13 August, 2007 10:22:15 PM
Subject: Re: [CinCVS] What I've been up to
On Mon, 2007-08-13 at 21:41 +0100, mark carter wrote:
> Feel free to drool
Just thought I'd tell you guys what I've been working on, to get you
interested.
Well, I've commited some "less than perfect code" to my git repository,
which I've cleaned up as I went along. It should be compilable at each
commit, though. So, if you see some stuff and thought "that's a load of
cr
On Mon, 2007-08-13 at 14:17 +0200, Christian Thaeter wrote:
> * Things will be on google for eternity, one has to fear that things he
> saied could be misinterpreted out of context.
And nobody wants to end up like this guy (humorous link):
http://www.ibiblio.org/Dave/Dr-Fun/df9601/df960124.jpg
On Sun, 2007-08-12 at 08:12 +1200, David McNab wrote:
> What I would strongly suggest is that as you flesh this out, split your
> interface into 2 layers:
>
> 1. lower-level C API, abstract, simple, completely free of any
> forth-isms
>
> 2. FICL layer - primitives as thin as possible,
On Sun, 2007-08-12 at 00:32 +0200, Jonas Wulff wrote:
> The problem now is that unfourtunately we don't have the webspace
> available to host the movie itself
Maybe you could consider using bittorrent.
___
Cinelerra mailing list
Cinelerra@skolelinux.
On Sun, 2007-08-12 at 08:12 +1200, David McNab wrote:
> On Sat, 2007-08-11 at 15:15 +0100, mark carter wrote:
> > Exciting stuff (for me anyway), but I've managed to get a scripting
> > interface going in Cinelerra. It could open up a world of possibilities
> > fo
On Sat, 2007-08-11 at 17:30 +0200, Stefan de Konink wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> mark carter schreef:
> > Well, it's a start, n'est pas?
> >
> > Interesting??
>
> Sure :)
Glad to hear it. Well, I'll tid
Exciting stuff (for me anyway), but I've managed to get a scripting
interface going in Cinelerra. It could open up a world of possibilities
for user scripting, building compound effects, whatever.
What I've got working so far is a menu item that brings you to the
script editor. You can then type s
On Fri, 2007-08-10 at 23:32 +0800, Graham Evans wrote:
> There
> are many defective codec implementations which make the job harder...
A user reported a bug in loading an MPEG-4 file. As I test, I find that
ffmpeg didn't like the file at all, and I couldn't get good results with
mencoder.
I'
On Fri, 2007-08-10 at 12:57 +0200, Herman Robak wrote:
> On Fri, 10 Aug 2007 11:53:28 +0200, Gordon JC Pearce <[EMAIL PROTECTED]>
> wrote:
>
> > On Fri, 2007-08-10 at 10:31 +0100, mark carter wrote:
> >
> >> Cinelerra is hard to grasp intuitively first off
On Fri, 2007-08-10 at 12:33 +0200, Herman Robak wrote:
> On Fri, 10 Aug 2007 11:31:12 +0200, mark carter <[EMAIL PROTECTED]>
> wrote:
> >
> > A thought: when you load a file in with iMovie, it actually "imports" it
> > - converting it into its own format
On Fri, 2007-08-10 at 17:10 +1200, David McNab wrote:
> On Thu, 2007-08-09 at 12:03 +0200, Herman Robak wrote:
> > On Thu, 09 Aug 2007 09:02:06 +0200, Raffaella Traniello
> > <[EMAIL PROTECTED]> wrote:
> >
> > >> From the Manual:
> > > "Cinelerra is not intended for consumers. [...]
> >
> > I
On Wed, 2007-08-08 at 21:59 +0200, Christian Thaeter wrote:
> I didn't meant that this way, for myself I am rather pro C (or using a
> real high level language). I'd rather meant fixes should be done in
> proper C++ way when the whole sourcefile is C++, for consistency and
> robustness. I really a
On Wed, 2007-08-08 at 11:27 +0800, Martin Ellison wrote:
> It would be nice to have a common plugin interface that could work
> across Cinelerra, Blender, Kino etc etc,
Don't forget Avidemux ;) I've used that on a number of occasions, and it
seems a nice bit of software.
> so that the work of w
On Tue, 2007-08-07 at 20:02 -0500, Daniel Jircik wrote:
> I've been using cinelerra in a production environment for a few years
> now and really the only instability issues I've had were when doing
> something blatantly wrong or mis configured.
Is there a format that the pros use that has good sup
I'd like to do some development work on Cinelerra. But I'd kind of like
to know that my work wont just lie around unpatched if I do it. So
cehteh's comments are particularly apropos here.
What I propose to start off with are the check_sig() functions in each
file loader. Nice and easy to begin wit
On Tue, 2007-08-07 at 18:26 +0200, Jonas Wulff wrote:
> Unfourtunately every major change of the codebase makes it harder to
> re-merge with the 'official' cinelerra version. That of course leads to
> the questions how important that *really* is, considering that cinCV
> seems to be the version mo
On Tue, 2007-08-07 at 11:35 +1200, David McNab wrote:
> Thoughts?
Well, I've been thinking about the whole business of file loading.
Although I'm completely new to Cinelerra and its development, I've had a
scratch around the file loading.
My basic thinking is that I think a lot of things are "t
On Tue, 2007-08-07 at 11:15 +1200, David McNab wrote:
> On the positive side, the developer's use of FLTK for the GUI is wise,
> he has a very fast responsive interface. Also, having everything on one
> window is nice. His window layout is very good.
I have yet to test it out, but from what I've
On Mon, 2007-08-06 at 17:29 -0400, Claude Jones wrote:
> On Monday August 6 2007 4:19:54 pm mark carter wrote:
> > In my travels I came across Open Movie Editor. There's a demo
> I'm curious - did you try this software before posting the above?
> I am asking because I
In my travels I came across Open Movie Editor. There's a demo of it over
on YouTube:
http://www.youtube.com/watch?v=9ljEb1PdEdM
The main website is:
http://openmovieeditor.sourceforge.net/HomePage
A cinelerra beater, perhaps??
___
Cinelerra mailing lis
I see that cinelerra/ffmpeg.C exists - but it does not appear to be
linked in file.C as a detectable format. This seems a pity, because I
understand it that ffmpeg can support a wide range of files and codecs.
Wouldn't class FFMPEG "solve" a lot of our file loading problems?
Comments?
__
I've been trying to puzzle this out - and it seems easier to ask. What
is a VFrame?
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
On Mon, 2007-08-06 at 11:34 +0100, mark carter wrote:
> I'm just throwing my thoughts
> out there.
I've been thinking about this. I might try to to a bit of
re-architecting. My problem is I know diddly-squat about threads,
processes, and IPC. And I'm thinking that might be a
The last couple of days I have been pondering bug 408:
Cine crashes when loading mp4 files. it doesn't with the same file in
avi.
The bug is reproducible, I just can't find out what's causing it. I'm
thinking that threads are complicating the whole issue, and I'm thinking
about ripping out some of
Am I doing something wrong? I do
% git-checkout origin
% get-fetch
Cannot get the repository state from git://git.pipapo.org/cinelerra/mob
___
Cinelerra mailing list
Cinelerra@skolelinux.no
https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerr
On Sun, 2007-07-22 at 20:07 -0400, Douglas Pollard wrote:
> When I try to enter as a permanent change I get permission denied. I
> used sudo and I am working as root I am using the single quotes is that
> correct?
No. don't use the single quotes. The filename is
/etc/sysctl.cong
> For a perman
I've been trying to get cinelerra 3 compiling, so far without success. It's
going wrong at:
gcc -DHAVE_CONFIG_H -I. -I../../../..
-I../../../../../pipapo.org/quicktime/ffmpeg/libavcodec/i386
-D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -DHAVE_MMX
-DUSE_MMX -DX86_CPU -DHAVE
I think this is bug 343:
http://bugs.cinelerra.org/show_bug.cgi?id=343
I'm a n00b to cinelerra and its development, and I had hoped to take a crack at
the bug. So far, I have been unable to compile cinelerra (3) with sufficient
debugging information to determine the problem. I had managed to cre
68 matches
Mail list logo
