Re: [PD] watchdog -> force restart

[Peter P.]

* michael strohmann  [2019-02-18 11:49]:
> wow, that looks interesting!
> so which object do you use to read out the gpio?
I use Miller's gpio object.

> would you be so kind as to share your gpioReading-demo.pd ?
Attached.
#N canvas 1 49 450 300 10;
#X obj 194 95 loadbang;
#X msg 194 121 open 1;
#X obj 162 187 outlet;
#X obj 162 154 gpio \$1;
#X obj 162 65 r pollPin;
#X connect 0 0 1 0;
#X connect 1 0 3 0;
#X connect 3 0 2 0;
#X connect 4 0 3 0;
#N canvas 306 67 553 819 10;
#X obj 363 30 loadbang;
#X obj 363 56 metro 100;
#X obj 363 81 s pollPin;
#X text 432 58 could be faster;
#X text 6 5 readPin: Argument is pin number in BCM fashion.;
#X obj 27 52 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1
;
#X obj 27 31 readPin 2;
#X obj 27 93 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0 1
;
#X obj 27 72 readPin 3;
#X obj 27 133 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 112 readPin 4;
#X obj 27 216 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 195 readPin 17;
#X obj 27 256 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 235 readPin 27;
#X obj 27 296 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 275 readPin 22;
#X obj 27 386 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 365 readPin 10;
#X obj 27 426 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 405 readPin 9;
#X obj 27 466 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 546 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 445 readPin 11;
#X obj 27 525 readPin 0;
#X obj 27 586 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 626 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 666 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 706 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 565 readPin 5;
#X obj 27 605 readPin 6;
#X obj 27 645 readPin 13;
#X obj 27 685 readPin 19;
#X obj 27 746 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 27 725 readPin 26;
#X obj 207 133 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 174 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 214 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 112 readPin 14;
#X obj 207 153 readPin 15;
#X obj 207 193 readPin 18;
#X obj 207 303 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 344 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 424 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 282 readPin 23;
#X obj 207 323 readPin 24;
#X obj 207 403 readPin 25;
#X obj 207 464 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 504 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 544 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 443 readPin 8;
#X obj 207 483 readPin 7;
#X obj 207 523 readPin 1;
#X obj 207 624 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 603 readPin 12;
#X obj 207 704 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 683 readPin 16;
#X obj 207 744 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 784 tgl 15 0 empty empty empty 17 7 0 10 -262144 -1 -1 0
1;
#X obj 207 723 readPin 20;
#X obj 207 763 readPin 21;
#X text 48 53 high by default;
#X text 48 92 high by default;
#X connect 0 0 1 0;
#X connect 1 0 2 0;
#X connect 6 0 5 0;
#X connect 8 0 7 0;
#X connect 10 0 9 0;
#X connect 12 0 11 0;
#X connect 14 0 13 0;
#X connect 16 0 15 0;
#X connect 18 0 17 0;
#X connect 20 0 19 0;
#X connect 23 0 21 0;
#X connect 24 0 22 0;
#X connect 29 0 25 0;
#X connect 30 0 26 0;
#X connect 31 0 27 0;
#X connect 32 0 28 0;
#X connect 34 0 33 0;
#X connect 38 0 35 0;
#X connect 39 0 36 0;
#X connect 40 0 37 0;
#X connect 44 0 41 0;
#X connect 45 0 42 0;
#X connect 46 0 43 0;
#X connect 50 0 47 0;
#X connect 51 0 48 0;
#X connect 52 0 49 0;
#X connect 54 0 53 0;
#X connect 56 0 55 0;
#X connect 59 0 57 0;
#X connect 60 0 58 0;
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Gem on Arch Linux (was: Gem / [pix_movie] trouble: "no movie decoding backends found")

[Carlos Franke]

> > Indeed "gemdefaultwindow.pd" is not packaged with Gem 0.94(_pre1>
> > instead there is "gemdefaultwindow-glx.pd"[2], but Pd/Gem still
> > seems to search for it. Any ideas why?  
> 
> it is packaged fine, but not as a file but as a symlink that is
> created at installation time, or whenver the admin chooses to enable
> a different default window using the "update-alternatives" mechanism.

I see, that makes sense. Thank you for explaining.

Indeed after I made the symlink, Gem (0.94) mostly works. Alas, now I'm
getting errors again when I try to load videos with [pix_movie]… I did
make the effort to try and convert all necessary plugin and library
packages from Debian with the help of debtap, but evidently I have made
a mistake somewhere.

I am giving up on this for now. I'm developing for Raspberry Pi at the
moment, so having Gem also on the Laptop would merely be a convenience
for me. Given how involved that turned out to be, I better focus my
energy elsewhere.


As a tip for anyone else running into this: There are Arch binary
packages for Purr Data (continuation of pd-l2ork with javascript GUI,
as I understand it) available in this repo:

https://bitbucket.org/l2orkaur/l2orkaur.bitbucket.org

Gem is included (0.93 again, though) and video playback works. The repo
is not mine and I don't know the maintainer, so please judge for
yourself if you want to trust these binaries or not.


> do not fuddle wit 0.93.3; even less so with binaries from this
> release! (seriously)

Okay, stopping now.

c


pgp07_HMgugr3.pgp
Description: Digitale Signatur von OpenPGP
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] Pd & massively multi-channel wi-fi speakers

[Peter Nyboer]

I did as project some time ago with the NextThing CHIP computer attached to 
speakers. Each of 8 CHIPs ran a PD synth patch, and was attached to a speaker. 
One CHIP was attached to a Livid DS1 MIDI controller, which broadcast commands 
over the network to all the PD patches. 
Each channel strip of the DS1 (1 fader and 5 pots) controlled the synth patch 
on each CHIP, so I had 8 channels of synthesis. 
In short, it was a WiFi spatial synth. I never really got to exploit this 
system in its final form, but I did test it all and it worked quite nicely. It 
wasn’t terribly complicated, and since the CHIP was pretty cheap, it wasn’t 
terribly expensive. You can still find them on Amazon for $20 or so.

  I should probably find a grant and residency at some Italian castle or 
something so I can finish this project :)

Peter


___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd & massively multi-channel wi-fi speakers

[Peter P.]

* Maximiliano Estudies  [2019-02-18 19:31]:
> the radio idea sounds like a lot of fun.
I guess Max Neuhaus has done such things.



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd & massively multi-channel wi-fi speakers

[Maximiliano Estudies]

the radio idea sounds like a lot of fun.

El lun., 18 feb. 2019 a las 10:24, Jean-Marie Adrien (<
jm.adrien@gmail.com>) escribió:

> hi
> as far as i know, two major problems
> - wireless speakers to be found for sale in the industry are based on the
> stereophonic paradigm, music coming out of two holes and that’s it
> - wireless technology introduces some latency, which is somehow
> contradictory with the  pd real time approach, even more since the industry
> runs now after the personal assistant segment, to generate more profit, and
> this introduces though even more latency, which is in itself not a problem
> if you playback dead sounds like in the last millenium.
>
> there must be some ways to turn around these problems though, like radios
> indeed :), but these ways around have to be considered in balance with
> installing simple cables, and this even more if sound sources are not
> mobile in space.
>
> i am however always curious to learn about the subject
> jm
>
> > Le 18 févr. 2019 à 09:19, Peter P.  a écrit :
> >
> > * Kerry Hagan  [2019-02-17 12:56]:
> >> Hello all,
> >>
> >> Has anyone used wi-fi speakers with Pd?
> >
> >>
> >> More importantly - I would ideally like to send 30 independent audio
> channels to 30 battery-powered wi-fi speakers (in the same room)
> > Do you mean Wifi or Bluetooth? Could you use small FM transmitters and
> > 30 battery powered radios, like, in the last millenium, instead?
> >
> >> I’ve never used any wi-fi speakers for anything at all, and I’m finding
> it hard to see how they are connected without some proprietary software
> made by the usual suspects. I’ve scoured eBay, Amazon, Curry’s without
> being able to answer my own questions.
> > Well, these pages don't give answers, they sell you things ;)
> >
> >
> >
> > ___
> > 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
>


-- 
Maximiliano Estudies
+49 176 36784771
omslo.com
maxiestudies.com
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] watchdog -> force restart

[Csaba Láng]

Not sure if this is what you are looking for, but I use a python script to
run 2 pd instances connected via netsend. The main patch sends a ing every
second to the other patch, if the ping is stopped, the second kills the
main pd. What the script recognizes and restarts both pd patches.
Best,
Popesz
On Mon, 18 Feb 2019 at 10:50, michael strohmann 
wrote:

> wow, that looks interesting!
> so which object do you use to read out the gpio?
> would you be so kind as to share your gpioReading-demo.pd ?
> thanks!
>
>
> > On 18 Feb 2019, at 10:54, Peter P.  wrote:
> >
> > * michael strohmann  [2019-02-18 10:47]:
> >>
> >>> On 18 Feb 2019, at 10:36, Peter P.  wrote:
> >>>
> >>> * michael strohmann  [2019-02-18 10:22]:
>  good morning,
> >>> Guten Morgen!
> >>>
> >>> I know you didn't want this answer, but, is there a chance you can
> >>> figure out why you are getting the watchdog message in Pd in the first
> >>> hand place?
> >>
> >> yes, i think/hope i found the reason (network related) but still would
> be happy to have a safetynet.
> >> can only access wiringPI_gpio in sudo mode (raspberry…)
> >
> > On an RPi 1 I managed to read the gpio pins as normal user by executing
> > the following script, which starts pd at the end.
> >
> >   #!/bin/bash
> >
> >   # set the TX RX pins to become inputs as well
> >   gpio -g mode 14 in
> >   gpio -g mode 15 in
> >
> >   # set the following pins to low by default
> >   gpio -g mode 4 down
> >   gpio -g mode 5 down
> >   gpio -g mode 0 down
> >   gpio -g mode 6 down
> >
> >   gpio -g mode 15 down
> >   gpio -g mode 8 down
> >   gpio -g mode 7 down
> >   gpio -g mode 1 down
> >
> >   # export the pins to be read by a normal user
> >   # This numbering is already by BCM_GPIO number
> >   gpio export 2 in
> >   gpio export 3 in
> >   gpio export 4 in
> >   gpio export 17 in
> >   gpio export 27 in
> >   gpio export 22 in
> >   gpio export 10 in
> >   gpio export 9 in
> >   gpio export 11 in
> >   gpio export 0 in
> >   gpio export 5 in
> >   gpio export 6 in
> >   gpio export 13 in
> >   gpio export 19 in
> >   gpio export 26 in
> >
> >   gpio export 14 in
> >   gpio export 15 in
> >   gpio export 18 in
> >   gpio export 23 in
> >   gpio export 24 in
> >   gpio export 25 in
> >   gpio export 8 in
> >   gpio export 7 in
> >   gpio export 1 in
> >   gpio export 12 in
> >   gpio export 16 in
> >   gpio export 20 in
> >   gpio export 21 in
> >
> >   pd -rt gpioReading-demo.pd
> >
> >
> >
> > ___
> > 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-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] watchdog -> force restart

[michael strohmann]

wow, that looks interesting!
so which object do you use to read out the gpio?
would you be so kind as to share your gpioReading-demo.pd ?
thanks!


> On 18 Feb 2019, at 10:54, Peter P.  wrote:
> 
> * michael strohmann  [2019-02-18 10:47]:
>> 
>>> On 18 Feb 2019, at 10:36, Peter P.  wrote:
>>> 
>>> * michael strohmann  [2019-02-18 10:22]:
 good morning, 
>>> Guten Morgen!
>>> 
>>> I know you didn't want this answer, but, is there a chance you can
>>> figure out why you are getting the watchdog message in Pd in the first
>>> hand place?
>> 
>> yes, i think/hope i found the reason (network related) but still would be 
>> happy to have a safetynet.
>> can only access wiringPI_gpio in sudo mode (raspberry…)
> 
> On an RPi 1 I managed to read the gpio pins as normal user by executing
> the following script, which starts pd at the end.
> 
>   #!/bin/bash
> 
>   # set the TX RX pins to become inputs as well
>   gpio -g mode 14 in
>   gpio -g mode 15 in
> 
>   # set the following pins to low by default
>   gpio -g mode 4 down
>   gpio -g mode 5 down
>   gpio -g mode 0 down
>   gpio -g mode 6 down
> 
>   gpio -g mode 15 down
>   gpio -g mode 8 down
>   gpio -g mode 7 down
>   gpio -g mode 1 down
> 
>   # export the pins to be read by a normal user
>   # This numbering is already by BCM_GPIO number
>   gpio export 2 in
>   gpio export 3 in
>   gpio export 4 in
>   gpio export 17 in
>   gpio export 27 in
>   gpio export 22 in
>   gpio export 10 in
>   gpio export 9 in
>   gpio export 11 in
>   gpio export 0 in
>   gpio export 5 in
>   gpio export 6 in
>   gpio export 13 in
>   gpio export 19 in
>   gpio export 26 in
> 
>   gpio export 14 in
>   gpio export 15 in
>   gpio export 18 in
>   gpio export 23 in
>   gpio export 24 in
>   gpio export 25 in
>   gpio export 8 in
>   gpio export 7 in
>   gpio export 1 in
>   gpio export 12 in
>   gpio export 16 in
>   gpio export 20 in
>   gpio export 21 in
> 
>   pd -rt gpioReading-demo.pd
> 
> 
> 
> ___
> 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

Re: [PD] watchdog -> force restart

[michael strohmann]

thanks for the clarification!
i must have imagined that sigup kills pd…indeed the rest of the system does not 
freeze.

i am still looking for a way automatically restart pd or the computer if pd 
freezes…


> On 18 Feb 2019, at 10:54, IOhannes m zmoelnig  wrote:
> 
> On 18.02.19 10:21, michael strohmann wrote:
>> i need help understanding this description of the pd-watchdog
>> 
>>> s_watchdog.c is the source of pd-watchdog, which was spawned in 
>>> sys_startgui(). 
>>> pd-watchdog monitors its stdin for any input, timing out after 5 seconds if 
>>> nothing was received.
>>> In this case it kills pd with a SIGHUP, but normally it will continue 
>>> looping as long as
>>> characters are received from pd' at a rate of at least one every 5 seconds. 
>>> So if pdtk_watchdog
>>> calls pd every 2 seconds and glob_watchdog() sends a CR each time through 
>>> the pipe, everything
>>> runs smoothly.  
> 
> which part of ths description gives you trouble to understand
> (yes, the description is pretty tech; but i don't know your personal
> background so it'hs hard to give an proper answer to *your* problem).
> 
>> "pd-watchdog monitors its stdin for any input” does this also work if i 
>> start pd with -stderr >2/dev/null ?
> 
> 'stdout' and 'stderr' are unrelated (well, they are related; but
> whatever you do with stderr does not have an effect on stdout).
> but anyhow: yes, this also works if you redirect your stderr.
> 
>> is the fact that i run pd as superuser responsible for pd NOT beeing killed 
>> by SIGHUP ?
> 
> ah well, Pd is not being "killed" by SIGHUP (btw, where did you get this
> from?).
> the watchdog sends a SIGHUP signal to Pd, and Pd *gracefully handles*
> this signal (by releasing the CPU; the idea of pd-watchdog is really to
> prevent a frozen *system*, in case a Pd with realtime-priorities goes
> havoc; the SIGHUP signal will give the *system* a chance to do their
> thing, whatever that is)
> 
> gfasdr
> IOhannes
> 
> ___
> 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

Re: [PD] watchdog -> force restart

[Peter P.]

* michael strohmann  [2019-02-18 10:47]:
> 
> > On 18 Feb 2019, at 10:36, Peter P.  wrote:
> > 
> > * michael strohmann  [2019-02-18 10:22]:
> >> good morning, 
> > Guten Morgen!
> > 
> > I know you didn't want this answer, but, is there a chance you can
> > figure out why you are getting the watchdog message in Pd in the first
> > hand place?
> 
> yes, i think/hope i found the reason (network related) but still would be 
> happy to have a safetynet.
> can only access wiringPI_gpio in sudo mode (raspberry…)

On an RPi 1 I managed to read the gpio pins as normal user by executing
the following script, which starts pd at the end.

#!/bin/bash

# set the TX RX pins to become inputs as well
gpio -g mode 14 in
gpio -g mode 15 in

# set the following pins to low by default
gpio -g mode 4 down
gpio -g mode 5 down
gpio -g mode 0 down
gpio -g mode 6 down

gpio -g mode 15 down
gpio -g mode 8 down
gpio -g mode 7 down
gpio -g mode 1 down

# export the pins to be read by a normal user
# This numbering is already by BCM_GPIO number
gpio export 2 in
gpio export 3 in
gpio export 4 in
gpio export 17 in
gpio export 27 in
gpio export 22 in
gpio export 10 in
gpio export 9 in
gpio export 11 in
gpio export 0 in
gpio export 5 in
gpio export 6 in
gpio export 13 in
gpio export 19 in
gpio export 26 in

gpio export 14 in
gpio export 15 in
gpio export 18 in
gpio export 23 in
gpio export 24 in
gpio export 25 in
gpio export 8 in
gpio export 7 in
gpio export 1 in
gpio export 12 in
gpio export 16 in
gpio export 20 in
gpio export 21 in

pd -rt gpioReading-demo.pd



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] watchdog -> force restart

[IOhannes m zmoelnig]

On 18.02.19 10:21, michael strohmann wrote:
> i need help understanding this description of the pd-watchdog
> 
>> s_watchdog.c is the source of pd-watchdog, which was spawned in 
>> sys_startgui(). 
>> pd-watchdog monitors its stdin for any input, timing out after 5 seconds if 
>> nothing was received.
>> In this case it kills pd with a SIGHUP, but normally it will continue 
>> looping as long as
>> characters are received from pd' at a rate of at least one every 5 seconds. 
>> So if pdtk_watchdog
>> calls pd every 2 seconds and glob_watchdog() sends a CR each time through 
>> the pipe, everything
>> runs smoothly.  

which part of ths description gives you trouble to understand
(yes, the description is pretty tech; but i don't know your personal
background so it'hs hard to give an proper answer to *your* problem).

> "pd-watchdog monitors its stdin for any input” does this also work if i start 
> pd with -stderr >2/dev/null ?

'stdout' and 'stderr' are unrelated (well, they are related; but
whatever you do with stderr does not have an effect on stdout).
but anyhow: yes, this also works if you redirect your stderr.

> is the fact that i run pd as superuser responsible for pd NOT beeing killed 
> by SIGHUP ?

ah well, Pd is not being "killed" by SIGHUP (btw, where did you get this
from?).
the watchdog sends a SIGHUP signal to Pd, and Pd *gracefully handles*
this signal (by releasing the CPU; the idea of pd-watchdog is really to
prevent a frozen *system*, in case a Pd with realtime-priorities goes
havoc; the SIGHUP signal will give the *system* a chance to do their
thing, whatever that is)

gfasdr
IOhannes



signature.asc
Description: OpenPGP digital signature
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] watchdog -> force restart

[michael strohmann]

> On 18 Feb 2019, at 10:36, Peter P.  wrote:
> 
> * michael strohmann  [2019-02-18 10:22]:
>> good morning, 
> Guten Morgen!
> 
> I know you didn't want this answer, but, is there a chance you can
> figure out why you are getting the watchdog message in Pd in the first
> hand place?

yes, i think/hope i found the reason (network related) but still would be happy 
to have a safetynet.
can only access wiringPI_gpio in sudo mode (raspberry…)
is it that bad to run pd as superuser?

> 
> Did you already check the results of
>   aptitude search watchdog
>> 
>> is it possible to automatically restart pd (or the computer) whenever i get 
>> watchdog: signaling pd 
>> ?
>> 
>> in other words: what would be the proper way to monitor a linux system and 
>> act upon e.g. CPU usage greater than xy% ?
>> does anyone have experience with ps-watcher?
>> http://ps-watcher.sourceforge.net 
> I just found these:
> https://rt.wiki.kernel.org/index.php/RT_Watchdog
> 
>> i need help understanding this description of the pd-watchdog
>> 
>> s_watchdog.c is the source of pd-watchdog, which was spawned in 
>> sys_startgui(). pd-watchdog monitors its stdin for any input, timing out 
>> after 5 seconds if nothing was received. In this case it kills pd with a 
>> SIGHUP, but normally it will continue looping as long as characters are 
>> received from pd' at a rate of at least one every 5 seconds. So if 
>> pdtk_watchdog calls pd every 2 seconds and glob_watchdog() sends a CR each 
>> time through the pipe, everything runs smoothly.  
>> 
>> 
>> "pd-watchdog monitors its stdin for any input” does this also work if i 
>> start pd with -stderr >2/dev/null ?
>> is the fact that i run pd as superuser responsible for pd NOT beeing killed 
>> by SIGHUP ?
> Please forgive me, but why do you run Pd as root? Do you really need to
> do so?
> 
> 
> 
> ___
> 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

Re: [PD] watchdog -> force restart

[Peter P.]

* michael strohmann  [2019-02-18 10:22]:
> good morning, 
Guten Morgen!

I know you didn't want this answer, but, is there a chance you can
figure out why you are getting the watchdog message in Pd in the first
hand place?

Did you already check the results of
aptitude search watchdog
> 
> is it possible to automatically restart pd (or the computer) whenever i get 
> watchdog: signaling pd 
> ?
> 
> in other words: what would be the proper way to monitor a linux system and 
> act upon e.g. CPU usage greater than xy% ?
> does anyone have experience with ps-watcher?
> http://ps-watcher.sourceforge.net 
I just found these:
https://rt.wiki.kernel.org/index.php/RT_Watchdog

> i need help understanding this description of the pd-watchdog
> 
> s_watchdog.c is the source of pd-watchdog, which was spawned in 
> sys_startgui(). pd-watchdog monitors its stdin for any input, timing out 
> after 5 seconds if nothing was received. In this case it kills pd with a 
> SIGHUP, but normally it will continue looping as long as characters are 
> received from pd' at a rate of at least one every 5 seconds. So if 
> pdtk_watchdog calls pd every 2 seconds and glob_watchdog() sends a CR each 
> time through the pipe, everything runs smoothly.  
> 
> 
> "pd-watchdog monitors its stdin for any input” does this also work if i start 
> pd with -stderr >2/dev/null ?
> is the fact that i run pd as superuser responsible for pd NOT beeing killed 
> by SIGHUP ?
Please forgive me, but why do you run Pd as root? Do you really need to
do so?



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd & massively multi-channel wi-fi speakers

[Jean-Marie Adrien]

hi
as far as i know, two major problems
- wireless speakers to be found for sale in the industry are based on the 
stereophonic paradigm, music coming out of two holes and that’s it
- wireless technology introduces some latency, which is somehow contradictory 
with the  pd real time approach, even more since the industry runs now after 
the personal assistant segment, to generate more profit, and this introduces 
though even more latency, which is in itself not a problem if you playback dead 
sounds like in the last millenium.

there must be some ways to turn around these problems though, like radios 
indeed :), but these ways around have to be considered in balance with 
installing simple cables, and this even more if sound sources are not mobile in 
space.

i am however always curious to learn about the subject
jm

> Le 18 févr. 2019 à 09:19, Peter P.  a écrit :
> 
> * Kerry Hagan  [2019-02-17 12:56]:
>> Hello all,
>> 
>> Has anyone used wi-fi speakers with Pd? 
> 
>> 
>> More importantly - I would ideally like to send 30 independent audio 
>> channels to 30 battery-powered wi-fi speakers (in the same room)
> Do you mean Wifi or Bluetooth? Could you use small FM transmitters and
> 30 battery powered radios, like, in the last millenium, instead?
> 
>> I’ve never used any wi-fi speakers for anything at all, and I’m finding it 
>> hard to see how they are connected without some proprietary software made by 
>> the usual suspects. I’ve scoured eBay, Amazon, Curry’s without being able to 
>> answer my own questions.
> Well, these pages don't give answers, they sell you things ;)
> 
> 
> 
> ___
> 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] watchdog -> force restart

[michael strohmann]

good morning, 

is it possible to automatically restart pd (or the computer) whenever i get 
watchdog: signaling pd 
?

in other words: what would be the proper way to monitor a linux system and act 
upon e.g. CPU usage greater than xy% ?
does anyone have experience with ps-watcher?
http://ps-watcher.sourceforge.net 



i need help understanding this description of the pd-watchdog

s_watchdog.c is the source of pd-watchdog, which was spawned in sys_startgui(). 
pd-watchdog monitors its stdin for any input, timing out after 5 seconds if 
nothing was received. In this case it kills pd with a SIGHUP, but normally it 
will continue looping as long as characters are received from pd' at a rate of 
at least one every 5 seconds. So if pdtk_watchdog calls pd every 2 seconds and 
glob_watchdog() sends a CR each time through the pipe, everything runs 
smoothly.  


"pd-watchdog monitors its stdin for any input” does this also work if i start 
pd with -stderr >2/dev/null ?
is the fact that i run pd as superuser responsible for pd NOT beeing killed by 
SIGHUP ?___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

[PD] Audio clicks with postgresql external

[Jakob Laue]

Hey all,

I am working on a sample player in pd.

In my patch I am using a postgresql external from here:

https://sourceforge.net/p/pure-data/svn/17183/tree/trunk/externals/postlude/psql/

 

Unfortunately, I get audio clicks when I send a query to my database, which is of course a no-go

as I am playing audio samples.

 

I am on a Raspberry Pi 2, Raspbian Jessie with pd 0.49.

I start my patch like this: sudo pd -rt -nogui mypatch.pd

(sudo because I am using a wiringPi_gpio external which causes pd to crash when it isnt run with sudo...)

 

My queries are only to localhost.

Do you have any ideas how I could solve this?
My first idea was to simply not use postgresql and somehow stick to tables within pd.

But postgresql would come in handy in my patch because I actually wanted to connect to the database from another

second Raspberry Pi aswell.

 

Thanks, Jakob



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] Pd & massively multi-channel wi-fi speakers

[Dan Wilcox]

My 2 cents:

Using just commercial speakers might be difficult. There are devices which use 
the DLNA protocol 
(https://en.wikipedia.org/wiki/Digital_Living_Network_Alliance 
) those which 
use AirPlay by Apple. There might be others, but I think those are the main 
ones right now.

If you are streaming over a network connection, you're always going to be 
running into latency & buffering issues. Also, if you need the channels to be 
synced (ie. mixed down multi-channel piece), you need the system to set 
latencies among the speakers so each is playing roughly in sync with the other. 
Other than professional gear like massively-multichannel over Ethernet 
(Cobranet) or Coax/Fiber (MADI, etc), I'm not sure it would be that easy. 
AirPlay manages this automatically but I have no idea if it could handle that 
many devices as it's probably focused more on consumer situations, up to 10 
devices probably.

On the other side of things, if you don't care about channel syncing as much, 
you could use an Icecast server and have the devices stream audio from the 
local server. This basically works like internet radio and you could probably 
have 16 stereo stream points or even 32 mono points. You'd need to stream from 
whatever is generating/playing the audio. There are a few options out there but 
almost all are focused on stereo, so mileage may vary.

In the opposite direction (streaming many to one), we did a streaming 
performance piece here last summer which forwarded live stereo mixdown from 4 
performances across town simultaneously. Visitors to our studio space could 
then mix & "mash" (apply effects on, etc) the streams using various interfaces. 
I set up an Icecast server as the in between and was able to pull all 4 streams 
at the same time using concurrent VLC clients and forward them to Pd using 
JACK. It was clunky but worked pretty well after some testing.

> On Feb 17, 2019, at 5:14 PM, pd-list-requ...@lists.iem.at wrote:
> 
> Date: Sun, 17 Feb 2019 11:48:43 +
> From: Kerry Hagan mailto:klha...@gmail.com>>
> To: Pd-List mailto:pd-list@lists.iem.at>>
> Subject: [PD] Pd & massively multi-channel wi-fi speakers
> Message-ID: <23bf28c9-deed-44f5-87d2-726af5e87...@gmail.com 
> >
> Content-Type: text/plain; charset=utf-8
> 
> Hello all,
> 
> Has anyone used wi-fi speakers with Pd? 
> 
> More importantly - I would ideally like to send 30 independent audio channels 
> to 30 battery-powered wi-fi speakers (in the same room)
> 
> I’ve never used any wi-fi speakers for anything at all, and I’m finding it 
> hard to see how they are connected without some proprietary software made by 
> the usual suspects. I’ve scoured eBay, Amazon, Curry’s without being able to 
> answer my own questions.
> 
> And, best I can tell, the most flexible assignable speakers cost in the 100s 
> or 1000s of USD/EUR
> 
> I’ve got a budget of a couple 100 euros at best.
> 
> Any advice or pointers are welcome.
> 
> Cheers,
> 
> Kerry


Dan Wilcox
@danomatika 
danomatika.com 
robotcowboy.com 



___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list