Re: [PD-dev] How to submit patches to to maxlib and other externals?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2014-09-07 17:22, Ivica Ico Bukvic wrote: I have a fix that allows average object to accept arbitrary amount of arguments to average against, rather than being hardwired to 128. Also, does checks against negative values passed into the right

Re: [PD-dev] [PD] more about float limitation

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-02-04 10:57, katja wrote: What would a legacy Pd build do with fat-precision binaries? Could we consider single precision the default and not rename the setup function compiled for single precision so it will still work with legacy

Re: [PD-dev] flext @ github

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-03-29 14:32, Thomas Grill wrote: Dear sourceforge pd repo admins, have i lost my read-write access to the pd-extended repository? yes you did (every now and then i remove non-active members from the project - not without prior warning

Re: [PD-dev] HD support in Pd

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 2015-02-22 17:10, Martin Peach wrote: There is already a t_int in Pd, it just isn't used. the t_int type *is* used quite a lot: it is the type to be passed and returned tp/from the DSP perform callback. i'm not sure whether using it as a

Re: [PD-dev] library class names loading depth 1000 reached

On 2015-04-28 10:27, Jamie Bullock wrote: Looking at the source code for these externals (and I guess this is a wider design pattern?), I notice that class constructor is bound to a symbol of the form “folder/object”, e.g. class_new(gensym(iemlib/soundfile_info”) … not in my book¹. which

Re: [PD-dev] Compiling externals for Windows

On 2015-06-23 15:01, Roman Haefeli wrote: On Linux, the order seems to be local first, system last: yes, that is what my flawed logic was based upon... I guess if we have that on Windows, too, things should work fine. i think the better approach is to filter the non-writable directories from

Re: [PD-dev] Compiling externals for Windows

On 2015-06-21 12:13, Roman Haefeli wrote: Hey all The new deken plugin makes me want to compile externals for Windows. There seem to be many ways to go and I might save some time if I knew beforehand what works and what no so well. I have access to the following archs: * Debian 7 (i386,

Re: [PD-dev] Compiling externals for Windows

On 2015-06-21 12:13, Roman Haefeli wrote: On a related note: How feasible is it to cross-compile for Mac OS X? i never tried, since you can install a proper toolchain (that can handle GNU makefiles and autotools) on OSX easy enough (unlike W32 where i found it virtually impossible) fsmdr

[PD-dev] compiling pd-watchdog on W32 (was Re: Compiling externals for Windows)

On 2015-06-23 00:54, Roman Haefeli wrote: Because IOhannes provided a fix, I then was also able to successfully cross-compile on Linux _with autotools_: ./configure --host i686-w64-mingw32 --prefix /opt/pd_win32/ for the record: the fix mentioned can be found here [552]. we also needed to

Re: [PD-dev] Compiling externals for Windows

On 2015-06-23 11:06, Roman Haefeli wrote: set ::deken::installpath $env(USERPROFILE) makes deken download to the correct path in W7. Can't test in Windows XP are you sure? i would expect that to install to %AppData% rather than %AppData%\Pd. but probably the best solution would be to check

[PD-dev] Re: External development: preventing several copies of external

On 2015-06-14 21:36, Alexandre Clément wrote: I tried going the same approach as checking if a receiver exists before attempting to send, but it doesn't seem to work. if (gensym(class_name)-s_thing) { post(Exists!); return false; } Any help is greatly appreciated. as you

Re: [PD-dev] moving to git?

On 2015-08-06 15:54, Jonathan Wilkes via Pd-dev wrote: In the original scheme I would just keep bothering you or Hans to give commit access to someone wanting to adopt an external lib. In the new scheme will I just keep bothering you until you add a reference to the centralized list?

[PD-dev] sourceforge...

due to the continued outage of the sourceforge repository service, i wonder whether anybody has a *complete* backup (including the entire history) of the Pd repository? if somebody has a recent checkout of the entire tree (or at least trunk) they might want to make a backup as well. just in

Re: [PD-dev] Windows installer for Pd

On 2015-11-11 10:41, Roman Haefeli wrote: >> iirc, the main problem with this is, that for the *uninstaller* you need >> > to enumerate the files as well (again you can use wildcards, but then >> > you risk deleting unrelated files) > Yes, one more reason to build the list of files dynamically. >

Re: [PD-dev] Windows installer for Pd

On 2015-11-10 21:54, Roman Haefeli wrote: > > The not so nice part about NSIS is that you have to list every single > file of your source packet explicitly and tell it where to install. > Since it is inconvenient to touch that script whenever a new version is > released, I added a bash script

Re: [PD-dev] sound filer samplerate outlet?

On 2015-11-04 07:17, Dan Wilcox wrote: > to simply output the samplerate out of a right outlet to compliment the > sample length from the left outlet? in which case i would suggest having the 2nd outlet output a *message* that also contains the property-name. e.g. [samplerate 44100, frames

Re: [PD-dev] how to package libs with third party deps with deken?

On 2015-12-15 16:18, Roman Haefeli wrote: > How can/should externals be distributed with deken that depend on other > libraries? Let's say I'd like to create a deken package for the aubio > library which depends on libaubio. What's the process? Would I just > include a libaubio binary and make

Re: [PD-dev] building on OS X

On 2015-12-15 16:09, Roman Haefeli wrote: > p.s.: > I converted the few externals I care about to Katja's pd-lib-builder > Makefile. please give back. the biggest problem with deken right now as i see it, is that it makes it super easy to upload some totally unreproducible foo. there is a

Re: [PD-dev] problem with PA and Jack on OS X

On 2016-06-14 14:50, IOhannes m zmoelnig wrote: > - start jackd (e.g. using qjackctl) or whatever your jack GUI of choice is, on OSX... fgamsdr IOhannes signature.asc Description: OpenPGP digital signature ___ Pd-dev mailing list Pd-dev@lists.iem

Re: [PD-dev] problem with PA and Jack on OS X

On 2016-06-14 12:57, Marco Matteo Markidis wrote: > I tried to start also Pd with Jack and in this case Jack didn't > start properly giving me an visible error message. so what was the error message? mine would say: > JACK: unable to connect to JACK server. Is JACK running? > JACK: server

Re: [PD-dev] deken package update

On 2016-06-01 15:00, Marco Matteo Markidis wrote: > Dear list, > > yesterday a guy on the general list reported me a bug and I did an update > to one of my external, that is available on deken. > Today I will update the deken repository; the suggested practice is update > the external with

Re: [PD-dev] [pure-data:pure-data] 2 new commits to pure-data

On 2016-03-22 21:18, IOhannes m zmölnig wrote: > - there is a separate "pd-deployment" branch in the deken repository, > where only "ready to be included" versions of the plugin are found. > it's always safe to include the latest version of this branch into Pd. ok, i've implemented that now.

Re: [PD-dev] [PD] can't load abstractions using fuill pathname?

On 2016-04-25 03:41, Miller Puckette wrote: > I think this is one for Iohannes... indeed. thanks for the report. > > I can't seem to load abstractions by typing the full pathname anymore... > e.g. [/tmp/output~] fails, even if /tmp/output~.pd exists. I get > > maximum object loading depth

Re: [PD-dev] DEFDACBLKSIZE and DEFSENDVS

On 2016-07-11 06:56, Giulio Moro via Pd-dev wrote: > Hi,what are the reasons why > a) DEFDACBLKSIZE is defined in multiple places extra/pd~/pd~.c:50:#define > DEFDACBLKSIZE 64src/s_audio_esd.c:71:#define DEFDACBLKSIZE > 64src/s_stuff.h:66:#define DEFDACBLKSIZE 64? well: - extra/pd~/pd~.c only

Re: [PD-dev] DEFDACBLKSIZE and DEFSENDVS

On 2016-07-12 04:51, Giulio Moro via Pd-dev wrote: > My original question was also about why it is defined in multiple places and > why DEFSENDVS is defined separately, yet setting them to two different values > gives errors. was it? i don't see this question in your original mail. also: what

Re: [PD-dev] DEFDACBLKSIZE and DEFSENDVS

On 2016-07-11 06:56, Giulio Moro via Pd-dev wrote: > b) DEFSENDVS is defined as src/d_global.c:10:#define DEFSENDVS 64/* LATER > get send to get this from canvas */ > and not as #define DEFSENDVS DEFDACBLKSIZE because they are unrelated. DEFDACBLKSIZE is the blocksize enforced by

Re: [PD-dev] comport - compilation with mingw

On 2017-02-27 10:59, Roman Haefeli wrote: > Now, I wonder whether I rather should host the git forks of those > externals under the umbrella of the pure-data group than under my > personal 'reduzent' account. What do you think? > > I'd like to contribute in a meaningful manner with causing as

[PD-dev] "comport" has moved to git (was Re: comport)

On 2017-02-27 11:14, Roman Haefeli wrote: > On Mon, 2017-02-27 at 11:02 +0100, IOhannes m zmoelnig wrote: >> On 2017-02-27 10:59, Roman Haefeli wrote: >>> >>> Now, I wonder whether I rather should host the git forks of those >>> externals under the umbrella

Re: [PD-dev] "comport" has moved to git (was Re: comport)

On 2017-02-27 11:36, Roman Haefeli wrote: > On Mon, 2017-02-27 at 11:22 +0100, IOhannes m zmoelnig wrote: > Ok, I requested access. > > Now, are you OK at all with me converting the build system to pd-lib- > builder? go ahead from my side. fgasdmr Ihannes signature.

Re: [PD-dev] Rewrite wrap~ to allow an extra block

On 2016-09-29 16:25, Ed Kelly via Pd-dev wrote: > Because the control-rate message doesn't happen until the end of the audio > block but ain't this just wrong? iirc, the control-rate message happens before the audio block. anyhow, at the end of the audio block, it's too late to do audio

Re: [PD-dev] Rewrite wrap~ to allow an extra block

On 2016-09-29 12:00, Ed Kelly via Pd-dev wrote: > Hey list,I'm tearing my hair out trying to re-write the wrap~ object, so that > it doesn't wrap instantly but waits until the end of the audio block to wrap~ > the signal. I hope you understand. no (nto trying very hard though). i'm pretty

Re: [PD-dev] Conflict: incoming OSC data and DSP on

On 2017-04-11 00:56, Niccolò Granieri wrote: > Hello Pd-dev mailing list, > > I am writing, for the first time, to point out an issue I'm having with > incoming OSC data in Pd and DSP being turned on. > > The problem occurs when, while receiving OSC data from inside my machine > (thus using a

Re: [PD-dev] Conflict: incoming OSC data and DSP on

On 2017-04-11 14:16, Niccolò Granieri wrote: > Hi IOhannes, thanks a lot for your feedback. > > I guess there is something else that I'm not taking into account. Because > both on the test patch I sent over, and on the actual patch I'm working on > with which I'm having issues, if I turn DSP on

Re: [PD-dev] Conflict: incoming OSC data and DSP on

On 2017-04-11 13:31, Niccolò Granieri wrote: > Here is the fully automated patch. Hope it helps. thanks. it's perfect. unfortunately it just shows that everything is working as expected. even if i lower the first metro to 1ms. i'm testing this on Debian/sid, with Pd-vanilla (0.47.1, as packaged

Re: [PD-dev] Conflict: incoming OSC data and DSP on

On 2017-04-11 11:30, Niccolò Granieri wrote: > - I'm attaching the minimal test patch with which I was able to reproduce the > bug. thanks. however, that test patch doesn't do anything (yet). could you make the TestPatch complete, so that it: - can be run as a standalone? (e.g. it includes a

[PD-dev] [ot] quoting (was Re: building with msys2)

On 2017-07-12 10:11, Roman Haefeli wrote: > On Mit, 2017-07-12 at 09:55 +0200, IOhannes m zmoelnig wrote: > >> - would it be possible to configure your mail-client to properly >> quote the emails you reply to? i'm spending more time figuring out >> what is a reply to wha

Re: [PD-dev] building with msys2

On 2017-07-11 17:26, patrice colet wrote: > I don't get why gcc is saying this: there's at least one pull request on github that tries to eliminate duplicate declarations (which is one of the errors you are getting). did you try it? fgmasdr IOhannes signature.asc Description: OpenPGP digital

Re: [PD-dev] building Pd with makefile.msvc

On 2017-06-29 13:55, Dan Wilcox wrote: > >> On 06/28/2017 04:20 AM, Dan Wilcox wrote: >>># statically link pthread into the exe, otherwise we get a missing dll >>> error >>>LIBS="-Wl,-Bstatic -static $LIBS -Wl,-Bdynamic" >> >> but that links in *all* libraries statically (not just

Re: [PD-dev] defining PDINSTANCE and PDTHREADS in libpd

On 2017-05-03 16:24, Miller Puckette wrote: > I think I need to find a way to detect at configuration time (?) whether > the compiler supports per-thread storage, hmm https://www.gnu.org/software/autoconf-archive/ax_tls.html mdra IOhannes signature.asc Description: OpenPGP digital

Re: [PD-dev] defining PDINSTANCE and PDTHREADS in libpd

On 2017-04-17 22:03, Miller Puckette wrote: > Meanwhile, there's no assumed relationship between instances and threads. i was tempted to say hooray, but then... ... i discovered the use of the PERTHREAD macro which expands to "__thread" which is the keyword for TLS (thread local storage); i

Re: [PD-dev] unable to load pdp library (mach-o, but wrong architecture)

(redirecting this to pd-list, as it is of general interest rather than developer centric, even though a compiler is involved) On 2017-05-08 02:13, cjniven wrote: > The problem is both pdp and pd that I’ve compiled from source are built for > my native architecture (x86_64), but the pre-compiled

Re: [PD-dev] atoms not same height as objects?

On 2017-09-20 18:53, Dan Wilcox wrote: > I'm thinking of having, at the very least, a start flag to choose the > extended styling ala "-style extended." This could be used as the basis for > adding some sort of styling file parsing/loading, but that's beyond what I'm > looking to do right now.

Re: [PD-dev] [pure-data:svn] New commit [r17643] by mrpeach

On 2017-10-11 23:00, Pure Data Computer Music System SVN repository wrote: > Don't use sys_fopen with MSVC as its FILE struct is not compatible. hmm, i'm pretty sure this is the wrong approach. the sole purpose of sys_fopen() is to help Windows users (as it wraps the use of non-ascii filenames!).

Re: [PD-dev] Pd-ceammc

On 2017-08-20 19:51, Dan Wilcox wrote: > (Sending again, in thread) > > Even if a lot of those changes come from Pd-extended? Kind of > forward-back-porting? this doesn't really matter. Pd-extended itself aimed towards GPL-3, so a lot of patches for Pd might have been distributed under that

Re: [PD-dev] How to customize Pd.app for macOS?

On 2017-12-13 14:56, Roman Haefeli wrote: > I guess I figured it out. > > From the scripts in /mac/ I found that /Contents/MacOS/Pd is > actually a wish binary, which starts /Contents/Resources/tcl/pd- > gui.tcl, which in turn starts the pd binary in > /Contents/Resources/bin/pd. actually, you

Re: [PD-dev] How to customize Pd.app for macOS?

On 2017-12-13 22:28, Ingo Stock wrote: > You can set the audio settings from within a patch by sending a message > to pd. > > The message would look like this: > > [; pd audio-dialog 0 0 0 0 1 0 0 0 0 0 0 0 2 0 0 0 44100 25 -1 128] two things: #1 while not being vanilla, i think the

[PD-dev] riddle

attached is a nice one. why do both patches look the same? fgamsdr IOhannes #N canvas 5 50 450 300 10; #N canvas 5 50 450 300 (subpatch) 0; #X obj 126 149 i, f 42; #X restore 119 147 pd; #N canvas 5 50 450 300 10; #N canvas 5 50 450 300 (subpatch) 0; #X obj 126 149 i; #X restore 119 147 pd, f

Re: [PD-dev] riddle

On 2017-11-16 13:21, IOhannes m zmoelnig wrote: > attached is a nice one. > > why do both patches look the same? > but of course, #1306 is exactly about this issue. mfgad IOhannes signature.asc Description: OpenPGP digital signature __

Re: [PD-dev] riddle

On 2017-11-16 13:31, Pierre Guillot wrote: > If it's about the size of the sub-patches, I already reported the bug. oh my: you got the award! thanks for pointing me to the PR (omg, i'm already assigned as a reviewer...) signature.asc Description: OpenPGP digital signature

Re: [PD-dev] PDINSTANCE: when and where?

On 2017-12-19 21:20, Giulio Moro via Pd-dev wrote: > i, > I just realized that there are a plethora of #ifdef PDINSTANCE in the Pd > source code, but no actual #define PDINSTANCE or -DPDINSTANCE, and grepping > the whole repo, I cannot find any place where it is defined. > So, is anyone defining

Re: [PD-dev] pd.lib & msvc - missing symbols

On 2018-05-23 11:29, Pierre Guillot wrote: > But there are missing symbols: on Windows > 64bit I can't use s_list and s_signal for example. I solved the issue by > creating my own pd.lib and pd.def from pd.dll. So if you encounter the same > issue, you can simply do > >> dumpbin /EXPORTS pd.dll >

Re: [PD-dev] backslash in Pd console

On 2018-05-23 12:30, Max wrote: > For the archive: > >     post("\u005C"); >     post("\x5C"); > > also produce \\ instead of \ > sure. all of these and post("\\"); produce the same ASCII character 92, which is double-escaped by Pd to produce the literal r'\\' (double backslash). > verbatim

Re: [PD-dev] distributing a collection of externals and abstractions using deken

On 2018-06-18 16:32, Joseph Larralde wrote: > Thank you IOhannes for your detailed answer. > I will remember not to push any binary files into my repos (something I > did in the past because github let me do it) good. (note: git of course allows you to track "binary" data; e.g. it's perfectly

Re: [PD-dev] pd external c++ example

On 2018-06-04 13:05, Joseph Larralde wrote: > And as you said, it compiles with extern "C" surrounding only the setup > function. > In fact it even compiles without any extern "C" at all (but won't load, > probably due to name mangling). yes. you only need the 'extern "C" {}' clause to prevent

Re: [PD-dev] Github being bought by MS

On 2018-06-04 15:53, Dan Wilcox wrote: > So MS is buying Github... good thing we still have the Sourceforge master > repo. Any dev thoughts on moving forward? ie. "dump Github", "it's not a big > deal", "let's find a self-host solution"... well. to start with, i never believed that GitHub was

Re: [PD-dev] Github being bought by MS

On 2018-06-07 03:00, Chris McCormick wrote: > If I recall correctly Jonathan Wilkes previously offered the use of the > GitLab instance where he is hosting Purrr Data. iirc think this was the OSUOSL (Oregon State University Open Source Labs), i mentioned in my reply. > >> It becomes harder to

Re: [PD-dev] PD_LONGINTTYPE

On 2018-06-24 21:08, Miller Puckette wrote: > Cool that just saved me hours of work going through PRs one by one :) great to be of help. please note, that there are a number of PRs that are *not* included, (e.g. the PD_LONGINTTYPE patch [7]). my rule of thumb for including patches in the PR

Re: [PD-dev] PD_LONGINTTYPE

On 2018-06-20 02:51, Miller Puckette wrote: > I think m_pd.h should make a reasonable guess, in a way that makes it > easy to override. Perhaps like this: > > #if !defined(PD_LONGINTTYPE) > #if (sizeof(void *) > sizeof(long)) > #define PD_LONGINTTYPE long long > #else > #define PD_LONGINTTYPE

Re: [PD-dev] MARCH in Deken file name

On 2018-04-30 10:29, Dan Wilcox wrote: > When I think "march" I think of the string I pass to the compiler to > explicitly get 32 or 64 bit. For clang on macOS, I say "x86_64" and for 32 > bit I say "i386". > > It's fine if deken uses the different string, I was more trying to clarify my >

Re: [PD-dev] MARCH in Deken file name

On 2018-04-29 21:46, Dan Wilcox wrote: > amd64? yes, "amd64". its an easy to remember, hard to confuse, well established term used for that architecture. "x86_64" is probably slightly more correct on the technical side, but a beast of a name (given that the full arch specifier consists of 2

Re: [PD-dev] pdlibbuilder overrides

On 2018-02-04 12:40, Dan Wilcox wrote: > I was trying to make a quick test build of an external which uses > pdlibbuilder (abl_link~) and wanted to simply disable optimizations and > enable debug symbol generation. > > I tried a simple CFLAG override but it didn't seem to work: > > make

Re: [PD-dev] savestate

On 2018-09-03 15:35, Dan Wilcox wrote: > The help patch says it can send/receive multiple list messages. I've not > tried yet, but does this mean it saves multiple #A saved ... lines to the > patch file? yep. > Also, does the right outlet effectively act as a "save bang"? seems so. it also

Re: [PD-dev] keep master on github stable

On 2018-09-04 09:41, Dan Wilcox wrote: > So the emphasis is based on the predominant use case: in the former, the > master as the release and the latter uses master as develop. +1 my stance is: apart from the "others do it as well", what would be the benefit for the Pd community? i don't see

Re: [PD-dev] Thoughts on git & github workflows

On 2018-09-11 12:49, Dan Wilcox wrote: > 7. Testing before merging: This is possible by adding the PR author's repo as > a remote and then pulling whatever branch (master or otherwise) they > submitted the PR with. This allows you to essentially do a checkout of their > PR branch that you can

Re: [PD-dev] Current GIT master builds are unable to load Gem on Windows

On 2018-03-20 05:48, Lucas Cordiviola wrote: > > Oliver and I did some tests on compiling Pd for windows. > > We found that the current master branch can't load Gem. > > We can load it with Miller's build or with self builds from > "pure-data-mingw-autotools2" branch from January ‎9, ‎2018. >

Re: [PD-dev] Updated Pure Data Reference Card

On 10.11.18 11:25, Niccolò Granieri wrote: > If that's not how we want to proceed anymore I can include a render for each > language in the GitHub, maybe under releases, +1 adding generated files to the *repository* itself is a bad idea in general. gfmadsr IOhannes signature.asc

Re: [PD-dev] removing pd/bin/msvr*.dll from Pd/win

On 24.01.19 08:25, Lucas Cordiviola wrote: > Few externals are compiled with VS where do you get that metric from? Pd-extended compiled everything with mingw, so *there* was indeed no VS involved. this spilled over to the packages available via deken. but i figure that there is quite a number

Re: [PD-dev] Compile i386 externals on Linux amd64

On 29.04.19 13:44, Roman Haefeli wrote: > Hey all > > Is there an easy way to use the pd-lib-builder Makefile to compile > externals for Linux i386 on Linux amd64? Currently, I'm using a Debian > Stretch i386 KVM VM specifically for this purpose. But since I am > successfully cross-compiling for

Re: [PD-dev] CAF file support?

On 29.04.19 14:09, Dan Wilcox wrote: > Hah, my other thought was to add an optional libsndfile backend to > [soundfiler], [readsf~], & [writesf~]... hmm. iirc the reason why there's no native libsndfile support has been to keep dependencies minimal. so far, the only dependencies Pd has are for

Re: [PD-dev] formatting HTML doc in Pd distro?

On 30.06.19 22:24, Miller Puckette wrote: >>> But I don't think it's a good idea to put latex compilation in the Pd >>> compile chain, >> why? >> > ATM I can (and do) compile Pd using only "make", "cc" and "ln" - trying to > keep the dependencies to an absolute minimum. > hence my suggestion to

Re: [PD-dev] PD Compile Farm

On 02.09.19 02:08, Jonathan Moore wrote: > Hi, > > > I would like too know how to start my own PD Compile Farm I have a dedicated > machine and am Running Ubuntu. > oh my. thanks for your interest! however, whatever you find on the "Compile Farm" on puredata.info is very outdated. it

Re: [PD-dev] Naming of patch when doing a "save as"

On 16.09.19 18:05, jakob skouborg wrote: > > I often do a lot of versioning when making complex patches, to avoid > ruining them. So most of my patches have numbers included. > > Like for example "Comb filter 1.0” ah yes, *that* use-case. if you want to do versioning of patches, you probably

Re: [PD-dev] Naming of patch when doing a "save as"

(one of the problems with this thread is, that i cannot refrain from answering...) On 18.09.19 19:26, jakob skouborg wrote: > >> the days of "Copy of Copy of Kopie von Comb filter 1.2 (17.12.1997) >> final copy.pd" ought to be gone for good. > > That is not what what I am saying or expecting.

Re: [PD-dev] Naming of patch when doing a "save as"

On 19.09.19 01:08, Dan Wilcox wrote: > I think that the actual answer is: there is no rationale, it's a bug. > actually, it turned out to be a bug *fix*. according to the git history, the current behaviour is entirely intentional, see [747] for a discussion. fmasdr IOhannes [747]

Re: [PD-dev] Deken not adding architecture

On 24.10.19 14:46, Jamie Bullock wrote: > 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 >

Re: [PD-dev] CAF file support?

On 02.12.19 13:25, Dan Wilcox wrote: > I'm bringing this back up as I will most likely take a stab at adding CAF > support to Pd at work very soon. > how so? by adding a(n optional?) dependency on libsndfile? by using some OS-specific framework (CoreAudio/...)? by implementing only a subset of

Re: [PD-dev] [PD] double precision merged

(i'm not sure how this ended on pd-list, m oving it back to pd-dev) On 25.02.20 23:53, Dan Wilcox wrote: >> On Feb 25, 2020, at 11:41 PM, Christof Ressie wrote: >> >> I think there's no configure flag (yet). In the meantime you can >> compile Pd with >> >> make CPPFLAGS="-DPD_FLOATSIZE=64" > >

Re: [PD-dev] [PD] double precision merged

On 26.02.20 14:12, Alexandre Torres Porres wrote: > I've tested loading externals and it just doesn't create and complain, but > trying to load cyclone with [declare -lib cyclone] crashes Pd! could that be a duplicate of ? fgmasdf

Re: [PD-dev] [PD] double precision merged

On 26.02.20 14:09, Dan Wilcox wrote: > Forgive me if this has been gone over, but what's the behavior if a > single-precision Pd tries to load a double-precision external or vice versa? > Does it fail to load or simply crash? with Pd>=0.51, the class_new will refuse to register the objectlcass

Re: [PD-dev] [PD] double precision merged

On 26.02.20 14:22, IOhannes m zmoelnig wrote: > On 26.02.20 14:12, Alexandre Torres Porres wrote: >> I've tested loading externals and it just doesn't create and complain, but >> trying to load cyclone with [declare -lib cyclone] crashes Pd! > > could that be a

Re: [PD-dev] [PD] double precision merged

On 26.02.20 14:26, Christof Ressi wrote: >> I've tested loading externals and it just doesn't create and complain > > Are you sure? Turn on log level 4. i think alex really meant: "I've tested loading externals and it just doesn't create[,] and [instead] complain[s]." mgfsdr IOhannes

Re: [PD-dev] libraries that crash in a double-precision runtime

On 03.03.20 14:55, Thomas Grill wrote: > Hi all, > thanks to IOhannes for debugging. > I have pushed fixes to https://github.com/g/flext which should make flext > (and flext-based objects) fully compatible with 64-bit DSP, that is, > flext-based project should compile and run (or at least,

Re: [PD-dev] pd-lib-builder question (on osx)

On 10/28/20 12:09 AM, Iain Duncan wrote: cflags = -I . -L . -l s7 if this works, then it's only because you somehow managed to have a libs7.so (or libs7.a) file lying around, against which it linked. afaict, this is not a safe assumption gdfmasdr IOhannes and some more nitpicking: i

Re: [PD-dev] [PD] Pd 0.50-2 on macos 11.0 BigSur beta

On 06.07.20 19:39, Martin Peach wrote: > The build farm used by Pd-extended worked very well for me. It would > be nice to have such a setup integrated with the deken system, so > anyone could upload their externals and they would be built and > packaged online instead of each developer needing to

Re: [PD-dev] Macs to transition to ARM processors

On 24.06.20 16:00, Dan Wilcox wrote: > >> On Jun 24, 2020, at 12:00 PM, pd-dev-requ...@lists.iem.at wrote: > >> so running on all >> architectures ever supported by OSX (modulo system libraries...). > > To be pedantic, it has been officially "macOS" for some years now. The > upcoming version

Re: [PD-dev] "int argc" giving weird values

On 3/3/21 7:52 AM, Alexandre Torres Porres wrote: why dear god, why? please please please, it's late and I'm losing sleep what's that `t_pd*dummy` supposed to do in the argument list of `del_new`? why don't you have it in `del_in_new`? gfmdasr IOhannes

Re: [PD-dev] multi-architecture deken packages

On 4/15/21 12:33 AM, Alexandre Torres Porres wrote: Ok, I got questions now on how loading works. We know .pd_linux for instance, can be used generically for any architecture. But I guess Pd knows if that .pd_linux file is actually good or not. Like, let's get the zexy bundle, for instance, you

[PD-dev] unifying loglevels

TL;DR i'd like to propose to unify the loglevels as used by verbose() and logpost() for unknown reasons, the values accepted by verbose() and logpost() have an offset. the current loglevels are like this: logpost(x, 0,...) -> CRITICAL logpost(x, 1,...) -> ERROR logpost(x, 2,...) -> NORMAL

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])

On 8/31/21 4:10 PM, Christof Ressi wrote: Writing to "C:/" and "C:/Windows" silently fails. "/tmp" obviously doesn't exist on Windows. "C:/Temp" should be "C:/Windows/Temp" - then it works! right. i had a C:\tmp\ directory on my system, that's why it works for me. However, it would only

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])

On 8/31/21 4:49 PM, Alexandre Torres Porres wrote: nice, now every time I open a new Pd patch, I get this window, I have to click pay so the window closes and the patch opens. Is there any way out of this curse? :) :-P remove the new paths from the settings and delete the exploit-plugin.tcl

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])

On 8/31/21 4:37 PM, Antoine Rousseau wrote: i wonder whether it would be possible (with Pd>=0.42) to create a patch that creates a gui-plugin on the fly. if this is true, then you can already do everything that [file] allows you to do - and much more yes, but [file] will be extremely useful

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])

On 8/31/21 3:12 PM, Christof Ressi wrote: The exploit successfully changes my MIDI settings and adds search paths, but unfortunately it crashes with a completely wiped stack before showing me the Tk dialog :-( you mean, it successfully creates an exploit-plugin.tcl but cannot run it? (if so

Re: [PD-dev] writing exploits in Pd (Re: [PD] [file])

On 8/31/21 4:45 PM, Alexandre Torres Porres wrote: Em ter., 31 de ago. de 2021 às 11:28, IOhannes m zmoelnig escreveu: So how do I pay the money? just click on "Pay". the rest is automagic. clicking 'pay' crashes Pd on macOS 10.14.6 (Pd 0.51-4) the important part is, that the

[PD-dev] [ot] asiosdk2.3 gone from steinberg's website

i just found out on the CI that since yesterday, steinberg obviously have removed the old asiosdk download¹ from their website. apparently a newer version can be obtained from https://www.steinberg.net/asiosdk mgdasr IOhannes ¹ http://www.steinberg.net/sdk_downloads/asiosdk2.3.zip

Re: [PD-dev] unifying loglevels

On 8/24/21 9:44 PM, Christof Ressi wrote: for unknown reasons, the values accepted by verbose() and logpost() have an offset. Why? Oh why? i've been involved in that code, and i don't have an anwer :-( If we let PD_CRITICAL start at 5 (or even higher), then both verbose() and logpost()

Re: [PD-dev] unifying loglevels

On 8/25/21 11:13 AM, Dan Wilcox wrote: Sounds good to me. I would suggest considering a compatibility mode / compile time option to preserve existing functionality for right, i was thinking about suggesting to use "-compatibility" for retaining backward compat. otoh. this doesn't help at

Re: [PD-dev] -verbose vs logpost() (IOhannes m zmoelnig)

On 8/26/21 2:28 PM, Dan Wilcox wrote: Maybe an additional -loglevel which allows you set the level explicitly? -verbose to me would set the log level to verbose overall & -noverbose would set it back to the default. that might work, but... do "-loglevel" and "-verbose" act on the same

Re: [PD-dev] -verbose vs logpost() (IOhannes m zmoelnig)

On 8/26/21 2:28 PM, Dan Wilcox wrote: Also tangentially, I would also bring up the handling of some of these flags which affect the state: using -verbose also sets the verbose setting which is then saved with the user settings. I find this annoying as I would rather have the command line

[PD-dev] -verbose vs logpost()

the other question that is tightly related to the "unifying loglevels" thread is, how to deal with "-verbose" resp "-noverbose". currently the two concepts ("use of '-verbose'" vs "use of logpost()/verbose()") are obviously in the same realm but somewhat independent. raising verbosity with

Re: [PD-dev] plans for next Pd release

On 9/14/21 7:35 PM, Miller Puckette via Pd-dev wrote: Well, I'm trying to get one last improvement in (multi-atom number/symbol boxes so you can type and/or see compound messages) - and then after that limit changes to bug fixes. i'd like to bring the 'develop' branch to your attention. as

  1   2   >