Topic: ASIO Problem [Solved] (Read 5993 times)

doctorjazz · « **on:** April 12, 2020, 06:53:50 pm »

I hadn't mentioned it, because I thought it was a problem with my DAC (Light Harmonic Geek Out Special Edition), but I haven't been able to listen to music either. I click play, and get an error message "Playback could not be started using output 'ASIO', format '196 khz, 2 ch...". I go into settings, and ASIO is the only option I have for this DAC. I have used the setup in the past with no problems (for quite a few years, through many versions of MC). This problem persists in MC25 or MC26. Not sure what is my next step here either, can't rip or listen to music in 26, can rip but can't listen in 25. (really nervous about disabling antivirus).

JimH · « **Reply #1 on:** April 13, 2020, 06:47:01 am »

The ASIO driver normally comes from the manufacturer of the hardware. If it's a 32 bit drriver, it will require using the 32 bit version of MC.

Otherwise use DSP Studio > Output format to force everything to a lower bitrate.

doctorjazz · « **Reply #2 on:** February 07, 2021, 03:13:18 pm »

Hi. Boy, time flies, getting close to a year since I posted this, no replies. I just haven't used JRiver since the problem started, except as a way to rip CD's (still more convenient than other ripping programs I've tried). The issue really does seem to be JRiver (using 27, still updating). When I play something from YouTube, for instance, I have sound, so the PC isn't the issue. I've tried 2 different DAC's (Geek Out Special Edition, CEntrance Hifi M8, actually both v1 and v2), tried updating drivers, still can't listen to music, JRiver gives me an error that the output format may not be supported by my hardware, which I'm sure is not correct. Tried looking for something in settings to fix the problem, can't find it. Hoping for some help, I always did like using JRiver, have been with it for many years, but it may be time to move on if I can't get it to work.
I'd appreciate any help.

JimH · « **Reply #3 on:** February 07, 2021, 03:19:40 pm »

The DAC may not support the format you're trying to play. Try others to see.

Try installing the 32 bit version of MC. It's on the Download Page.

Otherwise use DSP Studio > Output format to force everything to a lower bitrate.

doctorjazz · « **Reply #4 on:** February 07, 2021, 03:52:29 pm »

ASIO should be supported; I don't get other options for the DAC's. CEntrance told me the DAC didn't need specific drivers, but they sent me some that they said should work if I did have trouble. Nothing worked. I had been using the 64 bit previously without difficulty, but I guess it's worth a try.

JimH · « **Reply #5 on:** February 07, 2021, 05:06:59 pm »

Quote from: JimH on February 07, 2021, 03:19:40 pm

Otherwise use DSP Studio > Output format to force everything to a lower bitrate.

Did you try this?

wer · « **Reply #6 on:** February 07, 2021, 05:51:04 pm »

Quote from: doctorjazz on February 07, 2021, 03:52:29 pm

I don't get other options for the DAC's.

Really? If DirectSound weren't there, YouTube wouldn't play.

Please post a screenshot of contents the dropdown menu you get for Audio Device in MC's Audio Options.

larryrup · « **Reply #7 on:** March 20, 2021, 05:24:56 pm »

I have not been able to use the recommended ASIO driver by my Headphone amp manufacturer (XMOS USB Audio 2.0 ST 3066 [ASIO]) for some time. Seems any bite rate opens the MC ? message "Something when wrong with playback...". I am on v26. WOO Audio's owners manual actually gives instruction on how to set this driver in JRiver.

The only driver that works is WASAPI. I have no idea if this WASAPI driver is better or worse than the ASIO, but would be nice to know what the issue is.

Larry

JimH · « **Reply #8 on:** March 20, 2021, 07:21:46 pm »

Maybe it's a 64 bit vs 32 bit problem. Please try the 32 bit version of MC.

larryrup · « **Reply #9 on:** March 20, 2021, 09:46:51 pm »

Can I use a 32 bit v on my 64 bit windows machine?

Thanks

Larry

JimH · « **Reply #10 on:** March 20, 2021, 10:14:25 pm »

doctorjazz · « **Reply #11 on:** August 28, 2021, 06:15:31 pm »

Hi-dropped off here for a while, not because my problem was solved, but I just got tired of it, and thought maybe my PC was the problem. I spend much time with LP's on a speaker stereo anyway. So, gave it a rest for a while. In the meantime, the PC I was using (Windows 10) crashed, I brought it to a computer repair person, back, working well.
I upgraded to 28. Tried using JRiver to play some music, same "something went wrong with playback..." and whichever selection I make in Tools/options/playback, the same thing happens. I did try 32 bit, exactly the same outcome. In the meantime I bought an HP laptop, have 28 installed, works with no problem. Not sure what my next move is (aside from finding different music playback software, which would be sad, as I've been here for 10 or more updates/versions)-any suggestions?

JimH · « **Reply #12 on:** August 28, 2021, 09:32:30 pm »

The wiki has an Audio Setup topic. Try Direct Sound or Wasapi.

doctorjazz · « **Reply #13 on:** September 01, 2021, 11:07:45 am »

I've tried all the options WASPII, ASIO, direct. Upgraded to 28, uninstalled, reinstalled, no help. I can't find this set up WIKI you mentioned (there are thousands of related but not useful links that come up when I search for it).

Captor · « **Reply #14 on:** May 04, 2023, 02:31:12 am »

Hi, I have exactly the same problem. However, my DAC is an Audionet DNA 1. Otherwise all same. I am using the driver that comes with the DAC. I can chose ASIO from Audionet in the MC settings but then I get the message "Playback could not be started using output 'ASIO', format '44,1 khz, 2 ch...". In the MC settings I have other choices like WASAPI from Audionet and that works fine. It is only the ASIO driver that won´t work. Is there any update on this topic?
I have used this DAC with ASIO since 2016 but when I installed the MC30 I started to get problem.

JimH · « **Reply #15 on:** May 04, 2023, 04:34:37 am »

When you get the error message, it should tell you that you can use DSP Studio to choose output settings that will work.

It's also possible that the driver is 32 bit. In that case, you'd need to install a 32 bit version of MC.

Captor · « **Reply #16 on:** May 04, 2023, 05:09:52 am »

Jim, I have tried the different DSP settings but none of them works. Same result all the time: "Playback could not be started using bla bla".
It is a both 32-bits and 64-bits driver. So changing MC to 32-bits would not make any difference. And besides I have all the time used MC 64-bits versions only.

DJLegba · « **Reply #17 on:** May 04, 2023, 06:10:01 am »

Are you running another program that uses the ASIO driver? For example. the Qobuz desktop app can be configured to play through ASIO. However, ASIO can be used by only one program, and will fail if you have more than one trying to access it. Make sure Qobuz or whatever else may be configured to play through ASIO is closed before you open JRiver Media Center.

Captor · « **Reply #18 on:** May 04, 2023, 07:00:34 am »

DJLegba, No I am not running anything else on this computer. I mean that is using ASIO. I don´t have any streaming service like Qobuz att all. I only play flac files from my main library which is on the harddrive in the computer. So no separate server too for the flac files. And the driver from XMOS (Audionet) shows up in MC and there are 2 ways I can play: ASIO and WASAPI. Maybe Direct connect too I am not sure. However WASAPI works just fine but not ASIO. When I set the ASIO driver in the settings of MC I get that message again.

Awesome Donkey · « **Reply #19 on:** May 04, 2023, 07:38:16 am »

In my own experience ASIO drivers can be either very good (e.g. Schiit's ASIO driver is very nice) or pretty subpar (e.g. Topping's ASIO driver lacking exclusive mode for PCM audio) so you could be encountering some sort of weird issue with the ASIO driver. You might try uninstalling your DAC's ASIO driver and reinstalling it and see if it fixes itself.

It may not be a Media Center though, since ASIO is provided by the DAC manufacturer and if it can't output 44.1 kHz audio, then something's not right. You could try contacting the DAC manufacturer and see what they say about it. Using WASAPI (in exclusive mode, of course) is a good alternative at least.

Captor · « **Reply #20 on:** May 04, 2023, 08:09:50 am »

Thanks Awesome Donkey, Yes there is something not right. I have already contacted the manufacturer Audionet and unfortunately they have no idea for now. They are thinking it must be computer related not Audionet hardware related.
I have also uninstalled and reinstalled the driver several times. it is a mystery that it don´t work.

JimH · « **Reply #21 on:** May 04, 2023, 10:52:41 am »

Quote from: Captor on May 04, 2023, 05:09:52 am

It is a both 32-bits and 64-bits driver. So changing MC to 32-bits would not make any difference. And besides I have all the time used MC 64-bits versions only.

I think it's worth a try. It may not fully support 64 bit.

Captor · « **Reply #22 on:** May 05, 2023, 04:49:05 am »

Jim, I have now tried with MC30 32-bit version. It is same problem still so I am changing back to 64-bit version now. ASIO driver from manufacturer still not work. Only WASAPI driver from Microsoft works. Any other idea or suggestion out there, please?

JimH · « **Reply #23 on:** May 05, 2023, 05:19:39 am »

If you want to ask the device manufacturer to look at the problem, let them know we will provide a license.

Or use WASAPI. It's a good choice.

Captor · « **Reply #24 on:** May 05, 2023, 05:36:42 am »

Jim, OK, I will talk to them again this afternoon. I will let them know. You think that could be the problem? I have got the window several times saying that Windows can not verify the signature. But I had that message back in 2016 as well and it worked fine. I send some more screens. XMOS is the manufacturer of the drivers for Audionet.

Captor · « **Reply #25 on:** May 22, 2023, 04:28:42 am »

An update: I have sent the receiver to the producer as I can´t find the problem for not being able to use the manufacturers ASIO driver.
In the meantime while waiting for the outcome on that I am considering installing Windows 11 on this computer. So I wonder if there is anything to think about regarding Windows 11 and JRiver? Have there been any problems reported when using Windows 11 for example?

Awesome Donkey · « **Reply #26 on:** May 22, 2023, 12:28:30 pm »

Nah, it works as fine as it does in Windows 10.

Captor · « **Reply #27 on:** May 22, 2023, 05:07:54 pm »

Quote from: Awesome Donkey on May 22, 2023, 12:28:30 pm

Nah, it works as fine as it does in Windows 10.

OK, great! Thank you very much for answering.

Captor · « **Reply #28 on:** June 27, 2023, 10:28:59 am »

A short update on this issue. I had problem installing the ASIO driver in Windows 10 and also in Windows 11 in a proper manner. I too got this message "Playback could not be started using output 'ASIO', format '196 khz, 2 ch..."

For me it worked after I disabled "secure boot" in BIOS (UEFI).

It looks like all not too old computers have this BIOS setting and it is always enabled by default and because of that, a proper installation of the driver from the manufacturer of the DAC is blocked. Also other drivers might be blocked, not only sound drivers.

The driver options from the manufacturer of my DAC are named XMOS here in the print screen.

I hope this can help someone with the same problem. For me this problem is solved by this.

Best Regards
Andreas (Captor)

JimH · « **Reply #29 on:** June 27, 2023, 01:12:41 pm »

Thanks for posting the solution.

Awesome Donkey · « **Reply #30 on:** June 27, 2023, 01:24:32 pm »

You might want to contact the DAC manufacturer and see if they have updated drivers. If it's an older DAC with no driver updates, it makes sense. If memory serves, secure boot doesn't allow unsigned kernel drivers from loading, so this is likely why. It'll pose an issue with Windows 11 and in the future as Microsoft forces secure boot to be enabled and used.

If it's an older DAC and you're using Windows 11 (or Windows 12, etc. when it's released) you may have to give up ASUO and switch to WASAPI or replace the DAC with a newer one with signed drivers.

Captor · « **Reply #31 on:** June 27, 2023, 02:03:30 pm »

The DAC is from 2015 or something like that. I have talked to the manufacturer and they told me to make a clean installation of the driver. But that did not work. Why is the kernel unsigned in the first place? It has been signed before but it stopped to work when I still had Windows 10. I think it started after an update. How can it suddenly stop working that I can not understand. Maybe the manufacturer did not pay some fee or something?

JimH · « **Reply #32 on:** June 27, 2023, 02:19:42 pm »

You could use Google to read about driver signing.

Captor · « **Reply #33 on:** June 27, 2023, 02:43:04 pm »

Jim, earlier in this topic you answered this:
"If you want to ask the device manufacturer to look at the problem, let them know we will provide a license".
Is this what you meant then or did you mean a license about JRiver?

JimH · « **Reply #34 on:** June 27, 2023, 03:35:50 pm »

A license for MC.

Captor · « **Reply #35 on:** June 27, 2023, 05:05:38 pm »

OK
I have read more in google as you suggested and it look like I can sign a driver myself in the Windows settings if I trust the source of the driver. Maybe I misunderstood but I will look closer to that later.

INTERACT FORUM

Author Topic: ASIO Problem [Solved] (Read 5993 times)