Are there any popular formats for writing scores for ChucK scripts? I know a lot of people consume MIDI or OSC messages from controllers or other software, but I'm looking for something ChucK reads so that it's on ChucK's clock. -- Tom Lieber http://AllTom.com/ http://ckvlang.org/
Hey Tom,
I think that with the current FileIO operations, idiosyncratic score files
are easy to develop. You know, in the same old Chuckish DIY sort of way, of
course, you'll have to write your own parser/interpreter for them. But if
you keep your file simple, you should be able to do it anyway you want; and
you can specify any information you want. What's cool about that is that
you can write it in the way that makes the most sense to you.
Here's what I would do...
My parser would read the file in and create a Score object (some class that
keeps all the events of the song in some array somewhere) and then would
read those events off as Events (or some subclass) that my shreds would
respond to and make sounds.
Well, that's one idea anyway. You could always use CSound...
Good luck!
-Mike
On Tue, Feb 23, 2010 at 1:02 PM, Tom Lieber
Are there any popular formats for writing scores for ChucK scripts? I know a lot of people consume MIDI or OSC messages from controllers or other software, but I'm looking for something ChucK reads so that it's on ChucK's clock.
-- Tom Lieber http://AllTom.com/ http://ckvlang.org/ _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Tom: If your goal is simply to play scores using ChucK's strict timing, of course you could write them as .ck files and load them from the command line or via Machine.add() to play 'em -- no FileIO required. That's the approach I've taken in the past. I realize this doesn't answer your question about a "popular format" -- I don't know of any, but I'm sure others on the list do. And presumably a "popular format to .ck" converter program wouldn't be particularly difficult. - Rob On 23 Feb 2010, at 15:20, mike clemow wrote:
Hey Tom,
I think that with the current FileIO operations, idiosyncratic score files are easy to develop. You know, in the same old Chuckish DIY sort of way, of course, you'll have to write your own parser/ interpreter for them. But if you keep your file simple, you should be able to do it anyway you want; and you can specify any information you want. What's cool about that is that you can write it in the way that makes the most sense to you.
Here's what I would do...
My parser would read the file in and create a Score object (some class that keeps all the events of the song in some array somewhere) and then would read those events off as Events (or some subclass) that my shreds would respond to and make sounds.
Well, that's one idea anyway. You could always use CSound...
Good luck!
-Mike
On Tue, Feb 23, 2010 at 1:02 PM, Tom Lieber
wrote: Are there any popular formats for writing scores for ChucK scripts? I know a lot of people consume MIDI or OSC messages from controllers or other software, but I'm looking for something ChucK reads so that it's on ChucK's clock. -- Tom Lieber http://AllTom.com/ http://ckvlang.org/ _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
-- http://michaelclemow.com http://semiotech.org
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
I'm also searching for the solution of the same problem. I decided to try
the following approach: Create MusicXML or MIDI scores, then parse them
using Ruby and generate ChucK code.
I haven't tried it so far, but I have already succeeded to generate ChucK
code from Ruby and used it in my projects.
Regards,
Szilveszter (Hillaby)
2010/2/24 Robert Poor
Tom:
If your goal is simply to play scores using ChucK's strict timing, of course you could write them as .ck files and load them from the command line or via Machine.add() to play 'em -- no FileIO required. That's the approach I've taken in the past.
I realize this doesn't answer your question about a "popular format" -- I don't know of any, but I'm sure others on the list do. And presumably a "popular format to .ck" converter program wouldn't be particularly difficult.
- Rob
On 23 Feb 2010, at 15:20, mike clemow wrote:
Hey Tom,
I think that with the current FileIO operations, idiosyncratic score files are easy to develop. You know, in the same old Chuckish DIY sort of way, of course, you'll have to write your own parser/interpreter for them. But if you keep your file simple, you should be able to do it anyway you want; and you can specify any information you want. What's cool about that is that you can write it in the way that makes the most sense to you.
Here's what I would do...
My parser would read the file in and create a Score object (some class that keeps all the events of the song in some array somewhere) and then would read those events off as Events (or some subclass) that my shreds would respond to and make sounds.
Well, that's one idea anyway. You could always use CSound...
Good luck!
-Mike
On Tue, Feb 23, 2010 at 1:02 PM, Tom Lieber
wrote: Are there any popular formats for writing scores for ChucK scripts? I know a lot of people consume MIDI or OSC messages from controllers or other software, but I'm looking for something ChucK reads so that it's on ChucK's clock.
-- Tom Lieber http://AllTom.com/ http://ckvlang.org/ _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
-- http://michaelclemow.com http://semiotech.org
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
participants (4)
-
mike clemow
-
Robert Poor
-
Szilveszter Tóth
-
Tom Lieber