gmane.comp.video.lumiera.general

Hotel Froscon

Christian Thaeter — 2012-05-07T13:30:09

I've just got the confirmation about Booking the Hotel Rooms for me and
Benny. Also I asked how much rooms they still have free. That is 2
Single and 7 Double Room (at http://schmerbroicher-hof.de/). Guess
anyone who want a single Room should reserve ASAP!

Christian
_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

FrOSCon: Call for Exhibitors and Developerrooms

Inga Herber — 2012-04-26T14:58:35

// English \\ (für eine Deutsche Version siehe unten)

Hello Lumiera Team,

we would like to invite you to take part in the seventh Free and Open
Source Software Conference (FrOSCon 2012).

FrOSCon is a two-day conference on Free Software and Open Source, which
takes place on August 25th/26th, 2012 at the University of Applied
Sciences Bonn-Rhein-Sieg, in St. Augustin near Bonn, Germany.

Main part of the conference is a comprehensive range of talks and
workshops. Furthermore, there is a large exhibition area, where projects
have the opportunity to present themselves and get in touch with users
and other developers. Moreover, we offer a few rooms for Free Software
projects to organize developer meetings or to present their own program.

We would be pleased if your project would like to contribute to this
year's FrOSCon and thus support the communication and exchange within
the Open Source and Free Software community. Depending on the kind of
your participation, there is different information available to you.

To sign up for a booth, please visit
https://callforexhibitors.froscon.org and register your project. Please
feel free to contact us for any questions at exhibitors-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org
<mailto:exhibitors-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org>. The registration for booths will be
open until May 23rd.

If your project wants to sign up for a developer room, please write a
proposal to projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org <mailto:projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org>. The
proposal should contain a short summary (1-2 paragraphs) of what you
plan to do and which special requirements you have. Since the demand for
developer rooms usually exceeds the number of rooms we can offer, we
will choose the projects which look the most promising to us based on
the submitted proposals. If you have questions concerning the developer
rooms, feel free to contact projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org
<mailto:projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org>. The deadline for the submission of
developer room proposals is April 30th.

Additionally our Call for Papers already started, we are looking forward
to your submissions of talks and workshops. You can register via
http://cfp.froscon.org/. For further information concerning the Call for
Papers take a look at http://www.froscon.de/en/program/call-for-papers/.
The Call for Papers will end on May 23rd, too.

We hope to meet you at FrOSCon in St. Augustin.

Kind regards,
The FrOSCon Team

// Deutsch \\

Hallo Lumiera Team,

hiermit wollen wir dich herzlich einladen an der siebten Free and Open
Source Software Conference (FrOSCon 2012) teilzunehmen.

Die FrOSCon ist eine zweitägige Konferenz über Freie und Open Source
Software, die am 25. und 26. August 2012 an der Fachhochschule
Bonn-Rhein-Sieg in Sankt Augustin, in der Nähe von Bonn stattfindet.

Auf der FrOSCon gibt es viele Vorträge über aktuelle Themen rund um
Freie Software. Außerdem gibt es eine große Austellungsfläche, wo sich
Projekte mit einem Stand präsentieren können, um mit Nutzern und
Entwicklern ins Gespräch zu kommen. Zusätzlich bieten wir einige Räume
für Projekte an, in denen sich Entwickler treffen oder ein eigenes
Programm auf die Beine stellen können.

Wir würden uns freuen, wenn auch ihr zur diesjährigen FrOSCon beitragt
und damit den Austausch in der Free Software Community unterstützt. Je
nach euren Beteiligungswünschen gibt es verschiedene Möglichkeiten.

Der Call for Papers ist gestartet und wir freuen uns auf eure Vorträge
oder Workshops. Anmelden könnt ihr euch unter http://cfp.froscon.org/.
Weitere Informationen findet ihr unter
http://www.froscon.de/en/program/call-for-papers/. Der Call for Papers
wird am 23.05.2012 geschlossen.

Wenn ihr als Projekt einen Entwicklerraum haben möchtet, schreibt
einfach eine E-Mail an projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org
<mailto:projects-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org>. Die E-Mail sollte eine kurze
Zusammenfassung (1-2 Absätze) darüber enthalten, was ihr mit dem Raum
machen wollt. Falls ihr spezielle Anforderungen habt, würden wir euch
bitten diese auch mit anzugeben. Da wir in der Vergangenheit mehr
Bewerbungen als Räume hatten, wählen wir die vielversprechendsten
Projekte auf Grundlage der eingesandten Beschreibungen aus. Die Deadline
für die Bewerbung für einen Entwicklerraum ist der 30. April 2012.

Außerdem könnt ihr an der FrOSCon teilnehmen, indem ihr euch mit einem
Stand den Besuchern präsentiert. Dafür könnt ihr euch unter
https://callforexhibitors.froscon.org anmelden. Die Deadline der
Aussteller ist der 23. Mai 2012. Wenn ihr Fragen habt, dann könnt ihr
euch jederzeit an uns wenden (exhibitors-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org
<mailto:exhibitors-XR7Gx/IErD1AfugRpC6u6w< at >public.gmane.org>).

Wir hoffen euch auf der FrOSCon zu sehen,

Beste Grüße,
Das FrOSCon Team

New issue of Libre Graphics Magazine within the fortnight

Benny Lyons — 2012-04-19T11:44:17

Hi Lumierites, 
A new issue of Libre Graphics Magazine has been scheduled by the end of this month.  This issue, 1.4, will carry an advertisement on the Lumiera project with emphasis on attracting new developers to the project.

More details available at: 
        http://libregraphicsmag.com/

Cheers
Benn

Dev Meeting this week?

Ichthyostega — 2012-04-09T15:53:00

Hi Lumi hackers,

time is fleeting.... Seems that next Wednesday is already the 2nd of April. OMG.

This would bee the usual time for a developer meeting. Is there anything
important to discuss right now? I on my part have nothing urgend to settle.
While generally I hoped to get more time, I didn't manage to do anything for
Lumiera the last weeks. Situation seems to become better next weeks.
Anyway, for my part, I just need to continue with coding at the point
I am right now, and have plenty of stuff just to do.

Any thoughts, suggestions, things to discuss?
If necessary, I could arrange just to be at home and in IRC on Wednesday evening.


Cheers,
Hermann Vosseler



_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

quarterly news + website redesign status

Wouter Verwijlen — 2012-04-09T13:29:37

Hi there!

We're behind again on the quarterly news update. If the devs can e-mail their story then I'll mix it into a new report.

Second question: is any work being done to complete the redesigned website? At staging.lumiera.org is a nearly-complete template from what I can see.
A while ago I delved into the GIT branch and found out that it was structured in a real confusing way. I drew a scheme to propose a simplification of the structure. I've attached it to this mail.

Apart from the technical structure we need to look at how we want third-level (and lower) pages to be accessed. The current solution in staging shows an alternate layout with the menu-tree on the left.
I personally think it's confusing to switch layout from section to section. I suggest using the sidebar to show lower-level navigation.
Regarding the design: Francesco: have you taken a look at the improvements to your design that I proposed a while ago? (That was: making it more compact and giving more attention to the text by giving it a solid white background).

Kind regards,

Wouter_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

what kind of depot for apt-get for a mint distribution

magali marc — 2012-04-08T16:47:47

Hi,
i would like to install Lumiera on my mint distribution,
i've been practicing editing on  cinelerra since several years,

what kind of depot for apt-get do you advice me ?

thank you a lot !

m


       _______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

ANNOUNCE: Lumiera Developer Meeting, March 2012

Ichthyostega — 2012-03-13T01:38:35

Hi Lumiera hackers,


Wednesday, March 14, 2012 -- starting 20:00 UTC

would again be the time for our regular monthly Lumiera developer meeting.
Actually, I won't have much on my mind to discuss this time. The last weeks
I was quite busy with other stuff, and regarding Lumiera I have my tasks
to work on. Deep coding mode.

Anyway, I'll be at IRC/Freenode.net in #lumiera next Wednesday.
As usual. Feel free to propose things for discussion. Everyone is welcome.

Hermann Voßeler
(aka "Ichthyo")









_______________________________________________
Lumiera mailing list
Lumiera< at >lists.lumiera.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Fwd: Re: Lumiera ad in the next issue

Benny Lyons — 2012-03-08T09:23:31

Morning,
Received the attached from ginger at Libregraphics. This is the proposal for the plug in the upcoming edition of their magazine for the Lumiera project with emphasis on motivating people into getting involved in the Lumiera project.

Personally, I find the advertisement very good: one might possible be able to find critical aspects, but that would be intricates and somewhat pedantic. I think the advertisement catches what we'd like to say very well and relates the message very effectively. 'Well done ginger!' I say.

OK, I'd like to tell ginger to go ahead with the advertisement as it stands, but your opinions are important. Should you have any objections, please vent you tribulations, comments, etc. before tomorrow, when I'd like to send confirmation to ginger to go ahead with the advertisement as-is.

-------- Original-Nachricht --------
Datum: Tue, 6 Mar 2012 22:15:39 -0500
Von: ginger coons <ginger-UU8speA7kBf0176FNvkKTg< at >public.gmane.org>
An: Benny Lyons <Benny.Lyons-hi6Y0CQ0nG0< at >public.gmane.org>
CC: lumiera-cc-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org, lgmag-devel-cunTk1MwBs/p7az2iRsSj3siHgoa8vmX0E9HWUfgJXw< at >public.gmane.org
Betreff: Re: Lumiera ad in the next issue

Hi Benny, sorry for the long delay. I've put together something out of what
you sent. It's attached for your approval.

ginger "all-lower-case" coons
adaptstudio.ca
Phone: 647.865.7757
Skype: gingercoons
XMPP: ginger-UU8speA7kBf0176FNvkKTg< at >public.gmane.org

On 20 February 2012 11:34, Benny Lyons <Benny.Lyons-hi6Y0CQ0nG0< at >public.gmane.org> wrote:

nice "interactive" Git cheat sheet

Ichthyostega.. — 2012-02-29T16:55:00

well... not really interactive, but a bit of JavaScript magic.

Anyway, IMHO it shows the relation of working copy, staging area and
repository quite well

http://www.ndpsoftware.com/git-cheatsheet.html


_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Lumiera Trac #884: Fix the website content for the new asciidoc version

Lumiera Trac — 2012-02-28T08:26:20

#884: Fix the website content for the new asciidoc version
----------------------+-----------------
  Reporter:  ct       |      Owner:
      Type:  fixme    |     Status:  new
  Priority:  normal   |  Milestone:
 Component:  Website  |   Keywords:
Blocked By:           |   Blocking:
----------------------+-----------------
 Asciidoc deprecated the old table syntax years ago, we now upgraded to a
 new asciidoc version and these things become apparent and need eventually
 to be fixed.

 There is also an issue with locking up the asciidoc.js, this needs to be
 fixed too.

 Raw log of the build_website.sh output for your convenience:

  http://lumiera.org/,log

Maintenance Notice

Christian Thaeter — 2012-02-28T07:09:59

Because of upgrades the Web-Server will be down for some time now and
be back later today. Notably Trac will not be reachable. Mailinglists
will stay working.

cheers
Christian 
_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Question about scons and backporting asciidoc

Christian Thaeter — 2012-02-25T07:57:12

Hi Ichthyo,

I am working again on the new builddrone implementation and come along
scons now, with autotools I can build a project in very small steps and
produce reports about these (testing with nobug here, spare your rants
about autotools :P). That is, I can check for bootstrap, configure,
make (main program), make the tests, running the tests etc.

Mostly this works in scons too, but scons has no bootstrap and
configure stage (which is good, no doubt) but still it checks for
dependencies implicitly when building. Is there some way to factor
these dependency checks out (maybe by some empty build target)? There
is no much urge for this, builddrone could just generate prettier
reports when it can build the project in small steps.


Another question: how hard would it be to backport asciidoc and put a
debian package into our depot (note: this is just informal, I didn't
even tried if the wheezy package could be installed in squeeze
already). Simon helped with setting up a improved builddrone website
 http://builddrone.pipapo.org/
and we stomped on some nasty old asciidoc bugs, which we now worked
around but it would be somewhat nice to have a fixed version installed
on our server.

Christian
_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

An observation regarding Lumiera's parallelism

Ichthyostega.. — 2012-02-08T17:34:27


Hi Lumi hackers,

since we're discussing about advertisement, and also consider GSoC, there's
an
interesting observation I want to share.

Mostly, wer're discussing our thread handling in the render engine along
the lines of
"we have isolated jobs and a scheduler, and those jobs are made to avoid
blocking".

While this is certainly true, it not the full story. When considered at a
higher,
more abstract level, what we're actually doing in our engine is some kind
of
"modified fork-join". The similarities are striking -- the major difference
is, that fork-join is a generic handling pattern and typically implemented
through general purpose libraries, while we're creating something
specialised
and dedicated here. Yet still

- we have a "backbone level", which does "fork" new sub tasks: while
playback
  is running, we won't schedule all conceivable jobs at once; rather we're
  scheduling the first chunk plus a follow-up job to schedule the next
chunk.

- we *do* join the results together. We just do it in a clever way, so to
avoid
  blocking waits. Our "join operation" is actually implemented by
comparison with
  a time of delivery / deadline. When in time, results can be dropped in,
otherwise
  they are just discarded

Thus, the most relevant difference is, that the classical fork-join pattern
uses
a stack or deque for the forked worker tasks, while we're using a priority
queue
with intelligent time-of-delivery based ordering.

Cheers,
Hermann


_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

ANNOUNCE: Lumiera Developer Meeting, February 2012

Ichthyostega — 2012-02-06T00:36:17

Hi Lumiera hackers,

According to our usual habits, the next regular monthly
Lumiera developer meeting would be scheduled for

Wednesday, February 8, 2012 -- starting 20:00 UTC

The meeting will be on IRC/Freenode.net in #lumiera
Everyone is welcome. Please speak up if this schedule doesn't work for you.

Hermann Voßeler
(aka "Ichthyo")








_______________________________________________
Lumiera mailing list
Lumiera< at >lists.lumiera.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Forthcomming advertisement in the next issue of the LibreGraphics

Benny Lyons — 2012-01-31T21:18:11

Hi,
We've been in contact with the Libre magazine. They are willing to place an add for us in the next issue, 1.4, of their magazine.

They require a text of not more than 200 words, and some Lumiera graphics to accompany the advertisment, i.e. Lumiera Logos erc.

While I've managed to download some logos, my modem is still glowing after the ordeal, so I haven't managed to sift through the logos we'd like to appear in the advertisment. If anyone out there would like to select and send me Lumiera logos for the advertisement, me and my modem would be more than happy to accept your help, but we would be able to manage otherwise.

Below is my proposal for the text (I haven't bothered counting the words, it's just a first draft.)

If you'd like to make suggestions, corrections, etc to the text, please do so; but try to be concise, as we don't have much time to get the stuff off to the publisher, and there's little time to debate on the ML.

PROPOSED TEXT:

Lumiera is an Open Source project to create a professional,
non-linear video editor. The NLE is geared towards the
rigours of a professional environment, but it should equally
be at home to the casual, hobby user.
Born from the the Cinelerra project, Lumiera strives to be
innovative and offer a challenging and instructive ground for
developers.
While the project has an active community and is steadily evolving,
developers are few.
We are looking for developers. We believe that Lumiera can cater
from the novice to the more experienced developers.

We'd be delighted to hear from you.

Benny

ANNOUNCE: Lumiera Developer Meeting, December 2011

Ichthyostega — 2012-01-08T21:22:42

Hi Lumiera hackers,

According to our usual habits, the next regular monthly
Lumiera developer meeting would be scheduled for

Wednesday, January 11, 2012 -- starting 20:00 UTC

The meeting will be on IRC/Freenode.net in #lumiera
Everyone is welcome. Please speak up if this schedule doesn't work for you.

I'd like to propose two topics for discussion:

(1) Website/Docu. Can we think of an easy way to get "Wiki Links"?
    Explicitly writing links is tedious and error prone. Which just
    leads to not cross linking at all. Basically it would be desirable
    to have an easy syntax to link to
    - other pages
    - tickets
    - ...?
(2) Rendering to file: how do we intend to handle this?
    My question is entirely practical and technical (I know the general
    idea): Exactly what libraries do we want to support initially, and
    how do we invoke that in each of these cases, what degree of
    integration do we need/want and is doable with our resources?

Feel free to propose further topics....

Hermann Voßeler
(aka "Ichthyo")







_______________________________________________
Lumiera mailing list
Lumiera< at >lists.lumiera.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

ANNOUNCE: Lumiera Developer Meeting, December 2011

Ichthyostega — 2012-01-08T21:22:42

Hi Lumiera hackers,

According to our usual habits, the next regular monthly
Lumiera developer meeting would be scheduled for

Wednesday, January 11, 2012 -- starting 20:00 UTC

The meeting will be on IRC/Freenode.net in #lumiera
Everyone is welcome. Please speak up if this schedule doesn't work for you.

I'd like to propose two topics for discussion:

(1) Website/Docu. Can we think of an easy way to get "Wiki Links"?
    Explicitly writing links is tedious and error prone. Which just
    leads to not cross linking at all. Basically it would be desirable
    to have an easy syntax to link to
    - other pages
    - tickets
    - ...?
(2) Rendering to file: how do we intend to handle this?
    My question is entirely practical and technical (I know the general
    idea): Exactly what libraries do we want to support initially, and
    how do we invoke that in each of these cases, what degree of
    integration do we need/want and is doable with our resources?

Feel free to propose further topics....

Hermann Voßeler
(aka "Ichthyo")







_______________________________________________
Lumiera mailing list
Lumiera< at >lists.lumiera.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

ANNOUNCE: Lumiera Developer Meeting, December 2011

Ichthyostega — 2012-01-08T21:22:42

Hi Lumiera hackers,

According to our usual habits, the next regular monthly
Lumiera developer meeting would be scheduled for

Wednesday, January 11, 2012 -- starting 20:00 UTC

The meeting will be on IRC/Freenode.net in #lumiera
Everyone is welcome. Please speak up if this schedule doesn't work for you.

I'd like to propose two topics for discussion:

(1) Website/Docu. Can we think of an easy way to get "Wiki Links"?
    Explicitly writing links is tedious and error prone. Which just
    leads to not cross linking at all. Basically it would be desirable
    to have an easy syntax to link to
    - other pages
    - tickets
    - ...?
(2) Rendering to file: how do we intend to handle this?
    My question is entirely practical and technical (I know the general
    idea): Exactly what libraries do we want to support initially, and
    how do we invoke that in each of these cases, what degree of
    integration do we need/want and is doable with our resources?

Feel free to propose further topics....

Hermann Voßeler
(aka "Ichthyo")







_______________________________________________
Lumiera mailing list
Lumiera< at >lists.lumiera.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Happy New Year

Ichthyostega — 2012-01-01T01:42:24

Happy New Year to everyone, all the best for 2012


...and my personal good-New-Year-wish for our "baby" is to learn rendering ;-)

--Ichthyo





_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Lumiera threads (was: parallel2012 Conference inKarlsruhe)

Ichthyostega — 2011-12-25T03:06:53

Am 23.12.2011 15:05, schrieb Benny Lyons:


Hi Benny,

for Lumiera we intend to do pretty much the obvious thing, given the current
hardware and expected further development: for the stuff where performance
really matters, we create small quasi atomic jobs which get scheduled, using
a thread pool of a size in accordance with the real possibilities for
parallelism on the given system (# of cores). The ultimate goal is that running
jobs should never block. Thus there will be a second kind of pseudo-job, which
cares for preparing the IO, so the actually working jobs become activated only
when the input data is already mapped into memory.

One of the absolutely fundamental ideas of Lumiera is that the system shall
adjust and throttle its load, especially the IO bandwidth, to create an optimal
load, while not driving the system into "saturation".


A basic thread pool is in place since quite some time. Michael Ploujnikov did a
huge proportion of that work. Christian started working on the scheduler shortly
before the "woodwork interruption". We've already integrated the conventional
pthreads (used by the GUI and at places in the session) as a special case into
that "lumiera threads" framework. But we don't have a scheduler interface yet (I
am currently working towards an high-level
interface on my side). Surprisingly enough, this wasn't much of a problem.
Since, for me it turned out that the major challenge is to translate a quite
elaborate "high-level-model" (oriented towards the requirements of professional
editing) into a graph of simple nodes, which can be processed easily through
such quasi atomic jobs.

My starting point was that several of the practical impediments we suffer
from when using Cinelerra for professional work are due to Cinelerra's session
model being coupled too tightly to the engine. Thus Lumiera takes the opposite
approach: trying to separate both, so the session can be optimised for human
workflow, and the engine for efficient processing.



Libraries of that kind are very frequently proposed for use by Lumiera
(similarily stuff for using the GPU). This is almost kind of a FAQ.

There is one huge problem with such -- people tend to overlook that. Lumiera
isn't intended to run in some research department to do number crunching.
It's not so much a technical, but a social problem: The existing plug-ins for
processing video and audio with all the surrounding ecosystems. We're perfectly
aware that it's completely out of reach for a project like Lumiera just to
define a new shiny plug-in standard. We're roughly 10 years too late for that.
There is ffmpeg, ladspa, gstreamer, mplayer and vlc, plus several more.

Thus we rather focus on getting the typical execution situation of such an
already existing plug-in into line with our threadpool architecture: We will
care for preparing the input data, and then fed the already filled input
buffers to the external processing function of the plug-in running embedded into
a "job". Of course, supporting a (very popular) framework like gstreamer
(I fear we can't avoid that) will create a lot of headaches with this approach,
while something like Gavl / Gmerlin can be expected to play quite well with our
architecture.

It is likely that we'll write a very small number of absolutely basic stuff
ourselves (like a video fader, video overlayer, mask, colour adjust tool or
sound fader). But for anything beyond that, we should rather use the existing
code and expertise.

The combination of these two design decisions explains why such a huge deal of
work goes into measures to get the complexity under control and keep all of
that metadata processing out of the actual engine. When the playback or render
is started, the scheduler needs to be fed just with simple jobs, and we have
to care beforehand to get the right number of channels to the right number of
buffers, that the buffer sizes match, that each job uses the right processing
function from some plug-in and so on. I wouldn't be surprised if, for the final
app, 80% of the source base are either related to GUI and workflow or do just
metadata processing and transforming, with only a small performance critical
core for the actual processing. But if we succeed with getting that complexity
under control and build that architecture, then we'll be able just to integrate
stuff like GPU based processing as if it was just yet another external library
and plug-in system.

Cheers,
Hermann

_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html

Fwd: Santa LACus (your Xmas Linux Audio Conference 2012reminder)

Robin Gareus — 2011-12-21T22:38:11

Hi all,

Just a friendly reminder that JANUARY 11 is the deadline for all
submissions to the Linux Audio Conference (LAC 2012), which will take
place at CCRMA (Stanford, California) in April
2012!http://lac.linuxaudio.org/2012/

Santa LACus wishes a great paper-and-music-submitting holiday to all!

Ho, ho.

Bruno

- - - - - - - - -

LAC 2012: the Linux Audio Conference - Call for Participation
April 12-15, 2012 < at > CCRMA, Stanford University

http://lac.linuxaudio.org/2012/

[Apologies for cross-postings] [Please distribute]

Online submission of papers, music, installations and workshops is now
open! On the website you will find up-to-date instructions, as well as
important information about deadlines, travel, lodging, and so on. Read
on for more details!

We invite submissions of papers addressing all areas of audio processing
based on Linux and open source software. Papers can focus on technical,
artistic or scientific issues and can target developers or users. We are
also looking for music that has been produced or composed entirely or
mostly using Linux and other Open Source music software.

The Deadline for all submissions is January 11th, 2012

The Linux Audio Conference (LAC) is an international conference that
brings together musicians, sound artists, software developers and
researchers, working with Linux as an open, stable, professional
platform for audio and media research and music production. LAC includes
paper sessions, workshops, and a diverse program of electronic music.

The upcoming 2012 conference will be hosted at CCRMA, Stanford
University, on April 12-15. The Center for Computer Research in Music
and Acoustics (CCRMA) at Stanford University is a multi-disciplinary
facility where composers and researchers work together using
computer-based technology both as an artistic medium and as a research
tool. CCRMA has been using and developing Linux as an audio platform
since 1997.

http://ccrma.stanford.edu

Stanford University is located in the heart of Silicon Valley, about one
hour south of San Francisco, California. This is the first time LAC will
take place in the United States.

http://www.stanford.edu

We look forward to seeing you at Stanford in April!

Sincerely,

The LAC 2012 Organizing Team
_______________________________________________
Lumiera mailing list
Lumiera-aLEFhgZF4x639dL7tAm8iNi2O/JbrIOy< at >public.gmane.org
http://lists.lumiera.org/cgi-bin/mailman/listinfo/lumiera
http://lumiera.org/donations.html