-
francish
posted in technical issues • read moreI am really not getting this $ business

For example, I am using the [ctlin] to receive certain midi CC's. I figured it would be easy to send a variable to select midi channel & midi cc, but having no luck yet.
Do i always have to create an "abstraction" when I use the $1 $2 $3 stuff ? Like a sublayer or something, excuse my PD internal ignorance, it will get better I hope

[ctlin $1 $2] would be enough for now, I just dont know where/how to set $1 $2

so basicly I want to create a user-interface to quickly select:
- midi channel
- midi cc
- type of sub module to process the midi cc signal with
- option paramters for the sub module (invert signal, range, ... )
I looked at the $ examples in the browser but I am really missing some understanding of PD. I also do not understand why you can use arguments
but not send the arguments to an inlet. Whats the purpose of that ? -
francish
posted in technical issues • read moreGreetings,
I'm building a patch to extend the midi cc's I send from my BCF. Its pretty cool, I've managed to create 5 slow fades with the touch of a button
Some reversed, or with a bit of log added!I still notice somewhat high CPU usage of my soundcard when sending alot of midi data too it.
Would it help to somehow filter all non integer values ? I want only 1 till 127 to go to [ctlout] , and not the 1.01, 1.02, ..., values I get from [line]. This way I will not end up sending 2x or 3x the same CC number when doing a fade.
So [line] is outputting float, and I want only the round numbers to "pass" to my midi out.
another thing I am trying to figure out is a visual "switch", so I can predefine availible CC's and Midi Channels, and easily configure the second and third inlets of [ctlout], or point me to some example perhaps! I'll figure it out somehow

Thanks,
FH -
francish
posted in technical issues • read moreRight. Well, it was the idea to use *NIX for PD anyway..... why does this matter ? I have no idea how to compile on windows and looking at x_midi.c patching ctlin should be possible even with my limited C skills
I will start with just copying stuff from the ctlout which has the features I want!! stay tuned....INSTALL.txt tells me there should be a configure script in pd/src, however I can not find it. I downloaded the src from sf.net! Are there any current build instructions somwhere ?
-
francish
posted in technical issues • read moreOk thanks for the feedback. That thread makes things more clear.
However, I have yet to see how I make the variable setting dynamic....
I want to hook up a slider to set the midi cc for example. With these
$ & abstractions it seems I have to write them in the object box staticly.I am sure I am still missing something

onward!
-
francish
posted in technical issues • read moreOh goodie!! This Makes Things Better (TM)
My control smoothed midi cc faders are soon to be a reality!
Thanks for all the help guys

-
francish
posted in technical issues • read moreOk I am definitly getting excited about PD

Too select midi channel I do the following:
[ hradio] [ hradio]
[+ 1] [+ 9 ]
[toggle]
[number]Too select midi CC I can use Sliders, they seem to output
1 <> 127!I guess I can also send 16 differnt messages through the toggle...
Somekind of drop-down list would be nice!But its a step forward, so thanks for the pointers

-
francish
posted in technical issues • read more[change]! How beautifully simple
ThanksWell, for example, I want to toggle midi channel 1 to 16. Instead of filling it in with my mouse/keyboard inside a number box. To create easier UI.
That way I can create a subpatch (I think) and quickly configure what CC/Midi channel it should have as input and output!