1 Correct answer
For me the following simple trick solved this problem:
Go to setting/privacy settings/microphone
look at the setting that allows apps to access the microphone, if disabled set to "on"
(Disabling this setting apparently makes all audio inputs invisible to apps)
I got the idea from this discussion: www.reddit.com/r/pcmasterrace/comments/8k3vb4/psa_the_latest_windows_10_update_1803_has_caused/
11
Replies
davidf97879629 wrote
Forgive me if I'm overly harsh. I mean no disrespect to the forum, but Adobe really should be doing better on this. Maybe they could even train their helpdesk on using the software...
In general, using the software isn't an issue; fault-finding is, though, and that's not a thing you can effectively teach quickly (or sometimes even at all). On top of that, the helpdesk would have to be capable of doing this with every product, and there simply isn't the time available for that. I'm not trying to defend the helpdesk here, merely pointing out that their policy is perhaps somewhat inevitable. What they are actually there for is to sort out subscription problems - I'm not even sure if they cover installation issues any more, although they used to. To staff the helpdesk at the level you would like to see would add a significant amount of cost to the software, I'm sure.
I have already tried changing to WASAPI, which gave me no better result. I have no clue what the difference is. Shouldn't Adobe provide some kind of internal help that explains these technical issues so that we know what the different options are supposed to mean? Or do we just expect every end software user to be an audio technician?
WASAPI is Microsoft's latest version of a sound driver - it stands for Windows Audio Session Application Programming Interface, and is much more likely to work correctly with a modern operating system. I don't think that everybody needs necessarily to be an audio technician, although having a grasp of at least the basics of a system you expect to be able to use doesn't sound that unreasonable to me...
On your advice, I've downloaded the driver you mentioned. Of course, that's still problematic. I don't know what it's supposed to do, and I'm not really comfortable downloading free software from unknown publishers and allowing it to make changes to my computer, particularly not just because a person in an online forum told me to. Like I say, if I pay money for software - and particularly if I pay a subscription for it - I don't think it's unreasonable that it should work flawlessly out-of-the-box with the newest iteration of the world's most popular operating system without depending on me to download third-party software and troubleshoot technical problems.
In the real world, the people - particularly at Microsoft, but also Apple - who are 'responsible' for rolling out operating systems don't operate on the basis of keeping all software operating flawlessly all of the time; in fact that's the least of their worries. Neither do they operate any form of a sub-sequential loss policy, which means that effectively they don't even need to care about it - so they don't. And they can make changes to their OS's at any time they like, without even bothering to warn other parties. And they do. So I'm afraid that your expectations here are somewhat unrealistic. Even more so when you consider that many people use Audition with external sound devices, and they have their own driver issues from third-party suppliers to contend with as well - and that may well be an issue you have.
As for ASIO4ALL - if you were that worried about it, why did you download it without asking for more information first?
Never mind, I'll tell you anyway. Firstly, it doesn't make any changes to your computer, as such, at all. Secondly, we've been using it for many years now as a diagnostic interface, and there's nothing better available, certainly at the price. Audition's audio 'engine' is fundamentally an ASIO-based one, and ideally is best used with a manufacturer's ASIO driver, but they are generally not available for built-in sound devices. What ASIO4ALL does is to provide an interface between Audition's engine and the sound device driver Windows provides. Most importantly though, it diagnoses the state of the device, and tells you whether you have significant issues with it. Internally, Audition has something very similar to ASIO4ALL to operate with Windows drivers, but it's not visible and has no diagnostics as such. ASIO4ALL is simply replacing that with something you can see!
As a result of Microsoft's upgrade though, you may need to download from HP a revised sound driver; I have read some comments on the HP forums about people having similar problems to yours, and checking and updating that driver would be one of the first things to check. But initially, try selecting ASIO4ALL in the device class, click on the 'settings' button and have a look at the display - click on the spanner in the lower RH corner, and you should get a display like this:
If it looks exactly like the picture above (this is from my HP laptop, incidentally) then the interface is working fine, and we'd have to look at the sound settings elsewhere in the machine.
AdChoices