AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Remotepc no sound11/29/2023 ![]() A DAW, on the other hand (Reaper, Ableton, Logic, etc), outputs audio directly to the sound card/audio interface without going through the OS. I don't completely know how it works under the hood, but the concept is this: most programs output audio via the operating system, which then goes to the sound card. I have no experience running Resolve remotely, but I would imagine it's a similar problem to capturing audio during a screen recording in a DAW. Or if anyone here can tell me if he is using DaVinci Resolve per Windows RDP and his sound is transferred fine to local machine. is transferred fine, I want to ask you if there are any known compatibility issues with audio when using DaVinci Resolve on a remote machine? I do not get any remote sound on my local machine.īecause remote sound from YT (browser), MP3 (win 10 media player), etc. Even when I change it to "manually" and set it on "remote audio". But it automatically detects the correct sound device "remote audio" fine. I already checked DaVinci Resolve Preferences where you can change audio output. I tried with other remote Apps, started a game on remote PC, watched youtube video remote, and all remote audio is transfered to my local machine fine. But in DaVinci Resolve, I did not get the sound from remote to my local machine. Normally, I do not have a problem running Apps on a remote machine. Lifetime, sometimes those efforts are overtaken by events.I tried yesterday to run DaVinci Resolve on a Windows 10 Remote desktop. It is Fedora's policy to close allĪble to fix it before Fedora 23 is end of life. This message is a reminder that Fedora 23 is nearing its end of life.Īnd issuing updates for Fedora 23. More recent Fedora release includes newer upstream software that fixes Lifetime, sometimes those efforts are overtaken by events. Version prior this bug is closed as described in the policy above.Īlthough we aim to fix as many bugs as possible during every release's Of Fedora, you are encouraged change the 'version' to a later Fedora To see this bug fixed and are able to reproduce it against a later version Thank you for reporting this issue and we are sorry that we were notĪble to fix it before Fedora 21 is end of life. Plan to fix it in a currently maintained version, simply change the 'version' Package Maintainer: If you wish for this bug to remain open because you This bug will be closed as EOL if it remains open with a Fedora 'version' It is Fedora's policy to close allīug reports from releases that are no longer maintained. This message is a reminder that Fedora 21 is nearing its end of life.Īpproximately 4 (four) weeks from now Fedora will stop maintainingĪnd issuing updates for Fedora 21. When I run xfreerdp manually without this option and instead add "/sound:sys:pulse" or "/sound:sys:alsa" sound is properly reproduced on the local machine. audio-mode:1 (for sound on remote computer) audio-mode:0 (for sound on this computer) For sound it passes either of these options: Krdc delegates the actual remote connection to xfreerdp. The local pc properly reproduces the sound emitted on the remote pc Make some sound on the remote pc (for example by adjusting the sound volume) In the connection settings choose "On this computer" for the sound settingĤ. Use krdc to connect to a remote Windows XP machineĢ. Version-Release number of selected component (if applicable):ġ. I can't make this work with any of the above options. My goal is to play sound on the local pc. The connection settings in krdc allow three ways to handle the remote pc's sound: play it on the local (client) pc, play it on the remote pc or disable sound. I have set up an rdp session to a Windows XP vm via krdc.
0 Comments
Read More
Leave a Reply. |