Hi Rob, Automation is inherently control rate in blue and I believe there is a note that if you use automation on a parameter it will generate as a control signal. On the other hand, if you don't use automation and just use the widget value, it will generate as a constant numerical value. If you need an i-rate value but are planning to change values over time, you can try using something like i() which i think will convert a k-sig into an i value. I think this should work barring you don't use --expression-opt. I don't know if there's another way to cast a k-rate value to i-rate. Hope that helps! steven On Wed, Jun 4, 2008 at 10:35 AM, robcanning wrote: > Hi Steven, > > Many thanks for your reply - this has got me started nicely. > I have now made a granule BSB instrument which works perfectly from the GUI > controls. > one problem i still have is this: > > 1. the krate inputs work fine from the automation timeline kgize or kgap for > example - but i am having problems with the i signals such as ivoice, ipitch > or iatt. here is the error i get: > > error: input arg 'gk_blue_auto2' of type k not allowed when expecting i, > line 95: > ipitch1 = gk_blue_auto2 > > i am guessing: > gk_blue_auto2 > should be > gi_blue_auto2 > > or something... but cant find how to change the code for this. > > Many thanks > > rob c > > > > > Steven Yi wrote: >> >> Hi Rob, >> >> You can use a LineObject with a Sound SoundObject, but you would >> probably need to make the name of your variable gkgrainsize to make it >> a gk signal. However, I think it would be better to use a BSB >> instrument. You can try this: >> >> 1. On your Sound soundObject, right click and convert to generic >> score. That should add the instrument code to the project orchestra >> and the soundObject on the timeline should now be a generic score. >> >> 2. In the orchestra, right click and choose convert to BlueSynthBuilder. >> >> 3. In the UI editor, add a knob with boundary values (min/max) that >> are appropriate for grain size. Assign it an objectName of "grainsize" >> >> 4. Switch to the code editor, go to where you had "kgsize = 0.5" and >> the 0.5 is, delete the 0.5 and then press ctrl-shift-space. This will >> give you a list of all of the objectNames available from the widgets. >> Select "grainsize" and that should put into the code editor >> , so your text should now say "kgsize = > >> 5. Now you have an automatable instrument. You can just adjust the >> value of that grain size by adjust the widget, or if you want to >> automate, you can go to the timeline, find a layer you want to put >> that automation and hit the "A" button on the soundLayer panel, then >> navigate and select the "grainsize" parameter from the instrument. >> >From here you should the value of the parameter over time as a graph. >> You can then choose "Single Line" mode to edit the values of that >> automation. >> >> Let me know if that works for you. I would suggest going this route >> as I think after the small initial learning curve you get a lot of >> benefit from making your instrument this way, including not having to >> remember gk signal names, no worries about variable name clashing as >> blue will handle generating unique variable names, and increased >> portability/reuse of instrument. >> >> Cheers! >> steven >> >> >> On Wed, May 28, 2008 at 4:19 PM, Rob Canning >> wrote: >> >>> >>> hello, >>> >>> i am starting with blue & csound and would like a little help. >>> i have made a blue.SoundObject.Sound in the timeline >>> and would like to control one of its paramaters with a LineObject >>> >>> in my generic editor i have this: >>> >>> ;insert instrument text here >>> kgsize = .05 >>> >>> >>> a1 granule 7000, 12, 1, 1, 0, 2, 4, 0, 0, 4, 0.1, 30, kgsize, 30, >>> 20, >>> 20, 0.69, 1, 1.42, 0.29, 4, 0 >>> a2 granule 7000, 12, 1, 1, 0, 2, 4, 0, 0, 4, 0.1, 30, kgsize, 30, >>> 20, >>> 20, 0.39, 1, 1.42, 0.29, 4, 0 >>> >>> outs a1,a2 >>> >>> and in my table i have: >>> >>> f2 0 2097152 1 "/home/rob/mechanism.wav" 0 4 0 >>> >>> >>> ok so all that works fine... >>> >>> >>> i would like to have something like: >>> >>> kgsize = grainsize >>> >>> >>> then a LineObject called grainsize to control it. >>> >>> is this possible to work this way or do i need to make a BSB instrument >>> in >>> order to automate parameters? >>> >>> if the later what would such a BSB look like? i have had a go at making >>> one >>> and looked at some examples in the blue share but don't seem to "get it" >>> >>> many thanks >>> >>> rob c >>> >>> p.s. whats the csound community like here in london uk? i never meet any >>> csounders here... all pd and supercollider heads - i need to find some >>> people i can barter pints for knowledge with... >>> >>> >>> Send bugs reports to this list. >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >>> csound" >>> >>> >> >> >> Send bugs reports to this list. >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe >> csound" >> >> >> > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > csound" >