Selected Driver Not Found 10202 Logica
ImacG5 does't recognize audio output Discussion in. Int says 'Selected Driver not found.(-10202)' even with the headphones plugged doesn't find the audio input. Mar 19, 2007 iMac G5 not picking up internal speakers. Again I could not get sound. I found a bit of info that suggested I should. Selected Driver not found.
I am one of the ever-dwindling few who still run Logic Audio 5.5.1 on Windows (or at least I did on Win 8.1 before I upgraded to Win 10). I know, I know. Please don't ask (but you can probably guess why).
The error I am seeing when I try to play a Logic song (after successfully opening it within Logic) is as follows: 'Timer or midi-output inactive' OK I know this probably has nothing to do with RME products, but I have used an HDSPE AIO card for a long time now and I am really hoping that someone among all you talented and knowledgeable folk out there might be able to give me a clue or point me in the right direction. I have reinstalled Logic but the problem persists. I am an experienced IT professional so it is unlikely that I am doing anything REALLY stupid.
ALL other apps (and I have lots of them) are running fine under Windows 10 after the upgrade from 8.1. One more thing - just opening the song under Logic, then closing it and quitting Logic itself is really really slow (probably for the same reason that causes the reported error). I am reactivating this, because this problem has resurfaced, even with the 4.12 drivers. And reinstalling the drivers does not necessarily solve the problem. I also see that another user has a problem after upgrading to Windows 10, so I am not alone. Please remove Logic Audio from the picture, there are other underlying issues at play here.
From time to time, e.g after the recent Windows 10 upgrade to build 10586, something is corrupting the Audio Devices and/or the audio device configuration. It also happened after a BIOS update, and SOMETIMES even after just a cold boot!
Therefore I am a bit suspicious of some Intel software component somewhere, but I cannot point the finger at anything specific yet. Can anyone experiencing any Window 10 issues please contribute any further evidence? I can confirm that setting WDM device count to 0 always fixes the issue (does this point the finger at the Microsoft audio drivers?) (Reinstalling the RME drivers occasionally fixes the issue, most of the time it does not). Setting the WDM device count to 1 does NOT fix the issue (whether 1,2 or 3 it does not matter).
If I keep the value at 1,2 or 3 the problem eventually occurs. Setting back to 0 then fixes things. However, as I said above, this is not acceptable because I use other software (at least two products) that require WDM devices in order to function.
Note also that I DO use the 'AIO MIDI' devices. Please advise! I had never seen this issue until Windows 10. Thank you for the suggestions Matthias, but none makes any difference. Things do seem to be workable and acceptable for me for the moment though if I just configure ONE WDM device, viz 'Analog 1+2' stereo Just one more observation however - I am not at all convinced that it is just Logic Audio misbehaving.
I'm sure you remember some time ago that the published 'sample rate' in the DSP settings was misbehaving (a number of people had observed this in various posts). It would sometimes show the correct sample rate, sometimes incorrect, and sometimes would be 'grayed out'. Well I do recall that this was eventually fixed in a certain release of your drivers (cannot remember which one exactly).
Garageband Selected Driver Not Found (-10202)
Now for the bad news - those sample rate issues seem to have returned, it seems to show the incorrect sample rate quite often when opening files of various sample rates (that is in general - not just within Logic Audio, which makes me think that I cannot yet blame only Logic Audio for all of these issues I am seeing). In fact I now have to manually change the sample rate quite often in order to get certain applications to work. Is this expected behaviour? Sorry to throw in so many things at once, I am not trying to muddy the waters, but taken together this is all indicating to me that something is not quite right under Windows 10.
Sorry, I am trying to post screenshots of my DSP settings but I can't manage it. How can I attach a jpeg or paste a 'print screen'?
Can someone help me out here? I'll give you 2 examples of failing apps (there are others also). And this is all with single-streaming, I am not trying to run any two apps simultaneously. The best example is 'Cool Edit Pro'. When sample rate is showing as 96000 Hz under DSP settings (e.g. After a Logic Audio session with 96K sample rate), Cool Edit does not even let me play a 44k wav file - the 'play' button is grayed out. As soon as I set the sample rate manually to 44100 under DSP settings, everything is fine.
Another example is the 'AVerMediaCenter' TV application which gives me free-to-air TV output via a PCIe TV card. I get NO sound when the sample rate is showing as 96000 Hz but when I manually change to 44100 then I get sound.
I NEVER had this issue with any of these apps prior to Windows 10. Further Info: Please note I am running the latest Windows 10 cumulative update, OS Build 10586.11 And surprise, the Microsoft audio drivers have been updated (Date 29/10/15, Driver version 10.0.10586.0).
OK, OK I will shut up soon and give someone else a chance. But I have discovered one more interesting thing. I look at Control panel / Sound / Manage Audio Devices and see the following. When DSP settings are showing 96000 Hz THE PLAYBACK DEVICE RME Analog (1+2) DISAPPEARS (so no surprise that Cool Edit etc cannot play a 44100 file. there are no devices available!) As soon as I change the 44100 to 96000 manually within DSP settings, this playback device re-appears and all is well. I'll stop there.
Well I did stop my previous entry. But now after further testing, I have to make one more entry in this thread to clear up issues raised above (please humour me). The following is the only scenario that 'works' for me. Apart from one minor issue. Under DSP settings, select two WDM devices 1. 'Analog 1+2' and 2. 'Phones' Under SPEAKERS tab, select only 'Phones' Now under Windows Control Panel Sound/Manage Audio Devices, there should be TWO playback devices, 'Speakers' and 'Analog 1+2'.
Make sure the DEFAULT DEVICE is 'Analog 1+2' and the Default COMMS DEVICE is 'Speakers'. The sole 'Recording Device' should be 'Analog 1+2' The sample rates and bit depths are determined by the DSP settings. Logic Audio now works perfectly using a 96K sampling rate, and the DSP Sample Rate of 96K is grayed out (as it should be I think). Close down Logic Audio, the displayed sample rate is still showing 96K (but now ungrayed of course). Now open an application and play a 44k file/CD/TV broadcast or whatever. This works (in my previous post, the failure scenario was using one WDM device only, not two) My only further observation, of minor importance, is that the displayed DSP sample rate is still 96k at this stage. I am fairly sure that changes have been made to Windows 10 audio in the recent major upgrade (a quick search of the web seems to confirm this, as other audio-related issues have been reported).
Sorry, but I have to keep this issue going - there is still a problem, arisen after the latest updates to Windows 10 (OS Build is now 10586.29). No matter what I try by reinstalling RME driver, changing number of WDM devices, etc I am seeing the following error when starting Logic Audio: ASIO: Selected ASIO Driver 'ASIO Hammerfall DSP' not found (-10202) If anyone doubts that there have been substantial audio-related changes under Windows 10, just do a search on 'windows 10 audio' or 'windows 10 asio' and you will see what I mean. And this OS installation of Windows 10 is a fresh one, not an upgrade in case you are wondering. Question for MC please - is it possible to set NO device defaults under 'manage audio devices'? There seems that there must be a default device (by definition) under each of the 'playback' and 'recording' tabs.
Thanks Daniel for that suggestion. Yes Reaper seems to work fine with ASIO driver. I guess I have some thinking to do now, either dual-boot under Win 8.1 or abandon my much-loved Logic Audio. One thing that will make my decision more difficult though - I just tested Logic again under 'Windows XP Compatibility' option, and to my great surprise it worked!
It never did previously, when I tried that as suggested by MC. I guess one thing has been established - Logic under Win 10 is going to be erratic. I realise that I must be the last remaining person on the planet using Logic Audio 5.5.1 under Windows 10, but I just applied the 'Windows 10 Anniversary' upgrade (a very large patch, took over two hours to download and apply) and something very interesting has happened.
I had given up hope of the normal execution of Logic working properly (with a non-zero number of WDM devices specified), so I was getting used to the workaround that I described previously in this thread, but after this upgrade THINGS ARE WORKING NORMALLY AGAIN - I can leave the number of WDM devices to be 1 or more, and Logic behaves normally! I guess M$soft realised that there was an issue with the audio engine, and fixed it - or did this fix occur accidentally? I guess we'll never know.
But for now I am happy again.
Hi, I want to install Windows 98 on my modern Asus Z97-A PC, on a separate/spare hard drive for testing purposes (while leaving the windows 7 ssd drive disconnected). While using the spare hard drive, I set my BIOS to use 'IDE Mode', and 'Other OS' under secure boot settings. This has allowed Windows XP to install successfully, however not with Windows 98. So I've inserted my Windows 98 SE disk, booted to disk, then I run into the infamous 'OEMCD001' problem lots of other people seem to be having, 'Device driver not found: 'OEMCD001'.
No valid CDROM device drivers selected The Windows 98 Setup files were not found.' How can I get past this error?
'Device driver not found: 'OEMCD001'. No valid CDROM device drivers selected The Windows 98 Setup files were not found.' How can I get past this error? Windows 98 needed a boot disc which also included 4 files. The autoexec.bat file, the config.sys file, mscdex.exe file and oakcdrom.sys file. The driver was the oakcdrom.sys file.
Both the autoexec.bat and the config.sys were clear text files that needed information placed into them concerning how to use the mscdex.exe and the oakcdrom.sys files. You can goggle that information, should still be a lot of info on it across the web.