-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Run in background when a different user is signed in #3
Comments
I am able to do this with SrvAny.exe. You can download it from Microsoft. It comes with Windows 2003 Resource Kit. This makes it run as a service.
I then point SrvAny to ShairPort4w.exe. You must place the EXE in: I was NOT able to get the 64bit version of ShairPort4 working with these directions. I had to use the 32-bit version, but it runs on 64-bit as long as you put it in the SysWOW64 folder as instructed. With current version, the settings are located in the registry under HKU.Default\Software\SharePort4w key. |
Just set up a task with Create a new task (Not the basic tasks). Tested on Windows 10. :) |
I'm getting an error when trying to create the task as system:
Any tips on what I'm doing wrong? |
hi @jptrsn |
This is more of a use question, rather than an issue. Is there any way to set shairport4w to continue to route audio to my speakers when a different user account is signed into windows 10 pro? The scenario is this: I sign into the computer, start shairport4w, and it's working as expected. However, when a different windows user signs into the machine (without me signing out), the audio stream no longer works, as I think their account takes control of the audio output.
How can I set up shairport to maintain a connection to my external speakers? I've set the output device to specifically use the correct audio output in the advanced settings.
(BTW, the same issue happens when playing music from iTunes installed directly on the same machine, it will play songs, but no audio from the selected output device)
The text was updated successfully, but these errors were encountered: