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

memory usage
by Mario Buoninfante 16 Apr '20

16 Apr '20

Hi, I was trying to better understand how ChucK deals with memory management. I know there's no garbage collector in place and I also checked on the mailing list, where I found several really interesting conversations about this topic. But still, I've got this scenario where the memory in use keeps growing.: >From terminal I launch: chuck --loop then I run several times: chuck + gc_empty.ck every time I wait that this ends first. gc_empty.ck contains just 1 line: 1::second => now; at the same time I'm monitoring chuck using top (on MacOS High Sierra 10.13.1) and I get the following values for MEMORY: as soon as I launch ChucK: 9008K 1st time I run "gc_empty.ck": 9108K 2nd time I run "gc_empty.ck": 9112K 3rd time I run "gc_empty.ck": 9196K Why is ChucK using more and more memory? Sorry if this is maybe a silly question. Cheers, Mario

1 0

Re: [chuck-users] Oscillosope UI
by Mario Buoninfante 15 Apr '20

15 Apr '20

Hi Spencer, Amazing, I'll have a look at the links you shared, it's good to have a starting point :) thanks. About the Chugins I'll make a PR then, I think that due to their simplicity and general-purpose nature, it could be useful to have them in the Chugin repo. Cheers, Mario -- electronic musician, sound artist, creative coder, QA engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante On 15 Apr 2020 19:23, Spencer Salazar <spencer.salazar(a)gmail.com> wrote: > > Also, feel free to make a PR if you youre chugins are cross-platform and you want to share any of them in the main chugin repo! > > Spencer > > > > On Wed, Apr 15, 2020 at 10:00 AM Spencer Salazar <spencer.salazar(a)gmail.com> wrote: >> >> Hey Mario- >> >> Yep, Perry's got the right idea. The big cleanup in the ChucK 1.4 update left out a component that had been built to support GUI chugins, but two alpha-status examples you can look at are MAUI.chug and chugl (ChucK GL). These are currently Mac only. >> https://github.com/spencersalazar/MAUI.chug >> https://github.com/spencersalazar/chugl >> >> I recently spent a little time reimplementing support for these GUI chugins, which works in the current master branch of ChucK or will work in an upcoming 1.4.0.1 release that is being prepared soon. >> >> The basic idea is that most GUI frameworks expect to operate on a main thread of sorts. Chugins that want to run a GUI can submit a hook/callback for chuck to call in its main thread, which is otherwise mostly idle (chuck's VM and audio synth are running in a separate real-time audio thread). >> >> There are other considerations such as what happens if two GUI chugins compete with each other, how GUI chugins are meant to work in miniAudicle, Windows/Linux, etc. But the basic idea is there / not crazy! >> >> Spencer >> >> >> >> On Wed, Apr 15, 2020 at 6:50 AM Mario Buoninfante <mario.buoninfante(a)gmail.com> wrote: >>> >>> Hi, >>> >>> Recently I've been poking around with Chugins and created a couple of things I thought were 'missing' in the official ChucK and Chugin repos, UGens like Wrap, Clip, Sample and Hold, etc. (https://github.com/mariobuoninfante/ChucK_chugins), and I was thinking about adding an oscilloscope as well. >>> Recently I also put together a clunky class that allows you to plot things using gnuplot, but it's an offline thing, then you need to use Std.system() (that means using --caution-to-the-wind), I mean it's not ideal to be honest, especially if you're looking for an oscilloscope. >>> I was wondering, would a Chugin be the right thing to work on to create an oscilloscope? >>> I never dealt with UIs before, so I could be saying something completely naive here, but I was thinking about having a Chugin you can connect UGens to then display their waveform. >>> Then have methods that allow to change the oscilloscope settings (ie x-axis and y-axis resolution, etc.). >>> Does anybody have any experience with this kind of things? Chugins with UIs? >>> Is it even sensible? >>> >>> Cheers, >>> Mario >>> >>> _______________________________________________ >>> chuck-users mailing list >>> chuck-users(a)lists.cs.princeton.edu >>> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

1 0

Oscillosope UI
by Mario Buoninfante 15 Apr '20

15 Apr '20

Hi, Recently I've been poking around with Chugins and created a couple of things I thought were 'missing' in the official ChucK and Chugin repos, UGens like Wrap, Clip, Sample and Hold, etc. ( https://github.com/mariobuoninfante/ChucK_chugins), and I was thinking about adding an oscilloscope as well. Recently I also put together a clunky class that allows you to plot things using gnuplot, but it's an offline thing, then you need to use Std.system() (that means using --caution-to-the-wind), I mean it's not ideal to be honest, especially if you're looking for an oscilloscope. I was wondering, would a Chugin be the right thing to work on to create an oscilloscope? I never dealt with UIs before, so I could be saying something completely naive here, but I was thinking about having a Chugin you can connect UGens to then display their waveform. Then have methods that allow to change the oscilloscope settings (ie x-axis and y-axis resolution, etc.). Does anybody have any experience with this kind of things? Chugins with UIs? Is it even sensible? Cheers, Mario

2 2

Re: [chuck-users] Chugin for UI (oscilloscope)
by Perry R. Cook 15 Apr '20

15 Apr '20

Well, MAUI is a chugin, only for Mac, so there is precedent for UI in Chugin. MAUI is currently broken in the command line, only working in MiniAudicle. Perhaps Spencer/Ge can chime in on the vagaries of doing UI/graphics via Chugin?? Prc from MyiPhone > On Apr 15, 2020, 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. Oscillosope UI (Mario Buoninfante) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Apr 2020 14:48:25 +0100 > From: Mario Buoninfante <mario.buoninfante(a)gmail.com> > To: ChucK <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] Oscillosope UI > Message-ID: > <CAHs=M8TSCUvfz-Ry5Q-ifht4Y9MMxnZV6H_L74zosDi+We3J5A(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi, > > Recently I've been poking around with Chugins and created a couple of > things I thought were 'missing' in the official ChucK and Chugin repos, > UGens like Wrap, Clip, Sample and Hold, etc. ( > https://github.com/mariobuoninfante/ChucK_chugins), and I was thinking > about adding an oscilloscope as well. > Recently I also put together a clunky class that allows you to plot things > using gnuplot, but it's an offline thing, then you need to use Std.system() > (that means using --caution-to-the-wind), I mean it's not ideal to be > honest, especially if you're looking for an oscilloscope. > I was wondering, would a Chugin be the right thing to work on to create an > oscilloscope? > I never dealt with UIs before, so I could be saying something completely > naive here, but I was thinking about having a Chugin you can connect UGens > to then display their waveform. > Then have methods that allow to change the oscilloscope settings (ie x-axis > and y-axis resolution, etc.). > Does anybody have any experience with this kind of things? Chugins with UIs? > Is it even sensible? > > Cheers, > Mario >

2 1

Re: [chuck-users] Closing MIDI Ports (Mario asks)
by Mario Buoninfante 28 Mar '20

28 Mar '20

Hi Perry, Thanks for the suggestion, I'll try that out. In fact I realized that unfortunately killing the shred, or terminating the program is not enough to close the ports. You need to terminate ChucK. An alternative could be that of using Std.system("chuck midi_config.ck"). At this point I could simply print the port names on the terminal. Anyway, I'll try both and see. Cheers, Mario -- electronic musician, sound artist, creative coder, QA engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfanteOn 27 Mar 2020 16:09, "Perry R. Cook" <prc(a)cs.princeton.edu> wrote: > > I’m not sure if they can be closed, but as long as you don’t chuck them to now, the extra ones really shouldn’t take up (much) computational resources. > > One option would be to first run a MIDIConfig.ck file that opens them all and writes all the names and numbers into a MIDICONFIG.txt file. Then when you run your main file, it reads that and only opens the one(s) you need. Or your first MIDIConfig.ck file could pick the one(s) you need and write only them into the temp file. > > I’ve done this for PLOrk pieces, to figure out if laptops have accelerometers, and what orientation those are. > > prc > > from MyiPhone > >> On Mar 27, 2020, 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. Closing MIDI ports (mario buoninfante) >> >> >> ---------------------------------------------------------------------- >> >> Message: 1 >> Date: Thu, 26 Mar 2020 19:51:41 +0000 >> From: mario buoninfante <mario.buoninfante(a)gmail.com> >> To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> >> Subject: [chuck-users] Closing MIDI ports >> Message-ID: <dc574e2e-9f93-cb07-c743-38f88fa575e9(a)gmail.com> >> Content-Type: text/plain; charset="utf-8"; Format="flowed" >> >> Hi, >> >> >> Is it possible to close a MIDI port? >> >> I'm working on a MIDI class, and to print all the available ports, I >> open them one at the time and get the name. Then I end up with tons of >> open MIDI ports I'm not actually using. >> >> Apart from this, another user case could be a live set where different >> scripts are launched and each of them wants to talk to a specific MIDI >> port. Doing so one ends up with a lot of /leftovers/. >> >> >> Cheers, >> >> Mario >> >> -- >> electronic musician, sound artist, creative coder, QA engineer >> https://vimeo.com/creativecodingsalerno >> http://mbuoninfante.tumblr.com/ >> https://github.com/mariobuoninfante >> https://bitbucket.org/mariobuoninfante/ >> >>

1 0

Re: [chuck-users] Closing MIDI Ports (Mario asks)
by Perry R. Cook 27 Mar '20

27 Mar '20

I’m not sure if they can be closed, but as long as you don’t chuck them to now, the extra ones really shouldn’t take up (much) computational resources. One option would be to first run a MIDIConfig.ck file that opens them all and writes all the names and numbers into a MIDICONFIG.txt file. Then when you run your main file, it reads that and only opens the one(s) you need. Or your first MIDIConfig.ck file could pick the one(s) you need and write only them into the temp file. I’ve done this for PLOrk pieces, to figure out if laptops have accelerometers, and what orientation those are. prc from MyiPhone > On Mar 27, 2020, 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. Closing MIDI ports (mario buoninfante) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 26 Mar 2020 19:51:41 +0000 > From: mario buoninfante <mario.buoninfante(a)gmail.com> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: [chuck-users] Closing MIDI ports > Message-ID: <dc574e2e-9f93-cb07-c743-38f88fa575e9(a)gmail.com> > Content-Type: text/plain; charset="utf-8"; Format="flowed" > > Hi, > > > Is it possible to close a MIDI port? > > I'm working on a MIDI class, and to print all the available ports, I > open them one at the time and get the name. Then I end up with tons of > open MIDI ports I'm not actually using. > > Apart from this, another user case could be a live set where different > scripts are launched and each of them wants to talk to a specific MIDI > port. Doing so one ends up with a lot of /leftovers/. > > > Cheers, > > Mario > > -- > electronic musician, sound artist, creative coder, QA engineer > https://vimeo.com/creativecodingsalerno > http://mbuoninfante.tumblr.com/ > https://github.com/mariobuoninfante > https://bitbucket.org/mariobuoninfante/ > >

1 0

Closing MIDI ports
by mario buoninfante 26 Mar '20

26 Mar '20

Hi, Is it possible to close a MIDI port? I'm working on a MIDI class, and to print all the available ports, I open them one at the time and get the name. Then I end up with tons of open MIDI ports I'm not actually using. Apart from this, another user case could be a live set where different scripts are launched and each of them wants to talk to a specific MIDI port. Doing so one ends up with a lot of /leftovers/. Cheers, Mario -- electronic musician, sound artist, creative coder, QA engineer https://vimeo.com/creativecodingsalerno http://mbuoninfante.tumblr.com/ https://github.com/mariobuoninfante https://bitbucket.org/mariobuoninfante/

1 0

compiling miniAudicle on ubuntu 18.04
by Forrest Curo 25 Mar '20

25 Mar '20

The instructions for doing this when chucK 14 is already installed & working are basically unclear, ie changing some unnamed link from src in the miniAudicle directory to point to the directory containing chucK. But simply trying to compile this for whatever chucK the package contains: forrest@salvage:~/miniAudicle-1.3.5.2/src$ make linux-alsa qmake-qt4 "RTAUDIO_BACKEND=ALSA" -o makefile.qt-alsa miniAudicle.pro make -f makefile.qt-alsa make[1]: Entering directory '/home/forrest/miniAudicle-1.3.5.2/src' /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mAMainWindow.ui -o build/ui_mAMainWindow.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/madocumentview.ui -o build/ui_madocumentview.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mAConsoleMonitor.ui -o build/ui_mAConsoleMonitor.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mAVMMonitor.ui -o build/ui_mAVMMonitor.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mAPreferencesWindow.ui -o build/ui_mAPreferencesWindow.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mAExportDialog.ui -o build/ui_mAExportDialog.h /usr/lib/x86_64-linux-gnu/qt4/bin/uic qt/mADeviceBrowser.ui -o build/ui_mADeviceBrowser.h g++ -c -m64 -pipe -D__LINUX_ALSA__ -D__CK_SNDFILE_NATIVE__ -D__LINUX__ -D__PLATFORM_LINUX__ -Ichuck/src -DHAVE_CONFIG_H -O3 -w -D_REENTRANT -DHAVE_CONFIG_H -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++-64 -I. -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtGui -I/usr/include/qt4 -Ibuild -Ibuild -o build/mAMainWindow.o qt/mAMainWindow.cpp In file included from qt/mAMainWindow.cpp:28:0: qt/madocumentview.h:31:10: fatal error: Qsci/qscilexer.h: No such file or directory #include <Qsci/qscilexer.h> ^~~~~~~~~~~~~~~~~~ compilation terminated. makefile.qt-alsa:466: recipe for target 'build/mAMainWindow.o' failed make[1]: *** [build/mAMainWindow.o] Error 1 make[1]: Leaving directory '/home/forrest/miniAudicle-1.3.5.2/src' makefile:38: recipe for target 'linux-alsa' failed make: [linux-alsa] Error 2 (ignored) [help?]

1 2

Re: [chuck-users] float to int
by Perry Cook 10 Mar '20

10 Mar '20

Also, A more obvious and Java-like way to convert float to int is the built-in function: Std.ftoi(myFloat) => int myInt; Sent from my iPhone > On Mar 10, 2020, at 8:51 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. Std.fabs() keeps giving float (herman verbaeten) > 2. Re: Std.fabs() keeps giving float (Jack Atherton) > > ---------------------------------------------------------------------- > From: Jack Atherton <lja(a)ccrma.stanford.edu> > To: ChucK Users Mailing List <chuck-users(a)lists.cs.princeton.edu> > Subject: Re: [chuck-users] Std.fabs() keeps giving float > Message-ID: > <CAEygkh_FzLPeDuZQCPtgc4e0V=+BJwDU7-H+X8=ku8JJ4ZvkFw(a)mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > $ is the explicit cast operator -- see > https://chuck.cs.princeton.edu/doc/language/oper.html > > For example, Std.fabs( timedur ) $ int => period; > > ~Jack > >> On Mon, Mar 9, 2020 at 4:05 PM herman verbaeten <hverb54(a)hotmail.com> wrote: >> >> Hi, >> >> In your archives i found a way to cast dur as float. But every attempt to >> convert float to int >> failes somehow... Error message:* "[test dur-int.ck >> <http://dur-int.ck>]:line(4): cannot resolve operator '=>' on types 'float' >> and 'int'..."* >> >> 4400::ms => dur pduration; >> int period; >> pduration/1::samp => float timedur; >> <<<Std.fabs(timedur) => period>>>; >> >> kind regards, >> >> Herman >> _______________________________________________ >> chuck-users mailing list >> chuck-users(a)lists.cs.princeton.edu >> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users >>

1 0

using global variables as arguments in sporking functions
by herman verbaeten 10 Mar '20

10 Mar '20

Hi, I'm having a problem passing a changing parameter(by an LFO in another function) to a function i'm sporking . Maybe this isn't possible :-( but i'd like your opinion) This is part of my script. Let me tell you this: When i give float Cfreq an initial value of 0.3 LFO does change gain of SinOsc c. If i don't give it an initial value and have LFOtochangeCfreq change it -> no sound. SinOsc m => SinOsc c => Pan2 p => dac; 2 => c.sync; float Cfreq; //if i replace this line by: .3 => float Cfreq; spork ~ LFOtochangeCfreq(.1); spork ~ LFO(Cfreq); fun void LFOtochangeCfreq(float variation) { SinOsc lfo => blackhole; variation => lfo.freq; while( true ) { 1000::samp => now; <<<lfo.last() => Cfreq>>>; } } fun void LFO(float LFOfreq) { SinOsc lfo => blackhole; LFOfreq => lfo.freq; while( true ) { 1::samp => now; lfo.last() => c.gain ; } } while (1) 10::ms=> now;

2 1