Re: [sc-users] Request for SC 3.4 - a better NRT interface

[Scott Worthington <stwbass@xxxxxxxxx>]

I'm almost positive that you know about this, but just in case.... Recently I've started working in NRT using patterns. I was doing some granular synthesis things with grains every 0.005 seconds, so writing out a Score didn't really make me excited. I was using some soundfiles, which made the process slightly more complicated. If one is just doing synthesis there is a .render method that can be called directly on a pattern.

If it helps, my workflow was the following:

(
//SynthDefs
)

(
x = [ /*a series of OSC commands for any buffers, etc, one might need*/]
//definitely could be skipped if not using buffered sound
)

(
a = Pbind or whatever
)

//if no buffered sound is used
//listen
a.play
//record
a.render(path, maxTime, sampleRate, headerFormat, sampleFormat, options, inputFilePath)

//with buffer
d = a.asScore(duration)
d.add(x)
d.sort
// you can listen to it
d.play(s)
d.stop
//and record it
d.recordNRT(oscFilePath, outputFilePath, inputFilePath, sampleRate, headerFormat, sampleFormat, options, completionString, duration)



Using the buffered sound wasn't a 1-to-1 just adding one Object to record, but I found it to be very east to work that way. If there is only synthesis, it is just a 1-to-1 sort of like you asked, the catch being you'd need to use patterns. I think there is a function .render in wslib which might help too. That all being said, I would support attempts to find a way to streamline NRT more, although by SC 3.4 I'll probably have a faster computer and have no need for NRT :P

sw

-- 
Scott Worthington
stwbass@xxxxxxxxx
www.scottworthington.com