Any suggestions for an elegant wrapping counter? Simple thing...struggling...had a go but it just feels clunky...
Note number 126 = inc preset bank, 127 = dec bank. 10 banks with index of 0-9

What about [counter 0 100], which wraps between 0 and 100 in this case?

Thanks...hehe...I didnt even think to look for the obvious...teach me to be more diligent searching

A little help goes a long way

and one more:
inc-dec.pd

btw: do you know the FCB1010 Midi Remte Script?
link text

Thanks bang. Had a look at the FCB. No behaviours etc so its a bit limited...in reality, switch scenes that much is a big load to carry in the middle of esp. impro which is my main use. Im also running the Ossandust FCB Firmware hack which adds some really nice features that would otherwise be impossible eg there is nothing sent for bank up/down in the standard firmware. Pretty much I get 8 scenes with 6 instrument groups eg Guitar, synth etc that have 4 tracks each. Any track can stop on a long pedal up (which makes it easy to finish tracks with the rest of the band). Like the fcb script, I use scene 00 to drive Live as a loop player. Dedicated tap tempo, tuner etc from 1 fs so once you start using the behaviours...its hard to go back.

GRig preset management will be interesting. I only use 1 of 4 amp voicings but 3 dedicated slots of fx with cycle of 5 presets each...ie its like program change to select amp voicing BUT stomp box for fx per preset...seems to work well for impro.

All the supporting inf is so helpful! Great forum.

Still have a long way to go...next will be getting nice UI elements. Using a remote tab to the pc which sits on the mic stand so need some 'bang' for the graphics.

@image_engine I have been using "touchOSC" by Hexler for about 3 years now so that my musicians can do their own in-ear monitor mixes and I can go out for a cigarette during rehearsals (I have given up now unfortunately). Their whole mix is done in Pd on an old Pentium laptop with a 32 in/ 30 out soundcard on usb2.
It's the simplest way to get touch control into Pd. There are others doing more impressive graphics....... but.....
It's android and ios though....... but a 7" android tablet can be had for under $50.
http://hexler.net/software/touchosc still about $5 I think (and then you can put it on all of your devices "for free" in android).
David.

Sounds cool..and giving up smoking...well I encourage you to do so...killed my mum
I actually meant Im using Vectir as remote desktop on the tab and directly controlling the pc through the tab...the pc is an industrial i7 in my floorboard...need it more as a visual...fcb is doing 99% of it...just easier to see which tracks/scenes are flying on Live.

@image_engine Ahh! oh well, you just need to make your guis big enough to hit in a panic... and get rid of anything unnecessary on the main canvas........ I see you are using messages comprehensively, but you have not as yet used "graph on parent" to hide the "innards" of your patch by redrawing only the controls onto the parent patch..
The guis are the main gripe in Pd... not at all pretty.
David.

Will check that out. I guess it doesnt need to be pretty

@image_engine It's very simple....... here is an example........
cart.pd
It's simple, but it can be hard to recover from a mistake without resorting to a text editor..... make a backup of your patch first.
Right click your patch and open "properties" and tick "graph on parent"...... then change the size (and position) of the red box to what you wish and move all of your guis into it.
Now you can make a new patch "pedalling" (or a better name.......... "impro" maybe) and put an object [B_A_Sustain 07]. It will not work. That is because you have a space in the name, and so the 07 is taken as an argument for the patch [B_A_Sustain] which does not exist.
That is why you should never have spaces in names in Pd.
When you get it working you will have a slightly prettier working window, as [B_A_Sustain-07] will become the contents of the red box of its patch when it is displayed on its parent, without all the string..........
In the patch [cart] above the "guts" are not an external patch (an "abstraction" - as you would have made) but are an object [pd guts] contained within cart......... a sub-patch. You could do the same by creating [impro] and putting an object [pd sustain] and copying the contents of [B_A_Sustain 07] into that sub-patch....
A bit of a ramble, but I think its covered!
David.

Thats sounds good. Normally dont keep white space in names but its in alpha so versioning is pretty active atm. Sounds what Im looking for.

@bang Thats why not a lot of people use the FCB. The remote script is a great effort though. The main problem is that without behaviours...you rely on switching banks which is really clunky. The bank up and down...as suspected...has no function in the remote script here which adds to the confusion. There is no undo/delete current clip which, unless you are an absolute 1st take guru, is absolutely essential. You have to also separately arm/unarm. This not natural (for me anyway)...as soon as you jump to a track...it should be ready to go.
The track behaviours allow:
first click on a track to select
single fast click to fire/record (if blank)
double click/delete take/clip
long click/ stop on pedal up

Will have a look at the code as whoever did it...put in a lot of time...but unfortunately without the other firmware...it is limited...but still useful. Would be good to get feedback from users
Cheers