Virtual DAW Controller Device

[Raul (Raul (ulneiz))]

@Tamtam

No, it would just open the related devices when you pick a setup to load, so it would always make sure, the devices do exist on load.

I mean that the tool must be shielded against situations in which the device is not present. Not at the time of loading a profile, but during use.

For example, if the user deletes a device in an effect chain, the tool has to know that the user has deleted it, and act accordingly.

A tool is like a stupid machine. The programmer has to tell (program) everything he has to do.

@Tamtam

Hydras really are not anything close to it, because they need to be configured, and while diving into the Hyrda, I will forget (lose connection with it in my brain ^^) the creative Idea I want to follow, because the Software demands full concentration, instead of being of help for me to get quickly to a point, where I can realise my idea.

I love this paragraph. You should frame it in a box or something because it is magnificent. Precisely this is like a master guide to create any tool.

The issue of all this is that creating such a tool is not easy. You have to attend to many states, constantly update specific values. Everything has to be programmed.

At the moment you have two solutions. Try to learn Renoise’s native devices better, such as a Hydra, so that the head is not distracted.

The other solution is to learn to program (the API of Renoise + LUA code). Then with the vision in mind of the tool, start writing the code so that everything works. Here the GUI of the tool is also important. Because you will need a direct GUI, which does not distract you. You already have the name of the tool. It only remains to program it.

@Tamtam

Then on the Virtual Daw Controller the predefined control appears, which is already connected to the Synthesizers LFO filter (or whatever), it will load/create it on demand then and be set up as predefined (with predefined settings loaded etc.). So I have instantly my favorite synth sound to realise creative ideas quickly, to later manually change all detailed settings and dive into the software settings.

Renoise really works roughly like this. For example, if you want a whole chain of specific effects, you can create as many as you want and save and retrieve them in other projects. The controls are there too.

The only problem that I have understood that you have is that you need to have something like a centralized tool with only the specific controls that you think you need. And here is the difficulty. That the tool cannot guess what the user wants. Everything has to be programmed previously according to these criteria.

The best thing in this case is to make a very clear guide, before you start programming. You will need several notifiers that will be constantly working. Here a tool with an ON / OFF switch would be successful.
On the other hand, you will need to have clear notions of how to add or remove parts of the GUI. The other day a user was asking things about this precisely. Maybe you are interested.