MCCF Progress: Events Timeline and Route Editors. MCCF Design Philosophy
Watch the MCCF demo
A short video of the Multi-Channel Coherence Field working in an X3D scene. Watch it on YouTube.
Just a flyby.
We have completed most of the work on the Timeline Editor and Route Editor. The first enables a global time clock for triggered events similar to a DAW. The second creates routes and looks similar to Bergstrom's excellent work. I also highlights the eligible connections on a node when an out from another node is selected and will not allow circular routes.
We split out the dialogue editor. Because it has text, audio, lexicons for affect tagging, etc. it needs it's own editor and different export functions.
The main differences in this ecosystem is the MCCF does not edit the X3D directly. It creates a set of XML files with all of the properties the scene needs on export via the X3D loader. This enables us to keep MCCF semantics in the XML such as zones and dialogues, characters, etc. This allows the EBPS system to also be declared in the XML then applied to the active scene at runtime. Selective persistence (values passed between scenes) is easier. Because the semantic layers of X3D are in the protos, wherever possible we use protos to map to MCCF semantics. For example, animated lights and cameras are typed so declaring those in the XML is cleaner.
Another difference is MCCF is not a genealized X3D editor. So the route and events editor instantiate nodes that are placed upstream in the scene composer. That saves the author from having to pick from long lists of nodes they have not actually used. We only add nodes in the MCCF when we have a specific reason to use that node and some are grouped into the protos and only exposed via the editor to the proto. In other words, we are hiding as much X3D from the author as possible.
This is a different philosophy from a tree editor. There are advantages to both but given the export is standard X3D, the author can open it in any X3D conforming editor and work with the scene. However, they will lose those changes if they reload the scene in X3D because they will not be reflected in the MCCF XML.
An advantage of this approach is repurposing a scene's information. The MCCF XML can be used for reports, for creating film scripts, for narratives such as books or audio books. IOW, it is a film/theatre semantic with a real time emotional engine.
I am very pleased to see the work with glb and the new route editor. X3D is in a transition from a legacy technology to a vibrant ecosystem. Good for all.
cheers,
len




Comments
Post a Comment