Is it possible to clear the content of [vd~]?
I am using [switch~] to turn off unused synth voices which contain a [delwrite~] and a corresponding [vd~] object. When I turn the voice back on there is some "leftover" in [vd~] that causes clicks at the beginning of the new sound.
Ingo
On Tue, 1 Feb 2011, Ingo Scherzinger wrote:
Is it possible to clear the content of [vd~]?
You should ask your question like «Is it possible to clear the content of [delwrite~] ?» because that's where the sound is kept.
[vd~] and [delread~] are just read-heads that don't keep a copy of the sound.
[delwrite~] doesn't seem to have a clear feature. This could be added with a little bit of C code, but otherwise, there is a workaround : you temporarily set all of your read-heads to a blank portion of the buffer instead of where they're supposed to be. Yes it's ugly, and no, it doesn't always work. The clear feature would be a better idea.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2011-02-01 03:33, Mathieu Bouchard wrote:
[delwrite~] doesn't seem to have a clear feature. This could be added with a little bit of C code, but otherwise, there is a workaround : you temporarily set all of your read-heads to a blank portion of the buffer instead of where they're supposed to be. Yes it's ugly, and no, it
alternatively you can also multiply the output of [vd~]/[delread~] by "0".
mfga IOhannes
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I was always looking for a clear feature in delay lines. One way to do it is to use tables instead of delwrite~, and send them a clear message "; const 0". Kinda workaround though. P
On Tue, 1 Feb 2011, Peter Plessas wrote:
I was always looking for a clear feature in delay lines. One way to do it is to use tables instead of delwrite~, and send them a clear message "; const 0". Kinda workaround though.
Did you see my email that contains the code to modify [delwrite~] to add a 'clear' method ?
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Tue, 1 Feb 2011, Peter Plessas wrote:
I was always looking for a clear feature in delay lines. One way to do it is to use tables instead of delwrite~, and send them a clear message "; const 0". Kinda workaround though.
Did you see my email that contains the code to modify [delwrite~] to add a 'clear' method ?
Yes! I think usually Miller now would check it and see if it can be included in pd, no?
best, P.
On Tue, 1 Feb 2011, Peter Plessas wrote:
- Mathieu Bouchard matju@artengine.ca [2011-02-01 15:26]:
Did you see my email that contains the code to modify [delwrite~] to add a 'clear' method ?
Yes! I think usually Miller now would check it and see if it can be included in pd, no?
Either that, or ignore it, or assert that it's not useful because annoying workarounds are good enough for him (and therefore, good enough for everybody). It depends.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
--- On Tue, 2/1/11, Mathieu Bouchard matju@artengine.ca wrote:
From: Mathieu Bouchard matju@artengine.ca Subject: Re: [PD] how can I clear [vd~] To: "Ingo Scherzinger" ingo@miamiwave.com Cc: pd-list@iem.at Date: Tuesday, February 1, 2011, 3:33 AM On Tue, 1 Feb 2011, Ingo Scherzinger wrote:
Is it possible to clear the content of [vd~]?
You should ask your question like «Is it possible to clear the content of [delwrite~] ?» because that's where the sound is kept.
[vd~] and [delread~] are just read-heads that don't keep a copy of the sound.
[delwrite~] doesn't seem to have a clear feature. This could be added with a little bit of C code, but otherwise, there is a workaround : you temporarily set all of your read-heads to a blank portion of the buffer instead of where they're supposed to be. Yes it's ugly, and no, it doesn't always work. The clear feature would be a better idea.
Would the following do the same thing as a "clear" message?
[r del_period] | [delread~ foo] | | [r clear] | | | [b] | |\ [r del_period] | | \ | | [0( [del] | | / | | [1( | |/ [*~ 1]
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-----Inline Attachment Follows-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Hello,
Thank you for writing that up Mathieu, I was looking for that exact fix about 3 months ago. Could you or anybody else that wants to take up the issuse explain to me how to add that code to my current installation? I'm assuming it would need to be recompiled, and I've never recompiled a single library or object.
Or even point me to a existing tutorial? =)
Tyler
On Tue, Feb 1, 2011 at 12:44 PM, Jonathan Wilkes jancsika@yahoo.com wrote:
--- On Tue, 2/1/11, Mathieu Bouchard matju@artengine.ca wrote:
From: Mathieu Bouchard matju@artengine.ca Subject: Re: [PD] how can I clear [vd~] To: "Ingo Scherzinger" ingo@miamiwave.com Cc: pd-list@iem.at Date: Tuesday, February 1, 2011, 3:33 AM On Tue, 1 Feb 2011, Ingo Scherzinger wrote:
Is it possible to clear the content of [vd~]?
You should ask your question like «Is it possible to clear the content of [delwrite~] ?» because that's where the sound is kept.
[vd~] and [delread~] are just read-heads that don't keep a copy of the sound.
[delwrite~] doesn't seem to have a clear feature. This could be added with a little bit of C code, but otherwise, there is a workaround : you temporarily set all of your read-heads to a blank portion of the buffer instead of where they're supposed to be. Yes it's ugly, and no, it doesn't always work. The clear feature would be a better idea.
Would the following do the same thing as a "clear" message?
[r del_period] | [delread~ foo] | | [r clear] | | | [b] | |\ [r del_period] | | \ | | [0( [del] | | / | | [1( | |/ [*~ 1]
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
-----Inline Attachment Follows-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Tue, 1 Feb 2011, Tyler Leavitt wrote:
Thank you for writing that up Mathieu, I was looking for that exact fix about 3 months ago. Could you or anybody else that wants to take up the issuse explain to me how to add that code to my current installation? I'm assuming it would need to be recompiled, and I've never recompiled a single library or object.
First learn how to recompile pd (extended's core, or vanilla, whichever) and how to install it.
After that, you can install my fix by putting it in a textfile (let's say delwrite-clear.txt) and running those commands in terminal :
cd pd/src patch < delwrite-clear.txt make install
(with appropriate changes for saying which folders the files are really in)
(the "patch" command name is a word meaning something completely something else than a modular synth patch... it's a command for automatically editing programmes based on lists of differences such as what I wrote in the email)
Or even point me to a existing tutorial? =)
I don't know.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
You could also just build a delay using a [table] as the buffer. Then you can clear your delay line by sending the [clear( message to the table.
.mmb
On Tue, Feb 1, 2011 at 6:29 PM, Mathieu Bouchard matju@artengine.ca wrote:
On Tue, 1 Feb 2011, Tyler Leavitt wrote:
Thank you for writing that up Mathieu, I was looking for that exact fix
about 3 months ago. Could you or anybody else that wants to take up the issuse explain to me how to add that code to my current installation? I'm assuming it would need to be recompiled, and I've never recompiled a single library or object.
First learn how to recompile pd (extended's core, or vanilla, whichever) and how to install it.
After that, you can install my fix by putting it in a textfile (let's say delwrite-clear.txt) and running those commands in terminal :
cd pd/src patch < delwrite-clear.txt make install
(with appropriate changes for saying which folders the files are really in)
(the "patch" command name is a word meaning something completely something else than a modular synth patch... it's a command for automatically editing programmes based on lists of differences such as what I wrote in the email)
Or even point me to a existing tutorial? =)
I don't know.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On Tue, 1 Feb 2011, Mike Moser-Booth wrote:
You could also just build a delay using a [table] as the buffer. Then you can clear your delay line by sending the [clear( message to the table. .mmb
as far as I'm concerned, if I needed that feature, I'd consider just recompiling, instead of going as far as building a workaround, especially if the workaround has to emulate [vd~] as well.
Nowadays, I use [vd~] all of the time (almost whenever I do audio).
OTOH, building a [vd~] replacement as tables means that I could easily replace [tabread4~] by Cyrille Henry's [tabread4c~].
But I use silly numbers of [vd~], which tend to take most of the cpu in many of my audio patches, so, I wouldn't want to replace by anything significantly slower.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
Oh, I agree. I'd much rather use [vd~] than hack a workaround. But I don't think all of us are in the level of compiling our own externals (I, for one, have never done it). I'm merely suggesting it as an alternative.
It is a pretty simple workaround, though. If you use [poke~] to write, then the delay time is just an offset to the index of [poke~]. And then, as you suggest, one can use whatever object that employs whatever interpolation method one prefers.
.mmb
On Wednesday, February 2, 2011, Mathieu Bouchard matju@artengine.ca wrote:
On Tue, 1 Feb 2011, Mike Moser-Booth wrote:
You could also just build a delay using a [table] as the buffer. Then you can clear your delay line by sending the [clear( message to the table. .mmb
as far as I'm concerned, if I needed that feature, I'd consider just recompiling, instead of going as far as building a workaround, especially if the workaround has to emulate [vd~] as well.
Nowadays, I use [vd~] all of the time (almost whenever I do audio).
OTOH, building a [vd~] replacement as tables means that I could easily replace [tabread4~] by Cyrille Henry's [tabread4c~].
But I use silly numbers of [vd~], which tend to take most of the cpu in many of my audio patches, so, I wouldn't want to replace by anything significantly slower.
_______________________________________________________________________ | Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Tue, 1 Feb 2011, Jonathan Wilkes wrote:
Would the following do the same thing as a "clear" message?
If you don't need change the amount of delay while using it.
It works because [delay] doesn't keep a queue of unsent bangs, it just forgets them, while [pipe] does make a queue (which wouldn't work in that circumstance).
If you wanted to support variable delay (in the manner that [delread~] does) you'd need to use a [line] with a [<] to figure out when to turn the delread~ back on.
The other difference is that instead of sending a message to a single [delwrite~], you have to modify all [delread~]s that happen to read that delay-buffer.
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
--- On Wed, 2/2/11, Mathieu Bouchard matju@artengine.ca wrote:
From: Mathieu Bouchard matju@artengine.ca Subject: Re: [PD] how can I clear [vd~] To: "Jonathan Wilkes" jancsika@yahoo.com Cc: "Ingo Scherzinger" ingo@miamiwave.com, pd-list@iem.at Date: Wednesday, February 2, 2011, 6:22 AM On Tue, 1 Feb 2011, Jonathan Wilkes wrote:
Would the following do the same thing as a "clear"
message?
If you don't need change the amount of delay while using it.
Ah, right.
It works because [delay] doesn't keep a queue of unsent bangs, it just forgets them, while [pipe] does make a queue (which wouldn't work in that circumstance).
Yep.
If you wanted to support variable delay (in the manner that [delread~] does) you'd need to use a [line] with a [<] to figure out when to turn the delread~ back on.
The other difference is that instead of sending a message to a single [delwrite~], you have to modify all [delread~]s that happen to read that delay-buffer.
That's definitely a burden.
Did you add your patch to the tracker?
-Jonathan
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
On Tue, 1 Feb 2011, Jonathan Wilkes wrote:
Did you add your patch to the tracker?
No, but now I did : http://sourceforge.net/tracker/?func=detail&aid=3170987&group_id=557...
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC
[delread~ patch_review_buffer ???]
|
| [crickets~]
| |
[!=~]
|
| [applause~]
| |
[*~]
|
|
[dac~]
--- On Wed, 2/2/11, Mathieu Bouchard matju@artengine.ca wrote:
From: Mathieu Bouchard matju@artengine.ca Subject: Re: [PD] how can I clear [vd~] To: "Jonathan Wilkes" jancsika@yahoo.com Cc: "Ingo Scherzinger" ingo@miamiwave.com, pd-list@iem.at Date: Wednesday, February 2, 2011, 11:48 PM On Tue, 1 Feb 2011, Jonathan Wilkes wrote:
Did you add your patch to the tracker?
No, but now I did : http://sourceforge.net/tracker/?func=detail&aid=3170987&group_id=557...
| Mathieu Bouchard ---- tél: +1.514.383.3801 ---- Villeray, Montréal, QC