![]() It’s pretty impressive what the Soundcraft team have achieved with browser scripting. That’s pretty nice - but it also means that you’re stuck with what the common denominator offers you in terms of functionality. As long as there is a browser available that comforms to the specifications needed for the interface, you can use pretty much any device to control the mixer - Android, iOS, Windows, Mac, Linux, whatever. The main advantage of the HTML-based interface to me is that it is pretty much device-agnostic. There’s tons of JavaScript code in the Soundcraft GUI as well (that gets loaded and executed inside the browser), so you could call this an app as well - just a platform-agnostic one. Using an app or a browser to do the user event capturing, rendering and communication is a design choice - using a browser-based solution still means that there is a lot of code that needs to be executed on the tablet. ![]() ![]() I’m not entirely convinced that having an HTML based interface is necessarily superior from a “lag” perspective - in both cases, there is control information (moving faders, pushing buttons) that needs to be captured on the device (tablet, phone) and communicated to the mixer, and status information (levels, configuration) that needs to be communicated to the device from the mixer and rendered there. Just to clarify: I was talking about the audio latency when using the mixer as an audio interface, not about any latency in reacting to user input (“lag”). Nevertheless, I am not sure if I am diverting from the topic of this thread.įurther, the UI24R is not app based, but HTML user interface, so there is no latency. I know that it is app-based, so there is lag, but it has MIDAS preamps, and a stereo delay. I am not sure if the XR18 is multiclient. My primary complaint about the UI24R is that the delay is NOT stereo. I have used the UI24R since 2017, and it is rugged, sturdy and consistent. Finally, the UI24R has dbx and lexicon processors in it with extremely clean preamps. The reason for this is so that there is zero cutout or signal pause when switching cues (cues contain effects mixes, fader settings, eq etc.). ![]() Additionally, the UI24R has snapshots with cues (snapshots within a snapshot). Further, the UI24R is not app based, but HTML user interface, so there is no latency. This is because the audio interface is not restricted to servicing only one program at a time. This means that you can run Cantabile, and, for example, Ableton backing tracks from the same computer to the UI24R. The driver for the UI24R is a multiclient driver. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |