|
|
Post by ianorth on Dec 1, 2015 7:57:28 GMT -8
Is there a batch command for the little arrows in Ableton Live? They are smaller than the red dot in the windows for which there is a batch command - there should be one.
I feel that the Raven product is not been optimized for Ableton which tends to be visually smaller than Cubase & Logic.
The touchscreen works better with Cubase than Ableton and I don't even have the Cubase Raven software installed.
My fingertip more than covers the little arrows in Ableton yet I have to jab multiple times often with no success.
My ipad is less than half the size of this 27" touchscreen yet is far more precise - I can open and close far smaller windows.
Also the Remote does not update with my batch commands. Is the Remote on ipad supposed to reflect what is on the MTi 2?
I hope the developers deal with these issues soon. It would also be nice if there was a way to email support.
|
|
|
|
Post by Slate Media Technology on Dec 1, 2015 8:10:03 GMT -8
Hi ianorth, Are you referring to the "Marker Arrows" in Live? If so we actually have designated buttons to control those. While developing for Ableton and all other DAWs, we make sure to provide solutions in RAVEN for things that are too small to be touched. Email me, trevor@stevenslate.com and we can meet and go over Ableton Live. You can always email support here: slatemediatechnologies.zendesk.com/hc/en-usBest, Trevor |
|
|
|
Post by Jason Lackey on Jan 12, 2017 19:29:45 GMT -8
I too have the same issue with controlling the small buttons in Ableton. Particularly on effects like EQ8 that has the small buttons for changing the frequency.
|
|
|
|
Post by jameyz on Jan 13, 2017 6:17:04 GMT -8
I too have the same issue with controlling the small buttons in Ableton. Particularly on effects like EQ8 that has the small buttons for changing the frequency. You can turn EQ8 into a bigger version, just click the little "carrot"  UPDD also has a setting to click the nearest UI element, maybe adjust this will help you.  |
|
|
|
Post by Jason Lackey on Jan 13, 2017 8:25:08 GMT -8
Snap!! Nice! I'll give those a try. Thanks!!
|
|
|
|
Post by Jason Lackey on Jan 25, 2017 11:32:17 GMT -8
I was wandering if you have an ideal setting for the pixel setting when turning on the click nearest... function you mentioned above. I went with 5, and I'm assuming that it's not enough, but I am having a very hard time with precision touches of anything, expanding a track, turning on small buttons in devices. It's to the point where I end up using my mouse more than the touch screen for nearly anything other than pressing batch command buttons or using the raven mixer. I'm pretty close to sending it back because it has NOT eased my workflow one bit.
|
|
|
|
Post by jameyz on Jan 25, 2017 11:51:41 GMT -8
I was wandering if you have an ideal setting for the pixel setting when turning on the click nearest... function you mentioned above. I went with 5, and I'm assuming that it's not enough, but I am having a very hard time with precision touches of anything, expanding a track, turning on small buttons in devices. It's to the point where I end up using my mouse more than the touch screen for nearly anything other than pressing batch command buttons or using the raven mixer. I'm pretty close to sending it back because it has NOT eased my workflow one bit. I think the accuracy of touch will comes with practice and time using the display. Maybe try setting that function to 50 pixels. You should be able to use the "cursors" to expand the track too.. |
|
