Synchronization and cache problem

[Leander]

Hey!

When looking through the different settings, I saw that Cakewalk uses Asio4all here and not my audio device. I wanted to set it to Motu asio (my device), but it always resets to Asio4all. Why?

This setting is about recording latency compensation.
 

Edited Friday at 11:29 PM by Leander

[OutrageProductions]

Delete Asio4All from your system... it only causes problems. It's not real ASIO, but a wrapper for the Windows WDM driver.

This subject has been covered a thousand times in this forum.

[Jonathan Sasor]

1 hour ago, Leander said:

Hey!

When looking through the different settings, I saw that Cakewalk uses Asio4all here and not my audio device. I wanted to set it to Motu asio (my device), but it always resets to Asio4all. Why?

This setting is about recording latency compensation.
 

That's not showing the device you're actually using currently, its just a list. Go up to the devices tab of the Preferences and make sure the correct one is selected there.

[Amberwolf]

3 hours ago, Jonathan Sasor said:

That's not showing the device you're actually using currently, its just a list. Go up to the devices tab of the Preferences and make sure the correct one is selected there.

Perrhaps a good UI change to prevent confusion would be to force the currently selected driver (or the first if there is more than one?) to be what shows in that dropdown when it isnt' being dropped down. 

[Leander]

Thanks!

[pedwal wally wally wha]

15 hours ago, OutrageProductions said:

it only causes problems...

...in cakewalk/sonar/cbb... i'm getting 64 samples @ ~30% cpu in the live11 demo song, and the so5 demo song, on a standard onboard audio chipset... the a4a dev has also previously posted that cakewalk/sonar/cbb polls an unusually high number of times when parsing the drivers installed on a win box (iirc, something like 8 or 9 compared to 1 or 2 from all others)

so, it's not asio4all making itself incompatible, it's the way cakewalk/sonar/cbb implements asio, different than everyone else 🤷‍♂️

/goodluck

[Wookiee]

@Leander, Cakewalk uses the first Audio device that Windows initialises. It appears Windows does this in alphabetically, which is irritating. Don't blame Cakewalk it just uses what Windows gives it.

Unless you have a really good reason, and does have to really good one, ASIO4all should not be installed on a DAW.

[pedwal wally wally wha]

26 minutes ago, Wookiee said:

ASIO4all should not be installed on a DAW

it's very useful for traveling with a laptop, for example, without having a "proper" external audio device handy

/ymmv

[Leander]

Thanks! I uninstalled it. I did not install it on purpose...it was automatically installed with some VSTi or whatever (without asking me).

[John Vere]

23 hours ago, pedwal wally wally wha said:

it's very useful for traveling with a laptop, for example, without having a "proper" external audio device handy

/ymmv

You don’t need it anymore. Windows audio works better with out bloatware Ike asio4all . It’s a holdover from W7 days and obsolete on modern machines. 
It does seem to only be Cakewalk/Sonar that have issues with generic drivers. 

[pedwal wally wally wha]

2 minutes ago, John Vere said:

You don’t need it anymore. Windows audio works better with out bloatware Ike asio4all . It’s a holdover from W7 days and obsolete on modern machines. 
It does seem to only be Cakewalk/Sonar that have issues with generic drivers. 

It's not bloatware in the slightest, and every other daw supports it, but not Windows specific stuff like wasabi wyfic