- chuck-users - lists.cs.princeton.edu

Midi time problem
by Gonzalo 09 Dec '16

09 Dec '16

Hi, I'm using Bruce Murphy's MIDIsender class (http://www.rattus.net/~packrat/audio/ChucK/files/midisender.ck) to generate MIDI from my Chuck code. I'm sending this MIDI to various virtual MIDI ports (using OSX's IAC Driver). Then I have various software instruments in Cubase, each one listening to one of the virtual ports. Works well when I run my Chuck program, but if in Cubase I arm the tracks and try to record the incoming MIDI, all the events get 'collapsed' at the same time, specifically the moment I click record. They do get recorded, but all starting at the same time. This only happens if I want to record them, if I'm only playing, timing is fine. Using MidiMonitor I see that the time for all the MIDI events generated from Chuck is 0, that seems to be the issue. Any thoughts on how I can change that? Thanks! Gonzalo PS: in case anybody is curious, my project's site is here: http://www.whole-play.com

3 5

Re: [chuck-users] chuck-users Digest, Vol 137, Issue 1
by Arseniy Prosvirnin 08 Dec '16

08 Dec '16

I guess problem in Cubase. In Ardour (in Debian GNU/Linux) midi data records fine at least. I use Chuck version from Github. 9 декабря 2016 г. 3:09:01 GMT+03:00, chuck-users-request(a)lists.cs.princeton.edu пишет: >Send chuck-users mailing list submissions to > chuck-users(a)lists.cs.princeton.edu > >To subscribe or unsubscribe via the World Wide Web, visit > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >or, via email, send a message with subject or body 'help' to > chuck-users-request(a)lists.cs.princeton.edu > >You can reach the person managing the list at > chuck-users-owner(a)lists.cs.princeton.edu > >When replying, please edit your Subject line so it is more specific >than "Re: Contents of chuck-users digest..." > > >------------------------------------------------------------------------ > >Today's Topics: > > 1. Midi time problem (Gonzalo) > 2. Re: Midi time problem (Michael Heuer) > 3. Re: Midi time problem (Gonzalo) > 4. Re: Midi time problem (Gonzalo) > 5. Re: Midi time problem (Eugene Martynec) > > >------------------------------------------------------------------------ > >От: Gonzalo <gonzalo(a)dense13.com> >Кому: chuck-users <chuck-users(a)lists.cs.princeton.edu> >Отправлено: Fri Dec 09 00:52:51 GMT+03:00 2016 >Тема: [chuck-users] Midi time problem > >Hi, > >I'm using Bruce Murphy's MIDIsender class >(http://www.rattus.net/~packrat/audio/ChucK/files/midisender.ck) to >generate MIDI from my Chuck code. I'm sending this MIDI to various >virtual MIDI ports (using OSX's IAC Driver). Then I have various >software instruments in Cubase, each one listening to one of the >virtual >ports. Works well when I run my Chuck program, but if in Cubase I arm >the tracks and try to record the incoming MIDI, all the events get >'collapsed' at the same time, specifically the moment I click record. >They do get recorded, but all starting at the same time. > >This only happens if I want to record them, if I'm only playing, timing > >is fine. > >Using MidiMonitor I see that the time for all the MIDI events generated > >from Chuck is 0, that seems to be the issue. Any thoughts on how I can >change that? > >Thanks! >Gonzalo > > >PS: in case anybody is curious, my project's site is here: >http://www.whole-play.com > > > >------------------------------------------------------------------------ > >От: Michael Heuer <heuermh(a)gmail.com> >Кому: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >Отправлено: Fri Dec 09 01:28:09 GMT+03:00 2016 >Тема: Re: [chuck-users] Midi time problem > >On Thu, Dec 8, 2016 at 3:52 PM, Gonzalo <gonzalo(a)dense13.com> wrote: > >> Hi, >> >> I'm using Bruce Murphy's MIDIsender class >(http://www.rattus.net/~packra >> t/audio/ChucK/files/midisender.ck) to generate MIDI from my Chuck >code. >> I'm sending this MIDI to various virtual MIDI ports (using OSX's IAC >> Driver). Then I have various software instruments in Cubase, each one >> listening to one of the virtual ports. Works well when I run my Chuck >> program, but if in Cubase I arm the tracks and try to record the >incoming >> MIDI, all the events get 'collapsed' at the same time, specifically >the >> moment I click record. They do get recorded, but all starting at the >same >> time. >> >> This only happens if I want to record them, if I'm only playing, >timing is >> fine. >> >> Using MidiMonitor I see that the time for all the MIDI events >generated >> from Chuck is 0, that seems to be the issue. Any thoughts on how I >can >> change that? >> > >MidiMsg is defined as a four byte record > >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.h#L65 > >but ChucK only sets three bytes on send > >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L120 > >midisender.ck does the same. Is the unset byte supposed to be the >time? >Suppose I should go read the spec. > >It appears time is written and read from files separately > >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L823 >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L837 > >Not sure that helps, > > michael > > >------------------------------------------------------------------------ > >От: Gonzalo <gonzalo(a)dense13.com> >Кому: chuck-users(a)lists.cs.princeton.edu >Отправлено: Fri Dec 09 02:11:54 GMT+03:00 2016 >Тема: Re: [chuck-users] Midi time problem > >Thanks Michael, > >This might be a bit over my head, but I'll look into it. Never checked >Chuck's source code before, at the very least it'll be fun. :) > >Gonzalo > > >On 08/12/16 23:28, Michael Heuer wrote: >> On Thu, Dec 8, 2016 at 3:52 PM, Gonzalo <gonzalo(a)dense13.com >> <mailto:gonzalo@dense13.com>> wrote: >> >> Hi, >> >> I'm using Bruce Murphy's MIDIsender class >> (http://www.rattus.net/~packrat/audio/ChucK/files/midisender.ck >> ><http://www.rattus.net/%7Epackrat/audio/ChucK/files/midisender.ck>) >> to generate MIDI from my Chuck code. I'm sending this MIDI to >> various virtual MIDI ports (using OSX's IAC Driver). Then I have >> various software instruments in Cubase, each one listening to one >of >> the virtual ports. Works well when I run my Chuck program, but if >in >> Cubase I arm the tracks and try to record the incoming MIDI, all >the >> events get 'collapsed' at the same time, specifically the moment >I >> click record. They do get recorded, but all starting at the same >time. >> >> This only happens if I want to record them, if I'm only playing, >> timing is fine. >> >> Using MidiMonitor I see that the time for all the MIDI events >> generated from Chuck is 0, that seems to be the issue. Any >thoughts >> on how I can change that? >> >> >> MidiMsg is defined as a four byte record >> >> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.h#L65 >> >> but ChucK only sets three bytes on send >> >> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L120 >> >> midisender.ck <http://midisender.ck> does the same. Is the unset >byte >> supposed to be the time? Suppose I should go read the spec. >> >> It appears time is written and read from files separately >> >> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L823 >> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L837 >> >> Not sure that helps, >> >> michael >> >> >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> > >-- >http://dense13.com >http://www.whole-play.com >https://www.30daygroove.com > > > >------------------------------------------------------------------------ > >От: Gonzalo <gonzalo(a)dense13.com> >Кому: chuck-users(a)lists.cs.princeton.edu >Отправлено: Fri Dec 09 02:27:04 GMT+03:00 2016 >Тема: Re: [chuck-users] Midi time problem > >I found this: > >"...the MIDI specification has different parts. One part describes MIDI > >"wire" protocol (messages sent between devices in real time), and >another part describes Standard MIDI Files (messages stored as events >in >"sequences"). In the latter part of the specification, each event >stored >in a standard MIDI file is tagged with a timing value that indicates >when that event should be played. By contrast, messages in MIDI wire >protocol are always supposed to be processed immediately, as soon as >they're received by a device, so they have no accompanying timing >values". > >(https://docs.oracle.com/javase/tutorial/sound/MIDI-messages.html) > >Might suggest there's no problem with the MidiMsg. Maybe it's a Cubase >issue? Someone suggested it's a Midi TimeCode issue, but I know nothing > >about that. I'll keep looking, but if anybody has any more info that'll > >be very welcome. > >Gonzalo > > > >On 09/12/16 00:11, Gonzalo wrote: >> Thanks Michael, >> >> This might be a bit over my head, but I'll look into it. Never >checked >> Chuck's source code before, at the very least it'll be fun. :) >> >> Gonzalo >> >> >> On 08/12/16 23:28, Michael Heuer wrote: >>> On Thu, Dec 8, 2016 at 3:52 PM, Gonzalo <gonzalo(a)dense13.com >>> <mailto:gonzalo@dense13.com>> wrote: >>> >>> Hi, >>> >>> I'm using Bruce Murphy's MIDIsender class >>> (http://www.rattus.net/~packrat/audio/ChucK/files/midisender.ck >>> ><http://www.rattus.net/%7Epackrat/audio/ChucK/files/midisender.ck>) >>> to generate MIDI from my Chuck code. I'm sending this MIDI to >>> various virtual MIDI ports (using OSX's IAC Driver). Then I have >>> various software instruments in Cubase, each one listening to >one of >>> the virtual ports. Works well when I run my Chuck program, but >if in >>> Cubase I arm the tracks and try to record the incoming MIDI, all >the >>> events get 'collapsed' at the same time, specifically the moment >I >>> click record. They do get recorded, but all starting at the same >>> time. >>> >>> This only happens if I want to record them, if I'm only playing, >>> timing is fine. >>> >>> Using MidiMonitor I see that the time for all the MIDI events >>> generated from Chuck is 0, that seems to be the issue. Any >thoughts >>> on how I can change that? >>> >>> >>> MidiMsg is defined as a four byte record >>> >>> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.h#L65 >>> >>> but ChucK only sets three bytes on send >>> >>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L120 >>> >>> midisender.ck <http://midisender.ck> does the same. Is the unset >byte >>> supposed to be the time? Suppose I should go read the spec. >>> >>> It appears time is written and read from files separately >>> >>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L823 >>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L837 >>> >>> Not sure that helps, >>> >>> michael >>> >>> >>> _______________________________________________ >>> chuck-users mailing list >>> chuck-users(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>> >> > >-- >http://dense13.com >http://www.whole-play.com >https://www.30daygroove.com > > > >------------------------------------------------------------------------ > >От: Eugene Martynec <eugenemartynec(a)gmail.com> >Кому: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >Отправлено: Fri Dec 09 03:08:56 GMT+03:00 2016 >Тема: Re: [chuck-users] Midi time problem > >Greetings > >Why not send each track instrument a separate midi channel on a single >port. Question is will Cubase do that. It used to only allow one midi >channel at a time when recording. Certainly that is no longer the case? > >On Dec 8, 2016 18:28, "Gonzalo" <gonzalo(a)dense13.com> wrote: > >> I found this: >> >> "...the MIDI specification has different parts. One part describes >MIDI >> "wire" protocol (messages sent between devices in real time), and >another >> part describes Standard MIDI Files (messages stored as events in >> "sequences"). In the latter part of the specification, each event >stored in >> a standard MIDI file is tagged with a timing value that indicates >when that >> event should be played. By contrast, messages in MIDI wire protocol >are >> always supposed to be processed immediately, as soon as they're >received by >> a device, so they have no accompanying timing values". >> >> (https://docs.oracle.com/javase/tutorial/sound/MIDI-messages.html) >> >> Might suggest there's no problem with the MidiMsg. Maybe it's a >Cubase >> issue? Someone suggested it's a Midi TimeCode issue, but I know >nothing >> about that. I'll keep looking, but if anybody has any more info >that'll be >> very welcome. >> >> Gonzalo >> >> >> >> On 09/12/16 00:11, Gonzalo wrote: >> >>> Thanks Michael, >>> >>> This might be a bit over my head, but I'll look into it. Never >checked >>> Chuck's source code before, at the very least it'll be fun. :) >>> >>> Gonzalo >>> >>> >>> On 08/12/16 23:28, Michael Heuer wrote: >>> >>>> On Thu, Dec 8, 2016 at 3:52 PM, Gonzalo <gonzalo(a)dense13.com >>>> <mailto:gonzalo@dense13.com>> wrote: >>>> >>>> Hi, >>>> >>>> I'm using Bruce Murphy's MIDIsender class >>>> (http://www.rattus.net/~packrat/audio/ChucK/files/midisender.ck >>>> ><http://www.rattus.net/%7Epackrat/audio/ChucK/files/midisender.ck>) >>>> to generate MIDI from my Chuck code. I'm sending this MIDI to >>>> various virtual MIDI ports (using OSX's IAC Driver). Then I >have >>>> various software instruments in Cubase, each one listening to >one of >>>> the virtual ports. Works well when I run my Chuck program, but >if in >>>> Cubase I arm the tracks and try to record the incoming MIDI, >all the >>>> events get 'collapsed' at the same time, specifically the >moment I >>>> click record. They do get recorded, but all starting at the >same >>>> time. >>>> >>>> This only happens if I want to record them, if I'm only >playing, >>>> timing is fine. >>>> >>>> Using MidiMonitor I see that the time for all the MIDI events >>>> generated from Chuck is 0, that seems to be the issue. Any >thoughts >>>> on how I can change that? >>>> >>>> >>>> MidiMsg is defined as a four byte record >>>> >>>> https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.h#L65 >>>> >>>> but ChucK only sets three bytes on send >>>> >>>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L120 >>>> >>>> midisender.ck <http://midisender.ck> does the same. Is the unset >byte >>>> supposed to be the time? Suppose I should go read the spec. >>>> >>>> It appears time is written and read from files separately >>>> >>>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L823 >>>> >https://github.com/ccrma/chuck/blob/master/src/midiio_rtmidi.cpp#L837 >>>> >>>> Not sure that helps, >>>> >>>> michael >>>> >>>> >>>> _______________________________________________ >>>> chuck-users mailing list >>>> chuck-users(a)lists.cs.princeton.edu >>>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>>> >>>> >>> >> -- >> http://dense13.com >> http://www.whole-play.com >> https://www.30daygroove.com >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >> > > >------------------------------------------------------------------------ > >_______________________________________________ >chuck-users mailing list >chuck-users(a)lists.cs.princeton.edu >https://lists.cs.princeton.edu/mailman/listinfo/chuck-users -- Простите за краткость, создано в K-9 Mail.

1 0

Fauck!!
by Romain Michon 04 Nov '16

04 Nov '16

Hi folks, We're happy to "officially" announce FaucK!!: a tool allowing to write Faust (http://faust.grame.fr) code within Chuck. FaucK is essentially a Chugin embedding the Faust LLVM compiler. The installation instructions and the documentation of FaucK can be found here: https://ccrma.stanford.edu/~ rmichon/fauck/ FaucK is still being beta tested, so we didn't make a new official chuck package for it yet. Feel free to try FaucK and report any bug. Have fun! Romain -- Romain Michon PhD Candidate Center for Computer Research in Music and Acoustics Stanford Universityhttp://ccrma.stanford.edu/~rmichon

1 0

new to ChucK
by Panos Amelidis 29 Oct '16

29 Oct '16

Hello list I was wondering if I could make this code even shorter. Please see attachment Thanks! Pan

1 0

ChucK courses
by Perry Cook 16 Oct '16

16 Oct '16

Thanks Christian!! I want to also point out that both books are available at substantial discount for Kadenze Members. The discounts easily pay for a couple of months of membership. And membership lets you engage in the courses more deeply (do the assignments and final projects). See you all in class!!! Prc > Date: Sat, 15 Oct 2016 23:21:13 +0000 > From: christian(a)christianhuygen.com > > Hello everybody, I just want to say I stumbled across the Kadenze course and think it's amazing, and it's free. You can really feel that ChucK was built to help people learn and enjoy and create. > > > I picked up the book also, item 5 in Spencer's list. It's a wonderful resource that works very well with the online course. > > > Also note that Kadenze offers Perry Cook's free course https://www.kadenze.com/courses/physics-based-sound-synthesis-for-games-and… which continues to expand ChucK wisdom into the realm of physical modeling, which is my main interest. There's a book for that too. The code in the book is written in C, but all the examples (downloadable) are in ChucK, and ChucK is what Perry is teaching in this course. > > > So I'd say that there's a very strong, lively educational and learning community around ChucK, and I was happy to support it by buying the books. ChucK has enabled me to do things I've always wanted to do, like making a cloud of 200 oscillators that drifts up and down in frequency, each a fixed but changing distance from the next. > > > I'm very grateful for the Kadenze courses and would encourage anybody to check them out. > > > sincerely > > > Christian Huygen > -----Original Message----- > From: Blixa2(a)gmx.net [mailto:Blixa2@gmx.net] > Sent: Friday, October 14, 2016 04:51 PM > To: chuck-users(a)lists.cs.princeton.edu > Subject: Re: [chuck-users] Manual for Version 1.3 (?) > > Thanks for the detailed answer and the links! > > Well, seems my first impression was wrong ;-) > > Blixa > > Gesendet: Freitag, 14. Oktober 2016 um 19:44 Uhr > Von: "Spencer Salazar" <spencer(a)ccrma.stanford.edu> > An: "ChucK Users Mailing List" <chuck-users(a)lists.cs.princeton.edu> > Betreff: Re: [chuck-users] Manual for Version 1.3 (?) > Hi, > Yes, the manual is not very well maintained right now- I think most of its content is still relevant to the language now, but small bits like how to install are a little different. Other, more up-to-date resources for learning include the language reference [1], which is not just a dry reference as the name would suggest, but a mix of a walkthrough and reference, and our free online video-based course [2], which is based on what we teach at California Institute of the Arts. The examples are a great resource (included when you install ChucK; go to File->Open Example in miniAudicle). Graham Coleman's "Notes on ChucK for Music" is also a good tutorial [3] and Perry's ChucKU has a lot of learning resources centralized in one place [4]. If you want to go a little deeper, the ChucK book [5] costs money but has a few free sample chapters. > > The individual who generously created and maintained the ChucK manual stepped down some time ago. Producing and maintaining high-quality documentation is a big job, and with all of the other resources available, the ChucK manual has not been the top priority. That being said we would welcome pull requests to ensure the manual is up-to-date, relevant, and useful (and actually there have been a few such PRs recently). > > In the last year we've been developing a number of major updates to the language and ecosystem. I have been working on miniAudicle for iPad, a tablet-oriented coding environment for ChucK, which is going into beta testing very soon, and a number of individuals have recently contributed to our growing collection of chugins [7]--its worth checking out the new ones for ChucK coders who are looking for new stuff to play with. Small but impactful bits like more informative exceptions have been developed (and are coming to a release soon). > > spencer > > [1] http://chuck.stanford.edu/doc/language/ > [2] https://www.kadenze.com/courses/introduction-to-programming-for-musicians-a… > [3] http://www.dtic.upf.edu/~gcoleman/chuck/tutorial/tutorial.html > [4] https://www.cs.princeton.edu/~prc/ChucKU/ > [5] https://www.manning.com/books/programming-for-musicians-and-digital-artists > [6] https://ccrma.stanford.edu/~spencer/mini-ipad/ > [7] https://github.com/ccrma/chugins > > > On Thu, Oct 13, 2016 at 12:05 PM, <Blixa2(a)gmx.net> wrote:Is there a specific reason, why the manual is only available for Version 1.2 (chuck.cs.princeton.edu/release/files/chuck_manual.pdf) and even this one is hidden and not directly accessible, neither from chuck.cs.princeton.edu/doc/ nor chuck.cs.princeton.edu/doc/learn/ . > > The first impression that I get from this is, that developers have lost their interest in ChucK. Do you think this impression is true? > > > > > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > --Spencer Salazar > Doctoral Candidate > Center for Computer Research in Music and Acoustics > Stanford University > > spencer(a)ccrma.stanford.edu > > +1 831.277.4654 > https://ccrma.stanford.edu/~spencer/ > > > > > > > > > > > > _______________________________________________ chuck-users mailing list chuck-users(a)lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > > > >

1 0

Re: [chuck-users] Manual for Version 1.3 (?)
by christian＠christianhuygen.com 15 Oct '16

15 Oct '16

Hello everybody, I just want to say I stumbled across the Kadenze course and think it's amazing, and it's free. You can really feel that ChucK was built to help people learn and enjoy and create. I picked up the book also, item 5 in Spencer's list. It's a wonderful resource that works very well with the online course. Also note that Kadenze offers Perry Cook's free course https://www.kadenze.com/courses/physics-based-sound-synthesis-for-games-and… which continues to expand ChucK wisdom into the realm of physical modeling, which is my main interest. There's a book for that too. The code in the book is written in C, but all the examples (downloadable) are in ChucK, and ChucK is what Perry is teaching in this course. So I'd say that there's a very strong, lively educational and learning community around ChucK, and I was happy to support it by buying the books. ChucK has enabled me to do things I've always wanted to do, like making a cloud of 200 oscillators that drifts up and down in frequency, each a fixed but changing distance from the next. I'm very grateful for the Kadenze courses and would encourage anybody to check them out. sincerely Christian Huygen -----Original Message----- From: Blixa2(a)gmx.net [mailto:Blixa2@gmx.net] Sent: Friday, October 14, 2016 04:51 PM To: chuck-users(a)lists.cs.princeton.edu Subject: Re: [chuck-users] Manual for Version 1.3 (?) Thanks for the detailed answer and the links! Well, seems my first impression was wrong ;-) Blixa Gesendet: Freitag, 14. Oktober 2016 um 19:44 Uhr Von: "Spencer Salazar" <spencer(a)ccrma.stanford.edu> An: "ChucK Users Mailing List" <chuck-users(a)lists.cs.princeton.edu> Betreff: Re: [chuck-users] Manual for Version 1.3 (?) Hi, Yes, the manual is not very well maintained right now- I think most of its content is still relevant to the language now, but small bits like how to install are a little different. Other, more up-to-date resources for learning include the language reference [1], which is not just a dry reference as the name would suggest, but a mix of a walkthrough and reference, and our free online video-based course [2], which is based on what we teach at California Institute of the Arts. The examples are a great resource (included when you install ChucK; go to File->Open Example in miniAudicle). Graham Coleman's "Notes on ChucK for Music" is also a good tutorial [3] and Perry's ChucKU has a lot of learning resources centralized in one place [4]. If you want to go a little deeper, the ChucK book [5] costs money but has a few free sample chapters. The individual who generously created and maintained the ChucK manual stepped down some time ago. Producing and maintaining high-quality documentation is a big job, and with all of the other resources available, the ChucK manual has not been the top priority. That being said we would welcome pull requests to ensure the manual is up-to-date, relevant, and useful (and actually there have been a few such PRs recently). In the last year we've been developing a number of major updates to the language and ecosystem. I have been working on miniAudicle for iPad, a tablet-oriented coding environment for ChucK, which is going into beta testing very soon, and a number of individuals have recently contributed to our growing collection of chugins [7]--its worth checking out the new ones for ChucK coders who are looking for new stuff to play with. Small but impactful bits like more informative exceptions have been developed (and are coming to a release soon). spencer [1] http://chuck.stanford.edu/doc/language/ [2] https://www.kadenze.com/courses/introduction-to-programming-for-musicians-a… [3] http://www.dtic.upf.edu/~gcoleman/chuck/tutorial/tutorial.html [4] https://www.cs.princeton.edu/~prc/ChucKU/ [5] https://www.manning.com/books/programming-for-musicians-and-digital-artists [6] https://ccrma.stanford.edu/~spencer/mini-ipad/ [7] https://github.com/ccrma/chugins On Thu, Oct 13, 2016 at 12:05 PM, <Blixa2(a)gmx.net> wrote:Is there a specific reason, why the manual is only available for Version 1.2 (chuck.cs.princeton.edu/release/files/chuck_manual.pdf) and even this one is hidden and not directly accessible, neither from chuck.cs.princeton.edu/doc/ nor chuck.cs.princeton.edu/doc/learn/ . The first impression that I get from this is, that developers have lost their interest in ChucK. Do you think this impression is true? _______________________________________________ chuck-users mailing list chuck-users(a)lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users --Spencer Salazar Doctoral Candidate Center for Computer Research in Music and Acoustics Stanford University spencer(a)ccrma.stanford.edu +1 831.277.4654 https://ccrma.stanford.edu/~spencer/ _______________________________________________ chuck-users mailing list chuck-users(a)lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

1 0

ChucK syntax highliting for LaTeX code listings
by Jean Menezes da Rocha 14 Oct '16

14 Oct '16

Hello, I am wondering if anyone ever wrote some ChucK style for highlighting source code in listings inside LaTeX documents. Is there anything like that, or should I try and do it from scratch? I would like to show some beautiful ChucK code in my thesis. Thanks in advance! -- Jean Menezes da Rocha Compositor Professor Doutorando em Música pela Universidade Federal da Bahia

4 7

miniAudicle and AZERTY keyboard
by Micha K 28 Sep '16

28 Sep '16

Hello, I am on a laptop with a French keyboard (AZERTY) in the moment and I have the problem that the editor doesn't recognize the '}' -> close bracket key. It doesn't seem that miniAudicle let define any key bindings. So I have to copy/paste the close bracket every time I use a loop or function which is a bit annoying. Anyone has the same problem with a non-english keyboardand is there any workaround ?

2 1

miniAudicle on Ubuntu 16.04
by Stuart McDonald 17 Sep '16

17 Sep '16

Hi, I've installed miniAudicle 1.3.3 on Ubuntu 16.04 and pressing the 'Start Virtual Machine' button causes a segfault. There's an error logged in syslog: Sep 17 15:28:04 stuart-laptop2 kernel: [ 2418.070094] miniAudicle[17168]: segfault at 0 ip null) sp 00007fff889d0a68 error 14 in miniAudicle[400000+2c3000] The same problem occurs for both linux-alsa and linux-pulse builds. I've tried compiling from miniAudicle github source but compilation fails with: ./miniAudicle.h:36:27: fatal error: chuck_compile.h: No such file or directory compilation terminated. makefile.qt-alsa:473: recipe for target 'build/mAMainWindow.o' failed make[1]: *** [build/mAMainWindow.o] Error 1 make[1]: Leaving directory '/home/stuart/music/builds/miniAudicle/src' makefile:38: recipe for target 'linux-alsa' failed make: [linux-alsa] Error 2 (ignored) This is similar to the bug outlined in https://lists.cs.princeton.edu/pipermail/chuck-users/2013-September/007358.… except the solution there is already present in miniAudicle.pro. Any suggestions appreciated. Thanks! Stuart

2 1

anybody still use this thing?
by Colton Hill 08 Sep '16

08 Sep '16

Yo, it's Colton. I am a 15 year old boy in the US, and I am blind. ChucK has been the only audio language I can pick up and use, thanks to it's command line support. The mini audical is completely unusable, just like other ides for things such as super collider. I do have some questions about chuck, and I was wondering if anybody still used this thing that would be willing to answer. I need a guru!

10 19