I don’t know exactly what such virtual routing does to latency, probably quite a bit, but in a remote use scenario maybe that isn’t your biggest concern. You have to handle another layer of complexity, but have to set it only once, and you gain more routing flexibility than with the built-in loopback feature in TotalMix itself. I‘ve read about Windows solutions called „Virtual Cable“ or „Virtual Audio Cable“ which do the same, maybe VoiceMeeter falls into the same category. You choose that „interface“ as the audio input device or „mic“ within said app, and you’re set. It typically works like this: For any app that only listens to inputs 1/2, you create a dedicated virtual „audio interface“ which looks like a physical soundcard to the app, but in the background is fed exactly the channels you want it to have. Our solution is called Loopback, a Mac-only software by Rogue Amoeba which acts like a virtual patchbay between any ins and outs of your audio interface and the individual audio in/out of any app on your machine. In our (Mac-only) setup we run into this constraint with almost all chat / meeting (Teams, Google Meet, Zoom…) and far-end recording apps (Sessionlink, Studiolink) which we want to feed dedicated software returns and mixes from TotalMix to. chrome-remote-desktop-session file in your user folder and adding certain lines to it. Solution 3: Creating a Chrome Remote Desktop Session File. Sorry if that question is dumb from a non-Windows user, no ASIO/WDM knowledge here, but: Does your remote software on the Windows rig maybe support none other audio input than inputs 1/2 of the local audio interface(s)? If so, a dedicated virtual routing software could be part of the remedy. After the restart, your sound output should be restored and the other issues caused by Chrome Remote Desktop should be resolved. How are WDM Devices configured in the HDSP Settings? And which Outputs do you use for Windows? My understanding is this should be possible, but am I barking up the wrong tree? every possible combo I can think of (as suggested in a thread on this forum) but I can't seem to get anything coming from through the Mac. I have tried routing cubase to adat 7/8 then activating loopback and cue etc. all work fine) but no sound from Cubase no matter what I try. I have a Macbook Pro in the house that I can remote desktop into the studio PC with no problems, (configured to play audio on the mac and youtube etc. This article also provides steps for enabling sound for RDSH Remote Apps. No problems there, been using it for years. This article provides steps for enabling remote sound for a Windows virtual machine. RME HDSPe AIO up and running with totalmix and ARC USB. My main workstation is running cubase 11 on windows 10 in my studio at the bottom of the garden. I'm at the stage of complete defeat, perhaps it can't be done or perhaps someone can point me in the right direction! I've spent most of this evening trying to figure this one out. Volume: front-left: 65536 / 100% / 0.00 dB, front-right: 65536 / 100% / 0.00 dBĭevice.string = "/home/mustafa/.config/chrome-remote-desktop/pulseaudio#19d38190c5/fifo_output"ĭscription = "Unix FIFO sink /home/mustafa/.Hi all. (Alsamixer is no help either)įlags: DECIBEL_VOLUME LATENCY FLAT_VOLUME P.S.: Since I changed the above all works fine with remote desktop. I already deleted it, and I kept trying to follow online guides but they never worked. sound through the audio hardware available in the local client PC. Now Gnome takes that as my default sound output. This is due to this random sink that popped up when I installed Chrome Remote Desktop. In Device and Resource redirection, enable Allow Audio and Video Playback Redirection. And I noticed quickly that my audio did not work at all. Recently I upgraded to Ubuntu 17.04, which glitched out for me so I upgraded again to 17.10.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |