My guess is that I dont get the correct [ctlout]'s 2nd inlet value
because each control surface (template?) that ableton works with seems
to have different values set for that.
I never used any "control surface (template?)" and I think you don't
need to emulate one. You just create the custom
Hi Pd-list,
A couple times now I've thought that it would be very convenient to change
the name of a receive after instantiation, but I'm not finding any way of
doing that. If this is impossible, I'll clarify that essentially what i
want is for an abstraction to be able to point to the $0 patch nu
Hi,
You can do [s $0-foo] [r $0-foo].
See menu/help --> Pure Data/2.control.examples/13.locality.pd
--
Mensaje telepatico asistido por maquinas.
On 3/25/2020 12:29 PM, Francis Blair wrote:
Hi Pd-list,
A couple times now I've thought that it would be very convenient to
change the name of a
If you don't have any problem with using externals you can use
[iemlib/iem_send].
That's what I use. There is also a [iem_receive] in case that you happen to
need that.
Ingo
From: Pd-list [mailto:pd-list-boun...@lists.iem.at] On Behalf Of Francis Blair
Sent: Wednesday, March 25, 2020
On 3/25/20 5:04 PM, Ingo wrote:
> If you don't have any problem with using externals you can use
> [iemlib/iem_send].
what's that for?
i mean: what is the advantage over [send] (without arguments)?
> That's what I use. There is also a [iem_receive] in case that you
> happen to need that.
chang
changing the receiver is dangerous (as in: could crash your system).
Yes. Actually, I've experimented with different ways to make it safe, see:
https://github.com/pure-data/pure-data/pull/614
or
https://github.com/pure-data/pure-data/pull/849
I think the second version is not too unreasonable
Thank you all for your responses! I think I've found a solution that can
work. Basically what I did was create an abstraction where the first
argument is $0 and has a receive object inside with the name $1-parent. It
was right under my nose the whole time, but thank you all for helping me
sniff it
I had some cases where I had to send e.g. to different preset banks to dump
some data.
The bank name was different depending on the selected bank.
There can be a number of reasons to send to different objects depending on
other settings.
But I agree that you can find different ways of doing it.
IOhannes m zmölnig wrote:
changing the receiver is dangerous (as in: could crash your system).
really ? that's (bad) news to me.
how so ? why could that crash a system ?
and why is it not dangerous to change the receiver in the signal domain ?
would you say, it's "saver" to do dynamic patchi
Check out the following discussion on GitHub:
https://github.com/pure-data/pure-data/pull/604
TL;DR: if you unbind a symbol from a receiver while sending to the
symbol, Pd can crash because you modify the bind list while iterating
over it.
Personally, I've been using [iem_receive] in some pr
Christof Ressi wrote:
Check out the following discussion on GitHub:
https://github.com/pure-data/pure-data/pull/604
TL;DR: if you unbind a symbol from a receiver while sending to the
symbol, Pd can crash because you modify the bind list while iterating
over it.
Personally, I've been using [
Lucas, thanks so much! This is exactly what I needed!!!
fdch.github.io
> On Mar 25, 2020, at 4:26 AM, Lucas Cordiviola wrote:
>
>
>> My guess is that I dont get the correct [ctlout]'s 2nd inlet value because
>> each control surface (template?) that ableton works with seems to have
>> diffe
Haha, what I wanted to say is that if you're worried about the danger of
using [iem_receive], then dynamically destroying [r] is not a solution
because it is just as dangerous because the destructor of [r] will
unbind the symbol.
An easy way to avoid this problem on the user side is to always
13 matches
Mail list logo
