![]() ![]() I'm thinking about putting the MFX UI's on a similar diet, and trying to get those down to 2 pages rather than 3. This change - and a few labeling tricks on rotaries - made things so much more compact that I was able to put COSM synths and COSM guitars all on the same page. MOD boxes have transluscent backgrounds to distinguish them from MFX or post-FX.) colored) can be clicked to select the corresponding instrument or effect otherwise they're just labels. (In anticipation of COSM, MOD, and MFX interfaces possibly winding up on the same page, I've tried to be consistent in presentation: Any "boxtops" that are lit up (i.e. If you want a page with buttons for a couple of favorite instruments, and a few favorite effects, it's as simple as copying and pasting one together. The primary benefit beyond the cosmetic is that everything is modular. The sliders selecting type have gone away in favor of captions that turn elements on. :)ĬOSM, MOD, and MFX1-3 have gotten MASSIVE facelifts. Other changes have left a lot of open space on these pages, so they're due for a total overhaul, maybe this weekend.Īssign switches now appear under the CC controls on the FX page, making those controls significantly more powerful if you're creative with your Assign programming. (Also fixed the famous drum kit bug.) These are still a bit clumsy but at least now you know exactly what category you're searching in as soon as you touch the screen. PCM1/2 have gotten new independent slider controls for each instrument category. structure and detuning.ĮQ has gotten some more labels so I won't confuse treble and presence anymore. Things that I considered more global have been moved to page 1, e.g. So every button is a label imposed over a push button, doubling the control count. Oddly, I noticed that labels have OSC command strings, but they don't actually respond to touch. This makes pages load a little slower, and could even result in more TouchOSC crashes. And I'm using a lot more memory with this increased control count. I'm using a lot more screen space, which itself is both a pro and a con. Embarrassingly, I didn't realize that MA-28 etc were acoustic guitars I thought they were mics or pickups I'd never heard of! So it's been good to embed some of the documentation right into the UI. This is a little more "fun" for me as a guitar geek, and moreover, it's called out a lot of functionality that I didn't even know was there. (They light up when you touch them - neato! - but they don't persist to represent current state.) I've taken the opportunity to replace a lot of "lawsuit-aware" labels with real descriptions, for instance LIPS becomes Dano 56-U3 and so on. I’ve embedded two of the videos below that are REAPER specific, and you can see them all and more resources on his website."Many sliders have been replaced with banks of buttons, which I have found to be much more usable. In addition to the manual on the website, Tim Corpus has a new video series on setting up TouchOSC with REAPER and various other daws. You can use OSC to send MIDI Notes and CCs, Control Surface commands, Reaper Command IDS and more, plus it can feedback information from the project to the remote device. TouchOSC is an app for mobile devices to remotely control your DAW with custom UI and low latency using the OSC (open sound control) protocol. ![]() We support Windows / macOS / Linux / iOS / Android natively on multiple chips and bits. We support all major operating systems and architectures and the full feature set is available across all versions. From a Raspberry Pi to a Windows touch-screen workstation. TouchOSC runs EVERYWHERE! From the phone in your pocket to your iTablet Pro™. It looks like with the latest mk2 version of TouchOSC they’ve really worked on simplifying things for users by making a better editor, and making it available on all platforms. Its one of the reasons we tried to pack so much into the editor for REAPERWRB2 (now open source), but it was still limited to maybe half of what TouchOSC was capable of. ![]() ![]() Too many steps to get setup, WAY TOO complicated and time consuming to build my own custom layouts. I’ve had TouchOSC on my phones and tablets since 2012, but to be honest with you, I never used it for more than a few minutes outside of the videos I made on it. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |