![]() ![]() Regarding "workflow" and where i want to go: I'm currently constructing my first "bedroom producer studio" to do stuff, mainly for myself. Hm, tried Playtime and found it "limitating" and irritating - but maybe i have to read more documentation. Regarding Ableton: Add the Playtime Extension from Helgoboss together with a Launchpad to the above setup and you have an even more flexible non linear workflow in my opinion than Ableton incl Push has to offer. For those who want tons of extras there is DrivenbyMoss which I think is another great extension - just too heavy for my use case. It is just too easy to break things for users who have developed their habits around the normal MIDI message behavior, JSFX and what not which rely on the unchanged flow of MIDI data between keyboard and DAW / KK-Software. Also, I would not want the extension to manipulate the MIDI from the other MIDI ports of the keyboard. The basics should follow 1:1 NI design intent as per user manual. In general my philosophy is to keep things lean and not overload the extension with too much stuff though (also to keep CPU to the absolute minimum). ![]() Thus, if you have time to tinker around a little I would be interested to understand how we could make these buttons work. The reason why they are high on my wishlist is simple: I would like to tie more Reaper functions to the keyboard but we are running out of available buttons (even with extended Edit mode). If I have had more time I would have sniffed the USB traffic already w Wireshark to figure out how to control these. Even more than the displays or the light guide. These are exactly the ones I would be keen on too. Currently I am just tinkering and learning. just worked without limitations).Īnd - do you know if it's possible to also get control over the "machine" only controls (scene, pattern, track)? I haven't looked at it in detail yet. It completely killed my learning workflow with Ableton live light (because it. I had a _great_ "first" evaluation weekend with Reaper, reaKontrol and the Machine2 software. And - do you know if it's possible to also get control over the "machine" only controls (scene, pattern, track)? I haven't looked at it in detail yet. I wanted to take a look at qKontrol how the images are passed to the displays. That stuff (reaper + reaKontrol + the hardware, I own a S61) really interests me, it can be a great platform. a more "stable" device detection", code split into a little more readable functions/files - but that's more or less cosmetic style. I saw some small possibilities for bugfixes and refactoring (e.g. Just interested, are there any additional ideas about reaKontrol for the future? Regarding the changes - it should work but next time i can also try to compile it on Windows. You're welcome, if needed I can give further "support/testing" on OSX for reaKontrol. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |