went ahead and did it. (didn´´t find a way to add a label for documentation
though)
https://github.com/pure-data/pure-data/issues/1345
> Am 25.06.2021 um 22:11 schrieb Alexandre Torres Porres :
>
> open an issue on github https://github.com/pure-data/pure-data/issues I'll do
> it
>
> Em sex.
thumbs up.
:)
Mensaje telepatico asistido por maquinas.
On 6/25/2021 6:28 PM, hans w. koch wrote:
yes, of course :-)
i stated here for [div] and [mod]:
https://lists.puredata.info/pipermail/pd-list/2020-09/128152.html
and on git: https://github.com/pure-data/pure-data/issues/1150
Am 25.06.
yes, of course :-)
i stated here for [div] and [mod]:
https://lists.puredata.info/pipermail/pd-list/2020-09/128152.html
and on git: https://github.com/pure-data/pure-data/issues/1150
> Am 25.06.2021 um 23:20 schrieb Lucas Cordiviola :
>
>> not every object is double ready though in my experienc
not every object is double ready though in my experience.
It would be very useful if you tell whats not ready. Either here on the
"list" or issues on https://github.com/pure-data/pure-data/issues
:)
Mensaje telepatico asistido por maquinas.
On 6/25/2021 6:01 PM, hans w. koch wrote:
yes, i
yes, i am already using pd double.
not every object is double ready though in my experience.
sometimes hard to tell apart...
@alexandre: thanks for the offer to file a feature request for the helpfile
change.
i can do it too, but wasn´t sure if i should flood the long list with this
trivia.
be
I might be missing something but Hans said he was using "vanilla double"
d'oh. I didn't catch that.
On 25.06.2021 22:41, Lucas Cordiviola wrote:
Also, all numbers in Pd are 32-bit floats while all numbers in JS are
64-bit doubles.
I might be missing something but Hans said he was using "vanil
Also, all numbers in Pd are 32-bit floats while all numbers in JS are
64-bit doubles.
I might be missing something but Hans said he was using "vanilla double"
--
Mensaje telepatico asistido por maquinas.
On 6/25/2021 5:30 PM, Christof Ressi wrote:
or maybe another case of limitation on the
or maybe another case of limitation on the display-side of things?
This.
Also, all numbers in Pd are 32-bit floats while all numbers in JS are
64-bit doubles.
Christof
On 25.06.2021 21:27, hans w. koch wrote:
today to my amazement, i discovered, that the midi decimals in mtof equal cents
:
open an issue on github https://github.com/pure-data/pure-data/issues I'll
do it
Em sex., 25 de jun. de 2021 às 16:30, hans w. koch
escreveu:
> today to my amazement, i discovered, that the midi decimals in mtof equal
> cents :-)
> sorry, for stating the obvious. better late then never, at least
today to my amazement, i discovered, that the midi decimals in mtof equal cents
:-)
sorry, for stating the obvious. better late then never, at least for me…i
literally hit my head when i recognized this.
i´ve searched the archives for "mtof cents” and didn´t find a mention of this.
now that i´ve
Please don't just weed them all out.
In the past, I have found tables like [dbtorms] very instructive, to show
students "the old way we
used to do things with lookup tables", or as a visual aid to explaining what a
black-box object really does.
It would be nice to move them;
Maybe into into
The table method is faster but it probably doesn't matter on modern hardware...
although
I've never measured it :)
On Thu, Jun 08, 2017 at 03:35:07AM +0200, Matt Davey wrote:
> been going through the help files again for a project, and noticed there
> are heaps of them that use table lookups for
been going through the help files again for a project, and noticed there
are heaps of them that use table lookups for making midi notes and dbtorms
conversions.
any reason why these can't just be simplified by using [mtof~] and
[dbtorms] ?
___
Pd-list@li
xensynth
http://archive.org/details/xensynth
has abstractioins [ntof] and [ntof~]
which are not bound to the midi 100 cent interval
intervals can be set with a list message in frequency ratio format
xensynth can load scala .scl tuning files and when a .scl file is
loaded it sends the interval list
t always true. after I've created [zexy/wrap], [wrap] will
> always give me the zexy version, without a warning that the vanilla [wrap]
> has been overwritten...
>
> Gesendet: Mittwoch, 05. Oktober 2016 um 10:31 Uhr
> Von: "William Huston"
> An: "IOhannes m zmoe
On 2016-10-05 11:26, Christof Ressi wrote:
> mtof~.dll
> mtof~-help.pd
> I DID find the help in \pd-extended\externals\vanilla\ (Windows machine)
> But NOT under my Vanilla install (0.47-1).
this is because pd-vanilla has very few externals (an "external" is an
object that comes from a file other
2016 um 10:31 Uhr
Von: "William Huston"
An: "IOhannes m zmoelnig"
Cc: "pd-list@lists.iem.at"
Betreff: Re: [PD] [mtof~] !!!
Well I did. But I also stated that I wasn't sure.
I have several different versions of Pd installed,
and I generally point to a bun
Well I *did. *But I also stated that I wasn't sure.
I have several different versions of Pd installed,
and I generally point to a bunch of external libraries from -extended.
I searched my machine for things like:
mtof~.dll
mtof~-help.pd
I DID find the help in \pd-extended\externals\vanilla\ (Wi
On 2016-10-05 09:06, William Huston wrote:
> This is so handy, I would like to ask that [mtof~] be added to Vanilla
> (if it's not already there)
zhmm, so you've written that long email and did not bother to check
whether it actually is included in vanilla? (it is, at least since 0.33,
which was r
I just discovered this!
It looks like it shipped with extended?
Also looks like it is in Max?
This thing is awesome because it solves a problem I often have
with LFO wave-shaping.
I have an LFO like [osc~ 3] which has a range of (-1, 1).
I want to be able to use this to represent a frequency scal
Hallo,
I just discovered mtof~, which I never used before, through this redit thread:
https://www.reddit.com/r/musicprogramming/comments/2uis7s/harsh_noise_patches_for_pure_data/
In the merzdata example mtof~ is used in combination with noise~ to generate a
really nice chaotic osc~ behavior o
21 matches
Mail list logo