- #Touchosc editor custom layout ipad air how to
- #Touchosc editor custom layout ipad air android
- #Touchosc editor custom layout ipad air pro
You are obviously knowledgeable about MDP2 and I can't speak to the features you mention. My opinion, like dinosaurs - is thin at one end, fat in middle, and thin at the other. I think developing an iController for the Helix, or for the Atomic which was my first go, is fun but ultimately no substitute for a dedicated midi foot controller. And in those words I displayed my true bias. I also said "If you are thinking of playing with either app as an ios midi controller". At which point, in my opinion, it comes to personal preference. I was able to do it with both MDP2 and TouchOSC. More to the point, the feature set needed for controlling the Helix is pretty minimal.
#Touchosc editor custom layout ipad air android
And as an aside, something I didn’t pay attention to until I noticed it today, TouchOSC works with Android which could be appealing to some. So yes, the design approach is different. Rather than posting a picture, if you look at the first image in this link there are what I would call labelled buttons. But I'm not sure what you mean about not being to label a button. Yamaha MD BT01 is awesome IME (I just use general midi and sysex)Ĭlick to expand.You are obviously knowledgeable about MDP2 and I can't speak to the features you mention.
#Touchosc editor custom layout ipad air how to
If you have a question about how to achieve something in MDP2, ask a question and Dan answers really quickly.at least he has to my questions. MDP2 is actually fairly limited as far as color goes. The MDP2 fader is hideous, but you can forgive that for the power. The simple look of TouchOSC has more class. You can do that on ipad too I find mousing easier than touch.Ĭolors: you won't get gray or brown with MDP2 whereas TouchOSC has both gray and brown. On computer you can design the "widgets" for your layouts on separate pages and copy/paste them into your layout. I totally agree that it is waaaaay more cumbersome creating a layout directly on ipad compared to working on computer.
Understanding the difference between "copy" and "make similar" is critical with MDP2 and is far beyond TouchOSC. MDP2 has supercontrollers, presets, a "revert to default preset settings over time" functionality, custom named ticks. MDP2 is quite a bit more powerful than TouchOSC.
#Touchosc editor custom layout ipad air pro
Midi Designer Pro 2 allows for a labelled button TouchOSC does not. If you are thinking of playing with either app as an ios midi controller the current prices are $24.99 for Midi Designer Pro 2 (plus in-app purchases) versus $4.99 for TouchOSC. But for what it’s worth, today TouchOSC is ranked #64 in top paid ipad music creation apps whereas Midi Designer doesn’t rank. Which approach to take is obviously based on personal preference. The second is that I find the aesthetics of TouchOSC much cleaner and the layout scheme more flexible. One was that I find it easier to do the design on a computer. There are a couple of things that led me there. But after some iterations I ended up using TouchOSC. I initially went the Midi Designer route as doing everything on device seemed preferable. With Midi Designer you can do everything on the ipad whereas TouchOSC requires you to do the design on your computer (editor is free for Mac, Windows and Linux) and then transfer your design to the ipad. There’s a difference in workflow between Midi Designer Pro and TouchOSC. I posted this here but in light of the discussion thought I’d cross-post it.
0 kommentar(er)
