![]() ![]() Cubase support may help you remove these drivers as well (check to see if they exist anyway). ![]() Previously I could actually see a progress bar window flash during the loading process that said 'Generic Low latency ASIO driver' so thats how i knew it was the culprit. Of course be careful with the Windows registry, back up. HKEYLOCALMACHINESoftwareASIO HKEYLOCALMACHINE SoftwareWow6432NodeASIO now the apps in question load much faster, like they should with an SSD. Still I've never seen it on other systems so I understand your disbelief. Previously I could actually see a progress bar window flash during the loading process that said "Generic Low latency ASIO driver" so that's how i knew it was the culprit. Now the apps in question load much faster, like they should with an SSD. HKEY_LOCAL_MACHINE \Software\Wow6432Node\ASIO I removed the steinberg asio driver entries from If you are unable to remove the cubase "Generic Low Latency ASIO Driver" from add/remove programs or disable them you need to delete the settings out of the registry (backup first).Ĭheck the post by "hibrasil" here talking about the registry for full details. This shows somebody with a similar issue. Here the Generic Low Latency ASIO Driver is. Cubase won't necessarily use these drivers they just hang around in memory being useless and screwing up other ASIO applications, much like ASIO4 ALL. The key pieces of information are outlined here - the Input and Output latency being the most important ones. I've explained the reasons anyway why this often screws up ASIO apps.Īs I stated lots of reports of conflicts with Cubases virtual drivers and ASIO drivers. Just try it I suggest, if it doesn't work then you can simply reenable, nothing will change. Your audio interface should work totally fine in Maschine afterwards if this is the problem. Maschine is not using Windows to get the sound. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |