Jump to content

feature request: asio4all support


Recommended Posts

make cbb/sonar work with asio4all

it would mean all the new users (bl members) could just get on with their onboard realtek and enjoy the software, sonar a great daw, like they do with next and every other daw, without having to spend money on a "pro" audio interface

of course it means some code refactoring but everyone wins in the end surely?

and don't just say wasapi (that's a japanese sauce :P)

and if not, why not?

  • Like 1
Link to comment
Share on other sites

Do you know what ASIO4ALL is? Read about it here.

There are reasons why Cakewalk don't recommend it. Basically because there is no way to limit Sonar's use of the ASIO4ALL to only the small subset of use cases where ASIO4ALL is a reasonable choice. Sonar simply expects more from an AISO device.

Like folks say, if your Audio interface doesn't have a proprietary/native ASIO driver, you will be BETTER OFF using WDM, which Sonar ALSO SUPPORTS.

  • Like 3
Link to comment
Share on other sites

1 hour ago, Colin Nicholls said:

Do you know what ASIO4ALL is? Read about it here.

There are reasons why Cakewalk don't recommend it. Basically because there is no way to limit Sonar's use of the ASIO4ALL to only the small subset of use cases where ASIO4ALL is a reasonable choice. Sonar simply expects more from an AISO device.

Like folks say, if your Audio interface doesn't have a proprietary/native ASIO driver, you will be BETTER OFF using WDM, which Sonar ALSO SUPPORTS.

haha, yes of course i know what asio4all is, but hey other daws like say ableton live, explicitly do recommend it, cakewalk/sonar is the only daw that has issues, i guess because it's incompatible with their driver inplemetation, which has always been windows-only, and every other daw has a cross-platform driver implementation (being cross-platform daws)

cakewalk/sonar is now bundled with a social media account aimed at non-pros, so to make it work "out of the box" for teens who don't know what a "driver" would only benefit everybody

so don't take a suggestion as a criticism

fwiw, i've used this daw (and others) since the late 90s

it's perfectly possible to make chart/successful music without a nice audio interface 🤷‍♀️

Link to comment
Share on other sites

@pwalpwal can I ask why you want Cakewalk to support what was;

1. A 1990's workaround for audio interfaces that did not have a native ASIO driver?

2. A Windows XP WMD/KS driver in a wrapper to disguise itself?

3. A driver that fails Steinberg's own basic ASIO driver test?

Not sure why in 2025 you want to go back to a 30 plus year old technology.

Why not ask Microsoft to design a native Audio API, like the MAC Audio Units that is as efficient or more efficient than ASIO or AU? That would be a much more interesting demand.

  • Like 5
  • Great Idea 1
Link to comment
Share on other sites

because:

1. we've asked for it for ages

2. it makes sense for new users who don;t know what a driver is (bl subs)

3. why is everyone so upset about any suggestions about change

4. if the world was run by "yes men" we'd end up... oh.. errrr

Link to comment
Share on other sites

1 hour ago, Wookiee said:

A driver that fails Steinberg's own basic ASIO driver test?

I think you're thinking of the Realtek one; ASIO4All passes afaik.

Link to comment
Share on other sites

8 hours ago, Colin Nicholls said:

Do you know what ASIO4ALL is? Read about it here.

There are reasons why Cakewalk don't recommend it. Basically because there is no way to limit Sonar's use of the ASIO4ALL to only the small subset of use cases where ASIO4ALL is a reasonable choice. Sonar simply expects more from an AISO device.

Like folks say, if your Audio interface doesn't have a proprietary/native ASIO driver, you will be BETTER OFF using WDM, which Sonar ALSO SUPPORTS.

What isnt being realised here is: Yes, it is just a wrapper, but it offers more virtual inputs than the standard driver does.

There are times when im in a different city collaborating, when all we use is a laptop, Ableton or PT (yes, even protools allows it) with tons of USB midi gears like USB Mics, USB Keystations, USB Drum kits or a Midi Guitar using Asio4All.

MAudio has had its "Airhub out for quite sometime now. Arturia just began intergrated such ports in their Minifuse product. Nonetheless - Asio4All do offer more flexibility than the built-in WDM and WASAPI drivers of windows thats why it is still being used. Most low bidget Behringer devices use Asio4All for this very reason.

I do use it at times. When im on the plane with my laptop - for sure I use. It offers a higher buffer size too. Never had an issue with it AS IN NEVER. So, not sure why its seen as an issue with Cakewalk. 

Edited by Will.
Link to comment
Share on other sites

5 hours ago, Wookiee said:

1. A 1990's workaround for audio interfaces that did not have a native ASIO driver?

Exactly! It was a band aid solution in the day's when a Sound Blaster was one of the few audio cards sold in local stores. 

It has served it's purpose up until Windows updated the audio drivers to the new WASAPI modes. This has made asio4all totally obsolete. 

The argument that new users need it is totally unfounded. Why? 

Just last week or so I installed Sonar on a W10 Laptop. Sonar worked right out of the box and checking in preferences it was using WASAPI shared mode. So why would a new user need a 3rd party lower quality audio driver? Sonar/ Cakewalk are tested with WASAPI 100%. And if there's no ASIO driver installed it knows what to do. 

It seems the only time people end up using  asio4all is because some Chinese manufacture's of crap interfaces sometimes recommend it. They should have tried WASAPI first!     If a Audio device doesn't support WASAPI it's a  total POS. Toss it out. 

But that said it is true that Cakewalk/Sonar is possibly the only Daw that barfs on Generic ASIO drivers.Last Summer I had installed Cubase  demo so of course that gets you the dreaded Steinberg Generic ASIO driver. At the time I was avoiding Sonar as I tested a bunch of other DAW's. A month probably went by using a few other Daw's without issue, They all used my Motu interface. Actually only Cubase asked if I wanted to use it's driver which I ignored and didn't register what this meant.  I was totally unaware the Generic driver was installed until the day I opened Sonar and noticed it had taken over!  Go figure. 

  • Like 3
Link to comment
Share on other sites

Quote

A 1990's workaround for audio interfaces that did not have a native ASIO driver?

Quote

What started as a bedroom project in early 2003 – for the sole purpose to get ASIO support for the AC97 on my laptop – has become ASIO4ALL

Copyright © Michael Tippach

So is ASIO4ALL from the 1990s? or from 2000s?  Sorry, I am so old I can't remember dates; it just seems like it was around forever.  Maybe I have some old hard drives from when I used to have Sound Blaster Cards?  Maybe they will still work in some old PC I have collecting dust?

 

Link to comment
Share on other sites

14 hours ago, pwalpwal said:

because:

1. we've asked for it for ages

2. it makes sense for new users who don;t know what a driver is (bl subs)

3. why is everyone so upset about any suggestions about change

4. if the world was run by "yes men" we'd end up... oh.. errrr

  1. Who's "we"? I've never seen anyone specifically asking for ASIO4ALL support
  2. New users have a responsibility to themselves for at least researching the topic - I did and have never had a driver problem
  3. Because you're advocating a return to 30 year old technology which never worked properly. And besides, "upset" is a bit of a stretch, more concerned
  4. ?????????????????????
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...