@gsagostinho
I think I know the order of operations, but I don't know very much about triggers.

@whale-av
Actually I think I've read that once. The problem is that I'm not coding in PD daily. So things get lost sometimes.

By the way, I get the feeling the problem is how I understand the function of the patch. I coded it as kind of a forwarding device rather than a conversion of digits and symbols.

Well it should pass the command on when it's anything else than 10 (10 is the knob that does two things). Which is what [select] does if I got it right. So all the other commands except 10 should be passed on directly to the ctlout.
I don't know why, but it seems that it always sends the last command I gave twice no matter what the new command is. So if I press 10 it either sends 10 or 9 (which is fine), but when I press 19 afterwards it sends 9 or 10 again before it sends 19. So confusing.
I'm trying to tackle this problem for hours now. I need a break. Comming back tomorrow.
Thanks for your help dude! If I finally have a solution I will post it here.
... or maybe you can guess one while I'm away.
Cheers!

I'm sorry, I have not seen the post as I posted it.
So the status is: If I use the very basic version (Midischaltzentrale-V2.pd) it works.
When I try to make the one knob do two things it gets confusing. So far the status is this patch:
Midischaltzentrale_advanced.pd

@gsagostinho
pgmin just receives 10 and the channel number, nothing more. It's a very old pedal and doesn't do any more magic.

This seems to work!
Midischaltzentrale-V2.pd
I just don't know why.

Anyway, I'm trying to make one of the knobs do the play AND stop function now. I thought it might be the same routine as in the named trigger patch. But the problem is to seperate the one knob from "all the others" in that case. I'm trying to do this by using [select] which doesn't do quite what I want. I would need an object that sends the value to one output if it's true and to another if it's false.
I've even combined the trigger patch into this one here:
Midischaltzentrale.pd

Midiparse just realizes program changes. To see if it really does anything when I unpress the button I was putting bangs on every "cable" in the patch. It seems to do nothing when I let loose of the knob.
I already fumbled around with [change] but it didn't work either. It just made me press the controller three times to send a control change message.

I do have a pretty old midi footcontroller here, that I'm trying to connect to "renoise". The problem is, that renoise doesn't accept program change commands to control it's functions but just to play the instruments you've programmed. However, I'm trying to write a routine that just translates the program change numbers into control changes. That didn't seem too hard at first but now I've stumbled over a nasty problem.
When I hit the mf-1 it always sends the midi command twice and seems to get confused when I press one of the knobs twice as well. Any suggestions?

Midischaltzentrale-V2.pd
In the patch I've just connected the pgmin to the ctlout. I don't need any special value on the knobs, so I gave it 127 as standard.

I start to love this small programm more and more. So far I've even done my own little synthesizer with that one...
Cheers
Jens

Ahh... That's working! COOL!
Thank you so much!

Now it doesn't do anything at all.

I should point out that I'm not using [notein] but [ctlin]. Maybe this helps?

Sorry, dude. Still it's flickering. Change maybe doesn't work because when I press the button it senses the pressure every second so in fact it is different which is why it's flickering.
I've thought about only sensing the controller number and ignoring the value. Maybe this could be a solution?

Just tried the idea:

1. I didn't know about alternate. Fairly interesting... could help.
2. Still alternate gives flickering ons and offs on both sides. So no reliable "on / off - only - situation".
   Thanks for the quick answer though!

I have a midikeyboard here, that has 8 trigger pads. I would really like to use them in a live situation just like these monome controllers. The problem is that they have any kind of velocity. I would like them to turn something on with the first press, and off on the second. So far they send control messages and I've tried to connect them to a midi event via stripnote, but its always the same. When I rest my finger on the pad it continously posts messages.
Any ideas how to work around my way?

Is it possible that my synthesizer-patch uses more CPU when it's idle than when I'm actually playing?
Any suggestions to reduce cpu usage? I've already tried to switch off the phasor / osc objects when they're not in use. At the moment it uses about 18% when I'm playing and about 30% when it's idle.

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

Hi,
I'm trying to read the midi values of the knobs on my keyboard when I start pd. At the moment I have to move every single knob first.
Is there any chance to do this?

I'm using pd-extended on a ubuntu studio linux. I'm programming my own synthesizer (compareable with a microkorg). I'm heading for usage on stage so I'm trying to get everything running when you turn it on. I've managed to turn everything on when the patch starts except using ALSA-Midi instead of "default midi". Is there any way to load this with a loadbang and a message?

I'm pretty new to pd and I love it!
I have started to program my own synth that is based on a synthpatch from the internet. I've modified it to my needs (added a choice for waveforms, attack/decay and the possibility to add noise to the signal).
Now here's the problem:
I'm sure all of you will have realised that I'm adding up several signals of osc~. The problem - obviously - is that they are too loud when they add up. So is there any solution than reducing the signal so much that it's very quiet when you hit just one key and it's just loud enough if you hit six notes at once.
I hope to find a way to reduce the maximum output with every note that I hit and increase it with every note I release.
Any ideas?

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

... played around with the idea but it does just not sound okay. The noise is not controlled by the velocity anymore. Maybe I can reduce the cpu load by just using the pink noise (which sounds more musical to my ears anyway).