[Lumiera] BJMR's GUI mockup/brainstorm

Brian Rytel tesla.pictures at gmail.com
Sun Oct 10 11:53:05 CEST 2010


> I said theoretically,
> because actually implementing the GUI for this stuff is quite some work
> and we have to focus on other stuff firstly and for some time to come.
This is what I was reffering to about understanding the 'structure' to
design GUI
ideas from. Creating a Visual Interaction Mechanism for the tool is more
and requires that tool to be defined to work with.

Also, as I somewhat forgot, the use of existing plugin architectures will
(at least the way I see it) yield some sort of a pseudo-gui to adjust the
of varying architectures in a more uniform environment inside Lumiera.

There is a lot of work to be done brainstorming, designing and documenting
ideas! It gets my creative juices rather stimulated every time the
discussions starts up.

Thank You!


On Sat, Oct 9, 2010 at 9:49 PM, Ichthyostega <prg at ichthyostega.de> wrote:

> roland schrieb:
> > What do you mean by "asset"? Can you give an example?
> Hi Roland,
> the assets are sort-of "the bookkeeping view" at the things contained in a
> session (=project). The most prominent example is the media loaded into
> the session. When it comes to effects, the effect asset is rather like the
> effect processor, while the individual effect as attached to a clip in the
> timeline can be seen as an "instance", i.e. a single application of that
> effect processor. There are further kinds of assets which are mostly of
> internal interest only (Sequences, busses, processing patterns, tracks)
> All of this might seem exaggerated complexity, but you should note that
> Lumiera
> is not limited to a specific kind of effects (e.g. Lumiera plugins); rather
> the
> plan is to support the most popular existing frameworks or plugin standards
> by
> providing a suitable adapter. That has the direct consequence that we'll
> need
> to keep track of certain metadata, like what kind of effect-plugin it is,
> what library to load for that plugin, and especially important what version
> number of the effect to allow. It might well be that someone tries to open
> an existing session on a system/installation which doesn't provide the
> necessary library (or the right version). Instead of failing or just
> discarding the effect, Lumiera will flag it as missing and disabled.
> That's basically the same behaviour as for a piece of media which is
> currently unavailable.
> > The idea of "effect palette" (called "quick menu" by BJMR) is nice. It is
> a
> > sort of "customisable bar" where you can add your own links to your most
> > needed effects (or group of effects). But I find it an extra; the tab
> storing
> > all effects can equally contain a part where you can find these most used
> > effects.
> Indeed we didn't decide much about the actual representation in the GUI yet
> --
> so my considerations are largely regarding what should be possible through
> the
> internal structures (which I'm developing). Here we'll get some kind of
> folder
> or container holding other objects or nested containers. We'll use these
> folders
> uniformly, even the tracks are just such folders. In timeline view, we'll
> just
> get a different presentation of these folders (namely the classical tracks
> with clips on it). Thus, theoretically you could "playback" a clip bin or
> look at the timeline contents with the asset view. I said theoretically,
> because actually implementing the GUI for this stuff is quite some work
> and we have to focus on other stuff firstly and for some time to come.
> Cheers
> Hermann V.
> _______________________________________________
> Lumiera mailing list
> Lumiera at lists.lumiera.org
> http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
> http://lumiera.org/donations.html
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lumiera.org/pipermail/lumiera/attachments/20101010/ef5a7c53/attachment.html>

More information about the Lumiera mailing list