Vst Audio System No Driver
Emelia Lute
Update. The problem still exists. Ive restarted and fiddled with setting for 3 hours today with no joy. I think it is a project issue, perhaps my project being too big for my computer capacity. I only have 16gb ram.
If i open an empty project, and start working it will play fine from any audio driver (internal macbook or either of my two soundcards). If i open a big project with 50 channels lots of plugins it had this problem. Cannot load audio driver. Yet cubase sees the soundcard, any other app can play from the soundcard, just not cubase.
Last night the project worked. Today it wont.
Has anyone got any ideas?
EDIT: I sometimes have to freeze the channels when the audio driver is not loaded, save the project and then restart at which point it manages to load the audio driver. i.e., it requires a restart of cubase to work.
No its not a crash thing i dont think, the only correlation i have found is project size.
This only ever happens with big projects (the kind where i must increase buffer size to max to ensure no audio glitches). It may be because these big projects all also use a certain plugin or synth and that is the true problem (ie its a coincidence), but i dont think so because i have smaller projects which use my full range of vsts and synths too and i have yet to experience this issue.
Sometimes disbling program settings fixes it when i restart cubase. But not always. Yesterday it was working fine all day, then i went on chrome, did some other stuff and when i reopened cubase the problem returned. I tried restarting in all imaginable ways and nothing worked so after an hour i gave up!
Open up device manager and make sure your device is there and working. Then start Cubase. Before opening a project, look at the audio devices and make your native ASIO driver the one that is selected.
i have same problem with my steinberg AXR4T, i have installed everything but when i want to switch driver to Yamaha Steinberg Thunderbolt it says Device could not be opened. ? plz can anyone help me ?
06/01/2020. I got the same trouble this morning, but I easely resolved the issue by updating the eLicenser through the EL control center, and then restarting Cubase, after reboot. Hope this method could work for you too!
Update for anybody still struggling: this was my problem as well. Others may be encountering that same problem but with a different root cause but this worked for me so just make sure the CC switch is set to the off setting!
Sometimes, when I start my machine, the volume control is set to 100, but it plays relatively quiet. I can fix it by rebooting my machine. Is there a way to restart audio devices, without rebooting the computer?
Check your device manager and go to audio in and outputs. Now check the box show hidden devices (in view) and delete all the devices other than the ones that you have when you didn't show the hidden devices. Reboot.
Thanks for the answer, it helped me too. Something stuck in my sound card buffer and kept looping.I was not able to disable my card in Device Manager, (it wanted to restart Windows 7).But stopping the service helped, (though only that did not solve my problem alone).
I came looking for a way to restart my Creative X-Fi Titanium driver w/out restarting. Sometimes when I change the Mode, I'll get a buzz out of the right channel that may force me to restart Win7 several times to get rid of.
This fix didn't work for me but as I was unable to Disable the X-Fi in the Device Mgr., which stated it would require a restart when I tried. I'd tried to kill all related software, but maybe there was something I missed, being the massive driver that it is.
I'm in a need to develop an audio device driver for System Audio Capture(based on Soundflower).
But soon a problem appeared that it seems IOAudioFamily stack is being deprecated in OSX 10.10 and later.
Looking through the IOAudioDevice and IOAudioEngine header files it seems that apple recommends now using the API which runs in user-space. But I can't find lots of information on this user-space device drivers topic. It seems that the only resource is the Apple provided sample devices from
Looking through the examples I find that its a lot harder and more work to develop a user-space driver instead of I/O Kit kernel based.
So the question arises what should motivate to develop a device driver in user-space instead of kernel space?
The "SimpleAudioDriver" example is somewhat misnamed. It demonstrates pretty much every feature of the API. This is handy as a reference if you actually need to use those features. It's also structured in a way that's maybe a little more complicated than necessary.
For a virtual device, the NullAudioDriver is probably a much better base, and much, much easier to understand (single source file, if I remember correctly). SimpleAudioDriver is more useful for dealing with issues such as hotplugging, multiple instances of identical devices, etc.
IOAudioEngine is deprecated as you say, and has been since OS X 10.10. Expect it to go away eventually, so if you build your driver with it, you'll probably need to rewrite it sooner than if you create a Core Audio Server Plugin based one.
Testing and debugging audio drivers is awkward either way (due to being so time sensitive), but I'd say userspace ones are slightly less frustrating to deal with. You'll still want to test on a different machine than your development Mac, because if coreaudiod crashes or hangs, apps usually start locking up too, so being able to just ssh in, delete your plugin and kill coreaudiod is handy. Certainly quicker turnaround than having to reboot.
Regarding system audio capture, macOS 13 adds native support for this in the (possibly confusingly named) ScreenCaptureKit. As well as streaming the display contents (or individual windows), this can stream/record system audio, so no custom driver should be needed.
That being said, is there any kind of TaskTray icon you can see that is associated with your Audio System (configuration)? If so, is there a way you can disable or uninstall it for the time being to see if the hangs in Rhino go away?
The Nahimic is something that seems to be connected to the realtek driver on my motherboard. I found the device called NH3 on my computer device manager and uninstalled it. Tried to open rhino again after restarting my system.
OK, one thing you can try is to make a new user and see if things handles differently there. I had some issues with my windows10 a few years ago and before I did a full reinstall I checked and got confirmed that a new user did not have the issues I had. (So it might be worth as a shot in the dark, to check at least, while you wait for a fix )
Good luck!
Now I have not tried my system fully after this, I want to see if my audio still works and all the units that are connected with the nvidia card. I also have not tried the application fully, but so far there are no issues. ( I have tried with different views and modes, rendered, shaded, raytraced and wireframe all work.
I found my way here because i was troubleshooting a similar issue where Katana (all versions after the hydra viewport was introduced) would lock up when moving the Hydra viewer over to a second monitor.
Click Have Disk and then Browse. Browse to the folder that contains the driver you just downloaded. These files include all the information necessary for updating drivers.
Go to Audio, Video and Game Controller and look for the name of your sound card. It might include one of the popular sound, video, or game controllers visible in the screenshot below, or it may have another name entirely.
Avast Driver Updater scans your computer top to bottom, easily finds new or updated drivers for you, and keeps them updated automatically. It checks the compatibility of over 60 million drivers from more than 1,300 of the most well-known brands to make sure that your drivers get updated quickly and stay updated reliably.
But keep in mind that downloading drivers from third-party sites is risky and can expose you to malware and other threats. Only use sites you know and trust, or stick to the methods outlined above.
Periodically updating audio drivers can help avoid performance issues and introduce new product features. New audio driver packages may fix bugs that cause sound issues, while helping to enhance your sound devices. Generally, updating all your PC drivers will ensure your computer and accessories are functioning at their best.
If you are missing audio drivers on Windows 10 you have two options: you can run a Windows Update to automatically find new or missing audio drivers. Or you can use the Device Manager feature to search for missing audio drivers.
Thank you, but GoClever send me other drivers. Now I have other problem. I connect headphones to 3,5 mm sound jack. Work speakers on tablet. After I disconnect 3,5 mm jack from tablet and tablet speakers are "off". How to invert? Speakers are default device. Uninstall driver and again install still wont work.
I have drivers by GoClever Support (still wont exist Windows 10 TH2 (v1511 10586) new Audio driver for GoClever Insignia 800 Win by Intel) and working Audio driver is for tablet GoClever Insignia 1010 Bussines because other Intel driver wont work for me on Windows 10 TH2. I try upgrade from Win 10 10240 to TH2 v1511 10586 and now clean install Windows 10 TH2 (v1511 10586) from USB on tablet. After I install drivers + Windows Updates. Audio driver work only with headphones in 3.5 mm jack. Headphones wont work, work only tablet speakers. I this problem also report on support for Windows Insiders and Microsoft Support. Microsoft recommend contact Intel support.
Yes, I contacted GoClever. I wrote up that I have driver from GoClever Support, but they give me only driver for GoClever Insignia 1010 Bussines because someone else does not want work on GoClever Insignia 800 Win with Windows 10 v.1511 10586, but this audio driver have problem with 3.5 mm jack yet. If are headphones connected to 3.5 mm jack (wont work headphones), tablet speaker works. If I disconnect 3.5 mm jack, tablet speakers are off.