if CSound takes OSC messages you could send your data that way in real time.
> On Jun 23, 2017, at 8:00 PM, Forrest Curo <treegest...@gmail.com> wrote: > > It _looks_ like one could save and play a score file that basically said, say > : "f0 600" for ten minutes of communicating with it by other means... > > Instead I'll just start csound rendering away on one computer while another > sends it messages over a network cable. Would then use cm basically for > timing, scheduling, midi interface. > > I can barely imagine the hassles of writing something for multiple platforms. > > On Fri, Jun 23, 2017 at 5:22 PM, Taube, Heinrich K <ta...@illinois.edu> wrote: > at one point i had a real-time connection to libcsound, but back then it was > very hard to maintain and also to build the csound lib on the different > platforms. So i went back to basic writing files and calling csound from the > shell > > > > On Jun 23, 2017, at 3:59 PM, Forrest Curo <treegest...@gmail.com> wrote: > > > > I'm a little confused re real time interactions between Grace and csound, > > guessing that the possiblities (especially with OSC but probably also using > > simply "cs:i ...") have probably outrun the documentation. > > > > What is the actual situation? Lots of ways to run the two programs > > independently... but with one cm process running a real-time csound > > instance & sending it various forms of data? > > > > Wouldn't work well? Cumbersome? Redundant? > > > > Or should the best way be pretty self-explanatory by now? > > > > Forrest Curo > > San Diego > > _______________________________________________ > > Cmdist mailing list > > Cmdist@ccrma.stanford.edu > > https://cm-mail.stanford.edu/mailman/listinfo/cmdist > > _______________________________________________ Cmdist mailing list Cmdist@ccrma.stanford.edu https://cm-mail.stanford.edu/mailman/listinfo/cmdist
