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

Re: [chuck-users] reading random sample
by Julian Faust 29 Jan '15

29 Jan '15

If you know in advance what set of files to choose from, you could start by reading in a text file with all the file paths then make the random selection in chuck. This avoids system calls, which can mess with the timing of your real-time application since the chuck VM misses the time spent doing the system call (i.e. Std.system(“sleep 1”) causes mayhem). But if you want to be able to add files to a directory on the fly I think you have to do the system call. Just be aware of the timing issue - maybe it can be done in a thread. -Julian > From: Atte <atte(a)youmail.dk> > Subject: [chuck-users] reading random sample > Date: January 28, 2015 at 6:32:29 AM GMT-5 > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Reply-To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > > > Hi > > I'm trying to write a function that reads a random samples from a > directory into a SndBuf. I'm not aware of the the necessary > functionality being available in chuck, so I wrote a bash script that > picks a random file from a directory and writes the name with full path > to /tmp/random_file. When I call Std.system() I get a warning that I > should use --caution-to-the-wind. This works well in chuck, but in fact > I'm in miniAudicle, how do I call miniAudicle with that option? Just doing > > $ miniAudicle --caution-to-the-wind > > makes miniAudicle think I want to start with a blank file called > "--caution-to-the-wind"... > > -- > Atte > > http://atte.dk http://a773.dk > > > > From: Atte <atte(a)youmail.dk> > Subject: Re: [chuck-users] reading random sample > Date: January 29, 2015 at 6:25:08 AM GMT-5 > To: chuck-users(a)lists.cs.princeton.edu > Reply-To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > > > On 01/28/2015 12:32 PM, Atte wrote: >> how do I call miniAudicle with that option? > > Nevermind, I'm back to chuck, seems much more stable... > > -- > Atte > > http://atte.dk http://a773.dk >

2 1

reading random sample
by Atte 29 Jan '15

29 Jan '15

Hi I'm trying to write a function that reads a random samples from a directory into a SndBuf. I'm not aware of the the necessary functionality being available in chuck, so I wrote a bash script that picks a random file from a directory and writes the name with full path to /tmp/random_file. When I call Std.system() I get a warning that I should use --caution-to-the-wind. This works well in chuck, but in fact I'm in miniAudicle, how do I call miniAudicle with that option? Just doing $ miniAudicle --caution-to-the-wind makes miniAudicle think I want to start with a blank file called "--caution-to-the-wind"... -- Atte http://atte.dk http://a773.dk

1 1

Debugging Segmentation fault: 11
by Gonzalo 28 Jan '15

28 Jan '15

Hi, On a project I'm working on, I sometimes get a "Segmentation fault: 11" error, and the program crashes. But I can't figure out when it happens, and cannot reproduce it. It's a big project, with many components communicating via events, and I have no idea who's triggering the problem. My question is how would you go about debugging this? Any ideas what can be triggering it? It sounds very generic... Probably unrelated, but just in case, I also got this (only once so far): chuck(22226,0x7fff790ee310) malloc: *** error for object 0x1028f3408: incorrect checksum for freed object - object was probably modified after being freed. *** set a breakpoint in malloc_error_break to debug Abort trap: 6 Thanks! Gonzalo

5 15

Re: [chuck-users] WvOut sample size (????????? ????????)
by јеромонах Виталије 27 Jan '15

27 Jan '15

Thank you Michael Heuer, for your reply. I have already installed jackd and QJackCtl, but I am not so happy with it. It is much easer to work with ChucK compiled to use alsa and just start one single program (* chuck) than to wary about starting jackd, controlling it... Very likely I am missing something about jack but I have never made it to work smoothly. There were always some troubles with applications that utilize sound card when I run jack server, so I gave up. On the other hand, I don't understand why ChucK can not use sound card as any other application on my computer. For example: command line mp3 player mpg321 can play a mp3-file simultaneously with other programs. I can start several mpg321 commands from terminal and there will be no complains about hardware device being used. The same is with other audio/video players on my computer. None of them requires exclusively access to sound card hardware, and they all can cooperate smoothly. I would like very much if ChucK could do so. Vitalije

3 2

Re: [chuck-users] WvOut sample size (????????? ????????) (Joel Matthys)
by јеромонах Виталије 27 Jan '15

27 Jan '15

> Hello Vitalije. > > You can compile ChucK with 'make linux-pulse' to use the PulseAudio > server. That will allow you to use other audio applications at the > same time. > > You are right that jackd is not as easy to work with as alsa, but it > is very useful when you want to send sound from one application to > another. It is powerful in the right situation. > > Joel Thank you Joel, I have compiled ChucK as you have suggested and now it works very well indeed. :-) Vitalije.

1 0

Re: [chuck-users] WvOut sample size (????????? ????????)
by јеромонах Виталије 26 Jan '15

26 Jan '15

Thank you Perry Cook, for your reply. I have found what was the source of my main problem. It had nothing to do with quality, or sample size of generated file. Actually I was working on files located on an USB memory stick, and the stick was plugged in a USB hub device located very near speaker. When ChucK was executing file there were no interference between the USB cable and speaker cable, but when I was playing recorded file from the same USB there were some interference between cables that sounded like cracks. When I copied generated file to my desktop and played it from there, cracks disappeared :-) Maybe this will help somebody else if one run into similar problem.

1 0

Re: [chuck-users] WvOut sample size (????????? ????????)
by Perry Cook 24 Jan '15

24 Jan '15

It's likely just overloading and clipping on the output file. WvOut and WvOut2 must quantize to 16 bits to write out the file. So numbers that are greater than +/- 1.0 will overload. If this is really the problem (likely), then there's an easy fix. There's a method called fileGain() that sets an extra gain before the file is written out. The default is of course 1.0, but you can change it to anything. Example useage: MyPatch => WvOut bob => blackhole; "mywavfile.wav" => bob.wavFilename; 0.5 => bob.fileGain; // This is your friend for writing non-clipped files while (now < then) { // do whatever; } bob.closeFile(); Hope this helps. If not let us know and we'll dig deeper. PRC > On Jan 24, 2015, at 9:00 AM, chuck-users-request(a)lists.cs.princeton.edu wrote: > > 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. WvOut sample size (????????? ????????) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 23 Jan 2015 20:22:21 +0100 > From: ????????? ???????? <vitalije(a)kviziracija.net> > To: chuck-users(a)lists.cs.princeton.edu > Subject: [chuck-users] WvOut sample size > Message-ID: <54C29F6D.8070701(a)kviziracija.net> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hello, > I am a new member of this list. > I have made some ChucK program that sounds good when performed by ChucK > VM. However, when I record this music through WvOut in to file and later > play recorded file using system player, I hear some cracks (distortions, > noise). > It seems to me that it is some conversion taking place during recording. > In the documentation of WvOut class it is suggested that MATLAB file > format will write 64-bit floats. But even with that precision I get the > same sound in file. I have looked in to the source code and found that > every method of WvOut class (WvOut_ctrl_<filetype>Filename) opens file > with the same 16-bit sample-size (Stk::STK_SINT16). > > I have tried naively to change that parameter into Stk::STK_SINT32, and > recompiled successfully ChucK, but the quality of recorded sound was not > improved. Actually, file was again 16-bit signed encoded. > > What can I do to improve quality of recording. > > My computer is amd-64 Ubuntu 14.04. I have compiled ChucK with 'make > linux-alsa' command. > > PS: I tried to record sound from system sound-card by using some other > programs for recording, but with no success. Either ChucK could not > access sound-card or a recording program could not access sound-card. It > seems that ChucK insists on having exclusive rights over sound-card and > doesn't want to share it with other programs. Even if in my browser is > opened some site that uses sound, ChucK refuses to start. > > Vitalije > > > ------------------------------ > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users > > > End of chuck-users Digest, Vol 114, Issue 4 > *******************************************

2 1

WvOut sample size
by јеромонах Виталије 23 Jan '15

23 Jan '15

Hello, I am a new member of this list. I have made some ChucK program that sounds good when performed by ChucK VM. However, when I record this music through WvOut in to file and later play recorded file using system player, I hear some cracks (distortions, noise). It seems to me that it is some conversion taking place during recording. In the documentation of WvOut class it is suggested that MATLAB file format will write 64-bit floats. But even with that precision I get the same sound in file. I have looked in to the source code and found that every method of WvOut class (WvOut_ctrl_<filetype>Filename) opens file with the same 16-bit sample-size (Stk::STK_SINT16). I have tried naively to change that parameter into Stk::STK_SINT32, and recompiled successfully ChucK, but the quality of recorded sound was not improved. Actually, file was again 16-bit signed encoded. What can I do to improve quality of recording. My computer is amd-64 Ubuntu 14.04. I have compiled ChucK with 'make linux-alsa' command. PS: I tried to record sound from system sound-card by using some other programs for recording, but with no success. Either ChucK could not access sound-card or a recording program could not access sound-card. It seems that ChucK insists on having exclusive rights over sound-card and doesn't want to share it with other programs. Even if in my browser is opened some site that uses sound, ChucK refuses to start. Vitalije

1 0

ICAD2015 - call for submission
by Visda Goudarzi 21 Jan '15

21 Jan '15

Dear all, (With apologies for cross posting, please distribute!) This is a reminder that the call for participation for ICAD15 is currently open. http://icad15.iem.at Call for Papers, Posters, Extended Abstracts, Music, Installations, and Workshops - ICAD 2015 “ICAD in Space: Interactive Spatial Sonification” The 21st International Conference on Auditory Display July 6 - 7 Workshops and Student Think Tank July 8 - 10 Conference University of Music and Performing Arts and Technical University of Graz, Austria. The conference is organised by the Institute of Electronic Music and Acoustics (IEM). IEM is one of the leading institutions in the field of audio engineering and computer music. As part of the University of Music and Performing Arts Graz, IEM is a multidisciplinary institution, whose general mission is to bridge the gap between science and the arts. As a unique characteristic, IEM focuses on sonification as part of its research in computer music. IEM facilities include laboratories and performance spaces such as CUBE, which are equipped with spatial audio and motion tracking systems. Since 2014, IEM hosts the Sonic Interaction Design (SID) lab, in which interactive sound systems are designed and evaluated. ICAD is a highly interdisciplinary conference with relevance to researchers, practitioners, artists, and graduate students working with sound to convey and explore information. The conference is unique in its specific focus on auditory displays and the range of interdisciplinary issues related to their use. Like its predecessors, ICAD15 will be a single-track conference, open to all, with no membership or affiliation requirements. In addition to ICAD's core interests, we would like to take the opportunity of the conference being held at IEM to highlight this yearʼs theme ICAD in Space: Sonification, Sonic Interaction Design, and Spatial Audio. ::::::::::::::::: KEY DATES ::::::::::::::::: 15 February 2015 Submission of Papers, Posters, Music, and Installations 15 March 2015 Submission of Workshops 15 April 2015 Submission of Extended Abstracts 15 April 2015 Notification of acceptance for Workshops 01 May 2015 Notification of acceptance for Papers, Posters, Music, and Installations 15 May 2015 Notification of acceptance for Extended Abstracts 01 June 2015 Camera-Ready deadline ::::::::::::::::: AREAS OF INTEREST ::::::::::::::::: Relevant areas for ICAD include but are not limited to: Auditory Display: - Aesthetics, Culture, & Philosophy - Design, Theory & Methods - Technology: Tools & Applications - Perceptual and Cognitive Aspects - Usability & Evaluation - Accessibility Special Focus of ICAD15: - Sonification: - Exploration of Data through Sound - Sonification as Art - Sonic Interaction Design - Interaction design - Input technologies - Auditory Information Design - Spatial Audio - Binaural virtual acoustics - Loudspeaker-based sound field synthesis Accepted papers will be included in the published proceedings and made publicly available in the Georgia Tech SMARTech system (http:// smartech.gatech.edu/). The types of submissions solicited for ICAD15 include: ::::::::::::::::: PAPERS AND POSTERS::::::::::::::::: Paper and poster submissions will be 4-8 pages in length, including all figures and references. Typical paper contributions are between 6 - 8 pages, and typical poster contributions are 4 - 5 pages long. Full papers should describe work that offers a substantial contribution to the field of auditory display. Authors of accepted papers will be invited to give an oral presentation of their work, and at least one author must present the work at the conference for the paper to appear in the proceedings. Poster submissions should describe both finished work and work in late stages of progress. Work that is complete enough that meaningful conclusions can be drawn at the time of submission are encouraged. Authors of accepted submissions will be invited to participate in a poster and/or demonstration session, and at least one author must present the work at the conference for the paper to appear in the published proceedings. When weighing the decision to submit to poster and demonstration sessions, we encourage authors to consider their work in relation to the potential positive benefits (both to authors and their audiences) afforded by the personal interactions that occur in this type of session. Authors of selected full papers will be invited to submit an extended version (up to 12 pages) of their papers for publication in a Special Issue of the Journal on Multimodal User Interfaces (JMUI): Auditory Display. (http:// www.springer.com/computer/hci/journal/12193) ::::::::::::::::: EXTENDED ABSTRACTS ::::::::::::::::: Extended abstracts include, but are not limited to late-breaking results, works in early stages of progress, novel methodologies, unique or controversial theoretical positions, and discussions of unsuccessful research or null findings. Submissions for extended abstracts require a proceedings paper of up to 2 pages in length. Authors of accepted abstracts will be invited to give a short presentation of their work, and at least one author must present the work at the conference for the abstract to appear in the published proceedings. The deadline of the extended abstracts is later to allow very recent contributions in the field. Papers Co-Chairs Visda Goudarzi and Areti Andreopoulou papers.icad15(a)iem.at ::::::::::::::::: MUSIC AND INSTALLATIONS::::::::::::::::: We invite submissions of music and sound installations. Sonification should be a constitutive element of the proposed works. Priority will be given to works employing space and interaction as additional dimensions to an artistic data exploration. We therefore especially encourage the submission of multichannel electroacoustic or acousmatic pieces and interactive sound installations. The works will be reviewed by an international panel of sound and sonification experts. Preference will be given to submissions that are technically feasible and have a clear documentation of the setup. At least one of the authors who wish to have their works presented at ICAD15 must register and attend to the conference. As we would like to extend the presentation of these works beyond the time limits of the conference, authors of accepted works are encouraged to present their work also online using the Research Catalogue (http://www.researchcatalogue.net), an international database for artistic research. The conference page will provide a portal to these presentations. Music Co-Chairs Johannes Zmölnig and Gerhard Eckel music.icad15(a)iem.at ::::::::::::::::: WORKSHOPS :::::::::::::::: ICAD workshops and tutorials provide in-depth opportunities for conference attendees to discuss and explore important topics in the field of auditory display with like-minded researchers and practitioners. Please submit concepts for “hands-on” workshops or discussion platforms, possibly allowing participants to contribute, but no paper sessions on their own. Focus areas can range from applications and programming methodologies to interdisciplinary research skills, emerging concepts, and challenge problems. Space, facilities, technical support, and the number of sessions that can be accepted are limited, so early submission of proposals is encouraged. Workshop and tutorial organizers are expected to collaborate with the conference committee, issue calls for participation, gather and review contributed materials (if appropriate), and decide upon the final program for their session. Workshop Co-Chairs Franz Zotter and Derek Brock workshop.icad15(a)iem.at ::::::::::::::::: SONIFICATION CONTEST :::::::::::::::: The call for the Sonification Contest will be released in early 2015. ::::::::::::::::: STUDENT THINK TANK :::::::::::::::: The call for the Student Think Tank will be released in early 2015. We will provide child care during the conference and workshops. If you travel with a kid/ kids please drop us an email ahead of time. For more information on submission in different categories please refer to the conference website: http://icad15.iem.at Conference Co-Chairs Katharina Vogt and Ypatios Grigoriadis chair.icad15(a)iem.at

1 0

Re: [chuck-users] Inheritance and Arrays
by Casper Schipper 03 Jan '15

03 Jan '15

You could try assign subclass instances to arrays of it's parent class, as shown in the snippet bellow. It is not a very elegant syntax, but at least it makes your plus(A arg[]) function work like you would expect. best, Casper class A { 42 => int a; fun void print() { <<<a>>>; } } class B extends A { 101 => int b; fun void print() { <<<b>>>; } } fun void plus(A arg[]) { for (0 => int i; i < arg.size() ; i++) { arg[i].a ++; arg[i].print(); } } // first declare the 'container'. A @ foo[2]; // use new operator to create B instances. (new B) @=> foo[0]; (new B) @=> foo[1]; 1 => foo[0].a; 2 => foo[1].a; plus(foo); // notice, foo[0] & foo[1] still behave like a B instance. <<<"foo[0].a", foo[0].a>>>; <<<"foo[1].a", foo[1].a>>>; > > 1. Inheritance and Arrays (Julien Saint-Martin) > > From: Julien Saint-Martin <julien.saintmartin(a)googlemail.com> > To: chuck-users(a)lists.cs.princeton.edu > Date: 2 januari 2015 16:15:54 CET > Reply-To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] Inheritance and Arrays > > > Hi! > > I would like to pass arrays of objects to a function taking an array of parent class as argument. > I try different things but unfortunately I have compilation errors each time. > > The following example works with no array: > > class A { > int a; > } > > class B extends A { > int b; > } > > fun void plus(A arg) { > arg.a ++; > } > > B foo; > > 1 => foo.a; > plus (foo); > <<<"foo.a", foo.a>>>; > > > > > But When I try the same with arrays it doesn't compile: > [l13.ck]:line(22): argument type(s) do not match: > [l13.ck]:line(22): ... for function 'plus(...)' ... > [l13.ck]:line(22): ...(please check the argument types) > > class A { > int a; > } > > class B extends A { > int b; > } > > fun void plus(A arg[]) { > for (0 => int i; i < arg.size() ; i++) { > arg[i].a ++; > } > > } > > B foo[2]; > > 1 => foo[0].a; > 2 => foo[1].a; > plus (foo); > <<<"foo[0].a", foo[0].a>>>; > <<<"foo[1].a", foo[1].a>>>; > > > Any idea ? > > Thanks in advance and Happy new year!! > > Julien > > > > > _______________________________________________ > chuck-users mailing list > chuck-users(a)lists.cs.princeton.edu > https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

1 0