The attachment contains one ‘main-bpachter’ which you should open. The other two files are ‘sub-bpatchers’.

If I use this ‘main-bpatcher’ in my main patch, nothing is recorded into my buffer~ objects which are placed in the main patcher.
If I copy paste the whole ‘main-bpatcher’ content into my main patch and don’t use it as a bpatcher, everything works fine and I can record perfectly into my buffers~.
Can’t one maybe use poke~ or groove~ objects in bpatchers? Can’t imagine that. Don’t see the problem though.

Thanx a lot.
Cheers
Peer

regards max

that’s exactly the problem ! poke~ #1 works perfectly in the main patcher but if I use it in a bpatcher I really always get a poke~ 0 object….
Ok…I check out your patches and tell you later how far I came.
Thanx so far.

Cheers
Peer

Thanx so much for your help. I would have NEVER found that out by myself……
Cheers
Peer

Thanx again for all your help.
It helps a lot not to make my main patcher look too complicated.
Have a fine week.

Cheers
Peer

Thanx for your patience
Peer

Thanx again and again and again.
Enjoy the week :-)
Greetz
Peer

and yeah, max is cool, but if you are a musician you are sometimes doubting if you shouldn’t better put the time in your instrument. As usual with any programme: the deeper you go, the more complicated it becomes….but we go on fighting ;-)..and sometimes enjoying….

talk to you soon
All the best

sorry for disturbing you again….

-> did that, didn’t explain too much to me…sorry :-o

but your problem is not in trapezoid~ but rather in the < ==~ 1> below it and also in using ‘startloop’ message. Basically when the sync-signal from groove~’s right-outlet hits 1, < ==~ 1> outputs a 1 for just that moment/sample which triggers edge~’s right-outlet bang(when the 1 goes back to 0 afterwards to signal beginning of ramp again).
when you go in reverse, you want that to be < ==~ 0> (because in reverse, the end point of the ramp is not 1 but 0).

-> I also figured that out, but it didn’t help a lot cause I tried to solve this problem and then I tried to solve the ‘startloop’ problem…but I never tried to solve both problems at the same time and that was the problem I guess ;-)

also, your problem will also be that the ‘startloop’ message will not start the reverse playing loop from the end of the loop as you’d like, but from the start of the loop(then it travels in reverse, but it finds no audio because it’s already at the beginning of the buffer~…), so you also need to replace ‘startloop’ message with a changing message that applies to each situation(the exact start of the loop in ms when playing forward, and the exact end of the loop in ms when playing in reverse)

-> yep….that’ll make it…you just replace the ‘startloop’ with the loop-end-point in ms….and that’s it :-)

this patch is very similar to an example patch which you should study to gain more familiarity with these techniques located in your max app folder here:
Max5/examples/sequencing-looping/audio-rate-sequencing-looping/grooveduck.maxhelp
(or grooveduck2.maxhelp in that same folder; as well as the other files in that folder and the ‘lib’ folder within that folder…)
‘grooveduck’ is pretty popular and well-known(everyone talks about it here on the forums and it’s evident that Stefan created this crossfading-double-groove~ idea with the same knowledge in mind).

-> I looked at grooveduck and grooveduck2 which I also found on this forum but they didn’t help me. But I’ll have a look again…promised

also, i don’t mind answering, but you might want to address your questions to everyone in general, because if there’s a chance i miss it, or i’m away from the forums for awhile, other people might not bother to answer if they see it’s addressed only to me(in this case, particularly, you’d probably want Stefan to answer as well; i don’t even quite understand the purpose of the 2 groove~s. They go one after the other, but using an edge~ trigger, there can be a bit of a delay, so it seems this could also be possible with just one groove~(and they are attached to separate left and right channels, i guess granular would sound interesting but there are other ways of doing this), again, Stefan and others who have used the patch would know better than me). but no worries, i’m happy to help whenever i find the time.

-> I thought that too and put the question also on the ‘normal’ forum after I wrote to you. I didn’t hear sth from Stefan for quite a while that’s why. And also I have to say, that I would never put a question on the forum before having tried to solve it by myself for 5-10 hours….today I spent the whole day with that and I couldn’t figure it out so I got a bit stressed – which never helps of course :-) :-) …and makes it even worse…

this is my best attempt, but i think now, when you reverse, it will trigger both at the same time rather than one after the other(i didn’t have time to figure it out completely, but this might be because trapezoid~ up/down also needs to be adjusted, not sure…) i’ll let you figure that out:

- >here is my very simple solution which only works with negative values now, but it’s no problem to modify it to work with both (just using a gate or sth similiar).

Again thanx a lot
Cheers
Peer