-
Hi and welcome to the Studio One User Forum!
Please note that this is an independent, user-driven forum and is not endorsed by, affiliated with, or maintained by PreSonus. Learn more in the Welcome thread!
Touchscreens
- Thread starter Number6
- Start date
AAV
Active member
There was a post about touchscreens a little over a year ago on these forums - might be a start to avoid rehashing the previous discussions -https://studiooneforum.com/threads/touchscreen-monitor-feedback-with-studio-one.175/
OP
OP
Number6
Active member
I always search, came up with nada for some reason, so thanks for the links.
That post was created over a year, I'm sure there have been improvements, and I'm asking a related but different sort of question. Just like jazz I maybe playing the same notes, but it's in a different order.
I'm keen to hear from users of this Dell touchscreen but I'll listen to other people experiences too.
Not DAW related, but in my experience don't see the value of touch screens in anything that isn't a handheld (phone/tablet). In practice, I don't want to have my arm outstretchedto use it, and I don't want fingerprints all over my screen either 
.
The Studio One Remote app on a separate iPad or Android tablet is useful though.
.The Studio One Remote app on a separate iPad or Android tablet is useful though.
lokeyfly
Well-known member
I made this thread about a year back as AAV pointed out. It may provide you with further insight. https://studiooneforum.com/threads/touchscreen-monitor-feedback-with-studio-one.175/
From your experience, that might hold true. Only I dont think I'd pass that on. For some of us, there's plenty that can be accomplished in a DAW with a touchscreen. Here's an example of one of my music videos after posting the touchscreen video (above).Not DAW related, but in my experience don't see the value of touch screens in anything that isn't a handheld (phone/tablet). In practice, I don't want to have my arm outstretchedto use it, and I don't want fingerprints all over my screen either
The Studio One Remote app on a separate iPad or Android tablet is useful though.
""Reach Far", by James Cinrad Tucker
I encountered zero problems using the touch screen with Studio One. Many of the users here assisted with feedback.
TimC340
Active member
I use a Samsung A9 tablet to run Studio One Remote, and the touchscreen facility is absolutely necessary with that as there's no pen or mouse option. I also have a 15" no-name HD touchscreen (about £80 from Amazon) that I use to expand my laptop's work area, and that's a really useful tool. It connects via USB C;. It's worth pointing out that the computer needs to support video via USB natively to allow the touchscreen facility to work; neither of my desktops do and so with those it simply works as an extension monitor via HDMI (no touch other than to interact with the screen's firmware).
TimC340
Active member
As a mobile solution, my setup works well enough. The combination of my Dell XPS 13” (4k touchscreen) and the HD second screen is… ok. Not a patch on hardware controls or a desk-based 27” or 34” screen, but the two item fit into a slim laptop case that’s no more than 14” long, 9” deep and about 1” thick when packed, and weighs around 4-5lb max. Even with my thick fingers, I can do most things without issue, and there’s always the touchpad if I can’t grab the control I want easily!
Last edited:
lokeyfly
Well-known member
I dont believe much has changed in the last year, regarding consumer touchscreens.
Specifically, I dont see any difference between the Dell P2424HT and the Acer I picked up. With a touchscreen of greater than 24, to 30 inches and above, you'll want a flexible base. Meaning a base that dips inward, and downward as this will keep the monitor close to you. Something similar to how a mixer or synthesizer would be situated below your hands. Conventional vertical back mounted touch-displays make for very tired outstreched arms in a hurry. This and more (including touch interaction and feature requests are discussed in the link already provided to you (above).
Did you have some particular need? Thats always best to provide than others rehashing a lot of already stated info.
MMV, but I feel a 24" is the smallest screen usable where you expect a mixer-like or synth like real world experience. Think, shoulder width (about 28" to 30") where arms are roughly straight out, but of course downward. That's not to say one can't get along with a 20" touchscreen monitor. Its just that things get small, and movements will be less controllable.
If I were buying now, I'd look for an OLED screen that has touch, although I havent seen any as of yet (from a quick Google search). Of course that flexible position-down to 30 deg. base will also have to play into it.
just for fun........Future touchscreens:
Ideom have some interactive touch screen displays. They're geared more for gaming, story telling, and exhibits. I havent seen anything towards DAW related workfkows. How newly developed instructions would be implemented to make music creation any easier than the current use of controllers, mapping, and command syntax arent yet clear. Eventually, I'm sure it will get there, but its likely for the moment left to the imagination.
Last edited:
One minor thing most of the Touchscreen monitors also need access to a USB port, some for both power and the touch data input, so make sure you have a spare USB M/Board socket do not deploy through a USB hub.
As far as usability of Vsts, Zoom "pinch out" brings smaller controls to a workable size.
There is no haptic feedback, unlike a phone or tablet and you need to gain familiarity with single click and dbl' click response methods.
I agree with @lokeyfly the 24' OLED, if you can get one, is a good size suggestion and screen for a standard off the shelf monitor.
The Raven gear if you want to
is always an option and they offer an SO1 map within their Eco system, but SO1 does most of it out of the box and SO1 macro toolbars can be put on the touch screen.Good luck in your search, best of regards.
lokeyfly
Well-known member
Great info from sintil8
Yeah, I will only add that NI products are not great when using multitouch. Some of their plugins wont work at all. Arturia instruments work well, but resize when possible to a larger scale if you're going to edit a lot. That's pretty much with any plugins.
I use 2 monitors. A 34 inch non touch that is placed above my Acer 27 inch T272HL. To be comfortable you need the touch screen to be as shallow an angle as possible.
I dedicate the touch screen to the SSL 360 application. It's a great way to mimic working on a console. Touch works really well with this faux console approach.
Also not sure if many know but aside from the Android Studio One Remote app there is a dedicated Studio One Remote Windows exe. It is the same as the phone app. You can place it on the touch screen, it's a great way to navigate around Studio One. Check it out.
In terms of touch screen size I wouldn't go less than a 27.
I dedicate the touch screen to the SSL 360 application. It's a great way to mimic working on a console. Touch works really well with this faux console approach.
Also not sure if many know but aside from the Android Studio One Remote app there is a dedicated Studio One Remote Windows exe. It is the same as the phone app. You can place it on the touch screen, it's a great way to navigate around Studio One. Check it out.
In terms of touch screen size I wouldn't go less than a 27.
TimC340
Active member
I’m going to be building a new desk later this year, and I’m thinking of going the SSL UF1/UF8/UC1 route, recessed into the desk, with a touch screen above at a shallowish angle and a big monitor above that which I can use for video with the DAW on the touchscreen, or for the DAW with detail stuff on the touchscreen. I’d kinda like to get a 28” lo-profile screen, say 3840x1200, so that it can display whichever part of the DAW I want, or a selection of plugins, without taking up too much vertical space. Still working on that! The laptop+touchscreen+remote screen is definitely informing the thought process though.
Hi Tim, I'd suggest getting the touch screen first. Download the following SSL software
SSL 360 application
SSL 360 Link
SSL 360 link Bus Compressor
You can get them for free from here
When you've got the touch screen and set the 360 up so that you use the transport panel in 360 to control Studio One you can then start mapping your 3rd party vst3 plugins to the 360 Link plugin. You'll be able to control the plugins directly from 360. I've found that I don't need the hardware controllers because I can control everything directly from the touch screen.
This will also save you a lot of money by not needing to buy the hardware
TimC340
Active member
Ah, you're spoiling my fun - I do like a gadget!
I've already got SSL 360, and a few of their plugins. I wasn't aware you could map other manufacturer's vsts within it - I'll have a look at that today. I do use Nektarine to map plugins for control from my Panorama or Aruba, and I've been looking forward to PS updating S One to allow the v2.0 firmware for my S88 Mk 3 to directly control plugins within the DAW. I also have an Icon P-1M which is great, but its ability to control plugins isn't wonderful even with Ian Henty's scripts.
OP
OP
Number6
Active member
I pulled the trigger and got a Dell P2424HT, it's going to replace the monitor on the left.
I think in this environment it will be super useful, for example I would love to be able to fiddle directly on this Jupiter plugin whilst playing, yup I can use the faders on the keyboard, and no shortage of controllers, but it can be a little time consuming to figure out and memorise what fader does what. I keep reaching mouse on my table to the right of me in the meantime. Doesn't feel very intuitive. I guess I'll use the touchscreen for setting up, and then when recording/playing parameters the other controllers become more useful.
I think in this environment it will be super useful, for example I would love to be able to fiddle directly on this Jupiter plugin whilst playing, yup I can use the faders on the keyboard, and no shortage of controllers, but it can be a little time consuming to figure out and memorise what fader does what. I keep reaching mouse on my table to the right of me in the meantime. Doesn't feel very intuitive. I guess I'll use the touchscreen for setting up, and then when recording/playing parameters the other controllers become more useful.
Last edited:
Yes you can map other manufacturers plugins, you'll need the 360 Link plugin (and if you want to map compressors to the bus compressor section then you'll also need the 360 compressor). There are plenty of videos on YouTube showing how to map other manufacturers plugins. SSL themselves have also provided a couple of maps for Waves and Plugin Alliance. If you need any help just post a question on this forum and I'll help.
One tip I would give when mapping is be consistent, try and place the same type of parameters on the same control each time, that way no matter the plugin there will be a certain familiarity. This is why hardware mixers work so well, they look daunting at first until you realise that each strip is exactly the same. I don't tend to look at the arranger screen anymore when mixing, I just get those fingers on 360 and get to it. My workflow has improved massively working this way.
TimC340
Active member
Topic drift inbound....
OK, I spent a few hours with this and I think my main conclusion is I won't be going down the SSL route in any way at all! The 360 Link process is quite constrained by the design of the screen (or hardware) interface, and I found it really difficult - no, impossible - to come up with a consistent mapping scheme that I'd be able to remember for the wide variety of plugins that I have available. And mapping them to the visual representation of a UC-1 really makes little sense in many cases.
As a comparison, I went deeper into Nektarine, which I've had for some time, and realised that it's far more versatile and better thought through than the SSL system. Almost all the plugins I own have already been mapped by Nektar, and the process of remapping is simple and allows total flexibility in the naming and allocation of controls. It can be based on the front panel of either the Aruba pad box or my Panorama T6, and either device will show a comprehensive display of the controls on their screens. If only the CS-12 was compatible with Studio One, it would be almost perfect!
Nektarine allows up to 16 instruments to be hosted at once, with each having an FX chain of up to 4 plugins - and you can have as many instances of Nektarine in your DAW as your computer can handle. As I say, almost everything I have has already been mapped, so it's very easy to get going - though customising the maps would probably be a good idea for some of them. As an example, I set up a chain of the old Cakewalk Z3ta2+ synth (which has over 450 controls mapped) plus an FX chain of iZotope Neoverb, a BX chorus, an NI compressor and iZotope FXEQ. All were mapped already; I didn't have to do anything.
Z3ta2+ and Neoverb in Nektarine
Default mapping of Z3ta2+ to Panorama T6 encoders and screen buttons - there's no limit (that I found) to the number of pages you can create.
Same for the Neoverb. Every control on the T6 or Aruba can be used and has probably already been mapped.
Honestly, this blows the 360 Link away! It's also somewhat better than the Native Instruments S Mk3 Kontrol v2.0 plugin control capability, though that's a bit prettier on the keyboard screen (but isn't available in Studio One). I'm amazed that Nektar haven't shouted about this rather louder!
TimC340
Active member
All of the above said, I like the idea of using SSL360 to give me a channel strip on each track, but in Windows it doesn't seem to work - as soon as you click on the SSL360 window, the focus is taken away from S1 and it stops. Also, the transport bar doesn't work - though the SSL360 transport bar will reflect what I do on whatever other control surface I use. It seems to work more or less ok on Mac (I haven't tried that yet but I will) but there's a very annoying bug where pan isn't carried across from S1 to SSL360 and vice versa.