XXHighEnd

Here's my understanding. If 'Stop WASAPI Services' is engaged in the Settings Area, then there will be no WASAPI services available during 'Minimize OS' mode... However, these WASAPI services should restart when XX takes the OS back to normal.

But WASAPI services do not come back in normal OS mode.

Why am I even bothered about this when KS is clearly superior. Well, I'd like to try feeding the NOS1 from HQPlayer. In order to do this, I need WASAPI services.

Am I doing something wrong or is there a bug in XX?

Mani.

CORRECTION:

I'm not sure if it's the WASAPI services themselves cannot be restarted or if it's just the NOS1 that cannot be used in WASAPI mode.

I currently don't have any other audio devices active in my 'new' 3770K PC. I'll activate the onboard audio device and see if I can use it in WASAPI mode.

Mani.

Mani,

Shouldn't be related to the NOS1 ...

Just to be sure, this is the procedure to activate it :

a. You start out with all disabled in Minimized OS.
b. Reboot into normal;
c. Activate WASAPI;
d. Reboot into Minimized.

Then it should work.
If you, for instance, put c. in between a. and b., something which I needed often because otherwise I might forget it after b. - things may go wrong and I exactly never dared to try that.

More examples were reported of things going strange here, and I think it was Paul who for the life of him never was able to shut OFF WASAPI anymore. Until a fresh OS install.

HTH ...
Peter

Right, WASAPI services work in Minimize OS mode no problem. But neither W7 nor HQPlayer recognize the NOS1 as a WASAPI device. XX recognizes the NOS1 OK, but only as a KS device, not a WASAPI device.

Am I being really thick somewhere?

Mani.

Theoretically you can have disabled it while "Show disabled devices" (similar) is not ticked ...

Sorry Peter, where is 'Show disabled devices'?

Mani.

Yea, a bit strange if you don't know;
Rightclick on one of the devices and then the menu is there.

Btw, I now wonder what happens when all are disabled and this option is not On. Then there is no device to select ...
Ha, I'm not the only one implying a bug here or there.

But what I now also see accidentally, is that my own WDM NOS1 device (WASAPI) is disabled. Did *I* do that ??
I wonder.

Peter

OK thanks.

But it still doesn't find the NOS1. I think I may have set something in the BIOS that is stopping audio devices being detected. I'll explore when I have more time.

Mani.

Or uninstall the NOS1 driver and reinstall it ?

Maybe one other thing which springs to my mind :
The driver sure lets itself install in Minimized OS Mode. But I now wonder what can happen when you plug it into an USB port while in Minimized Mode (it will install the driver for that port when not used before !!) while you next go to Normal Mode. Nah, I'm thinking too wild now ...

Well maybe this sheds some light on the situation. The audio devices are there, but are not being detected by WASAPI?

Mani.

Too simple to provide the solution, but still an attempt :
If you boot into normal and next switch Off only the Desktop Services, reboot into Minimized ... does it work then ? If Yes, then reboot into normal, switch Off the other stuff (but not WASAPI) and retry.
Seems dumb, but it could "reset" things this way.

Please notice that oficially this just works (I use it all the time myself at watching movies).

Peter

Hi Peter, just tried your suggestion and unfortunately it doesn't work.

I still can't see the NOS1 as a WASAPI device either in W7's 'Manage Audio Devices' or in HQPlayer. But it's listed in W7's Device Manager as a WDM audio device.

Strange uh? Any more ideas?

Mani.

Okay, what about uninstalling your xxx device's driver (man, I forgot How it's called, but what you use for DSD playback). If you never installed that, never mind. But it seems logical to me that you did. And now I know a couple ot things about that and its driver ...

When you uninstall it, take care that it all went OK.

It could even be that you attempted to install it, but that it failed half-way (and that you now are unable to uninstall it).

Can I be in the proper direction ?

Peter

Nah... I've never installed the Mytek driver on this newly built PC.

So just to be clear, I'm simply trying to use the NOS1 as a WASAPI device either in HQPlayer or XX. But although it shows in W7's Device Manager, it doesn't in either of the players, or indeed in the W7's Audio Device Manager.

I'll try to post some more screen shots to help us get to the bottom of things.

It makes me wonder how other people are using non-NOS1 DACs in 'Minimize OS' mode...

Mani.

No problems here with the realtec audiocodec of the mobo. Plays pure ENGINE #3 @ unattended (but on "maximised OS"). Nice tight sound.

Very NON-NOS1  ;)

Maybe you should try the codec on your mobo too if this works at all on your pc.

regards, Coen

p.s. did you check all BIOS settings? Maybe there is some interaction between os and mobo.

Peter,

I remember having the same problem when using the Remote Desktop Connection (with Blue Tooth but I am not sure if the Blue Tooth connection has something to do with this...).

In RDC -> Options ->  Local resources (this is a litteral translation from French) -> Parameters... Verify if the Audio parameters are set correctly. After I checked the first choice, I was able to use WASAPI and I Was Happy ;)

Not sure if this is the source of the problem, but...

Alain  

CRACKED... but not solved!

Alain, thanks for your help... it didn't solve the problem but certainly led me in the right direction.

WASAPI works absolutely perfectly if the PC is booted in 'normal OS' and is accessed locally, i.e. monitor and keyboard/mouse connected directly to PC.

WASAPI does not work if the PC is accessed via bluetooth RDC. (It may well work via LAN RDC, but I haven't tested this yet.)

The two screenshots below were taken via the two diffferent access means. Absolutely no other parameters in W7 were changed.

Thanks again Alain.

Mani.

Cracked and solved!

In your RDC connection, you have to select 'Play on Remote Computer'. This solves the problem.

All credit to Alain.

Mani.

Yes, this can be very confusing and I am not even sure whether the below is 100% correct :

When the audio PC has WASAPI activated, but look at it through the RDC connection (say, the laptop), the speaker icon has a red cross implying no audio devices are there (well, in my case, and in your case Mani, I think one was left, so no red cross in your case I assume). While most certainly knowing how this works (including that setting you luckily found) I still don't get it much; it seems to tell that you will not be able to produce sound (KS not taken into account) from the laptop itself. You think like this, because you see that icon changing (just active on the audio PC - not active *anymore* when you hop over to the laptop. And well, it would be true, because through that RDC screen you can't go anywhere. But put it to the taskbar and you can ... (only then you look at the laptop itself).

But what's next ? (and I never really tried to think of it) ...
Now you apply that setting as Mani had it (abusively). So, now I must be able to play from the laptop. But how ? Nothing like a NOS1 (or whatever) will be seen there. Or ? and if not, what then ? Looking at the Audio PC's screen certainly nothing will be there. But what will we see looking at the laptop screen ? the NOS1 (etc.) after all ? The laptop mobo's sound device only ? or ...

No, we will see the below picture which shows on the audio PC (and what we see at the laptop). It is Mani's own picture. Ah, no red cross, because despite nothing is actually there, that remote audio device is there. But, what is it ? What is it played through ? I can imagine the laptops loudspeakers only and through the onboard (mobo) D/A. But maybe if you click that entry things can be configured differently (see the "default device" underneath it).

This one is similar but maybe more braindamaging :

When you find the remote keyboard from MS (so, not from XXHighEnd), you can start it on the Audio PC but you can just as well start it on the laptop. Both work out the same. But, now hop over to the tablet. Of course both will STILL work the same. But being with your nose above the tablet, try to figure out how in the world this can work out the same ...

Hi Mani,

I am glad I could point in the right direction ... And that you were able to select the right option. I should have written "third" instead of "first". My bad :(

Alain

I'm having problems getting any sound out of the NOS1 with HQPlayer. Weirdly, a test tone in W7's 'Manage Audio Devices' plays perfectly out of the NOS1.

I have the device in the NOS1's USB panel set to 'Stereo' (not 4.0) and the relevant switch on the NOS1 in the correct 'up' position.

It could well be a configuration issue with HQPlayer. Everything seems to be working fine - the track details show and the timer runs exactly as it should, but there's no sound out of the NOS1. It's strange because the HQPlayer/NOS1 combo used to work fine 6-9 months ago. But I guess a lot has changed since then with HQPlayer (and maybe the NOS1 driver too?). I'll contact Jussi at some point and see if he has any thoughts.

Mani.

Mani,

Not that I can see how it relates (but theoretically it can) - choose Stereo Reduced.
Also, choose the first option available where you choose the devices in HQPlayer. So, IIRC you will see two stereo pairs; use the first (I am not sure why but I know that works).

Otherwise, maybe just use XXHighEnd first ? in that case, switch off Is NOS1 to mimic all properly.

Peter

Mani,

Maybe try to set XX first to 16\44 and play a song for a few seconds. After that try again.

Just a wild guess

 :)

;)

And when you're sitting down tomorrow to post that your NOS1 is broken in some channel, think about this post.

Haha.

Thanks for the ideas guys.

Well, it's not an HQPlayer issue. I'm not getting any sound out of the NOS1 with XX either! Neither Engine#3 nor Engine#4! Again, everything seems to be working OK, the clock is counting and the slider is moving (in Attended, of course). But no sound out of the NOS1. Yes, there are two Engine#3 NOS1 devices and two Engine#4 NOS1 devices. Non give any sound out of the NOS1.

Peter have I got the latest USB driver? It says:
- driver version: 1.0.1
- build type: release
- interface version: 2.0

(But you sent it to me ages ago as v1.0.2.)

I could load the Mytek driver and see if I can get some sound out of the Mytek DAC, but I'd rather get the NOS1 working properly first.

Mani.

OK, it's nothing to do with the NOS1 either. I'm getting the exact same behaviour with the mobo soundcard.

Will continue experimenting...

Mani.

Ah, good. That is one day earlier than I expected.
:wacko:

Hey Mani where is your Windows volume? Turn it up if you are not in minimized mode.

Haha...

Just to eliminate any bluetooth/RDC affects, I've reverted temporarily to using a direct monitor & keyboard/mouse connection.

WMP works fine with the NOS1 (not WASAPI). But I just can't get a whisper out of HQPlayer or XX. It seems to me that WASAPI still isn't restarting properly after a 'Minimize OS'. (Even when following Peter's earlier advice about stopping only desktop services and then going back to normal OS.)

(Yep, I check Windows volume control very carefully before I hit play in any of the players - the NOS1 is going directly into the power amp.)

Mani.

A final thought on this for today: do the 'persist' buttons actually do anything?

Mani.

No, they still don't. But it looks interesting don't you think ?

It is that HQPlayer also doesn't work, but otherwise I would have said : change your Q1 to 14 (Q1F to 1).

Hmm ...

OK, this has been a comedy of errors... on my part!

I can't believe this, but apparently the particular track that I chose from a totally random album on my 2TB HDD has actually been ripped incorrectly. It plays, but as total silence. For some reason, WMP ordered the album tracks differently and I chose a different track when trying it.

Soooooo, to cut a long story short, everything seems to be working as expected. I'll start playing around with a few different configurations later this evening.

Sorry for wasting anyone's time...

Mani.

Costs you a pint.

Ok, two.

Per person.


PS: Glad you got it solved.