@Balwyn Very helpful. Wrapping my head around it at the moment...
Thank you !

@willblackhurst said:

maybe you could write to the daw afterward and just send the correct data after you re-calculate it.

DAW is after pd´s [noteout], in the role of a mere sound generator.

There is a chance to use Virtual Instruments in the DAW in monophonic mode, which cancels out overlapping notes, of course.

Just interested to generate melodic MIDI legato lines inside pd itself....

Dear Forum,

is there a chance to stop a MIDI note from ringing? The stop of the actual note should be triggered by the next MIDI note in terms of creating i.e. a walking bass line. I tried a bit with velocity set to 0, when a new note comes in, but no success, as it is written into the DAW with its given note length from [makenote] (of course). So they overlap...

In my view a logical next step could be to check out to calculate any note in ms. But is it really necessary?
My thought is to make a distinction of a note off value and a velocity 0 message, which is not the same obviously. The recorded MIDI note length is not interrupted by a velocity 0 message and refers to the given note length in ms preferably, as I would understand it at the moment at least.

Also for creating melodies with varying note legths, it would be nice that the ringing note could be stopped by the adjacent one and so on...

Thank you!!

@solipp
re-positioning the count unit helped in that case to a later stage. [moses] is on my learning list. so the change did its job as you mentioned. great!! I managed to build a synced pd patch to my DAW banging out bars and 16th notes. It needs some minor fixes, but runs as intended in a first version now. Thank you very much for your great and quick help, patience and time to everybody !!

@solipp
the [change] make no difference between value "-0" and "0", indicating negative decimal numbers. So if I want to send a bang with a comparator [>= o] the [change] really happens on 1, which is one beat late then.
Negative number are send by the [abl_link~] after a reset of beat_time, which guarantees the next bar by a preroll with negative numbers

Glad about help!!

Thank you!

Thank you to all!
Here´s the thing. I am experimenting on how to get rid of the multiple bangs running through the beat section. I just need one bang representing the beat...Truncating the decimal points with [int] does not really work, as bangs are sent through it. As the very fast ticks are printed, I am not sure if the [delay] method works here safely to cut out the bang stream, but let through the first bang intended by the [% 4]...

Dear Forum,

EDITED

I tried a bit on [playhead] in plugdata in a plugin and ableton link [abl-link~] in standalone mode.

The difference is that both objects work either in the DAW or only outside the DAW. What is a good approach to start out time aligning pd to every spot of the DAW (or vice versa), IF possible at all?

In some videos I sometimes see a 64 element [hradio] representing 16th of a section, I guess, that are switched once finished. Besides I am thinking about a continuous counter marking bar numbers to trigger any patch kind of [% 4] a 4/4 time signature. But I am not too experienced here and understanding larger sequencer setups.

What is good?

Thank you very much!!

@Balwyn said:

@Moothart This may work for you
the first bang closes the spigot stopping anymore bangs, anything else opens the spigot

This is a good thing at another place in my patch for just letting through one initial bang only. (hoping to get your aproach correctly...)
I have to experiment with it.
The question here is filtering out double bangs (so to speak on top of each other) if they happen occasionally, but opening it to bangs that are not close together like a beat´s time interval or so.

THANK YOU!!

@whale-av

Great advice! It is an occasional doubled bang for now at least.
Appreciating your quick help !!