Open Octave Project and lscp
Posted: Sat Jul 04, 2009 10:12 am
As a quick heads up, i'm also involved in the Open Octave Project, which is an orchestral and film based attempt at bringing apps and tools together in linux audio land.
Chris and I have been extremely busy getting this project off the ground, including branching an app,and going to work on the workflow, specific to building a professional use programme base. Open Octave Midi is our purely midi editor and sequencer, and we intend this to be the orchestral and film writer's tool of choice for working with MIDI, in conjunction with Linuxsampler at the beating heart of our project.
Ihave a question at this point.
Anders, and Chris, both made clever scripts to "convert' lscp maps to RG, and Midnam formats.
In order to streamline midi maps across applications, and be able to freely interchange them, what sort of work is involved in coding the lscp format into an app, by default? Example is, a user builds his or her maps in Linuxsampler, and then can simply import them into Open Octave Midi, without any need for any sort of conversion process. And vice versa.
Lscp as a mapping format seems to be robust, and i'm wondering if we can promote it further, as a unified format by default for linux audio midi bank and patch mapping. (I'd certainly like to do this, at least)
Perhaps a simple app with gui, in which users can build their maps, and save them for general use in lscp format apps?
Opinions?
Alex.
Chris and I have been extremely busy getting this project off the ground, including branching an app,and going to work on the workflow, specific to building a professional use programme base. Open Octave Midi is our purely midi editor and sequencer, and we intend this to be the orchestral and film writer's tool of choice for working with MIDI, in conjunction with Linuxsampler at the beating heart of our project.
Ihave a question at this point.
Anders, and Chris, both made clever scripts to "convert' lscp maps to RG, and Midnam formats.
In order to streamline midi maps across applications, and be able to freely interchange them, what sort of work is involved in coding the lscp format into an app, by default? Example is, a user builds his or her maps in Linuxsampler, and then can simply import them into Open Octave Midi, without any need for any sort of conversion process. And vice versa.
Lscp as a mapping format seems to be robust, and i'm wondering if we can promote it further, as a unified format by default for linux audio midi bank and patch mapping. (I'd certainly like to do this, at least)
Perhaps a simple app with gui, in which users can build their maps, and save them for general use in lscp format apps?
Opinions?
Alex.