film-machine (fm01) ::
fm01 perhaps best viewed not via this ancient description but through all other material on this site attempting to roughly describe the project.
[recent notes:
that textual lisp work with a pre-existing script will describe a trajectory meeting with arc of gdapp to constitute first fm01
this textual work is towards creating a compiler/interpreter which actively runs that script - gdapp is concerned with mobile code nodes which run and enact on data - both approaches lead to fm01 - runs the script creating new text or film - runs that script which acts on and suggests data sets - active across data sets and is inside-embedded within / as data sets
co-evolution of cell data-code interpreter elements in lisp (eg. evolution of edge detection + see "evolvable computing by means of evolvable components" - lukas sekanina, natural computing journal 2004 http://ipsapp008.kluweronline.com/ips/frames/fasttracks.aspx?J=5030&N=ForthcomingPapers&ADS=0#
co-evolving mobile modules explore and exchange different functionality and data/code whilst working on both script stream I/O and film stream I/O - basic idea is replacing fixed database software thing with mobile nodes and changing code/data streams across parallel architectures
script-data-code IS these modules (how module is defined) thus software is really the interpreter or some sort of bootstrap of language and interpreter
]
<b>fm01 will offer a total software environment for the semi-automated production, scripting and editing of endless cinema.</b>
fm01 transposes non-metaphoric systems and grammar theory (of computer languages, abstraction and data containers) to the realm of expanded cinema.
the base proposal concerns the development of a scripting language, data structures, and suitable filesystem? for the automated production and grammatical expression of endless cinema.
a relational, nodal language of connection will be formulated to descend through levels of scene, shot and frame (stored and to be shot).
however, fm01 is not totally automated and in parallel with ap03? forms a mechanism of personal insertion into systematics.
a filesystem will be devised to deal with such fragments (as language and as data), allowing rapid self-programmed, structural retrieval and re-assembly of material.
fm01 is not conceived as an engine for the manipulation of generic clips (an expanding database of all possible scenes categorised according to a huge number of elements and relations, although it does have some elements in common with this strategy) but is rather an enmeshing within script, a writing of script-now already filmed; a script written and to come via this now-empty machinery.
fm01 is a large-scale project which builds on previous http://www.1010.co.uk ap research and process to push the envelope of what can be achieved in terms of computer languages and data visualisation; re-thinking hard-wired notions of input and output.
http://sourceforge.net/projects/fm01/ link to sourceforge
1) the filesystem?:
a fast raw system for information retrieval of compression scene data and active code data enacting within such data. in common with schemes such as mpeg4?. fm01 expands the mpeg-4 approach towards the poetic.
2) the scripting language:
both senses of scripting are implied in the design of a scripting language; borrowing from computer science and cinematics. the scripting language conditions the dialogue between user/producer and fm01. it is though use of this language that the film script/ production regime is first created (see 3) below) and later shots are actively encoded without markup. the language is totally modular and extendible, allowing the user and fm01 to fluidly create new constructs together. the scripting language will be coded in lisp and glued to the underlying C code,
3) the production regime:
the shooting/production regime in interaction with fm01 could be described as follows:
a) scripting language/data structures and filesystem pre-programmed in fm01 as core software though that language is always open to change itself/be changed ie. this language is used by both system and author
b) in scripting language entry and response of script-in-progress
c) scenes shot and inputted in response to stage 2
d) generation of expanded film begins from moment stage c) begins and becomes 2nd level interrogative material marking a return to stage b) with d) now continuing with any new material. expanded film is now running (either in interrogative or auto-pilot modes)