Hi All,
New to the forum so hope this topic is in the right place. If not hope you can advise where to post this question.
I have the following situation:
PC 1 = Windows 11 Pro PC (powerfull, lots of resources, has all the licenses for VST's etc.), located at site A
PC 2 = Windows 11 Pro Laptop, located anywhere
Both are on the same LAN (either at Site A directly on the ethernet or connected via internet VPN).
I use Remote Desktop on PC 2 to open a remote session on PC 1. It is configured to play sound that is playing PC 2 on PC 1 speakers. Great because when I use my DAW on PC 1 I can hear it on PC 2! Works like a charm.
However, in this particular setup, MIDI devices that are connected to PC 1 are not recognised by DAW's or other MIDI consuming software on PC 1.
Solution: Before starting the Remote Desktop session, configure the sound to 'Play on remote computer'. In this setup, MIDI devices connected to PC 1 are recognised by DAW's or other MIDI consuming software on PC 1. Downside: I cannot hear sound on PC 2 (my laptop).
Microsoft seems (when using remote desktop) to let me (us) choose between using MIDI and hearing sound! Now I can play MIDI devices remotely but I cannot hear the music I am making! Argh!
Does anyone here have a solution or workaround? Or could we as a collective (midi association) urge Microsoft to fix this? I have scoured the internet and I have found complaints about this issue from as early as Windows XP and onward. Sounds like it is about time to be fixed...
Any help is appreciated. Many thanks in advance!
Kind regards,
Bert
A solution to your problem would be to install voicemeeter On the remote and a vban receptor in the other. The receptor is a very applic they will receive the vban signal. Therefore you wouldn't have to be dependent on the Remote Desktop connection audio I will be better You'll be digital and you unite both audios into one into the main computer if you need any help and how to do that Don't hesitate to give note I'll be happy to help you do it. Kind regards @lfonso
Create a fodle C:\scripts\ to save botyh of this files
ps1 delaying the startup of midi services for 15 seconds so RDC can do its thing select in RDC no audio from remote computer since you got vocemeter.
C:\scripts\init-midi2.ps1
Start-Sleep -Seconds 15
midi service restart
midi endpoint --watch
C:\scripts\init-midi2-task.xml
Task Scheduler script
Task scheduler import command
schtasks /Create /TN "InitMIDI2" /XML "C:\scripts\init-midi2-task.xml"
Voicemeter link
<a href=" removed link "> removed link
VBAN Receptor link
<a href=" removed link ">VB-Audio Network h removed link removed link
minimum hardware> CPU ~1,8 GHz, 512 MB RAM, disco <100 MB; salida de audio compatible con WDM, KS, MME o ASIO.
win+R
taskschd.msc
Windows 11 seems to do whatever it wants with audio. Even when your settings all appear to be correct, anything can happen 😓
I don't have much help to offer except asking if you have tried other non-MS remote desktop software?
Hi Jason,
No I have not tried any. I am a bit reluctant to use any of the free remote desktop offerings as I want my connection to be secure.
On the other hand, I am not sure paid remote desktop software would do the trick for me but any suggestions welcome!
In the meantime I have found a workaround: I use (free software) SonoBus to get audio from PC 1 to PC 2. As this piece of software only deals with sending audio between connected devices I am okay with it being free.
I have a bit of time lag but that was to be expected and I can play around with audio quality settings to get it to an acceptable level.
Cheers!
Bert