[PD] [PD-announce] 2019 Guthman Musical Instrument Competition Call for Submissions
Georgia Tech School of Music Guthman Musical Instrument Competition 2019 Call for Submissions Is Now Open! http://guthman.gatech.edu Georgia Tech's 2019 Margaret Guthman Musical Instrument Competition is an annual event aimed at identifying the world's next generation of musical instruments and unveiling the best new ideas in musicality, design, engineering, and impact. The Guardian called the competition "The Pulitzer of the New Instrument World," and The New York Times described the "special, otherworldly sound that you can feel permeating your soul" which became the hallmark of the competition. Fast Company explained how Guthman's "Futuristic Instruments will change how we make music," and the Atlanta Magazine suggests that "at the Guthman Competition, innovative instruments just might predict the future of music." The Guthman Competition will take place March 8-9, 2019 at Georgia Tech's Ferst Center for the Arts, in Atlanta, Georgia. The deadline for submissions is October 10, 2018. Approximately twenty semi-finalists will be invited to demonstrate, discuss, and perform with their instruments as they compete for $10,000 in cash prizes. Submit Your Instrument at: http://guthman.gatech.edu/2019-call-submissions-0 /// This Year's Judges PAMELA Z - Composer, Performer, and Media Artist ROGER LINN - Electronic Musical Instrument Designer GE WANG - Associate Professor, CCRMA, Stanford University /// To learn more about the competition, visit guthman.gatech.edu or https://www.facebook.com/guthmancompetition We’d love to hear your comments! ___ Pd-announce mailing list pd-annou...@lists.iem.at https://lists.puredata.info/listinfo/pd-announce ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
[PD] [PD-announce] Live Electronis Tutorial by Porres in English (& ELSE beta 12 released)
Hi, two related announcements! I've Finished translating the vol. 2 of my Live Electronics Tutorial to English, with now 323 examples! https://github.com/porres/Live-Electronics-Tutorial - It already relies on the (still in test phase) 0.49-0 release of Pure Data (though 99% will work in 48). Anyway, vol. 2 is where things gets a little serious... there's FFT stuff and I really like my take on filters (folder "29"). I hope this becomes a relevant tutorial for Pd. Let me know what you think. Next plan is to write a book where these are the examples. This is a very special announcement for me as I've been working on this for 10 years now and I'm happy to make it available in english. Not only that, but to finally port it out of Pd Extended and into Vanilla! Porting to Vanilla relies heavily and extensively in the ELSE library, and this is where most of my work has been put recently, in order to port this out of Extended. This brings us to the next announcement: I have a new release that it relies on, Beta 12! Find it on deken (pd => Help => Find Externals). See https://github.com/porres/pd-else/releases/tag/v1.0-beta12 for details. Newer additions to the tutorial now depend on developments of ELSE. The last release was a couple of weeks ago but I'm really proud of the advancements I made. I'd like to highlight the additions to [envgen~], you really should check it out, it's a very powerful and versatile envelope generator. I still wanna allow for exponential curves, maybe next time. This release of ELSE also already relies on Pd 0.49, but works for the most part with 0.48. cheers ___ Pd-announce mailing list pd-annou...@lists.iem.at https://lists.puredata.info/listinfo/pd-announce ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] select based on first "element"
On Wed, 12 Sep 2018 19:28:52 +0200 Kaj Ailomaa wrote: > A really simple solution is to use [route] instead of [select]. I feel so embarassed, of course, route is the solution, total newbie here... Thanks alot!!! Cheers -- Atte http://atte.dk http://a773.dk ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] select based on first "element"
On Wed, Sep 12, 2018, at 7:07 PM, Atte via Pd-list wrote: > Hi > > I'm getting back into PD after a long time. Sorry if the following is > either obvious, obviously impossible, unclear, or the wrong way to go > about things. > > I have an abstraction that I'd like to send different data through the > same inlet, say param1=0, param2=3. Taking the abstraction part out of > the equation, I guess I need to parse a list based on the first element. > > Here's what I have, which doesn't work: > > |param1 0( |param2 3( > |___| > | > | select param1 param2 | >||| > |print p1| |print p2| > > How would I go about that? I'm in vanilla... A really simple solution is to use [route] instead of [select]. Another way to do it is to store the parameter value in something that [select] will trigger, like [value]. The best solution might depend on what you are doing before and after. > > Cheers > -- > Atte > > http://atte.dk http://a773.dk > > > > ___ > Pd-list@lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
[PD] select based on first "element"
Hi I'm getting back into PD after a long time. Sorry if the following is either obvious, obviously impossible, unclear, or the wrong way to go about things. I have an abstraction that I'd like to send different data through the same inlet, say param1=0, param2=3. Taking the abstraction part out of the equation, I guess I need to parse a list based on the first element. Here's what I have, which doesn't work: |param1 0( |param2 3( |___| | | select param1 param2 | ||| |print p1| |print p2| How would I go about that? I'm in vanilla... Cheers -- Atte http://atte.dk http://a773.dk ___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] [PD-announce] PD 0.49-0test1 released- small things on Windows 10
a few remarks on Windows 10 only with the 64-bits version: in the window of menu-open one cannot use the address bar in the top see attached picture. with 32&64 bits versions: when opening a patch the window has scroll bars. when i move the window the scroll bars disappear. the appearances of the 32 & 64 bits versions are different: the 32-bits version gives bigger windows (~ 18%) and the font looks blown-up. rolf___ Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
Re: [PD] bug with edit-mode (was Re: [PD-announce] PD 0.49-0test1 released)
I am on Mac, yes, sorry I forgot to mention that. For me the problem is happening whenever a donecanvasdialog message is sent to a canvas, so I'd imagine that is triggering the same thing as the properties menu would? Also, if the donecanvasdialog message happens in an abstraction, it puts whatever patch the abstraction was created in into edit mode, and this seems to be where it's going into edit mode sort of silently, as in, it doesn't say [edit] at the top of the screen and there's no checkmark next to edit mode in the edit menu, but if you try to click anywhere inside the patch its obviously in edit mode as you are able to select/resize/etc. items in the patch but aren't able to click on a bang, for example, or anything else--but I've only been able to reliably reproduce this when first opening a patch that sends a donecanvasdialog message upon opening. It's happened occasionally after the patch has been opened, but usually the top of the pd window will indicate [edit] at least when a donecanvasdialog message is sent. The crash upon closing the patch happens every time, though. I realize that the donecanvasdialog thing is an unsupported method or whatever, but it seems like the crashing might be part of a more general problem somewhere, maybe? I've just tested 0.49-0test2-i386 just now and the crash and everything preceding it is still happening. I've attached a patch demonstrating how the problem is being triggered for me, if maybe someone with a mac wants to check it out to confirm. It should open in edit mode without the [edit] message appearing in the title bar or whatever its called or the edit mode option in the edit dropdown menu being checked, and then make the patch go into edit mode again each time the donecanvasdialog message is sent, and finally it should crash pd when the window is closed. ps - I seem to have mostly gotten around the issue by using coords instead of donecanvasdialog, which I normally do anyway, however it seems the crash is happening regardless, but I'm not completely sure that I didn't miss anything so please take that as a very tentative statement. It might just be too early yet for my brain to have come online. On Tue, Sep 11, 2018 at 9:13 PM Miller Puckette wrote: > I bet this is related to the "save as" crash bug. Are you on Mac OSX? > And... am I reading this correctly that you (1) open any patch; (2) open > the > "properties" dialog for the canvas; (3) hit "OK" on the dialog, and then > you find out that the patch went into edit mode? > > (And that it then crashes Pd to close the patch?) > > thanks > Miller > > On Tue, Sep 11, 2018 at 07:08:30PM -0400, JTG III wrote: > > Okay I can can confirm that using donecanvasdialog is triggering the edit > > mode thing, though I'm not sure why there is no indication from pd upon > > loading a patch on startup that it is, in fact, in edit mode. I tried > some > > patches made by other people, such as waveform.mmb or whatever it is > > called, and a couple of others and they all toggled edit mode on the > parent > > patch. > > They also all cause pd to crash when the parent patch is closed. I didn't > > get any hints from the terminal but the script I usually use to start pd > > wasn't working for some reason and I have to head out again for an hour > or > > two but I'll look into it more when I get back. > > > > On Sep 11, 2018 6:01 PM, "JTG III" > wrote: > > > > > Well I know that the canvas is in edit mode as anytime I try to click > > > anything I end up grabbing something and resizing it instead, and > toggling > > > edit mode on and off in the edit menu makes it behave as expected. The > > > thing with having no indication of currently being in edit mode was > only > > > happening when I would first open the patch, and as mentioned I could > tell > > > that it was in fact on because whenever I would try to click on > anything in > > > the PD window with the mouse the cursor would instead select or start > > > resizing whatever was beneath it. > > > Thinking about it now I figure it must have something to do with > > > donecanvasdialog, would that make sense? I'm not using any gui plugins > and > > > no externals are interacting with the gui, but I am using a number of > > > structs. I'll check that in a couple of hours when I'm back at home. > > > > > > On Sep 11, 2018 9:11 AM, "IOhannes m zmoelnig" > wrote: > > > > > >> hi. > > >> > > >> thanks for the bug-report. > > >> > > >> unfortunately it indeed doesn't contain much information about what > > >> could be the actual problem you are experiencing. > > >> > > >> things i could establish: > > >> - your patches switch to edit-mode when they shouldn't > > >> - there is no indication of being in edit-mode > > >> - you accidentally resize GOPs > > >> - abstractions/subpatches send "messages" > > >> - you are using a number of externals > > >> - Pd sometimes crashes > > >> - the problem appears under Pd-0.49-0test1 > > >> - everything works with Pd-0.48-2 > > >> (i
