Hello,
we usually using controllers and assigning they controls to give numbers or bangs. How to make a unique bang when pressing two buttons at the time for e.g. to reset to default value. I think this should be something about receiving to bangs and if a difference in time between them is in some range then makes a bang. But how is that possible?

One more...

I have numbers counting up to 8, and at the next loop (starting from 1) I want it to be 16 long. How to make this bang to wait after accidental bang until it begins a loop. I want to modify length, but on time, making loop to know that from now it is shorter or longer,....

I hope I'm good explainer.

Looking for help Smile

My controller is nanoKontrol(Korg) in this case and the buttons send 127 and 0 right away after release. I use [select 127] to make it bang ones. So I have two bangs of the same kind and don't know how to join them to make an independent bang for another purpose?

Appreciate your help.

Hmm..

Hmm..

I found that timer counts time difference between bangs. When pressing two buttons time difference is 0. Then [select 0] and I got a bang

Will I be so accurate then I need it most? I still looking for a proximal time between 0 and 20.

I'm here to speed up my work. Thanks for sharing your experience.

something like this?

[O] [O]
| |
[timer]
|
[> 100] <---maximum ms between bangs
|
[sel 1]
|
[O]

@keygap said:

I have numbers counting up to 8, and at the next loop (starting from 1) I want it to be 16 long. How to make this bang to wait after accidental bang until it begins a loop. I want to modify length, but on time, making loop to know that from now it is shorter or longer,....

i don't really know, what you are looking for. do you want a counter, that increments every cycle by its own initial length - e.g. count to 8, reset, count to 16, reset, count to 24, reset,....?
have a look at the attached file and see, if it's something you can use.

http://www.pdpatchrepo.info/hurleur/looplen_increment.pd

or add the values from the ctls, 127 + 127
and use [select 254] for output

mvh

Hello again,

Toxonic thank you, that was the part i was missing, just not [> 100] but [< 50] to my needs. Nice

Thanks for attachment, but this is not really what I'm looking for yet. I'll try to explain again.
My counter count from 1 to 8 and again to 8 as loop. If it is in case of music in live performance you wouldn't like to interrupt it. I created a possibility to change length by sending [bang 16] (or any) and when I hit it, it brake the sequence and start to count from 1, but now length is 16. I want to have an option to bang new length any time between the old length is proceeded, but it shouldn't brake it, but start a new length sequence after delay required to finish the old sequence (no matter what length it was) , in the same tempo and without unexpected jump to the beginning.

I guess this explanation unfolds my idea.

The choice of Pulsed seems to be more accurate, but one of the ctls must be hold and then banged another to have a sum of 254. [+ ] first right inlet and then left. I can't afford that because it slows down my counter twice.

Thanks

@keygap said:

Hello again,

Toxonic thank you, that was the part i was missing, just not [> 100] but [< 50] to my needs. Nice

Thanks for attachment, but this is not really what I'm looking for yet. I'll try to explain again.
My counter count from 1 to 8 and again to 8 as loop. If it is in case of music in live performance you wouldn't like to interrupt it. I created a possibility to change length by sending [bang 16] (or any) and when I hit it, it brake the sequence and start to count from 1, but now length is 16. I want to have an option to bang new length any time between the old length is proceeded, but it shouldn't brake it, but start a new length sequence after delay required to finish the old sequence (no matter what length it was) , in the same tempo and without unexpected jump to the beginning.

I guess this explanation unfolds my idea.

ahh, ok - then just use a modulo after the counter, and change the argument with messages, then the sequnce will not be interrupted by changing the sequence length:

[x]
|
[metro 500]
|
[f]x[+ 1] _________this is the counter
|
[mod 8] <------ send messages to the right inlet, e.g. [16( or [32(
|
[nbx\ <------ out for the step-#

EDIT: sorry, didn't read your post until the end, you want - when a change of length set - first to play the running sequence through before the change happens? then the attachment might be, what you want!?

http://www.pdpatchrepo.info/hurleur/seq_counter.pd

@keygap said:

The choice of Pulsed seems to be more accurate, but one of the ctls must be hold and then banged another to have a sum of 254. [+ ] first right inlet and then left. I can't afford that because it slows down my counter twice.

Thanks

why does it slow down your counter??

something like:

[ctlin #1] [ctlin #2]
| |
| [t b f]
| / |
[pack f f] <-----you can do this w/o pack, was easier to type...
|
[+]
|
[sel 254]
|
[o]

I know it's not a miracle, it's knowledge, but seems like a miracle to me having Pd just for few months. Looks like I'm trying to find my own logics to get an outcome I wish, because still can't understand how some of the pd objects function. As I understand until today, using some kind of objects for some kind of purposes even saves the CPU.

Thank you, the attachment is really what I was trying to explain and functions as Swiss clock.

Hm, I was playing with your patch and one unpleasant thing appeared. Try to start loop of 8 and in the middle of it bang 16 and then 32. Then it count ... 7, 8, 25, 26 ... I don't have separate control for each of length bangs. I made an increasing step up using one button control and some times need to jump through several lengths. That means, if I'm still in the loop 8, I bang my button twice to get loop of 32, but it isn't count from the start, just count ... 7, 8, 25, 26 ..., but should ...7, 8, 1, 2... 32, 1, 2...

Need your help to update your patch.

P.S. at last! Your two button bang is 100% satisfying

http://www.pdpatchrepo.info/hurleur/screenshot_008.png

hmm, how does your [pd length select] subpatch work? and you control by midi? do the buttons on your controller work like a trigger (1 event with 127, immediately back to zero), like a gate (on press 127, release 0 (like noteon/noteoff) or like a toggle (first press -> 127 and remains after releasing the button, and second press resets it to zero)?

A sub-patch is attached and works fine (comments inside), just how to identify the problem of count jump? No MIDI control yet, just USB Korg Nanokontrol.

http://www.pdpatchrepo.info/hurleur/pd_length_select.pd

hmm, i don't really know, what you mean - i don't seem to have that issue. or maybe i didn't get you?

There are Slider objects on pd, how to obtain knob objects like here...
http://lifofernandez.com.ar/wp/wp-conte ... /xlup2.jpg

your link does not work, but i guess it's the object [knob].
there are several gui objects like [entry], [text], [slider],....