[PD] one abstraction, different delay lines?

[Christof Ressi]

have a look at the [clone] object ;-)

On 28.06.2020 17:06, Jakob Laue wrote:
> One that I could do is build a delay-abstraction that receives the 
> number of different matrices on[loadbang] and then dynamically patches 
> inside itself the various needed [delwrite~]'s, [vd]'s and so on.
> All the best, Jakob
> *Gesendet:* Sonntag, 28. Juni 2020 um 15:33 Uhr
> *Von:* "Jakob Laue" <jakkesprinter at web.de>
> *An:* "Christof Ressi" <info at christofressi.com>
> *Cc:* "Pd-List" <pd-list at lists.iem.at>
> *Betreff:* Re: [PD] one abstraction, different delay lines?
> Hello again!
> Yep, maybe I should explain what I want to do :-P
> I am building a sequencer instrument that mainly consists of a matrix 
> of push buttons.
> When you press a button in a column and the sequencer arrives there, 
> then a certain midi note is played through an instrument and into [dac~].
>
> The user can go through several matrices, allowing him to play e.g. a 
> melody on matrix 1 and another melody on matrix 2.
> Now my next steps are:
> - implementing the possibility for an instrument change, so that the 
> user is able to specify an instrument he wants his midi note to go to 
> for his different matrices
> - implementing the possibility for a delay effect per matrix: Say the 
> user is on matrix 1 and plays a melody there. Now he chooses to 
> activate a delay effect for this matrix. For this I could take the 
> delay-effect-abstraction that I mentioned.
> The user plays a little bit with the "feedback", "dry/wet" and "delay 
> timing" settings. The user hears the delay effect.
>
> Now we are approaching what I want to achieve: The user is happy with 
> his melody and his delay-settings on matrix 1. Now the user changes to 
> the second matrix because he wants to play another melody on top. 
> Internally, he does this by incrementing a counter to value 2. The 
> second melody should NOT be affected by the delay settings that the 
> user applied for the melody on matrix 1. This means, that each matrix 
> needs to have its own delay effect or its own delay-effect-settings. 
> What I could certainly do, is to copy and paste my 
> delay-effect-abstraction to have two independent delay-effects for 
> each matrix/each melody. But I would like to avoid to copy-and-paste 
> because the number of matrices should be easily changeable. I want to 
> keep the patch as generic as possible. At the moment I have a number 
> for specifying the number of matrices. This number is [loadbanged] and 
> the patch does the rest on startup. I would like to keep this. But for 
> this, my delay abstraction has to be able
> - to listen for a matrix-change (receiving the corresponding counter 
> value)
> - to save the settings for each matrix and show them when a matrix 
> change is noticed
> - to write into different delay lines for having the audio effect 
> affect only the audio of a certain matrix.
>
> I hope that it is more clear now:-)
>
> At the moment, I have absolutely no idea how i could achieve this:-(
>
> All the best, Jakob
>
>
>
>
> Gesendet: Samstag, 27. Juni 2020 um 21:20 Uhr
> Von: "Christof Ressi" <info at christofressi.com>
> An: "Pd-List" <pd-list at lists.iem.at>
> Betreff: Re: [PD] one abstraction, different delay lines?
>
> so that it will be able to write into/create different delay lines "on 
> the fly"?It's currently not possible to dynamically changing the 
> source delay line ("write into") for objects like [delread~] or [vd~], 
> but it would be good feature request! I'm not sure why you would want 
> to dynamically "create" a delay line, though.
>
> Christof
>
> On 27.06.2020 19:06, Jakob Laue wrote:
>
> Dear pders:)
> Recently I have built my first abstraction for a delay-effect.
> Now I have a question. Is it possible to extend this abstraction in a 
> way,
> so that it will be able to write into/create different delay lines "on 
> the fly"?
>
> Thanks, Jakob
> _______________________________________________Pd-list at lists.iem.at[mailto:Pd-list at lists.iem.at] 
> mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
> _______________________________________________ Pd-list at lists.iem.at 
> mailing list UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list[https://lists.puredata.info/listinfo/pd-list]
>
>
>
> _______________________________________________
> Pd-list at lists.iem.at mailing list
> UNSUBSCRIBE and account-management -> 
> https://lists.puredata.info/listinfo/pd-list
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puredata.info/pipermail/pd-list/attachments/20200628/e1dc4c50/attachment-0001.html>