which stage is open, which deck active and which layer  is on. you can also adjust this per mouse click.

part of the screen flexible in size. shows all active  media.

users have their own settings, they can overrule system set-up's and vice versa. it have to be clearly displyed whose settings are the actual active ones.

set-up's are devided by locations, the system should automatically add a new set-up when other displays are connected. you can set it also to not switch and just ignore different hardware

how audio plays back..

the clips and all the media have a position in 3D space, when it comes to playing here int the set-up it is choosen how it mixes to the specific hardware

(most of the time) invisible

to translate human moves or a serie of moves into 'gestures'. depending an what is active on the 'ground layer' this will performe modification on the 'material'

automatic or manual group objects with a few different render options for the groups/bins. bins are universal objects which can transform to finished timelines and can be viewed in all the 'Views' provided in the 'Editor' stage. 'Views' are sub stages.

In 'Project Organizer' you have to define settings for each project such as how many sub-stages you will see, which hardware interfaces, how detailed options you want to see when exporting,... there should be some pre-configured scenarios five or so which covers all your needs. one of them should be 'easy setup' for beginners, online production,... and pro users can make their own.

this settings can be easily modified during the editing process but the aim is to have as less things around as possible.

maybe it's good to select a user here so that every project can include one ore more users and they can have their configurations  (environment).

all the stages should be available in a mouse/touch and keyboard/'lumiera hardware interface' only version. so that there are different environments without compromises

every user should have the possibility to show only his/her most important stages.

stages can have many view options, this are the 'views'. views are pre-configured by the system set-up or by the user. for example: show waveform, detailed zoom, ..

every view should be as intuitive and clear as possible. this small fragments of the system should really try to do 'one thing at a time'. it should allow an emotional link to what is going on.

there should be the possibility to save/mark/create 'subviews'  or 'presentation state' which stores specific position, selections, active commands, active clips, small details.. during one working scession to come by another time. this can be called 'worksite' (idea by hermann).

another thing inside views are 'commands' which are the modifying tools. they are also 'subviews' with some minor graphical changes to the actual view to show that the command is on and to let you intuetivly know what to modify. the command is performed by 'gestures' this are a set of human inputs through various devices (input devices). gestures define how the command  is performed.

and for some views in some substages e.g. in the 'title text tool' there can be the possibility to save templates as one possible subview. so that the user can manage to be very efficient when he/she has a repitative task by setting presets and hiding features.

also note that a change of input device (mouse to keyboard or 'lumiera interface') should happen when you switch between views, and stages only! for continuety in the workflow.

why the 'screens' and 'stages' together are such a long list: A. to have less buttons and distracting things around when you want to focus on one task. (one thing at a time vs. multitasking and windows) B. because the main input tool should be a wheel which makes it easy to switch around in a linear way (thats what we have to do anyways while editing movies)

magazine (newspaper) view, where you can explore your shooting. with description and tagging clips inside this bin/sequence/group

or have jsut one clip open

Loose arrangement and clip connecting in 2D space. object based montage.

'Relation Spyder' tool which sets the relations throught a static wall of clips, this produces a fexible line which is/become a new object (sequence) --> define time as a flexible line object

subview/command: Trim

subview/command: Slip/Slide

playhead

This is for time based views only. Each deck have one playhead. Playheads are static in the middle of the viewer and the media is transported through. (so we don't have the situation that the playhead is moving through the window and the timeline have to jump afterwards.)

curtains

each sub-stage can offer up to three different levels of details. form very simplistic to all  information available. like curtains on a stage and each one opens more depth showing more of the stage.

configuration as a layer should show only options  which are relevant to what we see now, underneath this layer. so to say every stage, view, ... have their own meta page where all the options are stored. also if some options are relative or overruled by more general configurations or the system set-up, it is shown here and greyed out

this layer puts detailed information over everything actual on the screen and should act as a quick lookup. there can also be git-tickets  on the elements for easy user-feedback.

 between two or more options

one time action

have a subset of functions which are controlled by 'gestures'

to use with mouse: since we have no buttons in this concept all the available commands (case sensitive) will be shown e.g. on right button click. then there is a graphical representation of each command arround the mouse in circles and sorted by topic. some modulation keys are available to.

it would be great if that could evolve to a standard in all open source creative media applications so that's easy to switch over to a application which you use seldom and start right away. a kind of a fallback or standarized interface. not the functions have to be the same but how they are arranged and how they are accesd and maybe how they are performed (gestures).

?? not really a serious idea

kind of gestures:

cut

modify edits

drag

*affecting the overall length (splice in, ripple)

*overwriting

take

*affecting the overall length (splice in, ripple)

*overwriting

place

*affecting the overall length (splice in, ripple)

*overwriting

handle clips

move

slip/slide

change the view and stage (program navigation)

however the relation to the OS looks like, at some point it will be interesting how we can trip arrount between lumiera and other software. so the interaction i think should be very well implemented in the concept.

here i suggest 'workboards' which contain project files on a 2d space like a desktop and a clipboard to hand them from one program to anoter. files can also be grouped freely or by software they belong to. there can be some alternative views like in a magazine view. they contain a whole project. you can open them in lumiera (see: stage/project organizer) or as a stand alone full screen app. in case of 'elementaryOS' as a host system there are options like 'D-bus' or 'contractor' which can be used i guess.