[PD] Bidirectional Module Problem - dynamically changing delwrite?

2007-05-15 Thread Kim Taylor
Hello everyone again Can anyone lend me their brain for 5 minutes so I can get a second opinion of my problem? Essentially what I'm trying to do is create a *generic* module that links bi-directionally to other modules: send audio information and also receive it with minimal time delay. It is

Re: [PD] Bidirectional Module Problem - dynamically changing delwrite?

2007-05-15 Thread Kim Taylor
for your help K On 5/15/07, IOhannes m zmoelnig [EMAIL PROTECTED] wrote: Kim Taylor wrote: So I am stuck. Is there any way I can dynamically create/set a delwrite~? It seems to be the only function that might work in this no, you cannot dynamically change the [delwrite~] name, because [delwrite

Re: [PD] Bidirectional Module Problem - dynamically changing delwrite?

2007-05-15 Thread Kim Taylor
as well use send/receive and setting receive like you did here, but s/r don't work at lower block sizes unfortunately :( Thanks for your help anyway K On 5/15/07, Steffen [EMAIL PROTECTED] wrote: On 15/05/2007, at 19.10, Kim Taylor wrote: [set varname2( | [receive~ varname] | [delwrite

Re: [PD] Zero delay feedback, with settable send?

2007-05-13 Thread Kim Taylor
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~

Re: [PD] Zero delay feedback, with settable send?

2007-05-13 Thread Kim Taylor
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

Re: [PD] Zero delay feedback, with settable send?

2007-05-12 Thread Kim Taylor
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

Re: [PD] Zero delay feedback, with settable send?

2007-05-12 Thread Kim Taylor
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

Re: [PD] Zero delay feedback, with settable send?

2007-05-11 Thread Kim Taylor
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...

Re: [PD] Zero delay feedback, with settable send?

2007-05-11 Thread Kim Taylor
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

Re: [PD] Zero delay feedback, with settable send?

2007-05-11 Thread Kim Taylor
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

[PD] Zero delay feedback, with settable send?

2007-05-10 Thread Kim Taylor
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

Re: [PD] simple Q- co-dependent values

2007-05-06 Thread Kim Taylor
Excellent, works perfectly thanks Kim On 5/5/07, Peter Plessas [EMAIL PROTECTED] wrote: Hi Kim, set is the magic word here: [set 100 | | (numberbox) sets the numberbox to 100 without causing it to output 100. [set $1 makes the value variable. lg, PP Kim Taylor wrote: Hello

[PD] simple Q- co-dependent values

2007-05-05 Thread Kim Taylor
Hello everyone I have a little question which should be simple but I can't think of how to do it. In Pd, I have two number boxes and I want for them to be ratios of each other. I want it so that If I change one then the value of the other changes accordingly, also vice versa so that changing

Re: [PD] Re: DSP loops

2007-01-31 Thread Kim Taylor
on a similar topic the minimum delay loop time with this is actually zero, so an extra [z] wouldn't hurt. Andy On Tue, 30 Jan 2007 19:24:12 + Kim Taylor [EMAIL PROTECTED] wrote: By the way, Kim, could you tell me what the feedback loop is? (what kinds of operations are you using

[PD] DSP loops

2007-01-30 Thread Kim Taylor
Hi again all I'm having a bit of trouble putting my program together. I'm trying to implement a series of object blocks that form the synthesis framework, up until now everything's been ok. My problem is that on the top level of the program, I'm trying to connect the blocks together, but the

[PD] Re: DSP loops

2007-01-30 Thread Kim Taylor
By the way, Kim, could you tell me what the feedback loop is? (what kinds of operations are you using? is it linear?...etc...) If it's linear, you should be able to replace the feedback loop with an equivalent operation, which circumvents the whole problem. The structure I am implementing

[PD] minimum delay time for delread~

2007-01-22 Thread Kim Taylor
Hi everyone, I'm new to the list (and pd) so I hope this posts OK. I'm creating a series of patches that rely pretty fundamentally on delays- and I've noticed that the function delread~ seems to have a minimum value of delay time (1.48ms). Values below this point simply trim to 1.48ms. Could I