New Tool (3.1.1): PhraseTouch v1.3 build 089

In order for the physical device to react (the buttons light up), the tool must be programmed on purpose for that specific device. This tool does not have that approach.

If you want to know more about these topics, look at this topic: New tool (3.2.0): Arturia KeyLab mkII v1.1 build 017 (August 2019)

so if i wanted to do something like that but really basic for the lanuchpad, should i look more into Duplex or is there an easy way to define toggles and colors for specific keys pressed?

No. Try the Duplex, see if it does what you want. But, generally, the only way to do it is to create a “specific tool.” Renoise has no use to create this kind of links and the manufacturers of physical devices refuse to provide information related to MIDI control, such as sysex messages, because it is “private code”.

The reasonable thing is, to know how to program in LUA (and the API of Renoise), and to create a tool on purpose investigating for yourself with the specific physical device. Is not easy. But it is possible.

I think Duplex is the best bet. The Launchpad is a well supported device in this environment.

I feel like it must be just a matter of defining a color palette as a tool.
There is even a basic configuration layout in XML

I am not a programmer but It should be really easy like:
for button in grid
if buttonstate off
toggle on red
else
buttonstate off

I just dont know how one would go about implementing this as code. Probably just take and existing application and delete everything realted to the actual tool

or just add one option in the keyboard duplex application that also accepts toggles insted of button release

There are members in the forums that have created specific templates for Duplex. Simply ask for help in the Duplex thread, referring to your Novation Launchpad device. Maybe they can help you.

thanks i posted in that thread.

I think the toggle option in the keyboard app should be fairly easy to realize

Hi, I wonder if its possible to trigger phrases from multiple instruments as in a live mode from the computer keyboard or mouse. Because currently I need to change the instruments as I go.

I suspect I need to use anchor like the manual says but I still dont get how that works /:

Cheers

This enormously complex and powerful tool desperately needs a series of video tutorials showing how to use it.

It’s good that it has a manual, but it’s really only useful as a reference, not for learning how to use the tool. Also, the broken English in it makes parts of it really difficult to understand, so even its use as a reference manual is limited. It has almost no examples, which makes it even harder to learn from.

It’s also frustrating that this tool deliberately hides some of its features from the user. I can’t for the life of me figure out why it does this.

That said, this tool looks amazing, and I’m sure it’s very powerful indeed. I also appreciate the enormous amount of hard work it must have taken to make the tool and write the manual.

It’s just a shame I can’t figure out how to use it. I gave up half way through the manual, which is which is written in too cryptic and concise a manner for all the novel ways the tool offers for interacting with Renoise.

Hi @Hossan

If possible. By activating the “ALL” switch, you can simultaneously play the trigger notes for each phrase according to each panel and their routing to the desired instrument or track. You can do it with the mouse or with the MIDI input (previous mapping).

With FavTouch it would be possible to do it with the keyboard. But I stopped developing the tool because Renoise didn’t improve the API and I got fed up with waiting. When I was programming it, the “released” keys did not exist in the API. Therefore, pressing and releasing was not possible. With API 6 it has changed. But I wasted time on other tools, even more interesting.

If you activate the chain from panels 2 to 16 and panel 1 activates the Mst, you can use panel 1 as a master.

That was a minor game.

This was a programming project for fun, which I shared. It was not a project to satisfy demanding users who want it all.
In fact, I didn’t even remember that I built “a manual”. These types of tools are somewhat complex because they do several things. Building a manual with multiple examples would take forever. A video would clarify many things, but I certainly don’t have time for this type of content. I am not like Taktik, who has a company with hundreds of workers under his care to maintain Renoise and has hundreds of hours a day to update his code. I’m obviously being sarcastic.

I certainly parked this project because I needed certain things that the old API didn’t have. That was very frustrating. In fact, it is not updated for R3.2. That would be a lot of work …