Thread: [Bluemusic-users] General question regarding parameter automatisation
Brought to you by:
kunstmusik
From: Jan J. H. <jj...@so...> - 2011-03-03 16:47:15
|
Dear List, I have got a general question regarding parameter automatisation. I have several similar sound objects on different layers, which point to the same instrument. Can I draw a different line on the other sound layer holding the same automatisation-parameter for this instrument, but with different values for each layer? E.g can I control the frequency of a simple oscillator instrument simultaneously and differently from several sound layers? Such as: Layer 1 instr. 20 frequency = 440 hz start-time 0 dur 5 sec Layer 2 instr. 20 frequency = 880 hz start-time 3 dur 5 sec Is there a way to achieve this in blue? All the best, Jan Jacob sound | movement | object | space sonic architecture | site: http://www.sonicarchitecture.de spatial electronic composition | 2nd order ambisonic music |
From: Steven Yi <ste...@gm...> - 2011-03-05 01:29:06
|
Hi Jan Jacob! Sorry for the delay in reply, but I've been on a business trip and have had little time for anything but work. Regarding your question, automation of parameters for a BSB instrument can only be done once per instrument, and does not work on the note-level. The only options at this time are to create copies of your instrument and automate them individually. In terms of abstraction, it makes sense as they are associated with parameters and those are global values that are read by the instrument. I can imagine adding a feature that would allow creating free-standing automations that would then generate just generic global values. Doing something like that, one could design an instrument to then read from a global variable at note time (i.e. pass-in a value in a pfield, instrument uses that value to lookup what free-automation to use). I can look into this if you would like, just add a feature request to the Request for Enhancement tracker (from the help menu). Hope that helps! steven On Thu, Mar 3, 2011 at 11:47 AM, Jan Jacob Hofmann <jj...@so...> wrote: > Dear List, > > > I have got a general question regarding parameter automatisation. I > have several similar sound objects on different layers, which point to > the same instrument. Can I draw a different line on the other sound > layer holding the same automatisation-parameter for this instrument, > but with different values for each layer? E.g can I control the > frequency of a simple oscillator instrument simultaneously and > differently from several sound layers? Such as: > > Layer 1 instr. 20 frequency = 440 hz start-time 0 dur 5 sec > Layer 2 instr. 20 frequency = 880 hz start-time 3 dur 5 sec > > Is there a way to achieve this in blue? > > All the best, > > Jan Jacob > > > sound | movement | object > | space > sonic architecture | site: http://www.sonicarchitecture.de > spatial electronic composition | 2nd order ambisonic music > > > ------------------------------------------------------------------------------ > Free Software Download: Index, Search & Analyze Logs and other IT data in > Real-Time with Splunk. Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, virtual > or in the cloud. Deliver compliance at lower cost and gain new business > insights. http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |
From: Mark V. P. <Mar...@te...> - 2011-03-05 20:07:04
|
Or maybe Blue could generate copies of an instrument when creating the csd, differing only in the automation signals. Just a thought. Steven Yi wrote: > Hi Jan Jacob! > > Sorry for the delay in reply, but I've been on a business trip and > have had little time for anything but work. > > Regarding your question, automation of parameters for a BSB instrument > can only be done once per instrument, and does not work on the > note-level. The only options at this time are to create copies of > your instrument and automate them individually. > > In terms of abstraction, it makes sense as they are associated with > parameters and those are global values that are read by the > instrument. I can imagine adding a feature that would allow creating > free-standing automations that would then generate just generic global > values. Doing something like that, one could design an instrument to > then read from a global variable at note time (i.e. pass-in a value in > a pfield, instrument uses that value to lookup what free-automation to > use). I can look into this if you would like, just add a feature > request to the Request for Enhancement tracker (from the help menu). > > Hope that helps! > steven > > On Thu, Mar 3, 2011 at 11:47 AM, Jan Jacob Hofmann > <jj...@so...> wrote: > >> Dear List, >> >> >> I have got a general question regarding parameter automatisation. I >> have several similar sound objects on different layers, which point to >> the same instrument. Can I draw a different line on the other sound >> layer holding the same automatisation-parameter for this instrument, >> but with different values for each layer? E.g can I control the >> frequency of a simple oscillator instrument simultaneously and >> differently from several sound layers? Such as: >> >> Layer 1 instr. 20 frequency = 440 hz start-time 0 dur 5 sec >> Layer 2 instr. 20 frequency = 880 hz start-time 3 dur 5 sec >> >> Is there a way to achieve this in blue? >> >> All the best, >> >> Jan Jacob >> >> >> sound | movement | object >> | space >> sonic architecture | site: http://www.sonicarchitecture.de >> spatial electronic composition | 2nd order ambisonic music >> >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT data in >> Real-Time with Splunk. Collect, index and harness all the fast moving IT data >> generated by your applications, servers and devices whether physical, virtual >> or in the cloud. Deliver compliance at lower cost and gain new business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> Bluemusic-users mailing list >> Blu...@li... >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users >> >> > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > > -- Mark _________________________________________ When you get lemons, you make lemonade. When you get hardware, you make software. |
From: Jan J. H. <jj...@so...> - 2011-03-06 08:53:53
|
Dear Steven and Mark, I see - making copies of my instrument and renaming the automatisation parameter also was my first attempt to archive the control of several simultaneous notes. As far as I do understand, you, Steven, do suggest that there could be one general parameter automatisation-line which feeds to every sound- object being capable to read it, regardless of notes and instances of an instrument. One automatisation could then control several simultaneous notes. I wonder if another concept would be possible: My suggestion is to link an automatisation line to a sound layer. This line could control then every sound-object being on that sound layer which was designed to be capable to read that automatisation- parameter. E.g. several different sound-objects containing different instruments on one sound layer could be automated then by one single line named "amplitude"on that sound layer, as long they were designed to do so. Another sound layer would maybe hold a different line also named "amplitude". This automatisation-line would control all the sound objects on that sound layer being capable to read the automatisation named "amplitude" here. The binding of the automatisation-parameter to the sound layer and the differentiation of automatisation-parameters on different sound layers, but with similar names would have to be managed internally in blue, without the user having to worry about it. What do you think about that, Steven? Would this concept be possible? Would this be reasonable? All the best, Jan Jacob sound | movement | object | space sonic architecture | site: http://www.sonicarchitecture.de spatial electronic composition | 2nd order ambisonic music Am 05.03.2011 um 02:28 schrieb Steven Yi: > Hi Jan Jacob! > > Sorry for the delay in reply, but I've been on a business trip and > have had little time for anything but work. > > Regarding your question, automation of parameters for a BSB instrument > can only be done once per instrument, and does not work on the > note-level. The only options at this time are to create copies of > your instrument and automate them individually. > > In terms of abstraction, it makes sense as they are associated with > parameters and those are global values that are read by the > instrument. I can imagine adding a feature that would allow creating > free-standing automations that would then generate just generic global > values. Doing something like that, one could design an instrument to > then read from a global variable at note time (i.e. pass-in a value in > a pfield, instrument uses that value to lookup what free-automation to > use). I can look into this if you would like, just add a feature > request to the Request for Enhancement tracker (from the help menu). > > Hope that helps! > steven > > On Thu, Mar 3, 2011 at 11:47 AM, Jan Jacob Hofmann > <jj...@so...> wrote: >> Dear List, >> >> >> I have got a general question regarding parameter automatisation. I >> have several similar sound objects on different layers, which point >> to >> the same instrument. Can I draw a different line on the other sound >> layer holding the same automatisation-parameter for this instrument, >> but with different values for each layer? E.g can I control the >> frequency of a simple oscillator instrument simultaneously and >> differently from several sound layers? Such as: >> >> Layer 1 instr. 20 frequency = 440 >> hz start-time 0 dur 5 sec >> Layer 2 instr. 20 frequency = 880 >> hz start-time 3 dur 5 sec >> >> Is there a way to achieve this in blue? >> >> All the best, >> >> Jan Jacob >> >> >> sound | movement | object >> | space >> sonic architecture | site: http://www.sonicarchitecture.de >> spatial electronic composition | 2nd order ambisonic music >> >> >> ------------------------------------------------------------------------------ >> Free Software Download: Index, Search & Analyze Logs and other IT >> data in >> Real-Time with Splunk. Collect, index and harness all the fast >> moving IT data >> generated by your applications, servers and devices whether >> physical, virtual >> or in the cloud. Deliver compliance at lower cost and gain new >> business >> insights. http://p.sf.net/sfu/splunk-dev2dev >> _______________________________________________ >> Bluemusic-users mailing list >> Blu...@li... >> https://lists.sourceforge.net/lists/listinfo/bluemusic-users >> > > ------------------------------------------------------------------------------ > What You Don't Know About Data Connectivity CAN Hurt You > This paper provides an overview of data connectivity, details > its effect on application quality, and explores various alternative > solutions. http://p.sf.net/sfu/progress-d2d > _______________________________________________ > Bluemusic-users mailing list > Blu...@li... > https://lists.sourceforge.net/lists/listinfo/bluemusic-users > |