Has anyone used an android app that works with Renoise, as a Midi controller input for Windows 10?
In summary, use a Tablet 10" as a pad MIDI through a usb cable to Windows 10 and Renoise.It’s possible?
Something like this:
https://play.google.com/store/apps/details?id=com.imaginando.lk
In fact, only the section of the matrix pad,to control specific functions with the buttons (not to play notes).
Has anyone experimented with this?
Does it have to be MIDI? 
Use TouchOSC on Android or iOS and you could be doing things like this
This is just an example. There are other presets (for matrix/mixer), and you can make your own ones too.
Does it have to be MIDI?
Use TouchOSC on Android or iOS and you could be doing things like this
This is just an example. There are other presets (for matrix/mixer), and you can make your own ones too.
Of course, I will see all this in depth when I have time.I have a tablet (a PIPO of 10" with wifi and Android), and a motherboard with an integrated wifi device, with Windows 10. I suppose it is necessary to configure the drivers of the tablet itself and also the OSC communication.Instead of wifi, could use a USB cable between the tablet and the PC.More toys to play! 
Thank you and happy new year!!!
Playing pads on a touchscreen is terrible, it is convenient when i am in elastic drums or something, but damn if i cant wait to connect pads or keys instead
Playing pads on a touchscreen is terrible, it is convenient when i am in elastic drums or something, but damn if i cant wait to connect pads or keys instead
Really, my intention is to use the tablet for control specific functions, using a bridge tool, not to play instruments.I guess the tablet will not have velocity of pulsation (the volume), therefore, loses charm to play instruments, especially percussion.
I have not seen this in depth yet, but I understand that this works well (I explain it with the idea that I have in mind):
Stage:
What is needed:
Steps:
On a 10 "tablet, the pads are large enough to include a small description.Using also colors, it would be really easy to use, despite being a bunch of buttons (but they all work the same).
This is the story or theory.The main problem is the Android APP… the Duplex tool of Danoise has a specific visual configuration, which moves away from this idea.In addition, it includes a lot of features for other programs, which end up complicating the handling, keeping in mind that the idea is to solve it as simple as possible.
Over time I could create a tool (API Lua) with a Matrix of 8x8(x2) buttons (each with a function) and MIDI Input (it is easy), with a lot of control functions (I would only need help in return communication with the APP Android and in some specific functions for control).Unfortunately, this idea is dead. Because we can not create a new special APP for Android (or other OS).But hey, at least I leave the idea :).
Happy New Year!
Edit : @Danoise,Would it be possible to create an Android App with only 8x8 square buttons, and that will work according to the previous description (with OSC Server or as it corresponds)?Is it complicated to build an APP for Android?The simplest case is a one-button APP.This could be very useful you would have your midi keyboard, and a tablet with 64 buttons to control various things of Renoise.
You can use Control to create simple Android OSC apps:http://charlie-roberts.com/Control/
Thanks Neurogami!
This is necessary to look at it with big eyes, and dedicate time.Unfortunately, to build it you need knowledge from various fields:
With Control APP it does not seem very difficult to build a mesh with many buttons, but it is enough to fail something to not work, finally.Perhaps to analyze this, the simplest thing is to create an APP with a single button. Also a tool with a single button with a specific function, and communicate the button of APP with the button of the tool through OSC Server.Check that it works, activating OSC Server and having the correct communication between the tablet and the computer (WIFI or USB, it also involves setting the tablet well).
The only one that seems to be able to illustrate us here is Danoise.However, everything together seems very complicated without a real guide, made on purpose.
These are my thoughts. Maybe it’s easier to build…
If someone has built their APP with Control (Android) for Renoise, leave a comment, please.
The main problem is the Android APP… the Duplex tool of Danoise has a specific visual configuration, which moves away from this idea.In addition, it includes a lot of features for other programs, which end up complicating the handling, keeping in mind that the idea is to solve it as simple as possible.
Indeed, Duplex does a lot of things, understands a larger range of messages than Renoise itself. That much is true. But you also get a lot of stuff “for free” that would otherwise complicate your project: two-way communication, optimized output stages (check if messages needs to be transmitted before sending), etc.
Also, although Duplex is perhaps complicated on the inside, the whole_configuration_aspect is designed to be simple, using configuration files, which - although using the lua syntax - doesn’t require any programming. They are simply configurations that can be loaded, interpreted by lua - could be text files, json, xml, any format really.
But, no matter what, you have to consider what you’re aiming for. As I understand your definition of “as simple as possible”, this pretty much means coding everything from the ground up. Which is of course not a problem if you’re willing to invest the time to do that. Sounds like you’re even willing doing an Android app from scratch? That’s a pretty complex task, especially once you get to the network, I/O parts. In many ways, the GUI is the easiest part to realize.
The alternative to making everything from scratch is, well, to rely on existing things (like Control/TouchOSC/Duplex :)).Basically, it means focusing on the interface instead of the transport layer (whether that’s MIDI or OSC, wired or wireless…)
I know about the Control app, used to have it installed on my phone and know that it can also be made to work with Duplex. TouchOSC, however, is what I have been focusing on myself. It comes with a pretty good editor (which you run on desktop Windows/OSX) that you can use for building your own interfaces. Next step is to make a rough recreation of your interface in Duplex (a “virtual control surface”), which instructs Duplex about the type of buttons, how they work, how they are laid out, etc. And really, then you should be good to go. But I would probably ask first: “I want to do XYZ, is that possible?”.
There is a lot of documentation about Duplex, but some of it is pretty hardcore - automatically generated from the source code itself. For example, here is the documentation for the control-map (XML file syntax):
https://renoise.github.io/luadocs/duplex/modules/Duplex.ControlMap.html
Could definitely have done a better job with this, but I’m happy to assist / answer any questions you might have.
@Danoise, when I comment "as simple as possible"I mean something like this (not a criticism of a Duplex tool):
“APP Renoise Control” (Android) and “Tool Renoise Control” (API Lua)have a very similar GUI (64 buttons in a mesh, or the amount that is necessary).It has no configuration options. At best, setup instructions for OSC server if necessary.
This is just an idea I have commented, at present, seeing what is necessary.I am unable to buildfor many reasons:
That is why it is the case of a single button application. Is it complicated to build an APP (Android) from scratch with a single button and OSC Server to work with Renoise? The tool (API Lua) only have a button (a function) and I guess the OSC server configuration to receive APP data.And if building the APP from scratch is very costly, is it possible to do it easily with Control?
The APP (Android) and the tool (API Lua) only have buttons (a button APP corresponds to a button of tool, nothing else), which conceptually, it is possible to reduce it to a single button, for simplicity.It would not include anything else. Simple, you take 64 control buttons. Use them.
Yes, commenting is simple, and building it is another very different topic.That is why I have commented that it is a “dead idea”.And what I’m not going to do is ask someone to build it for me.For now, I can build small tools for Renoise with some things, and others I need help with the Renoise Lua API, especially in specific functions (as I am now, I do not know how to separate a “copy” button from a “paste” button because I have to create a table and save it, to use after).So, building the tool (API Lua) would not be a problem for me, except for the I / O communication part (which is reduced to being able to control a button (pressed and released), no more elements).My conclusion is simple. If it’s so complicated to build by me (the APP Android, the I/O communication with OSC Server, etc.), I’m not going to waste time with it, at least now.I have enough in learning LUA code and the API of Renoise.
But hey, I leave the idea here, in case someone expert dares to build for himself, for their own use.Maybe I’m the only one who has a tablet with little use, and Renoise, and all this is a toy nonsense, that would only serve for me.
Thanks you for all the help and guidance!But some things are very complicated for me yet. 
Thanks Neurogami!
…
If someone has built their APP with Control (Android) for Renoise, leave a comment, please.
In my signature is a link to some code I wrote
https://github.com/Neurogami/renoise-ng/tree/master/control
Control is quirky, it can take some time to sort out details, but it lets you define custom surfaces with whatever OSC messages you want (unlike TouchOSC, as best I could tell).
There’s a learning curve.
In my signature is a link to some code I wrote
https://github.com/Neurogami/renoise-ng/tree/master/control
Control is quirky, it can take some time to sort out details, but it lets you define custom surfaces with whatever OSC messages you want (unlike TouchOSC, as best I could tell).
There’s a learning curve.
Thank you for this!For now, I have this subject parked. But maybe I’ll investigate when I have the courage and the time needed.
