From cinelerra-admin@skolelinux.no Fri May 9 10:32:19 2008 Return-Path: X-Original-To: cinelerra@e.kevb.net Delivered-To: cinelerra@e.kevb.net Received: from init.linpro.no (init.linpro.no [87.238.46.2]) by e.kevb.net (Postfix) with ESMTP id DB3A01040363 for ; Fri, 9 May 2008 10:32:17 -0400 (EDT) Received: from localhost ([127.0.0.1] helo=init.linpro.no) by init.linpro.no with esmtp (Exim 4.50 #1 (Debian)) id 1JuTai-0001dx-0q; Fri, 09 May 2008 16:29:19 +0200 Received: from [193.69.32.11] (helo=virusvask.itsjefen.no) by init.linpro.no with esmtp (Exim 4.50 #1 (Debian)) id 1JuTXy-0001OJ-0f for ; Fri, 09 May 2008 16:26:21 +0200 Received: from [193.69.32.11] by 80.232.38.252 (e-nough); Fri, 9 May 15:11:44 2008 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by virusvask.itsjefen.no (Postfix) with ESMTP id EBAB88AC04C for ; Fri, 9 May 2008 16:25:52 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at virusvask01.itsjefen.no Received: from virusvask.itsjefen.no ([127.0.0.1]) by localhost (virusvask01.itsjefen.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3dq82JE8xMiG for ; Fri, 9 May 2008 16:25:49 +0200 (CEST) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.187]) by virusvask.itsjefen.no (Postfix) with ESMTP id 2C2E48AC046 for ; Fri, 9 May 2008 16:25:49 +0200 (CEST) Received: from [192.168.8.23] (p5B0C2A17.dip0.t-ipconnect.de [91.12.42.23]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1JuTXg08pq-00014K; Fri, 09 May 2008 16:25:48 +0200 Message-ID: <48245EE3.6080007@ichthyostega.de> From: Ichthyostega User-Agent: IceDove 1.5.0.14pre (X11/20071018) MIME-Version: 1.0 To: cinelerra@skolelinux.no Subject: Re: [CinCV] I hope Lumiera turns into nodes :) References: <20080505222810.9542.59594.Mailman@init.linpro.no> In-Reply-To: X-Enigmail-Version: 0.94.2.0 OpenPGP: id=A1DE94B2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19YYVM0vFRKT62h7JqaNTVUp31Xc/rjAZDJKWV 9G7ekgK9JsSIECX1FEklLf2S4W6enLCiQRCU4QJ2AnBtkwbQsL V6UnmKnhSho6kXFSTTVgZWXmT3nHH3a X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on spamtrap X-Spam-Status: No, hits=-10.2 required=5.0 tests=DSPAM=-10.19694 version=2.63 X-Spam-Level: X-DSPAM-Signature: !DSPAM:48245bab58019521415745! X-DSPAM-Probability: -2.0000 X-DSPAM-Confidence: 0.9997 X-Spam-Score: 0.0 (/) Sender: cinelerra-admin@skolelinux.no Errors-To: cinelerra-admin@skolelinux.no X-BeenThere: cinelerra@skolelinux.no X-Mailman-Version: 2.0.13 Precedence: bulk Reply-To: cinelerra@skolelinux.no List-Unsubscribe: , List-Id: Mailinglist for Cinelerra, the community version List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 09 May 2008 16:25:39 +0200 X-Spam-Score: 0.0 (/) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 marquitux caballero schrieb: > As most of you know, i have been using Open Movie Editor, and the > Node editor have boosted a lot that app. I would like to suggest if > somekind to other NODE BASED APPS is possible (I know it`s > premature), I mean import/export to and from blender, or OME. Hi Marquitux, Lumiera is being built based internally on a node graph, so it seems reasonable that at some point we'll have a user visible node viewer or editor. Moreover, there is a lot of cooperation regarding the low level handling and treating of video and media between Lumiera and the OME folks. As you probably know, we are currently not at the point of worrying about how to edit nodes or to export/import to other Apps ;-) I'm sure we'll find out about it while we go... In the context of Lumiera there an additional problem with any "node editor" approach. Because Lumiera is focused rather on editing larger movie projects (and not so much on animation style work), the aspect of how to organize the tasks and how to get a smooth workflow is important. Especially for node editing, it isn't sufficient to be able to manipulate and tweak the data processing graph at a given point in my project. In the context of a larger project, this isn't much of a solution, rather it's creating new problems all over the place. We'd need a way how to do such a manipulation or customisation consistently "at every relevant location" all over the project. Such is possible for sure, but it's demanding: while every half-decent programmer knows basically how to deal with node editing and node graphs locally -- it's pretty much obvious -- there is no general off-the-shelf solution for the real problem mentioned above, so we are bound to consider the specific situation and work out a usable system and approach for the specific situation and workflow we are aiming at. Cheers, Hermann Vosseler -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIJF7jZbZrB6HelLIRAtJfAJ9QGMGdCVTLwT2+T+qnb3pFsaDeowCeP7el s4QVaQo32d9xQT2tg2wmrwQ= =oKtf -----END PGP SIGNATURE----- _______________________________________________ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra