Hi,

I'm trying to use pure data as MIDI filter before to entry to my DAW (Reaper) because I would like to modify the behaviour of a percussion midi device. The device send the message note on and off at the same time but I would like to use the percussion pad like a trigger. So with first stroke note is on and stay, second stroke note is off.
I'm able to do it entirely on pure data to control an oscillator or a sampler, but I'm not able to replicate this behaviour when I send midi message to the DAW trough noteout object. In fact I can send note on and stay to reaper but any note off.
Can someone explain me the right way to do that?

@JamesStick [makenote] is what you want.

@JamesStick It's an unusual request, so I don't think even using [makenote] will do what you want.
You will need a toggle....... a flip-flop so that each successive trigger turns the reaper note on and off.
This will probably work..... or be close to what you need....... flip-flop.pd
If you want to use many triggers....... all presumably sending different midi notes.... then you will need to use [poly] for the number of possible triggers... and feed it to [clone] containing the same number of [flip-flop]s.
I hope that makes sense.
David.

@whale-av Right you are. Apparently my reading comprehension was lacking.

@JamesStick But if you also want to keep the original velocity, you can use [stripnote] to get rid of the note offs and a one-zero-switch to send a note with the original velocity and a note off afterwards.

Just to use the toggle is simpler, but i try to avoid using GUI elements within the logic.

noteswitch.pd

If you're toggling between any two values a and b, then you can calculate c = a + b -- then to toggle a value x, it's c - x (one math operator per flip) -- the catch here is that math operations where a constant is on the left but the right side may vary are awkward in patchers. Max introduced e.g. !- (I think) for this but Pd still requires you to work around the limitation ([swap], or [expr]).

You could do

[f]
|
[- constant] (substitute a+b here)
|
[* -1] (or maybe there's a unary negation operator, I forget)

When toggling between 0 and 1, the constant is (intuitively) 1 -- but the approach can generalize to any two numbers.

hjh

@ddw_music This would oscillate between 120 and 0 for example:

noteswitch.pd

@ingox said:

noteswitch.pd

Hi Ingox,

thank for your reply.

I tried your patch and it works on pure data, but it still doesn't work when I connect to my daw.
In fact the problem is the patch change the behaviour when the final object is noteout. If you check the data trough print without connecting noteout we have at the first stroke note on and at the second one note off.
But if you connect it to noteout then note on and off are send again at the same time with every stroke.

@whale-av

Hi whale-av,

thank you too for your reply.

Your patch present a similar situation to Ingox's one. If I send the note on trough the message box and if the notein is not connecting to the second noteout the patch works well with reaper. But if both noteout are connecting at the same time, note on and off are sent at the same time twice. At least, using no.n, and disconnecting the first noteout (which is linked to message box), the patch is not working.

It seems like noteout is the problem

@ddw_music

Thank for your reply.

I'm sorry but I'm not sure to understand your message.

@JamesStick This should not be possible. [print] shows exactly what is going on, so you should connect it everywhere to see what is going on. Name the [print]s like [print this] or [print that] to differentiate different [print]s. First, i would look what is coming in through [notein].

Another source might be just midi. Channel in and channel out should be different, otherwise the note offs might just directly come from the percussion.

@JamesStick The [noteout] should be connected like this:

@JamesStick It seems Reaper has a problem with note off (that other programs do not). The forums are littered with complaints.
I haven't found why yet...... still looking.....
Are you using a plugin in Reaper?
David.

@whale-av

PureData-issue.mov

Thank you again!

I know it should be impossible, but it happens. I upload a video to show you.

I'm using a synth (Surge) but it's the same with others. I tried also with Ableton and I have the same problem.

@JamesStick Maybe you should post your patch too....

Also, in the video you should connect ONLY the output of [pack] to the first inlet of [noteout]
David.

@whale-av

my patch is similar to yours. I can post it, but the problem is the same : the patch changes behaviour when connected to [noteout].

NB I tried to connect only the first output of [pack] to [noteout], but it doesn't solve the problem.

@JamesStick Is it still the case that the first trigger starts..... but the second trigger doesn't stop?
David.

@whale-av

Yes. When noteout is connected, the patch send note on and off at the same time (as in the video). So it works like a normal percussion pad. But when noteout is not connected, the patch works well.

I replicate the same patch on max 7 and it works well. But if the pure data's patch is open (and noteout I connecte) while I'm using the max's patch, this one stop to work. I don't know how to explain that.

I upload some videos :

PuredataNoteSwitch.mov MaxNotesSwitch.mov MaxPuredataNoteswitch.mov

@JamesStick Have you take a look at what is coming in through [notein]?

The patch filters note offs. It then outputs every first incoming note on as note on and every second incoming note on as note off.

So if in one short sequence two pairs of note on/offs are coming in, it will output one note on and one note off.

It would be also possible to close the connection for some short period of time using [delay], but i suspect there is some midi thing going on.

@JamesStick The videos all say they are corrupted unfortunately.
But I will guess that you might have some kind of a midi feedback problem......... somehow when you send to reaper you are receiving a message back into Pd....... and whatever is sending it back is clever enough to recognise the loop and kill it.
That is all I can think of straight away.
Try setting Pd only to listen to midi from your pads. If that is already the case then the pads must be listening for midi from Reaper and then of course sending it to Pd.
David.

@JamesStick And..... you might be able to work around the problem using [xnoteout] from the cyclone library.
You can use it simply like this sending the midi note into the left inlet.
It will send a raw midi note off message (0x80 note...... rather than 0x90 note velocity 0)
0x80 is the Hex value of decimal 128.

Midi channel one. If you need a different midi channel you will need to play with the other inlets.
0x8F where F is the channel...... so you need to get it to print 129 for channel 2.
David.