![]() ![]() There is no way Microsoft officially allows you to use. Its a reverse engineered interface the control panel uses. Quote from: 6233638 on November 11, 2014, 01:53:03 am -But since both Airfoil and AudioSwitch both set the default device, it's clearly something that programs can do, so JRiver should be able to solve this. If I have to set that every time MC updates, it's more hassle than it's worth.īut since both Airfoil and AudioSwitch both set the default device, it's clearly something that programs can do, so JRiver should be able to solve this. The issue is that it keeps resetting the custom name, custom icon, output format, and full-range settings. I run AudioSwitch in the tray because Airfoil already has a bad habit of switching the default audio device when it activates. If it continues, add me to the list of people who will be removing it.Ĭhanging the default device is not a problem for me. I'm hoping that what's been happening is that there has been a change made to the driver in every update thus far, and once things are running smoothly, that will no longer happen. Recognizing that the windows reaction to driver installation can't be changed, couldn't the installer detect if the latest driver version is already installed and not reinstall if so? Quote from: mwillems on November 10, 2014, 08:57:23 pm -But what about the other (smaller) half of the problem: those of us who use the driver still have to reset our audio devices every build because windows de-defaults the driver. Under what circumstances does it set itself that way after every build? Mine does not, I believe, only on fresh installs.īest to solve that problem, if at all possible. And if the answer is "live with it" that's fine too D If anyone else has any ideas on what could be done on this particular face of the issue, I'm all ears. I would still need to leave auto-update off for WAF reasons in case the driver version did actually change on a given build, but installing the driver only when actually updated would simplify life for folks trying to use the driver on multiple systems and/or headless systems. If the installer could check to see if the latest version of the driver is installed, and then, if it's already current, not reinstall it, that would cut down drastically on the number of times I have to walk around the house and reset the audio drivers on different boxes (some of which I have to remote into). Looking at the driver versioning, it doesn't look like the driver version actually changes every build, but rather only every few builds (correct me if I'm misunderstanding this). That's a good solution to what's probably the bigger half of the problem: the folks who don't want the driver can opt out on a one and done basis, which I think is good.īut what about the other (smaller) half of the problem: those of us who use the driver still have to reset our audio devices every build because windows de-defaults the driver. Drink a nice glass of wine and think about how awesome you are. * Remember the setting of the checkbox for all future installations (as you do with other install options). * In the custom/advanced install mode, have a checkbox that you can uncheck to prevent the driver installation. * Do the driver install after the install wizard completes (post-install), not before. I think you need to reverse the order of things: Allowing the WDM driver and MC version to go out of sync could possibly cause all sorts of weirdness. Besides, the "their problem" is really our problem. Quote from: glynor on November 10, 2014, 08:41:02 pm -That's still going to require all kinds of custom builds, which Hendrik already frowned at. More > JRiver Media Center 20 for Windows New WDM driver is setting itself as the default audio device.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |