Pd-dev

pd-dev@lists.iem.at

2 participants
9620 discussions

Signing deken packages
by Thomas Mayer 30 Nov '22

30 Nov '22

Hello, I have uploaded packages to deken, but have just found out, that these packages were not signed correctly with my gpg key for reasons totally unrelated to deken. Should I reupload the packages or should I sign these packages with gpg, get the signature extension .gpg (or .asc or .sig), and should I upload those signatures via the webinterface to https://puredata.info/Members/residuum/software/purest_json/2.0.0/ Thanks, Thomas -- "It seems to me, Golan, that the advance of civilization is nothing but an exercise in the limiting of privacy." (Janov Pelorat in: Isaac Asimov - Foundation's Edge) http://www.residuum.org/

2 1

mac-dist-helper
by Dan Wilcox 28 Oct '22

28 Oct '22

Howdy all, I've been working on a single solution for creating distribution packages for macOS which automates the whole code signing and notarization process. What I have so far is a makefile inspired by pd-lib-builder which you can drop into a project and configure with only a few variables: https://github.com/zkmkarlsruhe/mac-dist-helper <https://github.com/zkmkarlsruhe/mac-dist-helper> I also have some hello world examples for a Cocoa app, openFrameworks app, console program, and Pure Data external: https://github.com/zkmkarlsruhe/mac-dist-helper-examples <https://github.com/zkmkarlsruhe/mac-dist-helper-examples> So far, I am able to build and package all 4 examples into dmg files which I can AirDrop to a second macOS system and run without warnings, errors, or right-click overrides. -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

2 1

Re: [PD-dev] release pd 0.52 update?
by Miller Puckette 26 Oct '22

26 Oct '22

(In reply to Iohannes - I can't reply directly to the mail for some reason) - I'm leaving for a 5-day trip Thursday - hoping to grind the release out Monday so I have time to fix whatever turns out to be broken before hitting the road. cheers Miller

3 3

CI doesn't see 0.53-0test3 commit?
by Miller Puckette 26 Oct '22

26 Oct '22

Hi all (but sorry, Iohannes really) - I'm back i nteh state where I can't push to github (I'm merging stuff on my own machine and "git push origin --tags" says it's synced but github still doesn't see the new commits I've made, or the tags. So now I'm making a new branch "pure-data/temporary-merge", pushing that successfully, then whacking buttins on the github site to merge it into master. This is stupid and I'd like to find the underlying problem but I'm stumped at the moment. Meanwhile, though, I've managed now to get github to see my "0.53-0test3" commit, and its tag, but now it doesn't show up on the CI system at https://git.iem.at/pd/pure-data/-/pipelines. ... I think this might be related to the first problem and the way I'm trying to work around it, but I could be wrong about that. Anyhow, if anyone can tell me what I have to do now to get the CI system to see and compile 0.53-0test3 I'd love to hear it. thanks Miller

2 5

oops, wierd filename in "po" subdir?
by Miller Puckette 22 Oct '22

22 Oct '22

HI all (but Iohannes I think, sorry) - CI build failed on a file "zho_HANT(a)tw.po" in pd/po . this looks like it's a real language file but not named correctly? cheers Miller

2 2

release pd 0.52 update?
by Miller Puckette 21 Oct '22

21 Oct '22

I just realized from the list that there's a pretty serious bug that's already fixed in git but not in Pd 0.52-0 ... I think it's worth putting out a bugfix version. My plan then would be to merge the latest running updates and some of Alexandre's documentation updates and then release a testing version this weekend. Are there other updates that need to make their way into Pd 0.52-1? (No improvements please, just bug fixes :) Miller

5 18

Re: [PD-dev] release pd 0.52 update?
by Dan Wilcox 16 Oct '22

16 Oct '22

(Whoops, sending again with correct subject line) So far, we have been merging simple fixes into the develop branch, but another approach could be to have two develop branches: * develop: merged things agreed upon for the next release, things which *may* need additional testing as we move forward * develop-stable: bugfixes only, as applied to the current release version For many projects which use git, the master/main branch would be a "develop-stable" and people would checkout releases based on tags. Then a develop branch would be stuff like new features and updates for the next version which would be merged to master/main later on. We have stayed out of touching the master branch since it would have conflicted with the original sourceforge git repository and only Miller touches it. Maybe this is no longer a requirement? > On Oct 15, 2022, at 12:00 PM, pd-dev-request(a)lists.iem.at <mailto:pd-dev-request@lists.iem.at> wrote: > > Even though it's not considered correct behavior, I still find it less > problematic to fully commit to changes in the main branch than to try to > maintain long twisted chains of duplicate bugfixes in both master and in some > 0.52 branch - this didn't work out so well this time around (I cornered myself > into taking the GUI updates into a minor release) but, ouch, we all just have to > deal with my 1970s-vintage coding skills :) -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

Re: [PD-dev] Pd-dev Digest, Vol 209, Issue 3
by Dan Wilcox 16 Oct '22

16 Oct '22

So far, we have been merging simple fixes into the develop branch, but another approach could be to have two develop branches: * develop: merged things agreed upon for the next release, things which *may* need additional testing as we move forward * develop-stable: bugfixes only, as applied to the current release version For many projects which use git, the master/main branch would be a "develop-stable" and people would checkout releases based on tags. Then a develop branch would be stuff like new features and updates for the next version which would be merged to master/main later on. We have stayed out of touching the master branch since it would have conflicted with the original sourceforge git repository and only Miller touches it. Maybe this is no longer a requirement? > On Oct 15, 2022, at 12:00 PM, pd-dev-request(a)lists.iem.at wrote: > > Even though it's not considered correct behavior, I still find it less > problematic to fully commit to changes in the main branch than to try to > maintain long twisted chains of duplicate bugfixes in both master and in some > 0.52 branch - this didn't work out so well this time around (I cornered myself > into taking the GUI updates into a minor release) but, ouch, we all just have to > deal with my 1970s-vintage coding skills :) -------- Dan Wilcox @danomatika <http://twitter.com/danomatika> danomatika.com <http://danomatika.com/> robotcowboy.com <http://robotcowboy.com/>

1 0

PD release plans for 0.52-3
by Miller Puckette 15 Oct '22

15 Oct '22

To pd dev - I've pushed version 0.52-3test1 and am waiting for Hannes's mighty CI system to make a Mac build. Meanwhile I've built and tested in wine but not on a real windows system. I'm away from my usual testing machines til Dec. 9 so will have to do the 0.52-3 release a bit creatively. I'll next get to a Mac (at Columbia U) next Tuesday or Wednesday. In the meantime I'll upload compiles for Mac, Windows 64 and 32, and source to the usual place to fish for whatever problems others mihgt run into. I wasn;t planning on putting any updates out til I can get back to my own lair but there's apparently problem in soundfile reading that necessitates an update. The update is mixed up with several improvements which I'm nervous about but not as nervous as trying to sort out a 0.52 branch would have made me. cheers Miller

2 1

Re: [PD-dev] tilde object rework ideas
by Miller Puckette 04 Sep '22

04 Sep '22

Yep, s_nframes is best. To Iohannes's point (s_n, s_nframes, and s_channels are redundant) , s_n needs to be kept in the struct, and then we could either have s_nframes, or s_nchannels, in which case you'd get the other one by dividing.?? I have a deep horror of integer division (if you ever divide by zero your program will crash, and anyway when I was a kid it could easily take a millisecond to compute). Probably I just have to get over it. (I think nframes is the better one to keep and nchannels should become a macro in the case that we don't just supply both in the structure.) Still wondering about s_samplerate... it's a long name but perhaps it's the shortest good one :) Meanwhile, I'm going to propose that we not bother (yet) with automatically vectorizing stuff like filters, because I think there will be lots of headaches, and anyway one is most likely to want to do more per-channel than just one object at which point the clone object becomes useful. cheers Miller

3 2

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