Pd-list February 2019

pd-list@lists.iem.at

52 participants
66 discussions

non-socket (88)
by michael strohmann 18 Feb '19

18 Feb '19

i finally could caught pd in the act of freezing: the console said: recv: Connection refused (111) netsend: Socket operation on non-socket (88) warning: 33 removed from poll list but not found i connect every second to mobile phones that run Lemur to send and receive OSC usually if a phone leaves the network, nothing bad happens, the console says: recv: Connection refused (111) netsend: Bad file descriptor (9) warning: 32 removed from poll list but not found So it seems to me that this non-socket(88) problem manages to freeze pd (or is it this number: 88, which has a bad connotation in austria ?) Thanks! michael

4 10

Re: [PD] Issue compiling pure data on Fedora (William Binta)
by Dan Wilcox 15 Feb '19

15 Feb '19

Note: That guide is 6 years old and for Pd-extended. It may not be up to date. Which Pd are you compiling? If it's vanilla, you should really only need the ALSA & JACK development libraries on Linux, aside form the usual compiler, make, & auto tools. > On Feb 15, 2019, at 6:42 PM, pd-list-request(a)lists.iem.at wrote: > > From: William Binta <william.binta(a)gmail.com <mailto:william.binta@gmail.com>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] Issue compiling pure data on Fedora (William Binta) > Message-ID: > <CAL4j8Cs79DN0B=y9OdseJUu-HbNkNi5-CWWuH=YWJmFtkwHhSA(a)mail.gmail.com <mailto:CAL4j8Cs79DN0B=y9OdseJUu-HbNkNi5-CWWuH=YWJmFtkwHhSA@mail.gmail.com>> > Content-Type: text/plain; charset="utf-8" > > Hi list, > > IOhannes, I forgot to specified that I already installed the headers and > everything specified on https://puredata.info/docs/developer/Fedora <https://puredata.info/docs/developer/Fedora>. Apart > from the video packages. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Re: [PD] Issue compiling pure data on Fedora
by Dan Wilcox 15 Feb '19

15 Feb '19

Also, you don't need to set any of the configure flags explicitly any more. Assuming you have the correct development headers installed, running the following will give you a default build like Miller's: ./configure In fact, running just ./configure will also print out the detected audio backends and warn you if it doesn't find some things. This has been true since the auto tools update was merged around 0.47. > On Feb 15, 2019, at 10:30 AM, pd-list-request(a)lists.iem.at wrote: > > Message: 3 > Date: Fri, 15 Feb 2019 10:30:07 +0100 > From: IOhannes m zmölnig <zmoelnig(a)iem.at <mailto:zmoelnig@iem.at>> > To: pd-list(a)lists.iem.at <mailto:pd-list@lists.iem.at> > Subject: Re: [PD] Issue compiling pure data on Fedora > Message-ID: <61e14c57-6d9f-0bf9-dc1a-4f355f235e54(a)iem.at <mailto:61e14c57-6d9f-0bf9-dc1a-4f355f235e54@iem.at>> > Content-Type: text/plain; charset="utf-8" > > On 2/15/19 7:16 AM, William Binta wrote: >> Hi list, >> >> I'm new to Linux and particullary to the Fedora distribution. But as some >> people, I failed at installing the last build (0.49) on Fedora 29. >> I precisely followed the steps on the INSTALL.txt, installed every thing >> necessary mentioned for a successful compilation but yet, my pure-data >> installation doesn't detects any audio devices. I get the "priority 92 >> scheduling failed; running at normal priority" on the pd console and >> "priority 94 scheduling failed" error message on the terminal. >> Even though I enabled jack on the "configure" step and put the -jack flag, >> I read on the terminal that pure-data was not build with JACK. > > > you must install the headers for ALSA and JACK prior to running > ./configure, if you want to use them. > something like: > > # yum install jack-audio-connection-kit-devel alsa-devel > > also: >> My installation configuration was= ./configure --enable-jack > --enable-fftw --enable-universal=x86_64 --disable-oss > --without-local-portaudio > > "--enable-universal" sounds very much like a OSX flag (i just checked > the INSTALL.txt, and it can indeed be read to suggest this flag) > > why did you add the "--without-local-portaudio" flag? > > fgdsar > IOhannes -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Re: [PD] Issue compiling pure data on Fedora (William Binta)
by William Binta 15 Feb '19

15 Feb '19

Hi list, IOhannes, I forgot to specified that I already installed the headers and everything specified on https://puredata.info/docs/developer/Fedora. Apart from the video packages. Well, about the "--without-local-portaudio" flag, this was one of my last test. I wanted to know if adding the flag would change anything, it did not. I tried to compile the previous version of pure data and I got the same problem. Best, William

1 0

hanging
by michael strohmann 15 Feb '19

15 Feb '19

i know its kind of a stupid question, but what causes a program (or pd in particular) to become unresponsive ? i just encountered that pd was stuck on looping a snipet of an audiofile…and i have no idea how to reproduce this...

2 2

[matchbox] with OS X - errors in console
by oliver 15 Feb '19

15 Feb '19

hi, i just discovered, that zexy's [matchbox] outputs the following error in the PD console when it receives an already existing list in its right inlet: zverbose(1): [matchbox]: refusing to add already existing list to buffer... this is with PD 0.49.0, OS X Yosemite 10.10.5 it's not occurring on my windows machine, which is Win7/64bit don't have a chance ATM to check it on linux best oliver

1 0

Issue compiling pure data on Fedora
by William Binta 15 Feb '19

15 Feb '19

Hi list, I'm new to Linux and particullary to the Fedora distribution. But as some people, I failed at installing the last build (0.49) on Fedora 29. My installation configuration was= ./configure --enable-jack --enable-fftw --enable-universal=x86_64 --disable-oss --without-local-portaudio I precisely followed the steps on the INSTALL.txt, installed every thing necessary mentioned for a successful compilation but yet, my pure-data installation doesn't detects any audio devices. I get the "priority 92 scheduling failed; running at normal priority" on the pd console and "priority 94 scheduling failed" error message on the terminal. Even though I enabled jack on the "configure" step and put the -jack flag, I read on the terminal that pure-data was not build with JACK. I'm available to send any particular infos. Someone on the Facebook group said that Miller Puckette himself uses Fedora... cheers, in hope to get some help William

2 1

help making a GUI object visible in GOP (cyclone/comment)
by Alexandre Torres Porres 14 Feb '19

14 Feb '19

Hi folks, I'm working on cyclone/comment, the last object we need to update in cyclone, and I need help. I haven't learned much (if any) when it comes to GUIs in Pd. I've tried all I could and I'm giving up, but I assume this must be so trivial and simple for a more experienced GUI coder out there. So I appreciate if anyone could help me out here. here's the code https://github.com/porres/pd-cyclone/blob/master/cyclone_objects/binaries/c… and one can always also just send us a PR in the repository ;) thanks

6 19

Re: [PD] SysEx In issue
by Mario Buoninfante 11 Feb '19

11 Feb '19

Hi Simon, all the info and the patches I used can be found here: https://github.com/pure-data/pure-data/issues/554 Cheers, Mario On Mon, 11 Feb 2019 at 19:46, Simon Iten <itensimon(a)gmail.com> wrote: > So record the received data with a DAW, and post it, so others can try. > Also try to play back the recorded midi sysex data and see if PD gets stuck > as well when receiving that. > > Is it new Hardware with usb-midi? (you wrote something about usb earlier) > > > On Mon, Feb 11, 2019, 19:50 Mario Buoninfante <mario.buoninfante(a)gmail.com > wrote: > >> Hi Lucas, >> >> Nope, I'm receiving MIDI from a HW device, and I monitored the messages >> both on Pd and MidiMonitor. >> >> >> On Mon, 11 Feb 2019 at 12:59, Lucas Cordiviola <lucarda27(a)hotmail.com> >> wrote: >> >>> So you are sending sysex to Pd without any hardware? Just from virtual >>> devices on the same Pc? >>> >>> >>> Mensaje telepatico asistido por maquinas. >>> >>> On 2/11/2019 9:50 AM, Mario Buoninfante wrote: >>> >>> No that's not the case. In my video I'm using MidiMonitor at the same >>> time,and that works fine also when Pd gets stuck. >>> Also because USB Midi bandwidth is pretty big. >>> >>> Cheers, >>> Mario >>> >>> Sent from my WIKO U PULSE LITE >>> On 11 Feb 2019 12:17, Lucas Cordiviola <lucarda27(a)hotmail.com> >>> <lucarda27(a)hotmail.com> wrote: >>> >>> Do you have the same trouble with other software? >>> >>> It could be that you are exceeding the bandwidth of the MIDI hardware. >>> >>> Describe your connection: >>> >>> drummachine >>> | >>> midicable >>> | >>> midiin-jack on the sound card >>> | >>> Pd >>> >>> In other words: How are you sending sysex to Pd ? >>> >>> >>> Mensaje telepatico asistido por maquinas. >>> >>> On 2/11/2019 9:07 AM, Mario Buoninfante wrote: >>> >>> I found a clunky workaround I only tested on MacOS Sierra for now. >>> I'm automatically setting the MIDI in every 200 ms, using a metro that >>> sends [midi-dialog 2 0 0 0 0 0 0 0 0 2 1 0 0 0 0 0 0 0 4 4( to [s pd] >>> >>> It seems to work, but of course I suspect messages are getting lost. >>> >>> Cheers, >>> Mario >>> >>> _______________________________________________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 >> >

2 1

Re: [PD] SysEx In issue
by Dan Wilcox 11 Feb '19

11 Feb '19

(responding again in thread) It is most likely a bug, maybe introduced in the MIDI overhaul I did for 0.48. Does the same issue occur in 0.47? Can make a *re-produceable* patch and/or project for testing and open an issue on the pure-data Github repo? The simplest thing for me would be the syses messages you're sending as bytes. You could also check the output of the midi tester patch I added: Browser -> Pure Data/7.stuff/tools/miditester.pd Hi, > > Not too long ago I wrote here reporting an issue with receiving SysEx > messages. > When Pd receives a big quantity of SysEx, the MIDI IN port 'gets stuck' and > then you need to go to 'Media->MIDI settings...' and re-select the port, > otherwise no MIDI messages will be received anymore. > Here's a video that shows the issue: > https://vimeo.com/316526250 > it's a private video, the pass is: sysexissue > Does anybody know what could cause this behavior and if it's possible to > 'fix it'? > The first time I reported it, it was when I stumbled on this using my > personal Linux machine and Miller Puckette suggested to change the MIDI > buffer in the source code, but unfortunately also setting that to something > insane like 2^20, the issue was still there. > Now I double checked on MacOS Sierra and Windows 10 and it is the same. > > Cheers, > Mario -- Dan Wilcox @danomatika danomatika.com robotcowboy.com

3 4

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 February 2019