Thanks that was a well written explanation, it makes much more sense now.
I read the help for [block~] about the catch~/throw~ 'weirdness'.
And although it says...
Patches using send~/receive~ or throw~/catch~ to intercommunicate must
have the same blocking...
...If I create a patch with [throw~
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
Thanks that was a well written explanation, it makes much more sense now.
I read the help for [block~] about the catch~/throw~ 'weirdness'.
And although it says...
Patches using send~/receive~ or throw~/catch~ to intercommunicate must
have
Blocking is always done per canvas, that is, a [block~ X] in a
subpatch will reblock that subpatch and all its siblings, however it
will not reblock the surrounding parent patch. In the patch you've
posted, you have two subpatches both with [block~ 1], but the
surrounding patch still has the
On Sun, 2007-05-13 at 22:38 +0200, Frank Barknecht wrote:
I thought of that.. I created a very simple patch with everything
block~ 1, nothing connected...
As soon as the program opens it gives errors.
Oh, yes, that's very strange. Even a simple:
[throw~ x]
[catch~ x]
[block~
Hallo,
Tim Blechmann hat gesagt: // Tim Blechmann wrote:
On Sun, 2007-05-13 at 22:38 +0200, Frank Barknecht wrote:
This very much looks like a bug somewhere in Pd.
this behavior is documented in the help patch of send~ ... afaict
tabsend~/receive~ should work, though
Ah, and I only read
Hallo,
Frank Barknecht hat gesagt: // Frank Barknecht wrote:
I don't understand how a minimum delay of 1 sample can be achieved
(although I admit I have made it work in practice!!!)
Actually I think, theoretically a minimum delay of zero samples could
be achieved (although I admit I have
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
Actually, sorry- I thought I understood this but I've got a problem
with this method
Considering the patch posted by Georg Holzmann (the same principle as
http://crca.ucsd.edu/~msp/techniques/latest/book-html/node121.html)-
Surely if the
Hallo,
Georg Holzmann hat gesagt: // Georg Holzmann wrote:
if the delread is computed after the delwrite you can read out the delay
line immediately - so down to 1 sample delay.
Make that down to 0 samples delay, unless I'm wrong.
Ciao
--
Frank Barknecht _
Frank Barknecht wrote:
as the block-delay of direct connections depends on the order in which
you made the connections, and that's to fragile: editing can change
the order without you noticing it.
actually to be accurate it is not the order in which you made the
connections but the order in
Hallo,
marius schebella hat gesagt: // marius schebella wrote:
Frank Barknecht wrote:
as the block-delay of direct connections depends on the order in which
you made the connections, and that's to fragile: editing can change
the order without you noticing it.
actually to be accurate
OK- after realising that throw~ can be set to different destinations
and operate at lower blocksizes, I tried to make a 0 length feedback
system using throw~ and catch~
See attachment or this link:
http://www.zen26398.zen.co.uk/temp/throwcatchfeedback6.pd
In this patch, a triangular excitation
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
OK- after realising that throw~ can be set to different destinations
and operate at lower blocksizes, I tried to make a 0 length feedback
system using throw~ and catch~
You cannot: The subpatch method only works for non-feedback delays!
You cannot get a zero-size feedback delay in Pd at all, regardless of
subpatch ordering or creation order. The subpatch-stuff only is valid
for non-feedback connections. The best you can do is do a [block~ 1]
or [block~ 8]
Sorry, I forgot to mention that I used [block~ 1] objects within the
On 12/05/2007, at 11.58, Kim Taylor wrote:
For example: lets say there is an input signal to the explicitly
defined sequence of delwrite~ - delread~ - output
At t=0 the sample starts playing. Surely only until t=64 can a block
be written by delwrite~ (immediately), and read (immediately) by
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
... The time it takes
logically is zero: The full block is written into the delay line
immediatly (that is: at the same time, delread~ reads it, see below).
OK,
But how can a full block be written to a delay line before it has
happened?
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
It seems to work, however: I get error messages at the output-
error: sigcatch A-test: unexpected vector size
error: throw~ A-test: vector size mismatch
I didn't get these with a default 64 bit blocksize. Why would the
vector size be
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
I have had success using throw~ and catch~, as the destination bus can
be changed by setting throw~, BUT- throw and catch use a minimum block
size of 64.
Hm? They don't, unless you do feedbacks, but then everyhting~ in Pd
has a delay of one
Hallo,
Kim Taylor hat gesagt: // Kim Taylor wrote:
I have had success using throw~ and catch~, as the destination bus can
be changed by setting throw~, BUT- throw and catch use a minimum block
size of 64.
Hm? They don't, unless you do feedbacks, but then everyhting~ in Pd
has a delay of
I have had success using throw~ and catch~, as the destination bus can
be changed by setting throw~, BUT- throw and catch use a minimum block
size of 64.
Hm? They don't, unless you do feedbacks, but then everyhting~ in Pd
has a delay of one block.
How true, I must have overlooked this...
Hallo!
If you really want to make sure not to pick up any unwanted delays you
need to use the double-subpatch technique described in Miller's book,
as the block-delay of direct connections depends on the order in which
you made the connections, and that's to fragile: editing can change
the
Thanks for this, its cleared things up. Is there any purpose in the
$0-delline2 delay line though?
K
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Actually, sorry- I thought I understood this but I've got a problem
with this method
Considering the patch posted by Georg Holzmann (the same principle as
http://crca.ucsd.edu/~msp/techniques/latest/book-html/node121.html)-
Surely if the block size is default 64 samples, the delwrite atom will
Hi everyone
Here's my problem:
The project I'm working on requires the use of feedback loops,
something I am currently implementing by using delread~/write~ in Pd
with a 0 length delay. This also adds a fixed minimum delay of the
block size, but this can be reduced by using block~.
The problem
23 matches
Mail list logo
