hello...
i'm looking for people who would like to help out with the completion
of the version 0.70 of the Eisenkraut audio file editor ( http://
sourceforge.net/projects/eisenkraut ; this current version needs to
be retrieved via SVN ). two main tasks remain for this version:
- getting the documentation (manual) done
- getting the OSC implementation done
( - adding sourceforge packages with platform-specific installers /
downloads )
in both cases work has been started but is very incomplete. The
current documentation can be viewed from the Help -> Eisenkraut Help
menu. the current OSC implementation is documented in the help file
"OSC Command Reference" and the example files in EisK_DEVEL/
SuperColliderTests.
For OSC, basic things like getting / retrieving markers, activating
transport, opening and closing files, copying and pasting chunks
work. what's missing:
- server replies in the case of commands that can fail, something
like the /done or /failed concept in scsynth
- a way to wait for the completion of asynchronous tasks such as paste
- a way to insert rendered audio as comes out of a scsynth NRT
process ("bouncing realtime plug-ins"). there is already an example
in EisK_DEVEL/SuperColliderTests/FilterTest(2).rtf that renders
output, however getting that automatically back into the document is
not yet possible
- almost no client (SuperCollider) side classes exists. High priority
should be on the EisKPlugIn which is very basic now and needs a
proper implementation. Otherwise in the long run it would be cool to
have proxy classes for example for an audio document in Eisenkraut
- in the most sophisticated version, there would be a notification
model where the client proxy classes get automatically build and
updated as the user opens documents and modifies them. the main
problem to solve here is the one of asynchronicity and client state
being potentially "behind" server state when getting active.
There's a mailing list eisenkraut-devel for people who like to join in.
I think this project is _very_ interesting for SuperCollider users if
the OSC implementation gets worked out properly. You can use OSC both
to programmatically edit sound files, swap information between SC and
EisK (e.g. marker positions), add custom editors using a combination
of SuperCollider / SwingOSC, add custom filtering plug-ins.
ciao, -sciss-
_______________________________________________
sc-users mailing list
sc-users@...
http://lists.create.ucsb.edu/mailman/listinfo/sc-users