Hullo, List, I'm playing around with some waveguide modeling stuff, mostly modeling strings, and my first trial patch is basically just a delay line that feeds back through a lowpass filter. It seems that the delay object of choice for long strings of delay (for if I want to apply non-linear interactions) is [z~] from zexy, but I can't change the delay time dynamically, and I'd like to be able to change the tuning on the fly. Is there a different delay object that I should be using?
I'm just starting to look into waveguide modeling, with the intent of playing around with sympathetic vibrations, like on a sitar, where the input signal induces vibrations in a collection of tuned strings. If anyone has any nice waveguide example patches, I'd be interested to see them.
thanks, spencer
Spencer Russell wrote:
choice for long strings of delay (for if I want to apply non-linear interactions) is [z~] from zexy, but I can't change the delay time dynamically, and I'd like to be able to change the tuning on the fly.
how comes? what makes you think you cannot change the delay time dynamically?
mfg.ad.r IOhannes
On 11/18/05, IOhannes m zmoelnig zmoelnig@iem.at wrote:
Spencer Russell wrote:
choice for long strings of delay (for if I want to apply non-linear interactions) is [z~] from zexy, but I can't change the delay time dynamically, and I'd like to be able to change the tuning on the fly.
how comes? what makes you think you cannot change the delay time dynamically?
I've been stuck using a windows machine recently, and maybe it's just something strange with the setup, but [v~] only seems to have one input.
-spencer
Spencer Russell wrote:
I've been stuck using a windows machine recently, and maybe it's just something strange with the setup, but [v~] only seems to have one input.
i don't know about [v~], but [z~] - while having just one inlet - still distinguishes between what it gets on this single inlet: if you send a float to the 1st inlet of [z~], this will denote the delay in samples.
i see that it is not mentioned in the documentation. (but it seems so natural to me, that i would at least expect people to try it out...) since this is not the first time that someone asks this question, i will probably add a 2nd inlet to [z~].
mfg.asdr IOhannes
HI IOhannes,
IOhannes m zmoelnig wrote:
i see that it is not mentioned in the documentation. (but it seems so natural to me, that i would at least expect people to try it out...)
With all due respect, users are not mind readers, and if you leave a feature undocumented you can expect that 98% of the people will never use it. And in that case, why did you spend time programming it unless only for your own use?
People will argue all kinds of things that are PD's main weakness, but un-helpful help patches are one of the biggest for me, from both a teaching and using point of view.
best, d.
derek holzer wrote:
With all due respect, users are not mind readers, and if you leave a feature undocumented you can expect that 98% of the people will never use it. And in that case, why did you spend time programming it unless only for your own use?
well, all of zexy is for my own use. so what do you expect me to do? not publish it, because there are no good docs? writing docs? - you pay ??
i do not expect people to be mind readers. i was just pointing out, that when i see an object which does approximately what i need, but i am missing a functionality that is crucial for me and which i think might be of general importance, i read the documentation and if that fails (which it does here) i might try to see whether i can still achieve the functionality. but otoh, i might soon switch to the sources of an object, and i totally agree that i cannot expect _that_ from anybody.
mfg.a.sdr IOhannes
Hallo!
With all due respect, users are not mind readers, and if you leave a feature undocumented you can expect that 98% of the people will never use it. And in that case, why did you spend time programming it unless only for your own use?
well, all of zexy is for my own use.
of course ...
so what do you expect me to do? not publish it, because there are no good docs? writing docs? - you pay ??
well, writing a help file, which documents the functionality somehow takes you about 1 or 2 minutes ;) ... and it's also for your own use: I always forget which syntax I used for an external ...
LG Georg
Georg Holzmann wrote:
Hallo!
well, writing a help file, which documents the functionality somehow takes you about 1 or 2 minutes ;) ... and it's also for your own use: I always forget which syntax I used for an external ...
hi, of course i do not doubt that i should have done a proper help-patch.
mfg.adsr. IOhannes
Hullo!
Spencer Russell wrote:
Hullo, List, It seems that the delay object of choice for long strings of delay
if you put the delwrite~ and delread~ in a subpatch together with a block~ you can get shorter delays, as Miller shows in 3.audio.examples/G04.control.blocksize.pd
ciau!
peter
I'm playing around with some waveguide modeling stuff, mostly modeling strings, and my first trial patch is basically just a delay line that feeds back through a lowpass filter. It seems that the delay object of choice for long strings of delay (for if I want to apply non-linear interactions) is [z~] from zexy, but I can't change the delay time dynamically, and I'd like to be able to change the tuning on the fly. Is there a different delay object that I should be using?
especially if you're using very low delays, you'll need subsample accurate delays ... so delwrite~ / vd~ are the tools of choice ...
tim
-
derek holzer -
Georg Holzmann -
IOhannes m zmoelnig -
Peter Plessas -
Spencer Russell -
Tim Blechmann