• SONAR
  • Driver issues since the newest Cakewalk Bandlab update. (p.2)
2018/08/05 22:12:25
igiwigi
Hi Scook
There could be a maybe there.
 
I noticed in the reg edit there is a low latency driver and It has about six chinese type symbols.
Is this from cubase?? or  a rogue driver from an update.
I will get rid of it anyway..
Does Cubase have a factory supplied generic driver ???
I am not worried as i only use ASIO
 
My Machine is virus free as I have gone through all checks.
 
before I start deleting I would like you to come back on this as I am nervous about delving Into dark corners!!.
 
 
All the best
john
2018/08/05 22:17:51
scook
Cubase installs a generic low latency ASIO driver. I have read posts in the past about problems with it. By factory driver I mean the driver from manufacturer of the interface. I can offer you no specific guidance on Cubase. Their support should be able to address how best to remove the generic low latency driver. If you can ID the dll, renaming it may be sufficient.
2018/08/05 22:25:40
igiwigi
Hi Scook
 
I cannot understand how a cubase low generic driver could interfere with Bandlab as I  only use Focusrite asio and I do not use the generic drivers,so they are not operational.
I have all the right boxes ticked in Bandlab and I had not touched Platinum and the same happens to that.
Everything was ok until these recent updates
 
 
all the best
john
2018/08/05 22:31:20
scook
CbB may be configured to use Focusrite but the program still goes through a discovery process in order to make all the drivers available in preferences.
2018/08/05 22:40:51
gustabo
igiwigi
I cannot understand how a cubase low generic driver could interfere with Bandlab as I  only use Focusrite asio and I do not use the generic drivers,so they are not operational.

The same reason why just having ASIO4ALL installed and not being used has caused issues for people.
2018/08/05 22:42:27
igiwigi
Hi Scook
 
Well, you are right about that Cubase driver .
I cut the folder out and stuck It on my D drive  as there were no uninstallers for It.They are dlls.
 
Problem solved.
I would like to give you massive thanks for that and Brad must also Know if he tunes In.
This only happenned though after the latest bandlab updates.
Anyway, Big Thanks for your help
 
 
all the best
John
2018/08/05 22:47:01
scook
Your experience may be recent but problems with the "Generic Low Latency" driver go back for years.
2018/08/06 00:13:49
Noel Borthwick [Cakewalk]
Thanks Scook - your troubleshooting skills are top notch. Kudos.
Please mark this post as solved. 
2018/08/06 00:27:32
scook
I would but cannot tell if the OP has the same problem as the user in msg #7. It was the partial error message "using low latency driver" and the user mentioning Cubase that lead to the solution for John's post.
 
Should Brad ever revisit this thread maybe he will provide some more information about his setup. It could be a driver conflict, bad driver mode or wonky driver install. It may already be resolved too. The OP never returned.
 
Edit: the problem seems different because CbB was not finding what it needed but Platinum was. In this case, I suspect a misconfigured CbB but the OP needs to return. Also prefer users avoid terms like "newest update" and instead provide version numbers. This makes it easier to reply and helps when someone bumps an old thread.
2018/08/06 01:07:57
abacab
I have seen the error message the OP referred to before.  It usually means that the ASIO driver was not released by the last audio application that had used it.  For example, say that I had closed another audio program that accesses ASIO, or it had crashed, and the task had not yet released the driver.  Or if you already have a program open that is using ASIO.  It is not multi-client, so only one program at a time can use ASIO.
 
In many cases, resetting the audio interface, or rebooting the computer should clear the error.
© 2025 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account