polosid

thank you ... i'll read it all with attention but what i was searching for was not exactly a mouse hack mathod i search a way to build a jog wheel like the ones you see in the traktorizer project putting an optical sensor under the jog wheel. i think this could lead to a more precise and durable result. this optical sensor could be ripped from a mouse (only y direction used) but for a more elegant solution i would like to buy such a sensor\kit and mount it in my project

i actually do that and with very good results. but a midicontroller stuffed with touchscreens + visuals should leave the main monitor(touchmonitor) free, while with the midicontroller you send notes, cc, pc,pb, qwerty controls, mouse messages for precision pointing and everything can make you save precious seconds during studio sessions

a second array of uv leds and a larger matrix (16x16) could solve these practical problems... do integrated leds with uv and visible light exist? eh eh .... it gets too complicated! :o ;D i'll concentrate my work on visual feedback using led matrix in the next months. probably i'll choose ARDUINO boards, because those have a friandly usb handling and i want to build a pc based app. i don't see usb compatibility so easy inside mios

sorry , i don't understand, what are you saying to me? anyway.. i think that the limitations of a ledmatrix multitouch sensor are: *it work only in dark ambients *you cannot print sprites\images while you use the matrix as a xy pad *bad resolution but maybe i'm wrong

regarding spectrasymbol + led bars... it's simple but a bit ugly... the idea about visual feedback was near to korg kp3. this solution could lead to a great variety of uses: vitrual sliders, pots,encoders,step sequencers and so on

regarding optical\led based touchscreens... as i know those screens cannot be small sized and are not so precise(you can't use fingernail) what kind of touch sensor is the korg kp3 one?

http://www.kronosrobotics.com/Anotes/Athena%20to%20Optical%20Mouse.pdf

i want to realize a rotary dial around a big happ trackball... i thought that the better way to realize it would be to place an optical sensor\encoder under the border of this dial. is there someone that knows what components are used in the optical mouses? is it possible to buy this components separately or mouse hack is the only way? is there a way to wire this components to the din boards?

regarding the idea of 16 xy pads... a vst version could be tryed. using the insetpizhere's midipads vst plugin ypu have a RESIZABLE plugin with amny configurations 1,4,16,64 pads presets that send xy cc's and notes every pad can load any type of image, so visual feedback is ok 4,16 sliders configuration, so you can use it as a controller for digital mixers... it has an option to take the velocity value and the trigger from an external midi signal (a piezo signal converted to midi) and preset inspired to the c-thu-music axis controller! latency: it depends on the touchscreen model. the software latency is 1ms. if you don't have budget limits you could buy another pc... an old model is sufficent to handle touchscreens. this solution is very very usefull, the plugin is freeware... the problems regarding this configuration are: * monotouch. actually the multitouchscreens are not supported by any os, and there are no kits or monitors avaible. * latency: i have a resistive (not elo) type and the latency is a little high. 35ms... i use midipads without any problem as a midimixer, xy controller and to control many programs... but if yu want to play complex drum solos it's not the best. i had good results using a piezo trigger on the border of the screen but the piezo signal arrives before the mouse pointer refresh , so you cannot play 16 pads at once with this precision. latency is a big problem if you use the original ps\2 drivrs the only touch technology that can be small sized and resistent enought to musical applicatins is the acoustic pulse recognition. if i'm correct the latency for this model is around 10ms... but the minimum for musical apps is 6ms!! i'm very intereasted in making a big controller with a lot of xy pads with visual feedback, but i'm starting from visuals, then velocity sensing and ar last (if i'm alive) on xy touch screen or every pad

http://it.youtube.com/watch?v=KyP4BUO_GBE :o

http://www.elotouch.com/Technologies/compare_all.asp the apr model seems to be perfect for small size music applications. using a piezo sensor under the screen, velocity sensing could be achieved... i made this experiment wit my touch screen: http://www.kvraudio.com/forum/viewtopic.php?t=192282&start=345 take a look at the midipads plugin from insertpizhere for inspiration!

yes i saw those some days ago... but i think that what kind of led matrix is the last problem a question for guru programmers: if i use 16 5x7ledmatrix connected to the dout modules(just like ledrings) is it possible to write a lcd driver that types ascii symbols on those led displays? how hard is it? is there a commercial interface to control 5x7led displays like an lcd? is it possile to interface this? http://www.itsdisplays.com/

absolutely yes! i would like to use 8x8 led matrix an not 5x7 because there are more grahical possibilities. and i think that it is not a problem to build some home made 8x8 led displays in experimental stage. but i have to say that the use of smaller matrix could leave enough free dout to add some encoders+ledrings...

i'll have some spare time this year and i would like to learn in depht how to develop mios applications... here i describe my idea... i'will try to learn all the necessary to make this real. i want to realize a 4x4 (or 4x3) velocity sensitive pads with visual feedback. for visual feedback i thougth there are two possible options: 1- use little glcd with rgb backlit 2 - use 8x8 led matrix (mios can handle up to 16 of these matrix , right?) the led matrix or the glcd will be but under the trasparent cover of the pad. but fixed with the enclosure of the box and detached from the pads to avoid damages... regarding velocity measurement i think that the most economic and practical solution is the use of piezo discs under the pads. but there will be problems with the note off messages, so some kind of contact or optic switches may be used. why? why not to buy a trigger finger???? i use a pc based music setup. i use many different music softwares: energy-xt for composition and sound design, cubase\nuendo as sequencer to make complete projects, adobe audition to trim samples and many other programs... i constantly search new solutions (mantaining a low budget) to have the better feel possible working in studio. i use touchscreens and midicontrollers very often to control everything in the most natural way possible. there is a list of thingh i want to do with my pad-midicontroller: - play jazzy drum solos with great detail regarding velocity and timing, having a visual feedback of what sound a pad will trigger - play chords or riffs or melodies, seeing the note names on the pads - trigger program functions like fade-in fade-out in a wave editor - trigger toggle functions (eg.loop function in traktor and so on....) since i want to use it with pc based configurations i think that all the preset\patch handling will be in the hands of the pc. i tryed this solution with my midibox64e and i'm really satified: i use and instance of energy-xt alwais running with the so called dummy-asio driver, so it can be used as a midi only modular vst host, it works as an interface between my midibox64e and all the music softwares i use. virtual midi ports like midi yoke are used to connect midi between different programs... the midibox64e power is directly connected to the pc (rack mounted) so the "dummy energy xt" instance is alwais active, i made a configuration that permits to change presets (different cc assignment of toggle\hold mode for buttons...) via software, with a latency of 1ms, and without the need of any lcd on my midibox64e. i found this solution very very helpfull... you can do a lot of things: use the midibox to trigger complex keyboard key cobinations or mouse directions and buttons (very helpfull with touchscreens when precision is needed). different pot\enc modes or morph functions will be enirely programmed by pc. many free-midiplugins can be downloaded and can be used as modules for various presets\configurations. regarding my 4x4 velocity visual pads i want to do the same: buid a software interface that will handle presets, note assignments, pad mode(toggle-hold), various nice features (a strip of 4 pads could be used as a virtual fader), all via software. the difficult point is how to make computer control the glcd or led-matrix. is the sysex comunication fast enough to send sprites to the midibox? if not, is there enough memory in the midibox to store a large number of sprites\symbols that can be wieved\triggered by the software. can i control 16 glcd with rgb backlit? what model can i use? is better to concentrate on 8x8 led matrix(one for each pad) or on glcd's? i'm intereasted in visual feedback more than in velocity sensing.. but is there the possibility to control 16 piezo discs and convert in midi impulses or it's better i use an unelegant combination of edrum and midibox? i actually have an alesis d4 with trigger inputs, i think i will concentrate on visuals first, and then in velocity sensing

SEARCH IN THE FORUM it's a great title for an album! thank you wisefire, i just solved the problem using my own brain, a lot of time, and the trust in myself that you gave me

what kind of joystick did you use? did you have to modify the code of they worked well at first try? i found a nice joystick here http://www.doepfer.de/home_e.htm doepfer says that it works good with 0-5v... but it seems a little expensive. what use are the leds over the sensors? are they controlled by the gate function? did someone find a solution to amplify the sensor signal to cover all the analog range of the ain?

could you please post here the code portions relative to the 8 pots unmuxed mode? ???

sorry but i'm a little confused... :-[ in the link you gave to me there is a c example called "Sending MIDI events on button movements" but now with mbkb i'm using the button matrix... is it the same thing? or better i start from sm_c_example1_v1.zip (download section)?

great! led rings are more brighter. thank you TK! but regarding midi remote control of douts: is it possible to make the douts to respond to midi and buttons together?

i finished my midibox kb... loaded bill's application and it seems to work. i need to know exactly how to assign notes and cc's to the keys and pots. i'm absolutely new in programming c or assembler so i'll need all possible details. what i need is simple: enery key assigned to a different midi note and every pot (i used 8 pot, actually only 2 pots work properly) to send a different cc. no seq and no arp. about bill's application: not all keys are assigned to a note is it an hardware or a software problem? thank you

i tryed to send back to the midibox the same melody i played, same channel, but nothing appens. my midiboxes are not stuffed with lcd. is there a way to activate the midi remote support using serge vmidibox programmers? another question: i use only 4 encoders + ledrings in my midibox64E. is it possible to gert most bright ledrings?

is it possible to modify the code of midibox 64 and 64e to allow dout pins (leds) to be controlled from external midi notes? the midibox 64e shows the status of the cc's associated to the encoders with ledrings but not the notes associated to the buttons. i think it's a usefull feaure when soft sequencers like nuendo cubase or similar are used(to see mute solo status for example)