Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[iamimdoc]

In an (apparently) stable Win 7 PROFESSIONAL (updated) PC with J River 19.0.117 -> USB DAC, no recent hardware or other changes made (that I am aware of) EXCEPT I have started using other DLNA devices on the network:

WASAPI has stopped working.  I get a "Something wrong with playback error"

I have read the posts re: this issue.  

I have tried all of the combinations (Open Device for exclusive access Off/On, Disable event  style On/Off, Manual select bit depth, change buffer size) to no avail .  Multiple reboots.

Using ASIO4ALL does work so I presume the DAC is working

JRiver 17 on same PC will also not work via WASAPI (but did prior to my going to JRiver 19)

Any suggestions as to what is going on and how to repair?

Thanks

[JimH]

Power everything down and back up.

[iamimdoc]

Have tried this but tried again.  Rebooted router even

After PC rebooted and JRiver restarted ->

Switched from ASIO to WASAPI
Equalizer showed activity, but no sound - progress (I thought).
Restarted JRiver ->  "Something wrong with playback error"  again. (? does one have have to reboot JRiver to activate WASAPI interface)

Go back to ASIO4ALL -> music.

Is there download for the Windows WASAPI driver? (not sure this is a pertinent question)

Thanks for help.

[JimH]

On the wiki, start at "Getting Started" and go through audio setup again.

Test from Windows Control Panel / Sounds.  You might learn something.

The WASAPI driver is part of Windows.

[iamimdoc]

Have tried this

Control Panel -> Sounds -> Right click device says "unable to play test tone" even though USB DAC is able to play music. 

Perhaps device is wonky?  (Even though plays via ASIO)

Will see if I can borrow a USB device to see if this helps...

Any other suggestions appreciated

thanks

[Hendrik]

Did you already test simply disconnecting the USB DAC, then rebooting and then re-connecting it, so that Windows has a chance to re-initialize it clean?
Sounds to me like something in the USB Driver has the Windows Audio confused, which both the control panel and WASAPI rely on.

[iamimdoc]

Uninstalled, reinstalled
Unhooked, rehooked

No help

yes but will try again

[iamimdoc]

USB DAC seen in Device manager - no yellow triangles, Windows reports working properly.  Drivers are up to date

Uninstalled USB DAC device via Device manger. Device no longer seen in Device Manager.  Unplug USB DAC

Reboot PC

USB DAC still not seen in Device manager

Plug in Device to USB
Scan for new audio devices
USB DAC found - High Resolution Technology Streamer II

In Control Panel -> Sounds - only Device seen is "Remote Audio".  I have no recollection of naming the HRT II USB DAC as Remote Audio (but I am old so who knows)

ASIO works
WASAPI does not

Also, FWIW, when PC reboots I used to get a few login tones from Windows - no longer get this

[JimH]

Is any other audio software using WASAPI in exclusive mode?  That would prevent another program from using it.

[iamimdoc]

Not to my knowledge. 
Media Center 17on machine but not running (and will not work with WASAPI now) .
No other programs run on machine (by me) except MC 19 server and Windows Remotedesktop for management

No virus checker. 

Machine does not ever use IE,  etc.
Only time it goes to internet (as far as I know) is to update Windows and whenever J River does

Machine used only for music playback - no movies, no internet surfing,

thanks

[Hendrik]

As long as Windows doesn't manage to recognize your audio device properly anymore and it doesn't work in control panel either, MC cannot work in WASAPI mode.
Its not MCs fault, as Windows seems to somehow have issues here - and WASAPI relys on Windows to function properly.

I would suggest to contact the support of the USB DAC as well, as their USB driver seems to be failing in Windows.

[iamimdoc]

Just sent them an email  Was working until last few days though.  Frustrating. ?

[iamimdoc]

I posted above issue at Computer Audiophile

Issue has to do with using RDP and its sound settings.  When I switched the RDP configuration as below

When you use RDP click on the "Show Options" in the lower left, then go to "Local Resources" tab. Click the "Settings" button under Remote Audio. Under "Remote Audio Playback" select "Play on remote Computer...

issues resolved.

Still not clear to me why ASIO4ALL worked and WASPAPI does not but clearly something different in how they function.  I now presume the error message was referring to the controlling PC not having a DAC hooked up and not to the server computer.

Take away: The above issue may be a problem for those who use RDP to control a headless server.

[6233638]

Still not clear to me why ASIO4ALL worked and WASPAPI does not but clearly something different in how they function.

ASIO bypasses most of the Windows sound engine that would be affected by this. (WASAPI is Windows Audio Session API)

[glynor]

ASIO4ALL is the same thing as MC's Kernel Streaming mode, wrapped in a driver.