Ableton Forum

Clearscreen wrote: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

I like your expanding idea a lot, thanks! Shouldnt be too hard to do.

Heres a screenshot of my new Piano Keyboard:

[old image removed]

My apps coming on well, it's starting to come together.

And heres a screenshot of my new full-screen xy Controller:

[old image removed]

fantastic man!! don't let us wait too long to test it ;D

Heres a screenshot of my new Trigger Pad:

[old image removed]

this is dope.

i use a remote server on my pocket pc to control fl studio when i do clubs, but it is just for minor changes so i dont have to go back to my rig as often. i think the real chalenge will be in how much cpu the server client uses because the one i use, uses about 30%, so i must disable it in between changes.

i'd be very interested in trying this out in club situations. count me in for a beta test.

onyx

I can't imagine my PC application using 30% by any means, i would tell you what it currently is but i can't seem to bring up windows task manager to see.
All it's doing is listening to data coming from PocketPC over a socket. If my app uses even 1% id be surprised as all the work is being done on PocketPC.
Im only sending simple data from/to pocketPC example is: "off:0:12:127". That's simply note off/channel 0/cc 12/value 127. Data is only sent when adjusting a slider or pressing a button.

If your application transmits the desktop display onto the pocketPC then yes i can understand why it's 30% as it has to capture desktop display several times a second and send it over WIFI, it's A LOT, mine jst sends simple strings, should be as fast and efficient as MIDI.

Trust me, your like my app to do your soundchecks.

I tried VNC(desktop remote app for pocket pc) couple of years ago and thougtht it was crap, was too slow and brung it too it knees.
Thats why im building my app to overcome such programs as Remote desktop applications.

i just found this totally different but nice ppc app:
http://pocket-djstudio.com

something is moving on the ppc front

Just out of curiosity, what are you using to create your PPC app.
Visual Studio or some other compiler?

apalomba wrote:Just out of curiosity, what are you using to create your PPC app.
Visual Studio or some other compiler?

Visual studio, it's by far the most productive.

zappen wrote:i just found this totally different but nice ppc app:
http://pocket-djstudio.com

something is moving on the ppc front

Check out sequancer app Griff.

i know griff since 2001 circa there are a few music/audio programs for pocketpc already, but not any for remotely control midi

Can someone please tell me if this is standard MIDI stuff?

When I press a clip button I receive midi value of 126.
When the clip starts I receive a value of 127.
When the clip loops I receive a value of 1.
When the clip stops i receive a value of 0.

Is this standard? or is it an ableton thing?

I need to know this as im building my trigger pad, I could for instance glow the button red when you press a button, yellow when it starts and green when it loops. Would this be an ableton thing or could this also work for other apps?

Any ideas?

Heres an update screenshot of my xyControllers & faders, i think it's coming on well.

[old image removed]