HI All!

I am seeking a way to stop the stream of bangs that come with a [counter].

I need to trigger some chords via midi. The idea is that PD is waiting to see if I hit and stay on a particular midi pitch number over 300 milliseconds. If I do, then PD plays a chord that harmonizes with that note.

In the attached patch you can see I have started to build something that strips the note-off message so that just the midi pitch numbers can be evaluated by select objects to the right. I use that same stripnote object to so that i can measure the time between note-on and note-off messages, which I 'count' in milliseconds.

So, I have a counter triggered by [metro 1] (at 1 millisecond to count time). Below the counter, I have [> 300] working as a threshold, so that when it is tripped, I can send the waiting midi pitch number over to the right to be evaluated (selected) to then play the chord that will accompany that note. You will see that there is no line connecting from the bottom of the threshold system to the top right, where i have a [s note#] object.

Regrettably the stream of bangs from the counter are also flowing creating a cacophony. Any help would be much appreciated. I have attached my (messy) preview below

NEUROTICA SONG.pd

I am so close to improvising with this thing! Just missing something simple I am sure. Or I am very misguided in my novice PD programming.

Thank you for your expertise!
Best,
D

I haven't looked at the patch but from the description I think it could be done with [delay 300]

basically when you hit a note, start the delay with a bang. if you hit another note or if the note releases, cancel the delay (with a 'stop' message). If not, trigger the harmony from the output of the delay. (which will happen after 300 ms)

@dkeller As @seb-harmonik.ar says...... or [change] can be your friend..... neuro.pd to reset the counter only when a note changes.
The [set 0( message to [change] allows for the same note to be used again for a new trigger, once the note value has been sent (reset by the bang from [sel 1] at the bottom of the patch.
David.

@whale-av: Thank you so much!

We are that much closer!

Indeed the the stream of counting 'bangs have ceased - thank you!

But, there is now a weird behavior. As mentioned, I am seeking to trigger an accompanying chord after 300 milliseconds - a threshold for sitting on a note long enough trigger the chord. I am testing this currently with any of 4 different octaves of 'E' from my guitar through a SONUSS 2 universal pitch to midi device. In your version of the patch (again, thank you!), the accompanying chord was triggered every other strike.

So I started toying with it. I tried deleting one of the [change] objects - the one to the upper left that had a [set 0] attached to it.

Now that I deleted that [change] object, the patch now does something slightly different: It plays (again) on the second strike of an 'E' and then thereafter, as long as I keep striking that E in the same octave. If I play a lick and land on any 'E' again, or strike a different octave 'E', I need to strike the same again to make it trigger an accompanying chord - as long as I keep striking it, and hold for over 300 milliseconds, the accompanying chord will trigger. Once I move to another note (or octave of the same 'E' pitch class), I have to strike an E twice (over 300 milliseconds) to make it trigger.

I have attached the patch you sent me with the change I made back to you:

KELLER-NEURO-2.pd

All best, and thanks in advance for having another look.
D

@dkeller I am going out all day..... so no immediate response.
Let me know if I am correct about what you want..... and maybe your reply will give you some ideas.

You want a first note...... held for more than 300ms...... to trigger a chord.
Then (only then) another note to trigger another chord immediately..... presumably all future notes to do this....... or only that one future note?

[once] is useful for such operations if only one future note is required...... once.zip

Presumably you will want a reset at some point to return to the initial state...... after a delay...... or once the second chord has been triggered?
David.

HI All,

Thanks to all'y'all that responded so quickly with very good guidance. And especially thanks to 'whale-av' for that little bit of brilliant code: [once]. I was able to integrate it and it now works.

The pitch-harmonic content is specific to a dramatic song cycle I am composing, entitled NEUROTICA. In this song that I am composing currently, there is a guitar part that plays a melody on which the guitarist (me) is invited to improvise at times throughout the piece. The pitch content of the melody is: F, G, Ab, A, Bb, B, C, Db, Eb, and E.

This content surely has different pitch centers, under which the chords that I have constructed more/less 'land' when improvising - so cool! If you look inside the subpatches, you will find that there are randomized choices for chords to harmonize the same pitch. For input, I am using a basic University Guitar to MIDI converter, the G2M, made by SONUUS (monophonic, yet chromatic input), but you could plug in any controller and play monophonically. For output, I am routing the midi to an FM8 synth that comes with Kontakt.

NEUROTICA SONG SOLO HARMONIZER.pd

Once last question, Whale-av: In which PD folder do I put your object? You will notice that made a subpatch after copy-pasting the content of your object to make it work. (Please forgive me, as I do not use PD all that often except for very specific creative projects, and I forget the directories/paths.)

Thanks again for all the help! And for those curious, enjoy!

All best, and happy holidays,
D

@dkeller Even working with some of the Jazz "greats".... or should that be "grates"?..... I have met almost none that can truly improvise. A huge learned repertoire of perfect riffs seems to inhibit their ability to really innovate.
This could perhaps be a great learning tool.

Pd looks in its standard directory (Pd/bin) and the externals folder (Pd/extra) and the patch folder as it opens a patch. You can add other paths to search in Pd preferences.
If you put an external or an abstraction (like [once]... abstraction because just a patch... not compiled) in the same folder as the patch it will work just with that patch.
If you put it in a sub-folder then in the patch you will have to tell Pd where to look..... so [subfolder/once] in your patch instead of [once]....... or declare the path in the patch by placing an object [declare -path subfolder] in the patch.
If you want to use it everywhere then dump it in the extra folder...... which means you can put it in every patch..... BUT..... when you share the patch you will need to remember to bundle it or the recipient will not be able to create the object.
David.