When you're quite ready, set the multi-out as your output device. Basically you're creating a virtual device that repeats its output and also provides a synchronised stream for use as input by other apps. Turn on drift correction on Blackhole, but not your system audio hardware. Set the master device to your system audio and also use it as clock source. Use Audio Midi Setup to create a "multi-output" device, that comprises both the system output device and Blackhole 2ch virtual device. If speech goes silent during installation, keep calm, wait a few seconds, and restart VoiceOver if it hasn't come back the script restarts CoreAudio which might disrupt audio temporarily but really it's fine. I don't use SIP so I didn't feel a thing, but you might. If you have to jump through hoops to approve the driver, do it. There's no app, just an installer package. If you Quit Screen Sharing with the window still open, it will reconnect when you relaunch it, helpfully. Presently, of course, the audio goes via the server's audio hardware. Turn off VoiceOver on the client (which you must do to use VoiceOver keys on the server remotely) by switching first to observe mode (Command+Option+X), turning off VoiceOver, going back to control mode (same keystroke) again, and then pressing VO keys and using VoiceOver on the server. In the Screen Sharing app, connect to the IP of the server. Simply grant the user that will log in access, or all users. You don't need to allow anyone to request to control your screen, neither do you need VNC support. The server is in System Preferences, Sharing.
Use Screen Sharing (open it from Spotlight) on the client to connect your computers for remote access. It's not my fault I don't like it either! Yes, they want your name and email address. Get that from here.īlackhole audio driver (two-channels) from Existential Audio. Mono 16 kbps Opus is absolutely fine for TTS and system sound effects. If you ignore this advice and try to communicate directly over the 'net then you had better hope nobody's listening and there are no vulns in Screen Sharing or SonoBus. Of course, if you're doing this all on your local LAN, there's no harm in not using a VPN, probably, if your network is trusted fully by you. Zerotier, or OpenVPN UDP bridged or routed to the target network. Point-to-point UDP highly recommended, i.e. You must arrange to be able to reach the controlled computer from the controlling computer, somehow, over an encrypted channel.
You have to somehow reach the TCP port used by Screen Sharing and the UDP port used by SonoBus. I just want you to know it's possible and I've done it: I now have fast and responsive remote screen sharing with VoiceOver feedback.Ī VPN. I don't intend to make a comprehensive guide of this just now I'm knackered, and anyway there's probably strength in having someone else on here replicate my results and document it properly.
0 kommentar(er)
