Kemper ASIO Driver won't load 😔

    • New
    The Profiler Model referred to in this thread is ...
    ☑️ Profiler Stage

    Profiler and Rig Manager are both upgraded to the latest beta (today) and the two Asio options are available in Rig Manager, BUT ... when I start Cubase, I'm offered to switch asio driver to the new KEMPER PROFILER ASIO, but if I accept, I get the message "The audio driver could not be loaded. Please make sure your audio hardware is connected correctly to your computer."

    I've tried uninstalling and reinstalling everything from scratch 3 times, but no difference.

    The cables have been connected to the computer for 9 months, while reluctantly using ASIO4ALL (which sucks btw!) but nonetheless, it "worked" ... Am I doing something wrong, or is anyone else having this issue??

    Would really appreciate if anyone could advise with this, cheers


    PS. OS is Windows 11, fully updated.

    • New

    Crazy idea but did you reboot the computer?

    • New

    Hi Mickg65,

    Was struggling with the same issue and found a solution:


    In Rig Manager options bar PROFILER->Audio Mode, I switched from USB Audio to Native Audio and it allowed me to switch in Cubase to KEMPER PROFILER ASIO driver. Now USB reamping finally works like a charm, had many problems with it on ASIO4ALL.

    • New
    Quote from Miszny

    Hi Mickg65,

    Was struggling with the same issue and found a solution:


    In Rig Manager options bar PROFILER->Audio Mode, I switched from USB Audio to Native Audio and it allowed me to switch in Cubase to KEMPER PROFILER ASIO driver. Now USB reamping finally works like a charm, had many problems with it on ASIO4ALL.

    Hi ... thank you, but for me, it doesn't work on either setting 😔 ... I already tried it yesterday, but after your post I just tried it again several times and I always get the same message...

    On the upside, at least your reply says it's not just me!! ... The fact there were so few replies and nobody else seemed to have this problem, I was starting to think I was alone in this!!!

    Thank you. 🙂

    • New
    Quote from Miszny

    Hi Mickg65,

    Was struggling with the same issue and found a solution:


    In Rig Manager options bar PROFILER->Audio Mode, I switched from USB Audio to Native Audio and it allowed me to switch in Cubase to KEMPER PROFILER ASIO driver. Now USB reamping finally works like a charm, had many problems with it on ASIO4ALL.

    I had to do the same thing. However, I also found myself being impatient and opening Reaper before the Kemper was 'ready.' By 'ready' I mean that when I selected the Native Audio option, I opened Reaper before the Kemper options for editing showed up at the bottom of Rig Manager.

    I initially had Reaper setup for 48000 and to request this setting from the Audio Device, I use a Lynx Aurora. I forgor to untick that option and when I selected the Kemper from the ASIO dropdown, my PC hanged (hung?). I had to hit the power button to shutdown.

    Brian

    • New
    Quote from TheSystem

    I had to do the same thing. However, I also found myself being impatient and opening Reaper before the Kemper was 'ready.' By 'ready' I mean that when I selected the Native Audio option, I opened Reaper before the Kemper options for editing showed up at the bottom of Rig Manager.

    I initially had Reaper setup for 48000 and to request this setting from the Audio Device, I use a Lynx Aurora. I forgor to untick that option and when I selected the Kemper from the ASIO dropdown, my PC hanged (hung?). I had to hit the power button to shutdown.

    Brian

    Thanks Brian... mine is definitely not the impatience thing. After Miszny replied earlier, I tried it every which way, but still keep getting that damn message that's making me want to frag the entire setup!!! ... It for some reason thinks that the kemper is not connected to the pc for the Kemper driver, despite it being hooked up and working with Rig Manager, and producing sound in Cubase with Asio4all as the driver.... It's not caused any instability in my PC at all though, no hanging or crashes... I think I'm just gonna have to wait for support... would probably have been more helpful if they released their updates on a Monday so we could at least get some official help without having to wait a full weekend ... glad you got somewhere with yours though. 👍

    • New

    There are two options: 1. the USB class compliant driver. 2. the Kemper ASIO driver

    The first one is what we are all using up to this point. It's a standard driver built for compatability with all devices using the USB class. So you can use the Kemper as a windows/Mac OS audio device for streaming purposes. It doesn't have ASIO features so isn't really recommended for DAWs because of latency.

    The second is what you should use for DAWs that are compatible with ASIO for recording. You get all the features of the ASIO platform (fast latency) specific to the kemper device you have. The ASIO driver does not stay running after the DAW is closed so your OS doesn't use it so that's why you don't see it.

    You can only choose one or the other.

    • New

    The windows ASIO driver seems to be a little buggy. With ASIO test app driver does not reporting nothing (opening error) .App has to be opened in admin mode to acces the driver. Buffer changes do not affect the latency which is the same as with the WDM driver.Generally it behaves as a WDM Driver wrapper like Asio4all. In free time I will try to make a problem list.

    • New
    Quote from DamianGreda

    The windows ASIO driver seems to be a little buggy. With ASIO test app driver does not reporting nothing (opening error) .App has to be opened in admin mode to acces the driver. Buffer changes do not affect the latency which is the same as with the WDM driver.Generally it behaves as a WDM Driver wrapper like Asio4all. In free time I will try to make a problem list.

    The "Class Compliant" driver should act like ASIO4ALL, as you said, a wrapper, but should allow sound from media player or Youtube at the same time, which asio4all does not... the "Native Asio" driver should be a fully fledged Asio driver, with the downside that all sound outside of the Daw itself will be blocked, at least this is how I understand it from the description.

    From your comments, I just tried opening both rig manager and cubase, using the "Run as administrator" command, and again tried to switch the driver from Asio4all to the new Kemper Class Compliant driver, which again failed with the connection error. I then closed everything down and repeated, this time using Rig Manager to use the new native driver. Then, when trying to switch from Asio4all to the new native driver, again, I get the same connection error.

    Up to the point of attempting to use the driver in Cubase, I get all the same warnings etc as the others who have written here above. It is very frustrating, but thank you for your reply.

    • New
    Quote from CelticGibson

    There are two options: 1. the USB class compliant driver. 2. the Kemper ASIO driver

    The first one is what we are all using up to this point. It's a standard driver built for compatability with all devices using the USB class. So you can use the Kemper as a windows/Mac OS audio device for streaming purposes. It doesn't have ASIO features so isn't really recommended for DAWs because of latency.

    The second is what you should use for DAWs that are compatible with ASIO for recording. You get all the features of the ASIO platform (fast latency) specific to the kemper device you have. The ASIO driver does not stay running after the DAW is closed so your OS doesn't use it so that's why you don't see it.

    You can only choose one or the other.

    Thank you. That is very helpful. So does that mean ASIO4all is still relevant?

    Edited 2 times, last by RVA213 (September 29, 2024 at 2:44 PM).

    • New
    Quote from Mickg65

    The "Class Compliant" driver should act like ASIO4ALL, as you said, a wrapper, but should allow sound from media player or Youtube at the same time, which asio4all does not... the "Native Asio" driver should be a fully fledged Asio driver, with the downside that all sound outside of the Daw itself will be blocked, at least this is how I understand it from the description.

    From your comments, I just tried opening both rig manager and cubase, using the "Run as administrator" command, and again tried to switch the driver from Asio4all to the new Kemper Class Compliant driver, which again failed with the connection error. I then closed everything down and repeated, this time using Rig Manager to use the new native driver. Then, when trying to switch from Asio4all to the new native driver, again, I get the same connection error.

    Up to the point of attempting to use the driver in Cubase, I get all the same warnings etc as the others who have written here above. It is very frustrating, but thank you for your reply.

    Sorry but i was not reffering to your issues. Just my observations. I will add another topic about ASIO driver issues.

  • Mickg65 September 30, 2024 at 1:33 PM

    Changed the title of the thread from “Windows ASIO Driver won't load 😔” to “Kemper ASIO Driver won't load 😔”.
    • New
    Quote from Karl

    Windows 11 Pro here. USB class compliant works. ASIO doesn't work with Reaper and there is no asio control panel either.

    Interesting... I think you are the first to write here where the class compliant driver works and the native one does not... neither work for me and the others have the opposite situation to yours.

    Out of interest, for the one which "doesn't work" do you get the same error as I do (Cannot load driver, check kemper is correctly connected to PC)?

    I got two replies to my support request yesterday, and both were less than helpful... The first simply said "you have to choose the driver in rig manager, which clearly Ive already done. The second just said to close Cubase before selecting the driver in Rig Manager, which again I was already doing!

    I've had nothing from support today yet, but would hope to receive something more meaningful/technical today because I'm starting to find this super annoying now.

    If I get a solution i'll post it here for everyone else.