The biggest problem is that USB devices on the tower are not accessible/visible through remote desktop, so I couldn't, for instance, plug my midi keyboard into the tower. It was not as straightforward as I had imagined, not by a long shot. I've just gone through the process of setting up remote desktop so I can use my laptop above my midi keyboard to control things while everything is actually running on my much more powerful tower PC, a few feet away. I've corrected things further down in this thread. On a reasonable powerful desktop DAW, I am hoping this will operate smoothly enough so that I can run the remote continuously during tracking.ĮDIT : I was in error when I wrote this post. My DAW desktop PC is connected to my router via GigE cat5 cable.Īnyone have experience using Windows Remote Desktop in the manner described above? In particular, I am interested in how this affects performance, latency, and display smoothness (eg meters, sliders, knobs, text updating, etc) on the remote device. I would have the Surface Pro networked on my home intranet via WiFi (802.11ac). I would use this to control Cbb, control the transport, tweak VST's, etc, as well as controlling the monitor mix using RME TotalMix for my UFX+ audio interface. I would use this when I am in various parts of the room where I can't easily get to the desktop DAW PC/Monitor/Kybd/mouse, eg sitting at the piano or the edrum kit. Jim suggested that I run Windows Remote Desktop on the Surface Pro 6. I would use this for multiple purposes in the studio, but most significantly as a remote control for my desktop DAW PC (i7 8700k 4.7 GHz, built by Jim Roseberry at Studiocat). I am looking to purchase a Surface Pro 6 tablet, running Windows 10 Pro.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |