-
Notifications
You must be signed in to change notification settings - Fork 136
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
problem with endpoints #15
Comments
+1 same here. Additionally I have to open Reaper as administrator in order to the SAR records or play peripherals to be available to reaper. |
It appears the issue is with how WIN10 now uses the trusted installer. The endpoint builder seems to not have full access to the registry entry and so can't remove or change it once it's set up. You can fix this by removing the registry entries for the endpoints under Search for 'Audio Router' in the above sections to locate them. Due to the fact these are controlled by the trusted installer and thus you can't delete them or set the permissions for administrators to do so, you need to use PsExec found here: https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx Then open admin cmd line and enter You can now set permission to full for administrator and remove the entries. After this when you run Reaper it will set up the devices again and this time it will work as intended. I know it's a bit of a workaround but you should not need to do this every day ;) |
Deleting an endpoint doesn't delete it from the registry, when remaking an endpoint it uses the same registry entry as the old one but doesn't rename it in Windows, right now this has to be done manually . If I make an endpoint called Microphone Out, delete it then remake it as Microphone Test, Windows retains that it was called Microphone Out originally. In sound devices it is still called Microphone Out, I have to rename it to Microphone Test manually. After editing the name in Windows, the registry for the old Endpoint changes the value of the Name field to reflect the new device. |
Yes, from what I could see it is because the 'Trusted installer' owns the registry entry and the software is not allowed to edit or remove it. |
Investigating this now. |
I can't get SAR to create any endpoints. All the dialogs seem to work but the endpoints never create. I get an error message "There was an error opening the audio hardware: Error initializing ASIO buffers". This is from Reaper. The ASIO device I am selecting for the hardware interface works in Reaper. Any thoughts on what to look at. I have removed and reinstalled. Same result. |
If you are running latest official update for Windows10 this is due to the driver being unsigned. You will need to disable this requirement in UEFI settings and potentially set 'test mode' which you can revert once the driver is installed. There is quite a few sites that will explain how to do this, I do not have one handy atm so do a search for it. If the driver for SAR shows as having an issue in Device Manager this is likely the issue you have. |
Thanks for the reply. I don’t see any issues in Device Manager. In fact is shows the driver is signed.
[cid:image001.png@01D2DEB2.CF60AC90]
I get no errors or warnings on install.
But it can’t seem to access any of the other devices asio drivers.
[cid:image002.png@01D2DEB2.E32910F0]
Regards,
G^2
From: paulheu [mailto:notifications@github.com]
Sent: Tuesday, June 6, 2017 09:39
To: eiz/SynchronousAudioRouter <SynchronousAudioRouter@noreply.github.com>
Cc: Giordano, Glenn <gag15d@my.fsu.edu>; Comment <comment@noreply.github.com>
Subject: Re: [eiz/SynchronousAudioRouter] problem with endpoints (#15)
If you are running latest official update for Windows10 this is due to the driver being unsigned. You will need to disable this requirement in UEFI settings and potentially set 'test mode' which you can revert once the driver is installed. There is quite a few sites that will explain how to do this, I do not have one handy atm so do a search for it.
If the driver for SAR shows as having an issue in Device Manager this is likely the issue you have.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#15 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXYZS3yPfKAGc-7THYxSHb_PDachGVSXks5sBVaMgaJpZM4NTRNA>.
|
This is not an option. As far as I know the ASIO driver of the device is working fine. I can connect to it from other applications. It just won’t work in the audio router…
Thanks,
G^2
From: paulheu [mailto:notifications@github.com]
Sent: Tuesday, June 6, 2017 11:20
To: eiz/SynchronousAudioRouter <SynchronousAudioRouter@noreply.github.com>
Cc: Giordano, Glenn <gag15d@my.fsu.edu>; Comment <comment@noreply.github.com>
Subject: Re: [eiz/SynchronousAudioRouter] problem with endpoints (#15)
MAke sure the ASIO driver is not in Safe mode as that will prevent using it
[image]<https://user-images.githubusercontent.com/12208547/26836864-e973ee34-4ad3-11e7-9620-ed3874d9a780.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#15 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXYZS1aQ0pEpyX_Iu3fwYl7ad5P8ZZogks5sBW4QgaJpZM4NTRNA>.
|
And what ASIO driver would that be? |
Well, I have tried it with my Soundblaster, ASIOfofAll and VoicemeeterBanana. As the hardware interface and all produce same results and all can be used in other programs like Reaper or Jack.
Regards,
G^2
Glenn Giordano
On Jun 6, 2017, at 13:13, paulheu <notifications@github.com<mailto:notifications@github.com>> wrote:
And what ASIO driver would that be?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#15 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AXYZS3f7lYF9aPs2cfz6ip5eTqkZNMlRks5sBYikgaJpZM4NTRNA>.
|
Hey there. I'm seeing the same behavior as paulheu mentioned in his original post. I'm very new to this and I've been trying to mess around with it in the evenings with Reaper. This issue has had me thoroughly confused about what I was doing. Input/output names weren't matching up, endpoints didn't seem to be deleting. I think I've fiddled with it so much adding/removing endpoints and applications trying to understand what it's doing that I have no idea where I am now. I was just wondering if there have been any further developments on this issue? Also, I'm not sure if this is related or not but it seems like I'm not able to save the correct endpoints to my programs. For example, I currently have 3 playback endpoints. Chrome Playback, which I created first, then VLC Playback, and then IE Playback. I set the endpoint for Chrome successfully, but when I try to set the endpoint for VLC it seems to keep getting flipped over to the Chrome Playback endpoint. Even if I set VLC to the VLC Playback endpoint in the Application Details window and click OK, and then immediately double click VLC to go back into the Application Details window, it has already flipped over to the Chrome Playback endpoint. And the same with Internet Explorer, when I try to set it to IE Playback it keeps flipping over to either the VLC Playback or the Chrome Playback endpoint instead. Would this weird behavior have anything to do with the things about registry and insufficient permissions and such that have been mentioned in this thread? |
Windows 7, also have the issue from the first post |
@kelan236 As I can see, there are no developments on what @LDEDRICK has explained. But how do you set the Chrome and IE Playback endpoints? |
It appears that all other applications and drivers that I have tested have the same behavior - they don't delete their endpoints even after complete uninstallation. |
I am having issues where I initially made some endpoints which seem to stick around after having removed them and added new ones. Possibly a registry issue, running WIN10 Creators update.
I get things working by choosing the endpoints I see in the applications I use as well as desktop and then just trying the available ones in Reaper until I find a match.. So working yes, but obviouslynot how it's intended
The text was updated successfully, but these errors were encountered: