JAMES

Hi Gen experts! Is there a way to reset a delay line? I am looking to start a new patch idea off with this concept. Perhaps it could be a bang that resets the buffer of the delay line so it can start from scratch upon the bang? Thank you in advance for any clues how to make this work...

Hi Gen experts! Is there a way to reset a delay line? I am looking to start a new patch idea off with this concept. Perhaps it could be a ba

reset-a-delay-buffer

i'd recommend going over the msp delay tutorial(from the "Delays" section here):

https://docs.cycling74.com/max8/tutorials/00_mspindex

not that i'm assuming you haven't but rather, to prepare your design. in that tutorial, you'll see one pic has the "clear" message sent(that can tell you one way to reset is to clear the line... i.e. set every sample in memory to 0), and if you play with that patch, you'll get ideas as to how much more specific you want to get(for example, 'clear' causes an audible click, and it doesn't set input-recorded-material back to the beginning of the delay... by playing around you can decide how you're going to want to handle those issues later as you design in gen~)... i always try to picture things in MSP first.

next, for the answer to your other question in another thread, and the rest of your question here, in gen~, you want to get to know ops like 'sample', 'wave', 'peek'(for the reading of memory), and then also 'poke'(for writing to memory), and finally 'buffer' and 'data'(for memory management itself). add to that 'delay'(i can't see a way to clear the delay op, but you might as well get to know it as it does everything else you'd want in a delay line including multiple taps). ...create an op to start, for example write: "peek test"(it needs a buffer/data name to display docs properly so i just call it 'test'), in a blank object in gen~, then with it selected, open the reference doc for it from the right-toolbar, you'll notice it says 'index - sample index to read', but then below that it says 'phase - phase to read' but if you mouse over the left-inlet of peek, you'll notice it tells you for sure, peek reads by default in samples(the truth is, these ops are the same, but their default setup is different, and you can get them to behave exactly the way you want by getting to know their attributes from the reference, playing around with them, etc...) you can also alt/option-click on any op to get a quick pop-up description of it in gen~... if you're new to gen~, you'll have to learn to cross-reference docs with usage more than with msp(gen~ is still a bit new... could use some more doc evolution, in my humble opinion).

to send signals down various 'paths' as you mentioned in the other thread: i'm not sure you need to think in terms of paths... instead, you separate the tasks into writing and reading(the writing to memory might happen continuously no matter what while reading can be designed in a completely different way to create multiple taps, interpolate, crossfade, perform changes in delay times, etc.)

in summary: since there's so many ways to create a delay line, the best thing for anyone not familiar wanting to start gen~ is to get to know the ops... start simple, get your delay line setup with memory('data'), get it to record/write the input('poke' with some type of counter like 'counter' or '+='), and finally get it to read/play('sample' or 'peek'). then other things you need to do will become clearer, plus you'll have a starting-patch you can refer to pasting here on the forums which will get you faster help and explanations, too.

there's too much to explain at such a general stage, but hope this can help get you started 🍻

i'd recommend going over the msp delay tutorial(from the "Delays" section here):
 https://docs.cycling74.com/max8/tutorials/00_mspindex  
not that i'm assuming you haven't but rather, to prepare your design. in that tutorial, you'll see one pic has the "clear" message sent(that can tell you one way to reset is to clear the line... i.e. set every sample in memory to 0), and if you play with that patch, you'll get ideas as to how much more specific you want to get(for example, 'clear' causes an audible click, and it doesn't set input-recorded-material back to the beginning of the delay... by playing around you can decide how you're going to want to handle those issues later as you design in gen~)... i always try to picture things in MSP first.
next, for the answer to your other question in another thread, and the rest of your question here, in gen~, you want to get to know ops like 'sample', 'wave', 'peek'(for the reading of memory), and then also 'poke'(for writing to memory), and finally 'buffer' and 'data'(for memory management itself). add to that 'delay'(i can't see a way to clear the delay op, but you might as well get to know it as it does everything else you'd want in a delay line including multiple taps). ...create an op to start, for example write: "peek test"(it needs a buffer/data name to display docs properly so i just call it 'test'), in a blank object in gen~, then with it selected, open the reference doc for it from the right-toolbar, you'll notice it says 'index - sample index to read', but then below that it says 'phase - phase to read' but if you mouse over the left-inlet of peek, you'll notice it tells you for sure, peek reads by default in samples(the truth is, these ops are the same, but their default setup is different, and you can get them to behave exactly the way you want by getting to know their attributes from the reference, playing around with them, etc...) you can also alt/option-click on any op to get a quick pop-up description of it in gen~... if you're new to gen~, you'll have to learn to cross-reference docs with usage more than with msp(gen~ is still a bit new... could use some more doc evolution, in my humble opinion).

to send signals down various 'paths' as you mentioned in the other thread: i'm not sure you need to think in terms of paths... instead, you separate the tasks into writing and reading(the writing to memory might happen continuously no matter what while reading can be designed in a completely different way to create multiple taps, interpolate, crossfade, perform changes in delay times, etc.)
in summary: since there's so many ways to create a delay line, the best thing for anyone not familiar wanting to start gen~ is to get to know the ops... start simple, get your delay line setup with memory('data'), get it to record/write the input('poke' with some type of counter like 'counter' or '+='), and finally get it to read/play('sample' or 'peek'). then other things you need to do will become clearer, plus you'll have a starting-patch you can refer to pasting here on the forums which will get you faster help and explanations, too.
there's too much to explain at such a general stage, but hope this can help get you started 🍻  

Thank you @Raja I have read a lot of your posts and I’m so grateful for your willingness to share, its help is tremendous. I’ll be back here to report on my findings!

Reset a delay buffer