[PD] [PD-announce] Networked Performance Livestream (Into the Multiverse) on Tuesday, Nov 10

[Fede Camara Halac]

Hi Everybody,
Here's an upcoming Networked Performance Livestream using a *hacked* Netty 
McNetface patch for 9 channels (before Miller bumped it up to 12 :) for the 
Wexner Center crew to tap the audio and mix in the video feed for streaming.

Tune in via the vimeo link on this website: 
https://wexarts.org/performing-arts/wexep-sonic-arts-ensemble

---

From Marc Ainger:

We will be presenting a Networked Performance Livestream (Into the Multiverse) 
on Tuesday, Nov 10 at 7 PM EST featuring  the Sonic Arts Ensemble (directed by 
Marc Ainger and Fede Camara Halac) with Elizabeth A Baker,  produced by the 
Wexner Center for the Arts.

Please tune in (It's free! And exciting!)

Best,

Marc Ainger

---



Cheers!



Fede

ps. the netty hack is here for now 
https://drive.google.com/file/d/1RpDCP0bEOjwCu93mNZiGM0OF0dlSv4vF
(be warned, it is a more colorful experience than the original Netty, but it is 
still vanilla)

fdch.github.io
___
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] Sample loop - start and end point (WAV files)

[Ingo]

Thanks for the update, Dan!

 

Ingo

 

From: Dan Wilcox [mailto:danomat...@gmail.com] 
Sent: Monday, November 09, 2020 3:14 PM
To: Ingo; Alexandre Torres Porres
Cc: Pd-List
Subject: Re: [PD] Sample loop - start and end point (WAV files)

 

Howdy all,

 

I did give up for a while. The discussion is here:

 

https://github.com/pure-data/pure-data/pull/897

 

I still have the relevant code but there was simply too much to do back then
and I had to pull back and put it on the back burner. It's still something I
think should be working in Pd, but maybe restricted to *read* only as a
start instead of me trying to implement full write access.

 

My first focus is to get the sound file updates into a Pd release as we need
CAF and AIFC support for a major project at work:
https://github.com/pure-data/pure-data/pull/855

 

Once that is in, say Pd 0.52, then I can refactor the previous meta read
code, otherwise there is no-one stopping someone from writing an external
using something like libsndfile to poop out metadata

 

On Nov 9, 2020, at 1:28 PM, pd-list-requ...@lists.iem.at
  wrote:

 

Date: Mon, 9 Nov 2020 13:15:15 +0100
From: "Ingo" <  i...@miamiwave.com>
To: "'Alexandre Torres Porres'" < 
por...@gmail.com>
Cc: "'Pd-List'" <  pd-list@lists.iem.at>
Subject: Re: [PD] Sample loop - start and end point (WAV files)
Message-ID: < 
01d6b691$fbb7acc0$f3270640$@miamiwave.com>
Content-Type: text/plain; charset="utf-8"

Dan Wilcox was working in the ability of [soundfiler] to read the loop point
within Pd.

In Pd 0.51.1 there was still no change concerning sample loop points -
unless it's not documented in the help file.



Reading and writing loop points outside of Pd is no problem. I've been doing
this for more that 30 years.



However, I need to be able to automatically read loop points within Pd when
unknown samples are being loaded.

So far I had to get the loop points in other softwares and write lists for
Pd to be able to handle them.

This is rather tedious and also prone for errors. One little typo and you
get clicks!



Especially this won't work for simply loading new sample into an existing Pd
patch by other users.



I hope Dan didn't give up on ths . . .



Ingo

 



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

Re: [PD] Sample loop - start and end point (WAV files)

[Dan Wilcox]

Howdy all,

I did give up for a while. The discussion is here:

https://github.com/pure-data/pure-data/pull/897 


I still have the relevant code but there was simply too much to do back then 
and I had to pull back and put it on the back burner. It's still something I 
think should be working in Pd, but maybe restricted to *read* only as a start 
instead of me trying to implement full write access.

My first focus is to get the sound file updates into a Pd release as we need 
CAF and AIFC support for a major project at work: 
https://github.com/pure-data/pure-data/pull/855 


Once that is in, say Pd 0.52, then I can refactor the previous meta read code, 
otherwise there is no-one stopping someone from writing an external using 
something like libsndfile to poop out metadata

> On Nov 9, 2020, at 1:28 PM, pd-list-requ...@lists.iem.at wrote:
> 
> Date: Mon, 9 Nov 2020 13:15:15 +0100
> From: "Ingo" mailto:i...@miamiwave.com>>
> To: "'Alexandre Torres Porres'" mailto:por...@gmail.com>>
> Cc: "'Pd-List'" mailto:pd-list@lists.iem.at>>
> Subject: Re: [PD] Sample loop - start and end point (WAV files)
> Message-ID: <01d6b691$fbb7acc0$f3270640$@miamiwave.com 
> >
> Content-Type: text/plain; charset="utf-8"
> 
> Dan Wilcox was working in the ability of [soundfiler] to read the loop point 
> within Pd.
> 
> In Pd 0.51.1 there was still no change concerning sample loop points - unless 
> it's not documented in the help file.
> 
> 
> 
> Reading and writing loop points outside of Pd is no problem. I've been doing 
> this for more that 30 years.
> 
> 
> 
> However, I need to be able to automatically read loop points within Pd when 
> unknown samples are being loaded.
> 
> So far I had to get the loop points in other softwares and write lists for Pd 
> to be able to handle them.
> 
> This is rather tedious and also prone for errors. One little typo and you get 
> clicks!
> 
> 
> 
> Especially this won't work for simply loading new sample into an existing Pd 
> patch by other users.
> 
> 
> 
> I hope Dan didn't give up on ths . . .
> 
> 
> 
> Ingo


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

Re: [PD] help on bash script

[Jakob Laue]

thanks, jack!
 
 

Gesendet: Montag, 09. November 2020 um 14:00 Uhr
Von: "Jack" 
An: pd-list@lists.iem.at
Betreff: Re: [PD] help on bash script
Here a bash script I used to use. You can adapt it for your needs :

#!/bin/bash
chemin1=$(dirname "$0")/PH.pd
sudo etherwake C8:60:00:2D:48:50
sleep 1
pd -nosleep -noaudio -alsamidi -midiindev 0,1 -midioutdev 0 -open $chemin1 &
sleep 1
KA=$(aconnect -i | grep "Pure Data")
while [ "$KA" = "" ]
do
sleep 1
KA=$(aconnect -i | grep "Pure Data")
done
aconnect 'Pure Data':2 'UM-1':0
sleep 1
aconnect 'UM-1':0 'Pure Data':0
sleep 1
aconnect 'nanoKONTROL':0 'Pure Data':1
echo "//Done.//"

++

Jack


Le 09/11/2020 à 13:25, Roman Haefeli a écrit :
> On Mon, 2020-11-09 at 12:54 +0100, Jakob Laue wrote:
>> Hey friends,
>> i have a raspberry pi that executes a bash script on startup. Inside
>> this bash script I want two things to happen.
>> 1) start my pd patch
>> 2) connect my launchpad mini (connected via usb) to pd using the
>> aconnect-command
>>
>>
>> ..i think i have to use aconnect because in pd itself i only see alsa
>> midi as a midi device.
>>
>>
>> At the moment, my bash script only looks like this:
>>
>> #!/bin/bash
>>
>> sudo /usr/local/bin/pd -nogui -rt -open
>> /home/pi/Documents/RSP/RSP/myPatch.pd
>>
>> aconnect 'Pure Data':1 'Launchpad Mini':0
>>
>> aconnect 'Launchpad Mini':0 'Pure Data':0
>>
>>
>>
>> The problem is that the aconnect-commands seem to be not executed or
>> executed too early because the virtual midi connections are not made.
>>
>> The aconnect-commands have to be done after pd is started, so how
>> could I change the script to wait until pd is done loading?
>
>
> Poor man's solution:
>
> put a 'sleep 5' after starting Pd.
>
> A slightly more advanced way:
>
> while ! aconnect --list | grep "Pure Data"; do sleep 0.1;
>
> Put that after firing up Pd. It continues only after "Pure Data"
> appears in the list of available MIDI ports.
>
> Roman
>
>
> ___
> 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[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] help on bash script

[Jakob Laue]

Gesendet: Montag, 09. November 2020 um 13:59 Uhr
Von: "Peter P." 
An: pd-list@lists.iem.at
Betreff: Re: [PD] help on bash script
* Roman Haefeli  [2020-11-09 13:25]:
[...]
> Poor man's solution:
>
> put a 'sleep 5' after starting Pd.
This of course introduces a race condition. Might almost always work™.

> A slightly more advanced way:
>
> while ! aconnect --list | grep "Pure Data"; do sleep 0.1;
>
> Put that after firing up Pd. It continues only after "Pure Data"
> appears in the list of available MIDI ports.
Which is much more elegant, thanks Roman. Note that this will cause
confusion when more than one Pd instance is running. A possible command
line flag to name a Pd instance for alsa-midi was discussed in the
aforementioned thread. It seems that it did not get implemented in the
end.

Yes, that looks elegant indeed! I will try that, thanks!
Regarding multiple instances of pd: For now I have not planned to run more than 
one instance of pd, so I think I am good with that for now:)



___
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] help on bash script

[Jack]

Here a bash script I used to use. You can adapt it for your needs :

#!/bin/bash
chemin1=$(dirname "$0")/PH.pd
sudo etherwake C8:60:00:2D:48:50
sleep 1
pd -nosleep -noaudio -alsamidi -midiindev 0,1 -midioutdev 0 -open $chemin1 &
sleep 1
KA=$(aconnect -i | grep "Pure Data")
while [ "$KA" = "" ]
do
sleep 1
KA=$(aconnect -i | grep "Pure Data")
done
aconnect 'Pure Data':2 'UM-1':0
sleep 1
aconnect 'UM-1':0 'Pure Data':0
sleep 1
aconnect 'nanoKONTROL':0 'Pure Data':1
echo "//Done.//"

++

Jack


Le 09/11/2020 à 13:25, Roman Haefeli a écrit :
> On Mon, 2020-11-09 at 12:54 +0100, Jakob Laue wrote:
>> Hey friends,
>> i have a raspberry pi that executes a bash script on startup. Inside
>> this bash script I want two things to happen.
>> 1) start my pd patch
>> 2) connect my launchpad mini (connected via usb) to pd using the
>> aconnect-command
>>  
>>  
>> ..i think i have to use aconnect because in pd itself i only see alsa
>> midi as a midi device. 
>>  
>>  
>> At the moment, my bash script only looks like this:
>>  
>> #!/bin/bash
>>
>> sudo /usr/local/bin/pd -nogui -rt -open
>> /home/pi/Documents/RSP/RSP/myPatch.pd
>>
>> aconnect 'Pure Data':1 'Launchpad Mini':0
>>
>> aconnect 'Launchpad Mini':0 'Pure Data':0
>>
>>  
>>
>> The problem is that the aconnect-commands seem to be not executed or
>> executed too early because the virtual midi connections are not made.
>>
>> The aconnect-commands have to be done after pd is started, so how
>> could I change the script to wait until pd is done loading?
> 
> 
> Poor man's solution:
> 
>   put a 'sleep 5' after starting Pd.
> 
> A slightly more advanced way:
> 
>   while ! aconnect --list | grep "Pure Data"; do sleep 0.1;
> 
>   Put that after firing up Pd. It continues only after "Pure Data"
>   appears in the list of available MIDI ports.
> 
> Roman
> 
> 
> ___
> Pd-list@lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
> 




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] help on bash script

[Peter P.]

* Roman Haefeli  [2020-11-09 13:25]:
[...]
> Poor man's solution:
> 
>   put a 'sleep 5' after starting Pd.
This of course introduces a race condition. Might almost always work™.
 
> A slightly more advanced way:
> 
>   while ! aconnect --list | grep "Pure Data"; do sleep 0.1;
> 
>   Put that after firing up Pd. It continues only after "Pure Data"
>   appears in the list of available MIDI ports.
Which is much more elegant, thanks Roman. Note that this will cause
confusion when more than one Pd instance is running. A possible command
line flag to name a Pd instance for alsa-midi was discussed in the
aforementioned thread. It seems that it did not get implemented in the
end.

cheers, P



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

Re: [PD] Sample loop - start and end point (WAV files)

[Ingo]

Dan Wilcox was working in the ability of [soundfiler] to read the loop point 
within Pd.

In Pd 0.51.1 there was still no change concerning sample loop points - unless 
it's not documented in the help file.

 

Reading and writing loop points outside of Pd is no problem. I've been doing 
this for more that 30 years.

 

However, I need to be able to automatically read loop points within Pd when 
unknown samples are being loaded.

So far I had to get the loop points in other softwares and write lists for Pd 
to be able to handle them.

This is rather tedious and also prone for errors. One little typo and you get 
clicks!

 

Especially this won't work for simply loading new sample into an existing Pd 
patch by other users.

 

I hope Dan didn't give up on ths . . .

 

Ingo

 

 

 

From: Alexandre Torres Porres [mailto:por...@gmail.com] 
Sent: Sunday, November 08, 2020 9:13 PM
To: Ingo
Cc: Pd-List
Subject: Re: [PD] Sample loop - start and end point (WAV files)

 

Ingo, did you have any luck on this throughout the year?

 

I'm also curious on this. Anyway, I had another thread here and someone 
suggested http://loopauditioneer.sourceforge.net/ that seems to read loop 
points - but I can't test it because it's linux

 

Em qua., 12 de fev. de 2020 às 05:39, Ingo mailto:i...@miamiwave.com> > escreveu:

There are softwares like AwaveStudio that do nothing else but format 
conversion between different sampler formats that can handle the loop points 
as well.


> I have been working with hardware samplers since the 80ies and used
> (mainly) softwares like SoundForge or Wavelab for looping.
> There was no extra file. All hardware samplers could read the loops. Once a
> file was looped with one sampler it would be looped with the next one.
> Same thing with modern software Samplers like Kontakt.
> I can use a sample that I looped in Wavelab and load it into SoundForge and 
> it
> recognizes the loops.
> (There are options for multiple loops, though that might not work with some
> samplers.)
>
> It can't be such a secret since over 30 years that all manufacturers 
> (software
> or hardware) know about it but noone else.
> I have been looking around but couldn't find any information where the
> loops are stored in the file but they definitely are.
>
> Ingo
>
>
> > -Original Message-
> > From: Pd-list [mailto:pd-list-boun...@lists.iem.at 
> >  ] On Behalf Of Roman
> > Haefeli
> > Sent: Wednesday, February 12, 2020 8:48 AM
> > To: pd-list@lists.iem.at  
> > Subject: Re: [PD] Sample loop - start and end point (WAV files)
> >
> > On Tue, 2020-02-11 at 21:22 -0800, Alexandre Torres Porres wrote:
> > > Well, I was really really hoping to see information here on how to
> > > get loop points from these files ;)
> >
> > I looked around for specifications of the .wav-format and I wasn't
> > able to find one that looks canonical. The ones I found didn't mention
> > any loop start- and endpoints. I wonder whether there is a convention
> > about how to encode this into some sort of metadata stored with file.
> > Some description of the format describe the ability to store anything
> > as metdata. Personally, I never dealt with such files (at least not
> > knowingly). Maybe a good start would be to provide such a file, so
> > that people can a have a look at it. It might be not that difficult to
> > retrieve such data with something like mrpeach's [binfile], once you know
> how it is stored.
> >
> >
> > Roman





___
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] help on bash script

[Roman Haefeli]

On Mon, 2020-11-09 at 12:54 +0100, Jakob Laue wrote:
> Hey friends,
> i have a raspberry pi that executes a bash script on startup. Inside
> this bash script I want two things to happen.
> 1) start my pd patch
> 2) connect my launchpad mini (connected via usb) to pd using the
> aconnect-command
>  
>  
> ..i think i have to use aconnect because in pd itself i only see alsa
> midi as a midi device. 
>  
>  
> At the moment, my bash script only looks like this:
>  
> #!/bin/bash
> 
> sudo /usr/local/bin/pd -nogui -rt -open
> /home/pi/Documents/RSP/RSP/myPatch.pd
> 
> aconnect 'Pure Data':1 'Launchpad Mini':0
> 
> aconnect 'Launchpad Mini':0 'Pure Data':0
> 
>  
> 
> The problem is that the aconnect-commands seem to be not executed or
> executed too early because the virtual midi connections are not made.
> 
> The aconnect-commands have to be done after pd is started, so how
> could I change the script to wait until pd is done loading?


Poor man's solution:

  put a 'sleep 5' after starting Pd.

A slightly more advanced way:

  while ! aconnect --list | grep "Pure Data"; do sleep 0.1;

  Put that after firing up Pd. It continues only after "Pure Data"
  appears in the list of available MIDI ports.

Roman


signature.asc
Description: This is a digitally signed message part
___
Pd-list@lists.iem.at mailing list
UNSUBSCRIBE and account-management -> 
https://lists.puredata.info/listinfo/pd-list

Re: [PD] help on bash script

[Peter P.]

* Jakob Laue  [2020-11-09 12:54]:
> Hey friends,
> i have a raspberry pi that executes a bash script on startup. Inside this bash
> script I want two things to happen.
> 1) start my pd patch
> 2) connect my launchpad mini (connected via usb) to pd using the
> aconnect-command

Have you tried searching for the keyword "aconnect" in the mailing list
archive?

See eg this thread
https://lists.puredata.info/pipermail/pd-list/2015-05/110230.html
It seems that [aconnect] is not found when using "Find externals". Its
sources are in SVN at least.

Dan's script from this thread
https://lists.puredata.info/pipermail/pd-list/2014-01/105522.html
is also nice!



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

[PD] help on bash script

[Jakob Laue]

Hey friends,

i have a raspberry pi that executes a bash script on startup. Inside this bash script I want two things to happen.

1) start my pd patch

2) connect my launchpad mini (connected via usb) to pd using the aconnect-command

 

 

..i think i have to use aconnect because in pd itself i only see alsa midi as a midi device. 

 

 

At the moment, my bash script only looks like this:

 


#!/bin/bash

sudo /usr/local/bin/pd -nogui -rt -open /home/pi/Documents/RSP/RSP/myPatch.pd

aconnect 'Pure Data':1 'Launchpad Mini':0

aconnect 'Launchpad Mini':0 'Pure Data':0

 

The problem is that the aconnect-commands seem to be not executed or executed too early because the virtual midi connections are not made.

The aconnect-commands have to be done after pd is started, so how could I change the script to wait until pd is done loading?

Thanks!




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