If I can get this to work out, we can eliminate our existing aging USB audio interface (and wall wart), amplifier, and older speakers.Īfter taking another look at those Klipsch R-15PM powered monitors, there appears to be two ways you can hook them up to a PC.
Asio for generic usb device driver#
We have a pair already, and they are connected via USB to a PC using the Windows 10 USB audio driver (not ASIO), and they sound quite nice for their size. Mcdonalk Can anyone recommend an ASIO USB audio driver? I would like to eliminate my audio interface and use this set of speakers for our DAW activities: These speakers implement, among other interfaces, a USB interface which connects to a PC via a USB interface for transporting audio. tl/dr? it's clearly specific to individual users (mis-configuration) and hardware, so presenting it as a general "no no" is the misinformation being spread /fwiw eta, only in exclusive mode is wasapi in kernal mode, in shared it is in user mode a al a4a nice pic:
have you had trouble with it yourself, or are you just repeating what you've read in the forum? the misinformation being spread is that asio4all is the issue - if it was really that way, how have i used it for years across multiple machines and devices without any trouble? i agree that one should use a manufacturer-supplied asio driver if one can, but sometimes there isn't such an option as the recent ezine stats showed that's the most popular driver used with sonar, so it 's weird that this forum says it doesn't work, don't use it.
Asio for generic usb device drivers#
how does it "interfere" with other drivers? there's no record of such on the asio4all forums, as there certainly would be if this were the case! it has also existed happily with other "real" asio drivers without issue. it's just another easy blame for errors with sonar. Hmm, shouldn t have said "wrapper" maybe "layer", i was under the impression that wasapi also communicates via te same wdm/ks stack but i don't mind being corrected however, "documented here numerous times" is all anecdotal no one has ever shown reproducible steps. The thing is that while WASAPI has been around since the days of VISTA, Cakewalk has in recent times with MS I proved on what it can do. It is a Windows driver model which is far in excess of what asio4all can do. It's been documented here numerous times that if ASIO4ALL is installed but not used, it can interfere with regular ASIO drivers. The entry level units are budget friendly, and should be the highest priority investment after purchasing your computer. The advantages to having proper low latency ASIO drivers, as well as the ability to record with your microphones or guitars using a proper preamp are priceless. I think that the advice to get a real interface is best, especially if you are serious about making music on your computer. Not attempting any recording with this rig either! It seems to run fine with playback using virtual instruments or audio only using the internal Realtek audio chip. I also have a Win 10 laptop with ASIO4ALL installed with no problems, but it is not my main DAW, and I am not attempting to connect an external audio interface. Some examples are Rapture Session, Cakewalk Pro, Rapture, etc. Some Cakewalk standalone instruments also demand ASIO only, and WASAPI is not an option. I have found that WDM works OK in this case. If using Sonar X3, you may not be able to access WASAPI on Windows 10. If you are using Windows 10, and a current release of Sonar, WASAPI is the best choice for those without a hardware audio interface and the vendor supplied ASIO drivers.
0 kommentar(er)
