Re: [Bluemusic-users] Conventions in instruments
Brought to you by:
kunstmusik
From: Steven Y. <ste...@gm...> - 2007-09-20 19:43:15
|
Hi Mark, I tend to do pitch then amplitude as that's the habit I got into over years and I guess pitch is easier to see that way, but no reason really beyond that. (MIDI note-ons also do key num then velocity which is somewhat related, maybe that was an influence.) I would assume most people who use instruments on blueShare will customize anyways for their own system. As for panning, Csound is unique in that always the case where panning will be done in a mixer. For example, I often do panning in instrument because I am sending panning in pfields. For that, I'm not typing each pfield, but that is generated by performer objects I use in python. So the performer object has a pan location, "performs" score and outputs the information the instrument will play, which will include pan there from performer. This allows me to do things like have 12 of the same instrument but panned to different locations. To do this in a MIDI based environment, one would need to create 12 tracks and assign panning as there is no performer abstraction in MIDI based environments. (At least, none I've seen). There are cases where one might want to do panning on a mixer; for that blue doesn't have a very clear solution. One can create an effect for that; I'll have to revisit the signal generation rules for if an instrument only generates one audio sig or two, etc. Perhaps a standard spatialization UI option would be useful for mixer. So you can do 2 channel and you would get a knob or slider (with option to customize pan code, though default to pan_gm2 from UDO archive). Then we can add options for more things, like quad, cube, or maybe even ambisonics, with an option to disable/enable per instrument. If this sounds interesting, please log a Request for Enhancement via blue's help menu. Thanks for the questions! steven On 9/20/07, Mark Van Peteghem <Mar...@te...> wrote: > Hi, > > I have some questions, not on how Blue works, but rather about > conventions in making instruments that you intend to share with others. > > I had the habit to make the field p4 the amplitude and p5 the frequency > (and/or pitch), because many opcodes like oscil and grain use the same > order, first amplitude and then frequency, so it's easier to remember. > But I noticed that many instruments in Blueshare do it the opposite way. > Is there a specific reason for that? > > I also noticed that many instruments provide panning. But isn't it > easier to handle panning in the mixer? > > Thanks for your attention, > > -- > Mark > _________________________________________ > When you get lemons, you make lemonade. > When you get hardware, you make software. > > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |