Pd-dev

pd-dev@lists.iem.at

2 participants
9620 discussions

Re: [PD-dev] macOS 10.15 notarization
by Dan Wilcox 13 Dec '19

13 Dec '19

Ja ja and Apple clubs a seal every time a million iPhones are sold. :P In any case, it seems that, so far there is an official work around for the new security scheme. I'm curious to see if anything will change as the grace-period regarding notarization in macOS 10.15 is supposed to expire. Hopefully ad-hoc apps will still work as the decision to run the app is still left to the user the first time it is launched on the system. If that feature is removed, then Pd and *lots* of open source apps may stop working. I understand the whole point of verification and security certificates, but I also hope they *never* remove the ability to run non-signed software. Fine, show us a warning, but don't lock things down completely for power users, etc. > On Dec 13, 2019, at 11:34 AM, pd-dev-request(a)lists.iem.at wrote: > > On 12.12.19 18:40, Dan Wilcox wrote: >> As for the initial app warning, as far as I can tell, the only way to >> remove it is to sign the app with a developer ID. This requires an >> account and $100 a year. > > Unfortunately there are some more hidden costs: One also needs a Mac for > the XCode toolchain. For the payment you need enable two-factor > authorization in your account (for which you need an iPhone) Both > devices need to run recent OS versions, so they can't be hardware which > Apple deprecated. > If you register a "corporate" account with apple you will have to apply > for a D.U.N.S Number. If you live in Germany, Dun & Bradstreet will sell > your Address Data to the GEZ and you'll have to pay another 69,96 Euros > a year for public radio and TV. > > Think Different! > :D -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

macOS 10.15 notarization
by Dan Wilcox 13 Dec '19

13 Dec '19

Howdy all, The newest version of macOS, 10.15 "Catalina", is out and with it comes a new "Notarization" requirement for applications, etc: https://developer.apple.com/documentation/xcode/notarizing_your_app_before_… <https://developer.apple.com/documentation/xcode/notarizing_your_app_before_…> As far as I can tell, applications do not need to be built via Xcode, but need to be screened and Notarized by Apple. I'm not 100% certain if this applies only to applications signed by a Developer ID or for *all* applications. Regardless of whether we approve of this security step or not (I don't), the practical matter is that Pd *may* suddenly not run for users on 10.15 as it is not notarized or signed. OTOH software that is not signed and is installed "from the wild" *may* still be launched via Right Click -> Open on first run... although I'm not sure. Apple has made the Notarization requirement optional until January 2020 to ease the transition. At this point, it would be helpful to hear from someone who has the new OS if Pd runs and if there are any warning dialogs. In the worst case, we will need an Apple developer account ($100 a year) to signed Pd for distribution and notarization. This also requires using the Xcode 10+ developer tools which rules out Miller's 10.6 build system for this step. it could be integrated as a makefile step. I have a dev account and can do some testing, when needed. In the best case, Right Click -> Open on first run still works. :) -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

5 11

Packaging of Libraries
by Pierre Alexandre Tremblay 13 Dec '19

13 Dec '19

Dear all We plan to use the fantastic Deken infrastructure to distribute the Fluid Corpus Manipulation objects (flucoma.org), but also to respect its folder architecture for any other type of download, i.e. GitHub binaries and such things… I read the very clear document here (https://github.com/pure-data/deken/blob/master/developer/README.md) but it is not clear how we can package extra material, like a folder of audio files used in the help files, and now that we can use html files, some extra references… and even maybe an example folder. Max and SC have clear folder structure for their packaging, and I presume Pd/Deken has it too, but I’ve been unable to locate it, searching the web and the archives of this list. Any pointer welcome. Thanks pa

2 4

Double precision externals extensions.
by Lucas Cordiviola 11 Dec '19

11 Dec '19

Could we have special extension for double-precision external? Something like foo.m_amd64dp ? This way we can have external pkgs including both single and double externals. Also instruct Pd to *not* try to load the not current precision and avoid crashes. -- Mensaje telepatico asistido por maquinas.

3 22

Re: [PD-dev] CAF file support?
by Dan Wilcox 02 Dec '19

02 Dec '19

I'm bringing this back up as I will most likely take a stab at adding CAF support to Pd at work very soon. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

4 3

pd compiled for web with emscripten
by Claude Heiland-Allen 26 Nov '19

26 Nov '19

Hi! As a proof of concept I modified pure-data and libpd just enough to get it to compile with Emscripten and run some patches: https://mathr.co.uk/empd/ Only -nogui mode. You can make GUIs using SDL2 and OpenGL, or using other web APIs (HTML forms, SVG, etc). Performance (provided you compile in Release mode) is about 2x worse than native in one of my tests. Changes were mainly annoying rather than hard: - Emscripten is stricter about calling function pointers with the correct type, this means pd_typedmess explodes from 6 cases to 60. - I also needed to special-case pd_objectmaker in more places, because its methods have return values other than void. - These type errors are only visible at runtime, so I may have missed some - please report. Some other smaller fixes I may make pull-requests for soon. Claude -- https://mathr.co.uk

3 3

Using PD and Patreon
by Agustín Riolfo 28 Oct '19

28 Oct '19

Hello, and thanks for your time. My name is Agustin Riolfo and I am developing a music software to make guitar effects. I found that your software is suitable for my application. I won´t sell the software but I would like to have a Patreon account so that if some fans would like to, can contribute with me. The question is, being that the software would not be sold and that would only be donations, is there any problem on having a Patreon account? Moreover, if I use blocks like [expr] or [expr~] that use a GPL licence (as far as I know), would donations through Patreon be a problem?? Thanks in advance

2 1

Deken GPG signing question
by Jamie Bullock 27 Oct '19

27 Oct '19

Regarding Deken’s GPG signing step… it seems that a “package” or “upload” succeeds even if I type an incorrect GPG password. I discovered this because I accidentally typed a wrong password and the upload still went through without errors. Can someone explain GPG works with regard to Deken, and what the consequence is if the wrong password was typed? Thanks Jamie

2 1

Re: [PD-dev] Deken not adding architecture
by IOhannes m zmölnig 25 Oct '19

25 Oct '19

On 10/24/19 4:48 PM, Jamie Bullock wrote:> > In the same directory as that file, @list: jamie sent me the data off-list > the steps would be: > > $ unzip ml.lib.zip > $ deken package -v 1.0.3 ml.lib.zip i guess this last line really reads: $ deken package -v 1.0.3 ml.lib > > I then get prompted to enter my passphrase to "unlock the secret key”. > On entering the passphrase, 4 files are generated: > > ml.lib[v1.0.3].dek.asc > ml.lib[v1.0.3].dek.sha256 > ml.lib[v1.0.3].dek > ml.lib[v1.0.3].dek.txt weird. it works on Linux with your zip-file. i'll try on OSX. gfmrdsa IOhannes

2 3

Deken not adding architecture
by Jamie Bullock 24 Oct '19

24 Oct '19

Hi list, I’m currently trying to package up a set of externals for Deken release. Following the docs here: https://github.com/pure-data/deken/blob/master/developer/README.md <https://github.com/pure-data/deken/blob/master/developer/README.md> Using version 0.6 of Deken on macOS 64-bit. Based on the README, my expectation is that if I type: $ deken package -v 1.0 foo It will create a file: foo[v1.0](Darwin-x86_64-32).dek However it actually creates: foo[v1.0].dek Is this a Deken bug, or do I need to do something extra? Thanks Jamie

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Pd-dev