WirelessPocketPC MIDI Controller Ended

gafferuk · Post by **gafferuk** » Thu Oct 19, 2006 1:55 am

Thanks for your post clearscreen.
I would imagine theres quite a demand for such a device for doing soundchecks ect. Especially if i give it 4 MIDI outputs, act as 4 independant controllers and control multiple pieces of kit/software. If your using multiple pc's i could imagine my little app becoming a central hub in a studio? Or is that going too far?
I wouldnt charge no more than about £10/$20 for it if i do charge, thougth it's getting a lot more complicated that what i thought it would take, but it is nteresting being the first as far as i know.

blakejarrell · Post by **blakejarrell** » Thu Oct 19, 2006 2:37 am

i would totally pay $20 for this but i would never use it live as i usually have 2-3 drinks for my nerves prior to playing and this would be like threading a needle for me lol

totally fucking cool though, i would indeed play with this.

any way to make it work on PalmOS?

gafferuk · Post by **gafferuk** » Thu Oct 19, 2006 2:42 am

blakejarrell wrote:any way to make it work on PalmOS?

Unfortunatly No, would require a total rewrite and i have not got a palmOS, this is the first time ive tried writing a pocketPC app, thougth it's just like desktop.

Clearscreen · Post by **Clearscreen** » Thu Oct 19, 2006 3:15 am

any way to make it work on PalmOS?

according to the bhajis loops forum there isn't a way to get realtime midi out of a palmos device. no hardware is being made that supports midi out later than OS version 4, and there doesn't seem to be a way to get it to send over wifi/bluetooth unfortunately. they also suggest that the latency on the midi output would be too high to be useful...

actually, gafferuk, is latency likely to be an issue with pocketpc devices?

gafferuk · Post by **gafferuk** » Thu Oct 19, 2006 4:06 am

Im not too sure to be honist... have to find out, im using an emulator at the mo, havent access to real ppc.
Should be more than fast enougth to do a sound check.

zappen · Post by **zappen** » Thu Oct 19, 2006 4:23 am

gafferuk wrote:Im not too sure to be honist... have to find out, im using an emulator at the mo, havent access to real ppc.
Should be more than fast enougth to do a sound check.

me available to test ;D
anyway with my previous tests with some ppc apps that were sending keystrokes thru wifi, the latency was fine

gafferuk · Post by **gafferuk** » Thu Oct 19, 2006 4:38 am

I would imagine the latancy well below latancy of soundcard.

Machinate · Post by **Machinate** » Thu Oct 19, 2006 12:48 pm

Cool stuff. I have two bluetooth pdas and two laptops... ! I'm ready for testing!!!

gafferuk · Post by **gafferuk** » Thu Oct 19, 2006 7:30 pm

Machinate wrote:Cool stuff. I have two bluetooth pdas and two laptops... ! I'm ready for testing!!!

2 pda's will be great for testing, ill keep you in mind. Im far off from releasing a beta release but heres a pic for now of my new xy xontrollers etc. Finished app should have around 2240 controls to play with across 4 devices.

[old image removed]

zappen · Post by **zappen** » Fri Oct 20, 2006 12:13 am

nice! keep us updated!

gafferuk · Post by **gafferuk** » Fri Oct 20, 2006 12:40 am

Well, i think ive completed the xyXControllerGUI, it's quite surprising visually what a couple of green squares can do.
[old image removed]

zappen · Post by **zappen** » Fri Oct 20, 2006 3:47 am

those squares will be cool also to drive visuals stuff, eg moving something on the screen, but i guess those little can't be that precise, can you propetly select any number between 1-128? what is the common ppc touchscreen resolution? same as the screen resolution? 320x240?
else could be possible also to have a big fullscreen one of those?
so it could be more precise!

gafferuk · Post by **gafferuk** » Fri Oct 20, 2006 4:09 am

zappen wrote:those squares will be cool also to drive visuals stuff, eg moving something on the screen, but i guess those little can't be that precise, can you propetly select any number between 1-128? what is the common ppc touchscreen resolution? same as the screen resolution? 320x240?
else could be possible also to have a big fullscreen one of those?
so it could be more precise!

yes, touch screen resolution is same as screen resolution 240x320.
My xy controllers are 112x112 so no there not 100% acurate but there pretty close. they are scaled thougth, bottom end is 0 and top end is 127 using equation: x = value * (panel.Width / 128)
I just thought having 2 xy controllers on one screen would be quite handy.
As for full screen size xy controller, i don't see why not.
Going to include some piano keys as well so can ploy off a few notes.
And load midi files from pocketPC memorycard, act as midi player so can play midi on external synths ect.

gafferuk · Post by **gafferuk** » Fri Oct 20, 2006 4:26 am

I just tested my edirol keyboard knob and tried being acurate and slowly incresing it's value, and it's skips values quite often. I would imagine this being the same for most controllers so i would imagine my pocketPC controller being about the same quality as a standard pot resistor type knob.

Clearscreen · Post by **Clearscreen** » Fri Oct 20, 2006 4:59 am

the reality is that if you have a controller with 128 fixed points and you map it to anything that has more or less points it's going to skip no matter what...
but it would be nice to have a couple more accurate fullscreen xy pads i guess. what about an option (like an onscreen button next to each pad) to expand any of the xy pads to fullscreen or maybe even 128x128 resolution? that way you could expand the one you want for finer control.

i have no idea how difficult that'd be for you to code, but you did ask for ideas in this post