Can't draw on MIDI piano roll with touch screen interface??

squarewave_9000
I was messing about with a friend's Sonar X3,

Perhaps your friend can pipe in on her/his Forum Account and also relate this issue.

Did you switch from the smart tool to the draw tool?

I have a touch monitor and really enjoy using it where I can.
 
Sonar depends heavily on the context area of the mouse to determine what the user might be wanting to do, and this works great for the 'smart tool' and other mouse related things.
 
This is anathema to touch, since Windows touch does not have a hover equivalent. You touch the screen or you don't.
 
Effectively, this means that the user would have to provide the context to Sonar. Like have a button in the control bar that says, 'entering data in PRV' that is different from 'scrolling PRV'. Right now, if you pinch and slide your finger on the PRV it only scrolls.
 
Consider the behavior of touch in the flyout EQ. It supports multipoint touch, so if you put four fingers down you can move the four points on the EQ at the same time. Now, if you pinch one of the points, you should be able to adjust the Q for that point, but it's difficult to not have Sonar jump two points when you try to pinch the one point. So basically, I don't use pinch-touch to control Q in the flyout EQ. Instead, I just touch the Q nob and adjust it there. Sliding finger left and right is gross adjustment while up down is fine tuning.
 
*if anyone can give their touch tips on the flyout-eq I'd be glad to hear them.
 
So, coming soon is the touch keyboard. You will definitely be able to enter midi data using that bad-boy. I imagine you could use it with the step-record feature too if you can't play close to time. This will be useful for a kind of forward midi entry scenario.
 
I do think that touch control of Track-View Envelopes, Clip Editing, Speed-Comping, Midi-Data etc, is all coming fast, but is currently effectively disabled. Right now, touch in these areas is basically for scrolling only.
 
Touch is most useful for me in live performance/practice where I can adjust synths without touching the keyboard or mouse. I reach up while a chord is ringing and tweak as I like. This includes TH2. I can turn on and off pedals using touch... adjust gain... change the current amp.
 
Mixing in Console view is also way cool with touch.
 
So, touch is slowly being built into Sonar. They aren't rushing things. There is very little that is made more complicated by touch, and almost all things touch work properly. Some VST plugs have very small buttons and nobs with can be frustrating.
 
In general, touch is still in the budding stage.

URLs are prohibited from new users to keep the fan-base safer from bots. This gives the algorithms a little time to determine if you're human before they start letting your links through.
 
Sonar supports multi-point touch. Not just 1 or 2 points (required for pinching). You can grab ten faders and move them all at the same time. You and a friend can work the faders like you might together at a real board. For that matter, you can turn on effect or plugin on your track while your friend disables something effecting her sound.
 
When windows need focus, this doesn't work so seamlessly, but if it's all exposed in Sonar, it does work.
 
What I mean is this...
If you are sitting on one side of the desk with a TH2 guitar amp sim and the window up, you can adjust settings, right? And if your friend does the same on her side, she has to wait for you to stop fiddling for her turn. But if you map the controls into a FX Chain, you can both turn off Overdrive at the same moment by each touching the screen together and at the same time.
 
To do this, Sonar enables multiple entry points into the application. 2 New concurrent threads spin up together to catch and handle the separate touch input. Or 10 new threads.
 
So, while I can boot to Ubuntu Studio and do all kinds of things with my touch screen, it is not Multi-Point Touch Enabled.
 
-------------------------------------------------------
Next, there is almost NO clamor for this feature in the traditional user-base. One of the main calls from the user-base was 'go slow! we don't care!' I think more than anything this was driven by the fact that Windows 8 supports multipoint touch and the Cakewalk developers are super talented and super interested in how to take advantage of it.
 
I'm sure you can agree that touch could make a lot of tasks more efficient than mouse work. For example, with a mouse, only one person can go through a track ans split clips and slip edit. Imagine if 2 could concurrently. Faster at least by a factor of 2 right?
 
So, there arises a question. Currently, the mark for the split is defined by the now time. In order to have 2 people concurrently splitting tracks in track view, you would have to change this constraint. Remember: Nobody is asking for this.
 
Worth the risk to irritate all the paying user base by changing this behavior now? Probably not. Let's just make it work first, and in a way that doesn't mess anything up.
 
Lots of the folks here care MOST about STABILITY. Reliable behavior. I couldn't deal with it if my little cousin came over and drew patterns in the PRV. (Well, maybe it'd be cool.)
 
What's the point?
Multipoint Touch is about enabling multiple concurrent entry-points into the code base. It is being implemented conservatively because few are actually depending on it.