Re: [Bluemusic-users] Instrument Meta-Information
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2007-07-23 00:27:20
|
Hi Dave, Thanks for taking a look and glad you're interested! There is already a fair amount of code we can reuse from the Tracker for doing pfield types (most of that could probably be reused). The current types available there are documented here: http://www.csounds.com/stevenyi/blue/usermanual/html/tracker.html We may need to add a few more types, such as OCT and frequency as well as make MIDI be separated into MIDI_NOTE_NUM and MIDI_VELOCITY, as even though the range is the same, the meaning is different and tools will want to use them differently. I think perhaps the best place to start is to figure out the types of pfields possible; implementation shouldn't be too difficult after that! Thanks! steven On 7/22/07, Dave Seidel <da...@su...> wrote: > Sorry I didn't notice this when you first published it, Steven, but I > like this idea very much. It would clearly make it possible for blue to > have some very user-friendly features. Also, if done in such a way that > it could be incorporated into standard CSD files without breaking > Csound's current parser, it could also be useful for other front-end > programs; for example, we could use comments with a special syntax > immediately following the initial ';' character. It's a nice step > towards moving Csound assembly language paradigm to something more > modern and type-safe. > > Although I don't have tons of free time, I would be more than willing to > assist in the implementation of this feature. > > - Dave > > Steven Yi wrote: > > HI All, > > > >>From a a conversation with Stephane Boussuge, I was reminded of an > > idea that I haven't yet acted on but think might be very useful. I > > was thinking of adding a meta-information are for instruments that > > describes pfields of the instrument. One way to do it would be to > > have something like note templates (ala pianoroll) where one enters > > for each pfield a descriptor of what that field can take in (pch, int, > > float, etc.). Another way to do it would be to have it like the > > Tracker, where one chooses from predefined constraints for the fields > > though the options allow a range of options, including the catch-all > > string option which would allow any text. > > > > The importance of this would be that many tools could then be built > > from this meta-information. Simple things like auto-filling in note > > templates for piano roll or auto creating Tracker tracks would be > > possible. Verification tools could be made as well so that generated > > notes are withing the constratints given in the meta-information. > > Also, analysis and visualization tools could be made in a generic way > > (i.e. show all generated notes in a pianoRoll-like canvas to show > > global view of piece, harmonic analysis, etc.). Other things like > > generating notes from analyzing sounds in a spectral composition > > fashion might be easier to do with this kind of meta-information. > > > > I had thought a few days ago that if I was going to design a new > > Music-N system (which I'm not planning to do anytime, btw!), that > > defining pfields with constraints would be one thing I would > > specifically for easier tool building. > > > > Any thoughts on the idea and/or implementation? > > > > Thanks! > > steven > > > > p.s. - This would be implemented in an optional way so that older > > instruments, if meta-information is not enabled, just won't be usable > > with tools that require instrument meta-information, so as always > > older projects and work will be protected to work exactly as they have > > been. > > > > ------------------------------------------------------------------------- > > This SF.net email is sponsored by DB2 Express > > Download DB2 Express C - the FREE version of DB2 express and take > > control of your XML. No limits. Just data. Click to get it now. > > http://sourceforge.net/powerbar/db2/ > > _______________________________________________ > > Bluemusic-users mailing list > > Blu...@li... > > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > > > > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |