Hello,
My preference ist to name of binary pd double precision:
pd
- since all my scripts calling pd can use double precision if I install it
instead of pd.
- most want just double precision or not
- the ones with need of both, can hold them in seperate pathes like "dp/pd",
2:00 PM, pd-dev-requ...@lists.iem.at wrote:
Message: 1
Date: Mon, 12 Jun 2023 09:08:36 +0200
From: IOhannes m zm?lnig
To:pd-dev@lists.iem.at
Subject: Re: [PD-dev] double precision pd?
Message-ID:
Content-Type: text/plain; charset="utf-8"; Format="flowed"
On 6/8/23 15:23, IOhan
equ...@lists.iem.at wrote:
>
> Message: 1
> Date: Mon, 12 Jun 2023 09:08:36 +0200
> From: IOhannes m zm?lnig mailto:zmoel...@iem.at>>
> To: pd-dev@lists.iem.at <mailto:pd-dev@lists.iem.at>
> Subject: Re: [PD-dev] double precision pd?
> Message-ID: <mailto:d02e
On 6/8/23 15:23, IOhannes m zmölnig wrote:
Oh no, compilation will be complex.
Not really.
You basically have to build twice...
oh no, i forgot about the intricacies of the windows build.
with macOS and Linux we have this nice single "pd" binary (or "pd64").
but with Windows we need the
It will work and I don't think separate apps would be needed.
The executable within the .app bundle (Contents/MacOS/Pd) is just the renamed
Wish executable which calls the Tk GUI which, in turn, starts the pd core which
could be either 32 or 64 bit float precision. This could be selectable via
TBH, I think the real issue here is external compatibility. End users need
to know if their version is going to have the externals they need. Given
how often external libraries get abandoned, the need for re-compilation is
a non-trivial issue.
I think this puts me in favor of clear separation.
Am 8. Juni 2023 11:15:17 MESZ schrieb Lucas Cordiviola :
>How hard it would be to have both apps together in a single "Pure data"
>package:
>
Interesting idea.
Esp for the windows packages (both the zip and the installer) I think that
would make a lot of sense.
For the macOS app, I don't know
From: IOhannes m zmoelnig mailto:zmoel...@iem.at>>
> To: pd-dev@lists.iem.at <mailto:pd-dev@lists.iem.at>
> Subject: Re: [PD-dev] double precision pd?
> Message-ID: <5cf4aa6d-c70e-8fd3-993a-e4d1b49d1...@iem.at
> <mailto:5cf4aa6d-c70e-8fd3-993a-e4d1b49d1...@iem.at>>
How hard it would be to have both apps together in a single "Pure
data" package:
Oh no, compilation will be complex.
--
Mensaje telepatico asistido por maquinas.
___
Pd-dev mailing list
Pd-dev@lists.iem.at
How hard it would be to have both apps together in a single "Pure data"
package:
$ pd
$ pd64
?
--
Mensaje telepatico asistido por maquinas.
On 07/06/2023 16:25, cyrille henry wrote:
Hello,
BTW, did anyone made a benchmark :
"pd double" will of course be lot's slower on 32 bit
Hello,
BTW, did anyone made a benchmark :
"pd double" will of course be lot's slower on 32 bit architecture, but what
about 64 bit architecture?
Will "pd double" perform as fast as "pd float" on modern computer? or do we
need to have both version installed on the same computer? (some patch need
Em qua., 7 de jun. de 2023 às 11:43, IOhannes m zmoelnig
escreveu:
> i think one of the questions is, where the name will actually be exposed.
>
> - of course, the webpage (https://msp.ucsd.edu/, https://puredata.info/)
> cou use whatever descriptive name to lure the people into downloading
>
On 6/7/23 12:55, Antoine Rousseau wrote:
Le mer. 7 juin 2023 à 10:47, Lucas Cordiviola a
écrit :
For me pd64 gives more chances of confusion than pdd or pdpd.
(...)
Starting with a new name of the app seems the most sane.
Funnily, my personal feeling is the opposite :-)
I feel that
>
> My trouble with Pd64 is that it will get listed next to Pd in almost any
> package manager and may be many people
> opt Pd64 (thinking that is the one for 64bit cpus)
I think almost all (recent) package managers no longer offer 32bit-CPU
packages?...
Antoine
Le mer. 7 juin 2023 à 13:08,
Funnily, my personal feeling is the opposite :-)
I feel that Pd64 clearly describes Pd working with 64 bit data.
I myself don't have any trouble with whatever name we use as I know
perfectly well the situation. My trouble with Pd64 is that it will get
listed next to Pd in almost any package
Le mer. 7 juin 2023 à 10:47, Lucas Cordiviola a
écrit :
> For me pd64 gives more chances of confusion than pdd or pdpd.
>
(...)
> Starting with a new name of the app seems the most sane.
>
Funnily, my personal feeling is the opposite :-)
I feel that Pd64 clearly describes Pd working with 64
For me pd64 gives more chances of confusion than pdd or pdpd.
Apart from the name of the app we should try to give this new app as
much separation of Pd's paths and preferences as we can.
Starting with a new name of the app seems the most sane.
--
Mensaje telepatico asistido por maquinas.
>> On Mon, 2023-06-05 at 11:46 +0200, Miller Puckette wrote:
>> Pdouble?
>
> Pd?
pdpd?
enohp ym morf tnes
---
Dan Wilcox
danomatika.com
robotcowboy.com
___
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev
On Mon, Jun 5, 2023, 15:27 Roman Haefeli wrote:
> Pd²
or actually doubling it to pdpd?
... which could be read as pure double precision data.
I do prefer pd64 though despite the possible confusion - assuming that
semantics for names and endings are clearly (enough) different.
On Mon, 2023-06-05 at 11:46 +0200, Miller Puckette wrote:
> Pdouble?
Pd²
Roman
signature.asc
Description: This is a digitally signed message part
___
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev
Pdd
Le 05/06/2023 à 11:44, IOhannes m zmölnig a écrit :
On 6/4/23 17:22, Alexandre Torres Porres wrote:
well, great then, cause it's been merged :) time to get ready for double
precision finally then I guess! Really excited about it <3
the other question that ought to answered is: how do we
> On Jun 5, 2023, at 12:00 PM, pd-dev-requ...@lists.iem.at wrote:
>
> Message: 3
> Date: Mon, 5 Jun 2023 11:44:54 +0200
> From: IOhannes m zm?lnig
> To: pd-dev@lists.iem.at
> Subject: Re: [PD-dev] double precision pd?
> Message-ID: <0891ab25-d572-828b-881a-cef4cc65c...@iem.at&
Pdouble?
On 6/5/23 11:44, IOhannes m zmölnig wrote:
On 6/4/23 17:22, Alexandre Torres Porres wrote:
well, great then, cause it's been merged :) time to get ready for double
precision finally then I guess! Really excited about it <3
the other question that ought to answered is: how do we
On 6/4/23 17:22, Alexandre Torres Porres wrote:
well, great then, cause it's been merged :) time to get ready for double
precision finally then I guess! Really excited about it <3
the other question that ought to answered is: how do we actually call it
in order to prevent confusion?
"Pd
PS: there's also some more of my PRs which i would like to draw
special attention to (for inclusion with Pd-0.54)
To follow up, it would be great if Pd 0.54 could include my scheduler
fixes/improvements:
https://github.com/pure-data/pure-data/pull/1756
It has been tested by several people on
well, great then, cause it's been merged :) time to get ready for double
precision finally then I guess! Really excited about it <3
cheers
Em sáb., 3 de jun. de 2023 às 18:38, IOhannes m zmölnig
escreveu:
> On 6/3/23 20:02, Alexandre Torres Porres wrote:
> > Hi, with pd 0.54-0 round the
On 6/3/23 20:02, Alexandre Torres Porres wrote:
Hi, with pd 0.54-0 round the corner, what is still preventing us from
shipping double precision pd downloads?
from my side: https://github.com/pure-data/pure-data/pull/1605
it would be nice if this could be merged for the 0.54 release¹
in the
Hi, with pd 0.54-0 round the corner, what is still preventing us from
shipping double precision pd downloads?
been waiting on it for a while now
cheers
___
Pd-dev mailing list
Pd-dev@lists.iem.at
https://lists.puredata.info/listinfo/pd-dev
28 matches
Mail list logo
