2009-01-14 Lumiera Developers Meeting

Two groups are created, each of these have someone responsible to bring them forward.

The group nudger is some director/moderator who keeps it going and nudges the people constantly, leading the discussion, not making the decisions alone. This supervisor doesn’t need to be someone to do the work of that group, but someone who can spend some efforts and time to coordinate it.

Work discussion will proceed on the Mailing List but following the directions stated during the IRC meetings.
Messages will have [ARTWORK] or [LOGO] or [WORKFLOW] in the subject. Groups can schedule IRC meetings separated from the monthly meetings that are meant for general organization.

A new Nobug is nearly ready with new documentation (cehteh). The error handler has been improved, as announced on the ML. Cehteh emphasised the importance of using nobug everywhere and not #if DEBUG:

DEBUG is not a standard C/C++/buildsystem defined macro when it works its just coincidence but NDEBUG is standard. Neither does such code use nobug facilities nor respect nobug build levels.

in new nobug you can do: NOBUG_IF_ALPHA( alpha code here ) it’s the same for BETA RELEASE and there’s a NOT variant for each but even then that should be avoided and higher level nobug facilities should be used instead. (http://www.lumiera.org/nobug.html)

beta and release builds shall be possible with nobug soon .. waiting for metta to integrate the new test.sh test.sh with regex is awesome because you can test output which contains no exact things like addresses, version numbers, times and running the testsuite under valgrind works properly now

Ichthyo expressed the importance of not having dedicated kinds of tracks, but to be able to use any track for anything (audio, video etc.). This will require more work in the proc layer. Tracks are also not just layered but are trees which can fold. Any clip can contain N streams of various kinds. When a clip contains video and audio streams it still occupies just one track and the system automatically connects the audio to an audio bus etc. but the user is free to split off the audio as an independent clip and treat it separately from the video. The plan is to have various kinds of links between clips. This basic idea will need further refinement and consideration by the workflow team (Nikola et. al.) e.g. the user will need some way to direct the sound to a different bus even though it may be in a compound clip. By default all the video should be layered in the order of the tracks and a user should be able to say "don’t mix the audio from track 4 and its child tracks directly to master but route it to the music subgroup". This is where the tree of tracks plays an important role because each track with its children forms a group. There was further discussion on the general aims, objectives and focus of Lumiera and the reasoning behind them. Integration with control surfaces, jog wheels, sliders etc. should also be considered for the workflow. Nikola expressed the importance of stability and a simple and clean UI.

cehteh proposes a recurrent core dev meeting, more frequent than the monthly meeting since there is the a lot of stuff ahead that needs communication.