diff --git a/NEWS b/NEWS index 85053d59b..b083567c4 100644 --- a/NEWS +++ b/NEWS @@ -1,6 +1,7 @@ Lumiera -- Significant Changes ============================== -:Date: 11/2015 +Version: 0.pre.04~rc.1 +:Date: 11/2025 ************************************************************* Lumiera is a non-linear video editing and compositing tool. @@ -8,32 +9,39 @@ Lumiera is a non-linear video editing and compositing tool. NOTE: as of 11/2025, Lumiera is in early development stage; it is not usable yet. This is a preview Release of a current development snapshot in pre-alpha stage. +************************************************************* -Visit http://Lumiera.org and join the mailing list -when interested in Lumiera planning and development. -**************************************************************** + +In the current stage of development, the focus is primarily on the +overall integration of fundamental functionality at all levels of +the code base. Lumiera pre-Alpha Versions -------------------------- -**This source tree doesn't yet contain a working video editing application** + -Rather, it contains the framework and technology core -of the envisioned Application ``Lumiera''. - -See http://issues.lumiera.org/roadmap[Project roadmap] +As of _11/2025_ (0.pre.04):: +This version is again motivated by a series of major upgrades and clean-up. +Compilation now requires C++23 and Debian/Trixie is considered the reference +platform. The GUI is connected to the core over an asynchronous messaging +bus and the timeline display has been reshaped to accommodate flexibly +nested structures of media content, instructed by the session through +a series of _diff messages_. A scheduler has been implemented to drive +the Render Engine, but the connection to the player and UI for output +is yet unfinished. As of _11/2015_ (0.pre.03):: -a lot of long standing maintennance work has been done. The Project switched +A lot of long standing maintenance work has been done. The Project upgraded to C++11 and in the end even to C++14 and Debian/Jessie as reference platform, -followed by clean-up of now obsolete workarounds. On the GUI side, we largely -made the transition to GTK-3, which lead to rework of our timeline widget, not -finished yet. This work also spured an effort the connection and communication -between Proc and the UI, which is expected to be asynchroneous. Due to the -limited developer resources, work on the Engine and Player part is stalled. +followed by clean-up of workarounds now obsoleted. On the GUI side, we largely +made the transition to GTK-3, which leads to a rework of our timeline widget, +which is in progress but not finished yet. This work also spurred an effort +to reorder the connection and communication between core and the UI, which +is expected to be asynchronous. Due to the limited developer resources, +work on the Engine and Player part is stalled. As of _10/2013_ (0.pre.02):: -the data models have been elaborated and some significant parts of the session +The data models have been elaborated and some significant parts of the session are finished. Work has continued with time handling, a draft of the output connection framework, a draft of the player subsystem and interfaces to the engine and processing network. Unfortunately there was a considerable slowdown @@ -41,22 +49,28 @@ and decrease in team size, yet still the code base is growing towards 90k LOC. No tangible progress regarding the GUI and the backend. As of _1/2011_ (0.pre.01):: -the project has created and documented a fairly consistent design, -partially coded up -- starting from the technical foundations and working up. +The project has created and documented a fairly consistent design, +and some parts implemented -- progressing from the technical foundations. The code base is approaching 65k LOC. Roughly half of this is test code. The Application can be installed and started to bring up a GTK GUI framework, -but the GUI is very preliminary and not connected to core functionality. +but the GUI is rather preliminary and not connected to core functionality. The video processing pipeline exists only in the blueprints. As of _2/2008_:: -the project has been separated completely from ``Cinelerra'', the parent project. +The project has been separated completely from Cinelerra, the parent project. The Community, which at that time was largely identical to the Cinelerra-CV community, -choose the new project name ``Lumiera'' through a collaborative selection and vote. -The basic project infrastructure is up and running, and work on the new codebase -has started. We can show nothing beyond a test suite for some time to come. +choose the new project name **Lumiera** through a collaborative selection and vote. +The basic project infrastructure was established, and work on the new codebase +was underway. It is clear that no results other than a test suite can be shown +in the foreseeable future. As of _7/2007_:: -we started with the backend and render engine draft, some example code -complemented by several unit tests. There is a TiddlyWiki with detailed -design considerations and developer documentation and a UML model +A group of volunteers has formed to address some longstanding issues and limitations +of **Cinelerra**, which we all used for video editing tasks requiring professional quality. +The plan was to restructure some central parts of the render engine: introduce a Builder +for render pipelines and use Placements to control arrangement of clips and a unified +Data-Backend to coordinate usage of system resources. These innovations would serve +as anchor, with the intention to propose the reworked codebase as a new version +of Cinelerra, in the hope of turning Cinelerra development into a more +participatory process going forward. diff --git a/admin/setVersion b/admin/setVersion index ea95fe63b..1a60b7c55 100755 --- a/admin/setVersion +++ b/admin/setVersion @@ -40,5 +40,6 @@ rewrite doc/devel/Doxyfile 'PROJECT_NUMBER\s*=' "$VER" rewrite doc/devel/Doxyfile.browse 'PROJECT_NUMBER\s*=' "$VER" rewrite admin/scons/Setup.py 'VERSION\s*=' "\'$VER\'" rewrite README 'Version:' "$VER" +rewrite NEWS 'Version:' "$VER" echo -e "\nSUCCESSFULLY rewritten version $VER\ncheck git diff\n\n" diff --git a/wiki/thinkPad.ichthyo.mm b/wiki/thinkPad.ichthyo.mm index 2e8851945..ac0620652 100644 --- a/wiki/thinkPad.ichthyo.mm +++ b/wiki/thinkPad.ichthyo.mm @@ -169979,8 +169979,48 @@ that situation will improve in forseeable future. - + + + + + +

+ ...ein Commit-Log einer größeren Applikation ist für sich allein nicht aussagekräftig; es muß in den Kontext gestellt werden durch ein offiziell verbindlich vorgegebenes Urteil wo das Projekt steht und wohin es sich bewegt. +

+ + + + + + + + + + + + + +

+ alle diese Preview-Releases wurden bisher bedingt durch Änderungen im Kontext, wie z.B. der Umstand, daß ich allein die Zügel tatsächlich übernommen habe, oder der Upgrade auf eine neue Refernz-Plattform und höhere Sprachstandards. Zwar wollte ich das immer, aber es ist mir nie gelungen, diese Releases auch mit Erreichen eines Meilensteins zu koppeln. Zudem haben wir noch keinen der großen Meilensteine erreicht. +

+ + + + + + + + +

+ NEWS sollte neben einem Datum auch die Versionsnummer tragen +

+ + + + + +