From emviveros at gmail.com  Sun Sep  6 21:42:31 2020
From: emviveros at gmail.com (Esteban Viveros)
Date: Sun, 6 Sep 2020 16:42:31 -0300
Subject: [PD-dev] Static/dynamic linking glibc
Message-ID: <CAJQqjJTrmG8p5AcmgcSbzfcanwUKY5JhbeUjL0OTs-F2hgTAQg@mail.gmail.com>

Hello list!

I´m working in compiling Cyclone and Else binaries. We have an issue
<https://github.com/porres/pd-else/issues/779> with glibc version at run
binaries in ubuntu 18.04 (glibc 2.27). I´m compiling it in Ubuntu 20.04
(glibc 2.29). Since compiling it libs with pd-lib-builder I obtain dynamic
link against glicb I think about static link glibc 2.29 using -static flag.


1. I´m looking about how to set this flag to pd-lib-builder avoiding to
break other default assignaled flags.

2. If I have success in embbed glibc in external binaries this cause
problems with the use of licenses that are more permissive than GPL when
using these libs to make other softwares?


Maybe the best is downgrade glibc to 2.27 and offer support from linux
system with this version? what is the standard procedure in distributing
external binaries for these cases?

Thanks
Esteban Viveros

-- 

 Esteban Viveros

www.estebanviveros.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20200906/2389b9bd/attachment.html>

From jmmmpais at gmail.com  Sun Sep 27 01:58:03 2020
From: jmmmpais at gmail.com (=?UTF-8?Q?Jo=C3=A3o_Pais?=)
Date: Sun, 27 Sep 2020 01:58:03 +0200
Subject: [PD-dev] pdmax with settable sampling rate
Message-ID: <CAN46m5oSxPB6XNZ+64N5hqSGWqtCvmXrm053yBSiDv=oPywyAw@mail.gmail.com>

Hello list,

the current version of pdmax only allows the pd sample rate to be set as a
parameter "-sr xxx". Would it be possible to send that as a pd~ message, so
that it can be changed after the object has been initiated? This would
allow for the same patch to be used with different sampling rates.
In my particular case, it would be ok to stop the pd sub-process to change
pd's sample rate, and then reinitiate it.

Best,

Joao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-dev/attachments/20200927/e522bddb/attachment.html>

From zmoelnig at iem.at  Sun Sep 27 12:59:50 2020
From: zmoelnig at iem.at (=?ISO-8859-1?Q?IOhannes_m_zm=F6lnig?=)
Date: Sun, 27 Sep 2020 12:59:50 +0200
Subject: [PD-dev] pdmax with settable sampling rate
In-Reply-To: <CAN46m5oSxPB6XNZ+64N5hqSGWqtCvmXrm053yBSiDv=oPywyAw@mail.gmail.com>
References: <CAN46m5oSxPB6XNZ+64N5hqSGWqtCvmXrm053yBSiDv=oPywyAw@mail.gmail.com>
Message-ID: <BCDAADA7-7D50-44BB-BEC9-C8DAB1B5D4F1@iem.at>

Am 27. September 2020 01:58:03 MESZ schrieb "João Pais" <jmmmpais at gmail.com>:
> Hello list,
> 
> the current version of pdmax only

what's "pdmax"?
how does it differ from [pd~] compiled for max/msp? more to the point: is the issue you are raising here specific to the max/msp-object, or is it a [pd~] issue on all platforms?

>  This would
> allow for the same patch to be used with different sampling rates.

would it?
at least with a Pd-host, the actual sample rate would be determined by the host.
So while the child process might believe that it is running at (say) 96kHz, if the host runs at 44.1kHz the child would still only process 44100 samples per second (and channel).




mfg.hft.fsl
IOhannes