Re: [jazzplusplus-devel] It's a night. Reduced trackwin's global variable dependence

[Joakim V. <jo...@ve...>]

>Ultimately I'd like to have Jazz using its own project file format and reading 
>midi files will be done by importing the file.  There are bad reasons to do 
>this, and good ones.  Mainly I want to be able to embed wav data in a project 
>file, and have a good open project file format that will allow easily adding 
>patterns, templates, and stuff, and easily support multiple midi devices in 
>the studio (similar to RoseGarden, in fact as a proof-of-concept when we get 
>there, someone (me?) should write an importer for RoseGarden projects).
>  
>
Yes, Jazz would need its own format at some point.

Something I did with Jazz was to add the facility to play tracks from 
other tracks,
a playtrack event. This was a feature in a sorely-missed amiga sequencer 
I used, Music-X.

This doesnt entirely fit with the normal midi-file standard(although 
there are sequence play midi events),
so i kind of kludged it in in Jazz midi format :-P

Anyway, these kind of features would be easier with a new format.

I would advocate looking at existing formats before inventing something, 
like
music-xml or something(music-xml has taken some flak, but it can't be 
all bad can it?)

An xml based aproach would open up for many cool concepts, like using 
XSLT transforms
for midi event processing, which could be re-used in other projects.

One of my ideas for Jazz is to open up for plugins and so on that 
manipulates event data,
like GIMP:s python, scheme, and perl interfaces.


Cheers,
Joakim

>Dave
>
>  
>