Instrument Design for sequencing clips of events
Date | 2016-05-04 15:18 |
From | Ed Costello |
Subject | Instrument Design for sequencing clips of events |
Hi, I was wondering what would be the best way of designing an ableton live like clip triggering system where one could add and remove notes within clips in realtime, and these clips would trigger sound making instruments in turn. Just thinking about it, I suppose you would have a master instrument which triggers clip instruments. This master instrument would have the master clock and would schedule the individual clip instruments start and stop times. The clip instruments would contain a list of events, which ideally could be added to or removed from in real time. Clip instruments would be able to play once or loop indefinitely. The clip instruments would in turn trigger actual noise making instruments to produce the music. Would this be currently possible in Csound? -- Edward Costello
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
|
Date | 2016-05-05 18:52 |
From | Rory Walsh |
Subject | Re: Instrument Design for sequencing clips of events |
Hi Ed. I think this could be done with ftable/arrays or arrays, or arrays of ftables. I've done somewhat similar things in the past with a master clock triggering all other instruments. When a flag is set for the clip to be on, it will only start when it's time has come. I guess there are probably hundreds of ways of doing this in Csound. I've always stayed away from using MIDI as I prefer to keep things as generic as possible. In the hope that I might be able to plug and play it elsewhere if needed. On 4 May 2016 at 15:18, Ed Costello <phasereset@gmail.com> wrote:
|
Date | 2016-05-05 22:54 |
From | Søren Jakobsen |
Subject | Re: Instrument Design for sequencing clips of events |
I would recommend using a modern, general purpose language (e.g. Python) for all types of general data management and just use Csound (through the API) for time/audio related processing. Best regards, Søren On Wednesday, May 4, 2016, Ed Costello <phasereset@gmail.com> wrote:
|
Date | 2016-05-06 00:19 |
From | Rory Walsh |
Subject | Re: Instrument Design for sequencing clips of events |
That's a good point. And one I generally agree with. The main reason I keep doing these things in Csound is so that I can port them to other languages by simply using the Csound API. I've moved quickly and efficiently from C to Python to Java in the past because I've used Csound to look after and manage higher level data abstractions. I've found it particularly useful when porting instruments to Android. But it is true, you do get far more when you can tap into the power of the hosting language. It's always a trade off. On 5 May 2016 22:55, "Søren Jakobsen" <sorenkj@gmail.com> wrote:
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
I would recommend using a modern, general purpose language (e.g. Python) for all types of general data management and just use Csound (through the API) for time/audio related processing. |
Date | 2016-05-09 16:34 |
From | Steven Yi |
Subject | Re: Instrument Design for sequencing clips of events |
I like the idea of implementing something like this this in Csound code. I've been looking into some modular synth kind of approaches to sequencing patterns. I think it might have different requirements but would share some as well. Anyways, I'll probably give it a go sometime. :) On Thu, May 5, 2016 at 7:19 PM, Rory Walsh |
Date | 2016-05-09 19:30 |
From | Ed Costello |
Subject | Re: Instrument Design for sequencing clips of events |
Yeah, as far as I know the idea for Ableton started off as some kind of elaborate Max/MSP patch, which was then redone in C++. The thing that I was thinking would be the hardest part of this to implement would be adding to and removing events from a list inside a clip instrument, would that require some kind of new opcode to be implemented? On Mon, 9 May 2016 at 16:35 Steven Yi <stevenyi@gmail.com> wrote: I like the idea of implementing something like this this in Csound -- Edward Costello
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
|
Date | 2016-05-09 20:03 |
From | Rory Walsh |
Subject | Re: Instrument Design for sequencing clips of events |
http://createdigitalmusic.com/2014/03/see-max-patch-robert-henke-built-ableton-live-hear-music-made/ I'd say it could all be implemented in csound but may be easier with a few dedicated opcodes. On 9 May 2016 7:31 pm, "Ed Costello" <phasereset@gmail.com> wrote:
Csound mailing list
Csound@listserv.heanet.ie
https://listserv.heanet.ie/cgi-bin/wa?A0=CSOUND
Send bugs reports to
https://github.com/csound/csound/issues
Discussions of bugs and features can be posted here
|