Ardour remote controll at android

(Lefteris) #1

Hi I would like to see a android app for controlling basic function of the ardour that i have to my laptop. I found that there was a app but it has no progress 2 years now.I have start learning to build android apps and i am willing to do some research. Can someone give me some more information from where to start?Is anyone else intresting to help?
Also i would like to ask if there is any plug in or api that i can use to interact with and control ardour from there.
The app could start with something simple like controll play amd stop to a channel.
So the steps of how this app could be real.

Sorry for my english…

(Robin Gareus) #2

As for ready-made apps, there is dedicated to Ardour and some more generic ones, e.g. For the latter there are also some presets:

To start anew, you’ll want to look at to remote control Ardour.

A quick commandline example to test OSC: Install oscsend (comes with the liblo-tools on most GNU/Linux distros), enable Ardour > Preferences > Control Surfaces > OSC and run

 oscsend osc.udp://localhost:3819 /transport_play

(Sciurius) #3

I have problems installing ardmix. The installer complains that the apk is corrupt.

(Robin Gareus) #4

I suggest to file an issue at I’m not sure if ardmix’ author frequently visits this fourm.

(Lefteris) #5

Thank you for your reply. I looked for the ardmix but it did not seemed good solution.I am thinking a app that can be modular and add or remove what ever I want. How this can be possible? How a project like that can be driven from the community?I have some time to offer and help with writing some code too.But I need someone to save me time from learning all the structure of the ardour.
Thank you

(Robin Gareus) #6

Another option is to use open-stage-control, a web-browser-interface (HTML, JS, CSS), that can also interface with ardour’s OSC (Open Sound Control) interface.

That’s not an android app, but it can work in a browser on android and already does a lot of the heavy lifting.

(Len) #7

control surfaces that use OSC are backwards to MIDI based controllers. With midi based controllers, the controller sends midi events for each control based on the manufacture’s preference or user’s editing. The DAW then needs a “MIDI map” to map those events to control something.

However, with OSC, the reverse is normally true. The DAW is set to use specific OSC commands to do something and the controller requires a map that sets it’s controls to something the DAW understands. Therefore, OSC apps like TouchOSC or Control or OSCAR (touchOSC clone) or Lemur, all have editors to allow these commands to be set. All of these are android/ios applets though the editors may expect to be run on a desktop (windows/mac/linux) Most of them have tabs that allow expanding the control set for a single strip or plugin. And of course all of them allow switching from one “map” to another… though that would loose state information in switching. Using tabs is much better.

(Sciurius) #8

@x42 Apparently, the ardmix author doesn’t seem to look at his github either…

(Robin Gareus) #9

That is a pity. Thanks for reporting the issue anyway. Perhaps someone experienced with android development can recompile/re-upload it.

(Saam R Sany) #10

I’ve posed this question before and the consensus seems to be to go with OSC. I haven’t actually gotten around to trying it out yet but I’ll try to do so this week and see if I can save you the trouble of reinventing the wheel. If however, it doesn’t seem to do the job I would definitely be willing to help get a project started. I’ve never programmed anything for a mobile platform but its about time I learned and this would be as good an excuse as any.