Re: Asio Sound Driver Download

0 views
Skip to first unread message
Message has been deleted

Avery Blaschko

unread,
Jul 11, 2024, 1:31:51 PM7/11/24
to frigegocul

i already tried to reinstall the driver and virtualdj, and i tried to use different usb ports, but it didnt work. i even tried to deactivate the device in the windows sound options, hoping that would prevent it from using wdm...
then i tried to test the device with the asio test signal generator from this website:

Any idea what this could be? Is maybe the USB3.0 driver of Windows 8.1 the problem? Should I try to replace it with the Intel driver (which is only available for Windows 7, so a little hack will be needed in order to do that)?

Asio Sound Driver Download


Download File https://urloso.com/2yLNgJ



However, instead of installing old drivers, I would rather suggest going into the computer's BIOS first and see if your can disable the xHCI function for the USB ports (might be called USB 3.0 support or some other name, so please consult the user manual). This seems to have help other users and is much easier to change back.

do me a favor. Make sure 64 bit processing is turned off, restart Cubase and try again. Someone else is having problems if they have 64bit enabled. It would be interesting to see if that is this problem.

However, I think it may be defaulting to use only the optical spdif side of the dual use headphone jack as the output and gives no option to change it.
It does not work in either 32bit processing or 64bit processing.

But, I tried with Absynth Standalone after reading the above post and it worked BUT I had to select a sample rate (defaulted to zero). Then, I closed Absynth and opened Cubase. Now it reports the same latency as Absynth did but still no sound (it did show the audio outputs connected and active).

Having the same issue, and Google brought me to this thread. Should I just stick with using the Steinberg Generic Low Latency ASIO driver, or would using something like ASIO4ALL be a better choice? Thanks for any help!

When I click on the channel strip to open Channel Output Configuration Menu it indicates physical outputs Digital Audio (s/pdif). Clicking on that, I get the popup window with no other options other than 'not connected'. My ASIO driver is not showing up, despite the audio settings showing 'running'. This where I'm stuck! Thanks if you can help.

Resolved! For those who have a similar issue, NI service guided me through running a few utilities to resolve a few file corruption issues (that I didn't know existed), and fully update my Windows OS and drivers (which apparently were not current). Then switching to WASAPI(Exclusive mode) rather than ASIO allowed me to get sound with impressively low latency. Thank to NI Service! (That's real, not sarcastic.)

in the output section did you try clicking "Presets/Batch Configuration" and the selecting "Reset Output Section"? If that does not work you may have to configure the outputs manually, by clicking "+" next to outputs, enter the "Quantity" of outputs you want, whether they are stereo ("Number of channels" = 2) or Mono ("Number of channels" = 1), select the first soundcard output from the "Souncard/Host Output" dropdown. and select "Delete Existing Channels" then click OK. once you get sound, you can save it as default for "Standalone" under "Presets/Batch Configuration"

Also, I downloaded and installed a Komplete ASIO driver that I found somewhere on the support pages. It appears on the list on the Cubase Studio Setup screen, but nowhere else is it an option. So that's not it.

I just noticed in Kontakt standalone that under options/audio/ it has the ASIO device as "Generic Low Latency ASIO", whereas it should be ASIO DirectX Full Duplex Driver, as is my default in Cubase, and my system in general. On this dropdown, the DirectX driver is not on the list of choices.

I tried to switch it to the Komplete ASIO driver and got this error message the following error message. This had not happened on previous attempts. Regardless, after closing and restarting Kontact it was selected. But resetting outputs and trying to manually replace existing ones now only gave me options of "output1" and "output2" for the driver/host. Still no sound.

And just an FYI, Kontakt in Standalone you can only assign as many audio outputs as your interface has... so if there are only 2 outs (Like the KA2 which I suspect you might have) that's all you can assign. When Using Kontakt as a VST in a Host (Cubase in your Case), you should be able to create up to 32 stereo channels and those channels will be available to select in Cubase!

I'm using Samplitude Pro x6 on a Windows 11 PC and am having trouble with system set-up. I use Realtek Audio, Driver version 6.0.9285.1, which appears to have an ASIO component. When I try to select Realtek ASIO under Driver System, I get an error message that says "Realtek ASIO loading failed. No ASIO Driver error." However, my Realtek driver is up to date, and the ASIO component has been installed and appears to be activated. Thoughts?

ASIO4ALL didn't do it for me (I still got error messages when I tried to use a plug-in), and in trying to resolve those errors I've apparently fiddled with the Samplitude settings so egregiously that I've disabled all sound. Will be off trying to reverse my changes or maybe just reverting to a system restore point. I appreciate your input, though!

Thanks for the additional information, and sorry ASIO4All didn't help! However, you now mention error messages when I tried to use a plugin. What error message? Is this related to your original question? Within the control panel (Advanced view) of A4All, are the "correct" inputs and outputs selected?

If ASIO4ALL doesn't help you can still test the FL Studio ASIO driver (install the free FL Studio demo to get it) or the Steinberg Generic ASIO driver (install the free WaveLab Demo to get it. You can select in the installer to only install the driver).

The error message said "For software instruments realtime monitoring you have to activate the following options: ASIO driver system; ASIO software monitoring or FX monitoring; input monitoring (REC M)." It was in trying to follow these instructions that I shut all of the sound down. I'm now back to square 1 having restored the default settings. All of my issues relate to a single goal: adding percussion or instrumental effects to existing (fully mastered) .wav files. I'd hoped to do that to further my hobby, which is scoring choregraphed freestyles for horses. I don't create or produce any music; I just do rudimentary editing (e.g., changing tempo or pitch) of existing music tracks, and wanted to expand my tools a bit. Given my lack of music or sound production knowledge, it's been tough trying to Google my way to proficiency!

I need After Effects to release my audio driver when AE is minimized. Yet there is no where in the preference to check the box "Release Audio Driver when in Background". I need to watch youtube while working or have occasional Video Chats. What is strange, I explicitly set Windows 10 not to allow apps to take exclusive control of my audio driver, yet AE does not seem to respect it and overide Windows 10. If there is one thing I really cant stand is when developers do not respect MY SETTINGS. Not sure why it is not possible to set this in AE, when in any other app it is possible. Any ideas?

I'm not sure what you need but After Effects has in its preferences a tab called "Audio Hardware" for the audio settings where you can select an Output, but it remains selected even if you put it in the background. However, if you open a browser to watch YouTube that should not interfere with the output of the system because it is independent.

You might not be familiar with the intricacy of windows audio drivers, but there are different device classes and hence also some differences in how the different audio drivers behave. Most people will be using standard WDM and MME drivers under windows and will therefor most likely not notice any "driver release" issues. The third audio standard for windows sound drivers is ASIO, which is used by professional sound studios and serious DSP apps. This is a mission critical audio driver that by default locks the audio device to a specific app.

In order to to maintain multitasking capability across apps while using an ASIO setup, there needs to be a checkbox in settings under "Audio Hardware" that will read something like "Release audio driver when app is in the background". This will keep the mission critical aspect when the app is in the foreground, but will release the driver to other apps when Windwos recognizes when the app is in the background. This pertains specifically to ASIO device class drivers and hardware.

For some reason, Adobe has failed to add this option in After Effects, which is bad practise for ASIO and any PRO setup. Any sound professional using AE in their studio will most likely run into this same issue, as they will most likely also use ASIO drivers. Hope that further clarifies my questions.

I never face this issue, I always use AE while I listen to music no problem at all, and the good things you can set the audio interface you want to use for AE, example if you comment on a Bluetooth device you can let AE use that device only, really as Mylenium said you should give us more info about your audio hardware

7fc3f7cf58
Reply all
Reply to author
Forward
0 new messages