Sysadmin

9230 readers

24 users here now

A community dedicated to the profession of IT Systems Administration

No generic Lemmy issue posts please! Posts about Lemmy belong in one of these communities:
[email protected]
[email protected]
[email protected]
[email protected]

founded 2 years ago

MODERATORS

[email protected]

LAN RDP Suggestions (lemm.ee)

submitted 2 days ago by [email protected] to c/[email protected]

7 comments fedilink hide all child comments

Hi, I apologize if this is not the place for this (if not please direct me where to) but I am in need of some advice for LAN RDP solution. These will be used in recording studios to minimize noise. The configuration goes like this; there are two different computers being remoted into over the LAN. In the studio are three monitors, two of them are used for one RDP session while third for the second tower. I initially had some trouble with Multi-mon until I checked the MS Learn rdp page. https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/mstsc

The problems start occurring when recording audio to Adobe Audition (I think that's the name of the product). Initially the sound card wouldn't show up until I set the audio flag to 1 https://learn.microsoft.com/en-us/azure/virtual-desktop/rdp-properties#device-redirection. One of the things done in the user's workflow is to capture audio from the browser into the Adobe product which also wasn't initially working until I checked "Release Audio Driver to the Background" in the settings menu. However, this only works in Edge not even Chrome can do that surprisingly. And even then, it's not consistent, there are some weird things the user has to with which program's window is active. In the same vein of the issue, the fixes I just described only work on towers with a dedicated soundcard. Another employee installed something called Virtual audio cable (https://vb-audio.com/Cable/index.htm). Unfortunately, I wasn't around at this time to see what problem it solved and how. And furthermore, I've a single complaint about program windows not showing up on one of the remote computers. Not sure if that is a result of their RDP session not being an administrative one (that's my first guess). I haven't been able to observe this myself, so I don't have any details, and my emails aren't being returned.

Prior to my attempt at an RDP solution, we were using Dell Wyse thin clients and Teradici gpus. This equipment is fairly old, failing consistently now and also very expensive to replace. I'm open to all suggestions though, I've been sort of eyeing VNC but I'm unsure of how it interacts with audio recording and multi monitor sessions. Sorry for the wall of text and thanks to any who reply.

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 4 points 2 days ago* (last edited 2 days ago) (1 children)

Why are you using third party RDP clients?

What operating systems are you using for each system?

It would probably help to understand better what you're actually trying to do, rather than assuming RDP is the solution.

Maybe a simple long cable for video, or something. Hard to say without really knowing what you're trying to do.

[–] [email protected] 1 points 2 days ago

Everything is on Windows, I did initially try to run Fedora Kionite but the freeRDP didn't seem to have the level of device redirection as Windows. I'm using the built-in Windows RDP solution to do this at the moment. Essentially all the audio equipment soundboards, mic, etc are connected back to the remote computer via CAT5/6 cable so the thinclient is there to allow them to control the remote computers and keep noise out of the studio. I appreciate your response.

[–] [email protected] 3 points 2 days ago (1 children)

Are you trying to record audio over an RDP session via device redirection? As in, the PC you're remoting into is running Audition and the terminal/client PC is where the audio is input from the mixer.

If the answer is "yes", I would STRONGLY advise against that. You will never get it to work properly. If you're in a recording studio, you need consistent, reliable, real-time, lag free audio processing. There is simply no way to achieve that with RDP or any other remote viewing solution. Your audio feed needs to be directly connected to the computer Audition is running on. Remote desktop software is just not designed for this situation.

[–] [email protected] 1 points 2 days ago* (last edited 2 days ago) (1 children)

I didn't have a hand in setting up these studios but my understanding is everything for audio input is ran directly back to the computer being remoted into over CAT5/6. So the audio is being captured in the studio with a mic that essentially has a long cable running back to the recording computer. The thin client is just there to allow them to control the computer remotely. Also, thanks for your reply.

[–] [email protected] 1 points 1 day ago* (last edited 1 day ago)

is the distance too big to replace the thin client with just long cables for display and input? if so, and if this is really only for control, an SBC like a raspberry could be used with rustdesk (a n open source teamviewer clone), but there are SBCs with a better price-value ratio.

but if it's just for control I don't understand why do you need device redirection

[–] [email protected] 3 points 2 days ago (1 children)

what kind of network switch equipment are you using to connect them all?

Are running a 1G or better network with vlans?

seems like a network issue. RDP is a bloated monster unless you use optimization.

[–] [email protected] 1 points 2 days ago

The network is 1G and there is some segmentation, some of the devices do need to share files with devices on other networks. Eventually I'd like to just get everything that needs to talk to each other on one network and partition the rest but that will take some time to implement. Thanks for replying.