nILS

Darn. [me=nILS Podewski]hands wilba the 1c2s pcb[/me] :D

Soooo, in order to make creating the patch manager easier you want the firmware changed? Good one ;D If it's too hard/doesn't work: Why don't you use some other tool like synthmaker or even better yet pd.

I'm in favor of .svg and .pdf :)

Why thank you Wilba ;) Actually I could have thought of just posting the "special_characters.inc" myself... ::)

sorry for bumping. I just tried it with 100k linear stereo pots - the result is incredibly nice :D

You mean this?

As I've never really liked the appearance of the special character arrows, I went ahead and changed them. What I've done is this: * make the arrows smaller and * move them around so * switching between the combined left/right arrow and the single left/right arrows keeps them in the same spot all the time Code change in "special_characters.inc": ;; char #0: left-arrow db b'00000001', b'00000011'; 1st and 2nd line of special char db b'00000111', b'00000011'; 3rd and 4th line of special char db b'00000001', b'00000000'; 5th and 6th line of special char db b'00000000', b'00000000'; 7th and 8th line of special char ;; char #1: right-arrow db b'00000000', b'00000000'; 1st and 2nd line of special char db b'00000000', b'00010000'; 3rd and 4th line of special char db b'00011000', b'00011100'; 5th and 6th line of special char db b'00011000', b'00010000'; 7th and 8th line of special char ;; ... ;; char #7: left/right arrow db b'00000001', b'00000011'; line 1 / 2 db b'00000111', b'00010011'; line 3 / 4 db b'00011001', b'00011100'; line 5 / 6 db b'00011000', b'00010000'; line 7 / 8[/code]

Here's what works for me: // the "\0" character gets added automatically, so defining // a length of 8 gives you 7 characters to work with const char strings[3][8] = {"SomeStr", "MoreStf", "1234567"}; // ... void DISPLAY_Init(void) __wparam { MIOS_LCD_Clear(); MIOS_LCD_CursorSet(0x00); MIOS_LCD_PrintCString(strings[0]); MIOS_LCD_CursorSet(0x28); MIOS_LCD_PrintCString(strings[2]); }[/code] I fixed the length of the two dimensions of the array for two reasons: 1) it doesn't work like that if you don't 2) the compiler generates warnings if you mess up the indexes/indices

Not there? If that's really the case then the mb6582 firmware is really different - so I assume it would be faster for someone who's got an mb6582 than for me to dig through the source. Anyways - I'm curious now: 1) Does pressing the left-most/first menu button get you to the "Ensemble" menu? 2) If so, what are the menu items you can select there? I don't see any changes to the menu structures for the mb6582.

Why not send sysex from the VST?

Pretty clever: "The first 3 people to post get them" or sth like that was in your original message. You posted twice after that and Enth was third, so even w/o editing your initial post, everything would have worked out :D

Well it ain't really pretty, because... * you have to skip the first page of each page as it's just the paypal logos and so on (see picture 1) * the sections aren't clearly divided (see picture 2) * the forum view is a bit messy It's still cool that it works :D Support for more characters per line and more lines would really be neat though. But, well, let's just not go back to text-browsing ;D

This effect sounds like wrong wiring to me. A data line on ground might affect the audio out and lead to weird noises. Is the CS working (except for the buttons and encoders not doing what they're supposed to ;))?

What s1 meant is that having two funtions would make more sense as a function called "ALL" should work on *ALL* events. So it would make more sense to add a new function called "SELECTED" which affects all *selected* events.

I'm saying you don't necessarily need a bankstick to save the configuration for you buttons ;-)

http://www.ucapps.de/index.html?page=midibox_sid_manual_up.html 1) Press the left-most menu button 2) Press the menu button under INS 3) Press the menu button under Chn 3) Use menu encoder to set channel 4) Done.

1: yes.. 2: wait and check the forum. 3: in the near future, yes.

The posts don't look so bad, but the rest is tremendously clustered... Here you go:

Just get a copy of lynx and try it out yourself :D

That might be interesting for you: http://www.ucapps.de/mbhp_iic_midi.html

I'm at work atm and the only possible way to get into the interwebs (which are BAAAD) is a version of lynx that is about as old as this machine (200Mhz). Don't get me wrong, I love the console and all but text-browsing the forum is worse than writing asm for MIOS in hell while David Hasselhoff sings for you. Seriously :D

Well apparently the PIC transforms what ever the touchpad controller does to PS/2, as you can directly plug that thing into the PC.

The bankstick doesn't have anything to do with the buttons though ;-)

I was referring to problems on your side - not the controller side. A multi-core midibox can surely handle the amount of buttons you wish to have, but 260 buttons is two full computer keyboards - can *you* actually find the correct one in a fraction of a second? wouldn't 64 buttons (8x8) with different layers be a much better idea? Dedicated LCD for each knob: That's not going to work. Just look at the price tag - a small 1x8 charcter LCD display costs about $4. You want 200 of them. Besides a core can only take two LCDs at best so you're looking at building 100 cores.... You could use 7 segment displays but this would mean a *lot* of extra outputs. Speaking of pricing - an encoder will cost you ~$1. A button ~$0.10. Each knob for the buttons another $0.50. Just taking these few components you're in the $1000 range. Did you look at the size of the controller you want to build? A channel strip is usually around 3.5cm. 20 of them is 70cm already. Your 200 buttons shouldn't be any closer than 2cm or you won't be able to press one without risking to press others - that adds another 30x28cm. This thing will be huge. Sketch up the thing and show us a pic that'll help!

Welcome aboard! Your project does seem rather ambitious ;-) First up I'd suggest you take a look at the whole thing you want to build. Draw up a sketch and show it - this might help you to find some possible design problems early. Are you sure you need 200 buttons? I mean if you want to use this thing you would have to be able to identify each and every single one in less than a second or the whole thing won't do much good. 200 buttons is a matrix of ~14x15 buttons. That's a lot of buttons. * Endless pots: rotary encoders * Displaying values: how about adding an LCD display? * CC numbers: You could use differenct channels for the events, so event 0 - 127 -> Channel 1, event 128 - 255 -> Channel 2...