Pd-list December 2018

pd-list@lists.iem.at

54 participants
60 discussions

Pd Vanilla donecanvasdialog GOP starts edit mode
by João Pais 15 Dec '18

15 Dec '18

Hello list, I just noticed something new: when sending a donecanvasdialog message to a subpatch in a GOP, it starts editmode in the parent patch. Afaik, this wasn't the previous behaviour (it still isn't in pd extended). Here is a patch to illustrate the problem. Doesn't happen with coords, though. Best, Joao

4 4

ENC: Grid, x y control
by Henri Augusto Bisognini 14 Dec '18

14 Dec '18

Oh, sorry! I've added in the readme.md that easyflow is a dependencie but i forgot to add: -it is not included in the [guilla] repository so you need to download it separatedly. -easyflow is on Deken :) cheers, Henri. ________________________________ De: oliver <oliver(a)klingt.org> Enviado: sexta-feira, 14 de dezembro de 2018 14:22 Para: Henri Augusto Bisognini Assunto: Re: [PD] Grid, x y control hey, henri ! looks very promising ! in principle the grid works, but the helppatch is missing some abstractions easyflow/listpick ... couldn't create easyflow/Counter ... couldn't create easyflow/Counter ... couldn't create best oliver Henri Augusto Bisognini wrote: > I have an vanilla object that does that and doesn't require going into > editing mode. > > Check [pdPad] from "Guilla". It's not on Deken yet but i can put it if > you want to. The library is in an early stage but [pdPad] should be > ready for work despite not being customizable yet (GOP size etc etc) > > https://github.com/HenriAugusto/guilla > > Cheers, > Henri. > > ------------------------------------------------------------------------ > *De:* Pd-list <pd-list-bounces(a)lists.iem.at> em nome de Max > <abonnements(a)revolwear.com> > *Enviado:* sexta-feira, 14 de dezembro de 2018 12:34 > *Para:* pd-list(a)lists.iem.at > *Assunto:* [PD] Grid, x y control > Hi list, > > what's the current recommendation for a simple x-y Pd GUI controller > type of thing? Like a slider but horizontal and vertical. > There are probably a few externals providing this, which one is the > best/most compatible/future proof? > In vanilla this can be emulated with an object reporting its position on > a canvas, but to use it one must change to the edit mode which is kind > of counter-intuitive. > > Anything I'm missing? > > m > > > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> > https://lists.puredata.info/listinfo/pd-list > > > _______________________________________________ > Pd-list(a)lists.iem.at mailing list > UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list > -- \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\ /////////////// http://pendler.klingt.org ////////////// \\\\\\\\\\\\\\\ http://oliver.klingt.org \\\\\\\\\\\\\\ ////////////////////////////////////////////////////////

1 0

[PD-announce] ELSE 1.0 beta 15 and Live Electronics Tutorial 1.0 beta 5
by Alexandre Torres Porres 14 Dec '18

14 Dec '18

The ELSE library has been updated and ELSE 1.0 Beta 15 has been released! Find Binaries up in deken. There are many new objects for a total of 286 - more details about the release at: https://github.com/porres/pd-else/releases/tag/v1.0-beta15 I also have this Live Electronics Tutorial that depends on ELSE and it also gets updates at every new ELSE release to reflect what's new or make it compatible for any breaking change, so here's the release that depends on ELSE 1.0 Beta 15: https://github.com/porres/Live-Electronics-Tutorial/releases/tag/v-1.0beta-5 This might be the last update of the year, so merry xmas and happy holidays cheers _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

2 1

virtual raspberry to compile externals
by Alexandre Torres Porres 13 Dec '18

13 Dec '18

Hi, I'm now finally using virtualbox to compile for windows and linux 32/64 bits and I wonder if there's a way to setup a virtual machine to compile for raspberry pi... (?) cheers

3 5

name of latency measurement algorithm
by Roman Haefeli 13 Dec '18

13 Dec '18

Hey all I once read about a simple and robust way to perform latency measurements with an audio signal. Explained in a few words, the test signal consists of a sweeping sine tone. The return signal ring-modulates the source signal and the resulting signal consists of two frequencies, the sum ( f_src+f_ret ) and difference ( f_src - f_ret), while the lower frequency is proportional to the latency and can be detected quite easily with with e.g. [sigmund~]. I have troubles finding the name of this algorithm and don't remember the original source. I would like to read more about it and correctly attribute the original author / inventor. Thanks, Roman

3 5

German translation of Pd
by Peter P. 13 Dec '18

13 Dec '18

Hi list, looking at a german translation of Pd right now I am wondering if it makes sense to translate technical terms such as object, message, into their german-dictionary-counterparts. I find it counter-intuitive to be using, like most others, the english words object and messag in german but having these a bit awkward translations in the pulldown menus. Does anyone else have an oppinion on this? Thanks! Peter

11 37

iemmatrix (deken) behaviour on linux
by padovani 12 Dec '18

12 Dec '18

Hi, a student of mine is trying to use iemmatrix on linux and we are having problems. We have installed the only version available for linux in deken and even if we put it in the search path and initialize in the startup, patches with mtx_*~ don't initialize the objet. We have also tried with declare -lib. But... when we try to create the object (i.e., not loading a patch containing it), it instantiates as expected. Do you have any clues? This behaviour happens on ubuntu with vanilla versions 0.48.1 and 0.49.0. thanks, José

2 1

[PD-announce] CfP: 6th International Conference on Movement and Computing (MOCO19), 10-12th October, Tempe, Arizona, USA
by Cumhur Erkut 10 Dec '18

10 Dec '18

Apologies for cross-posts, please distribute. ——————————————————————————————————————— 6th International Conference on Movement and Computing (MOCO19) https://moco19.movementcomputing.org/ ——————————————————————————————————————— 10-12th October, Tempe, Arizona Arizona State University, USA Arizona State University [ASU] will host the 2019 the 6th International Conference on Movement and Computing [MOCO] which is to be held in Tempe, Arizona. The MOCO 2019 theme will be Movement Imaginaries. Paper presentations, panels, performances, demos, workshops on all MOCO-related topics are welcome. MOCO is an interdisciplinary conference that explores the use of computational technology to support and understand human movement practice, as well as movement as a means of interacting with computers. We welcome submissions with an interdisciplinary understanding of movement that ranges from biomechanics to embodied cognition and the phenomenology of bodily experience and identities. We therefore invite submissions from a wide range of disciplines including, but not limited to: Human-Computer Interaction, Psychology, Dance, Artificial Intelligence, Neuroscience, Sports Science, Machine Learning, Cognitive Science, Visual Arts, Robotics, Philosophy, Anthropology, Music, Affective Computing, Games, Healthcare and Animation. All proposal abstracts for roundtables, panel sessions, contributed papers, and posters must be submitted by Wednesday, February 27, 2019 (midnight EDT). See Submissions for more information and the full CFP. ———————————— Important Dates ———————————— NB There will be no deadline extensions Submission deadline: 27 February 2019 Notification: 23 May 2019 Camera ready papers: 30 June 2019 ABOUT https://moco19.movementcomputing.org https://www.movementcomputing.org/past-conferences/ —————————— Submission —————————— We would like to invite submissions for paper presentations, performances, workshops and more to the 6th International Conference on Movement and Computing (MOCO) which is to be held in Tempe, Arizona. MOCO is open to a wide range of ways of presenting your work. As well as papers for oral and poster presentations, we invite submission of a wide range of practice work such as demos, performances, games, artistic works and movement workshops (in which participants take part in a guided movement activity). We encourage submitters to be creative in proposals for practice sessions and are open to novel formats. This requires a wide range of computational tasks including modeling, representation, segmentation, recognition, classification, or generation of movement information but also an interdisciplinary understanding of movement that ranges from biomechanics to embodied cognition and the phenomenology of bodily experience. We therefore invite submissions from a wide range of disciplines including (but not limited to): Human-Computer Interaction, Psychology, Dance, Artificial Intelligence, Neuroscience, Sports Science, Machine Learning, Cognitive Science, Visual Arts, Robotics, Philosophy, Anthropology, Music, Affective Computing, Games, Healthcare and Animation. ———————————— Suggested Topics ———————————— • Expressive movement-based interaction • Movement analysis and analytics • Machine learning for movement • Movement representation • Somatic practice and design • Modeling movement qualities and expressive movement • Mechatronics and creative robotics • Design for movement in digital art • Gesture Interaction • Movement generation • Movement and sound interaction • Movement computation in ergonomics, sports, and health • Sensory-motor learning with audio/visual feedback • Embodied cognition and movement • Visualizing and sonifying movement • Modeling kinaesthetic empathy • Embodied and whole body interaction • Expressive movement analysis and synthesis • Design for movement in digital art • Semantic models for movement representation • Movement Notation Systems (e.g. Laban or Eshkol-Wachman) and computation • Dance and technology • Biosensing, biocontrol and movement • Movement expression in avatar, artificial agents, virtual humans or robots. • Music and movement • Philosophical perspectives and reflection on movement and computing The conference is an opportunity to present a research or study or details of collaborative work. Participants will have the opportunity to offer a presentation of the results of their research on one of the themes of the symposium and to interact with their scientific/ artistic peers, in a friendly and constructive environment. We encourage submission of a wide range of formats, the submission categories are: Long paper with oral presentation (8 pages maximum) Short paper with oral presentation (4 pages maximum) Extended abstract with poster presentation (6 pages maximum in the extended abstract format) All submissions should be in pdf format and should use the ACM proceedings format: http://www.acm.org/publications/proceedings-template ———————————— Tracks ———————————— MOCO is open to a wide range of ways of presenting your work. Besides papers for oral and poster presentation, we invite submission of practice works such as demos, performances, games, artistic works and movement workshops (in which participants take part in a guided movement activity). ———————————— Papers and Posters ———————————— The conference is an opportunity to present original research and details of collaborative work. Participants will have the opportunity to offer a presentation of the results of their research on one of the themes of the conference and to interact with their scientific/artistic peers, in a friendly and constructive environment. We encourage submission of a wide range of formats. Authors of papers and posters may submit an accompanying demonstration proposal in addition to their regular paper or poster submission, by completing the proposal form for practice works (see items 2 and 3 in the next section) and sending it along with their submission. Together with the form, authors have to provide a link to a video about their work. The proposal form for practice works is mandatory for all paper and poster submissions including an accompanying demonstration and must include details about technical set-up and space requirements. ———————————— Practice Works ———————————— We deliberately use a very open term – “practice work” – to encourage diverse ideas of what practice in movement and computing is and how such practice can be presented. We suggest the following as examples of what a practice work might be, but also stress that the list is not exhaustive and any types of presentation can be considered, the only criteria being excellence of the work and whether it is possible to stage the work given the resources, time and space available to the conference. Suggested practice works topics: * Technology demos * Performances (e.g., dance, physical performance, music) * Artworks * Interactive Installations * Movement workshops (i.e., a session in which participants engage in movement based activity) * Games * Video presentations Submissions consist of: 1. An extended abstract (2 pages maximum). 2. The proposal form for practice work, including detailed technical requirements and possible additional information. The form is available here (Ms Excel format) or here (OpenOffice format). 3. Supporting media (videos, pictures, audio, and so on), which should provide an overview of the practical work and details of the practical and technical requirements for putting the work on (this is very important to ensure that we can accommodate the work within the resources of our conference). Extended abstract for practice work with presentation format to be suggested by the author for example demonstration, performance, art work, movement workshop, game or other practice presentation (2 pages maximum + Demo proposal form). Please note that we are an academic conference with a low fee which means we cannot pay for commissioned performances and art work. Also, we cannot guarantee facilities for all possible sessions, so please give full details of your needs in the proposal form so we can judge whether it is possible. Submissions will be by extended abstract (2 pages maximum) and a proposal form which will give details of the practical requirements for putting on the work (this is very important to ensure that we can accommodate the work within the resources of our conference). Please note that we are an academic conference with a low fee which means we cannot pay for commissioned performances and art work. Also, we cannot guarantee facilities for all possible sessions, so please give full details of your needs in the proposal form so we can judge whether it is possible. ———————————— Doctoral Consortium ———————————— Doctoral papers are an opportunity for PhD students to present their work in progress on their doctorate, share and develop their research ideas in a supportive environment and with the participation of experts in the field. Students will have the opportunity to establish a community, together with other doctoral students at a similar stage of their research. Accepted papers will have an oral presentation in a dedicated session. We encourage students to submit a paper even if they are early in their doctoral work. Papers should not be longer than 4 pages including the references. The first author must be an actual PhD student. Doctoral Consortium papers will be indexed and published in the ACM digital library. Videos and other supplementary materials are highly welcomed. Students accepted to present their work at the Doctoral Consortium must plan to attend it. Submission Format and Procedure All submissions must be written in English. Submissions must be in pdf format and they have to be prepared using the ACM proceedings template: http://www.acm.org/publications/proceedings-template All contributions must be submitted online through EasyChair: https://easychair.org/conferences/?conf=moco2019 All submissions must be anonymous and will be peer-reviewed. The MOCO proceedings will be indexed and published in the ACM digital library. ———————————— CONFERENCE LOCATION ———————————— ASU is a massive Research One university, giving the conference access to a great diversity of programs, practices, and scholars working here. MOCO at ASU presents a unique opportunity to build upon existing fields of interests and forge new avenues for research and knowledge creation that resonate across the arts and sciences and branch into health, philosophy, education and other application areas that include both computational techniques and human movement. The range of interdisciplinary labs and centers and the beautiful October weather make this an ideal locale for the conference. ASU is located about fifteen minutes from the Phoenix Airport. ———————————— Contact ———————————— If you have any questions please contact: moco2019(a)easychair.org or Grisha Coleman ———————————— Committee ———————————— • Conference Chair: Grisha Coleman (ASU) • Scientific Chairs: Sofia Dahl & Cumhur Erkut (Aalborg University) • Performance & Practice Chair: Christian Ziegler (ASU) • Doctoral Symposium Chair: Garett Laroy Johnson (ASU) • Local Organizers: Kimberlee Swisher, Stacey Moran, Julie Ackerly, Jessica Raijko, Adam Nocek, Pavan Turaga • Steering Committee: Frédéric Bevilacqua (IRCAM), Sarah Fdili Alaoui (LRI-Université Paris-Sud 11), Jules Françoise (CNRS, Université Paris-Sud Université Paris-Saclay), Philippe Pasquier (Simon Fraser University), Thecla Schiphorst (Simon Fraser University) -- http://movementcomputing.org/ _______________________________________________ Pd-announce mailing list Pd-announce(a)lists.iem.at https://lists.puredata.info/listinfo/pd-announce

1 0

hammerembed gc1 garbage bindings?
by Ricky Graham 07 Dec '18

07 Dec '18

Anyone any ideas what object or issue this message in console could be related to?

2 3

Re: [PD] Keyboard patching
by Henri Augusto Bisognini 06 Dec '18

06 Dec '18

I forgot to say one important thing that i must make clear heh :p i've suggested a "conn" ecause there is already a "connect" selector which is the one used internally by PD. ex: to connect the 1st outlet of the 10th to the 2nd inlet of the 13th object you would send it "connect 10 0 13 1" I'm thinking about another more flexible syntax because only being able to create a single connection per message might get cumbersome if you need to connect a lot of stuff. We could have something like: conn 10,11,12/1,2 30/2 > 5/1 33/2 Which would mean: create connections from: * 1st and 2nd outlets of objects #10,11,12 * 2nd outlet of object #30 and connect each of those outlets to: * 1st inlet of object #5 * 2nd inlet of object #33 What you think? hmm ________________________________ De: José de Abreu <abreubacelar(a)gmail.com> Enviado: segunda-feira, 3 de dezembro de 2018 09:37 Para: Henri Augusto Bisognini Assunto: Re: [PD] Keyboard patching just a suggestion: conn 10-3 -> 23-1 it would be faster to type like this conn 10 3 23 1 the user only has to know the meaning of each argument, and this is also how it is done in the .pd file too

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Pd-list December 2018