XXHighEnd - The Ultra HighEnd Audio Player
March 26, 2017, 05:27:24 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Dec. 31, 2012 : XXHighEnd + Phasure NOS1 DAC receive 6moons Blue Moon Award !
** "Lonely at the very top" **
Search current board structure only !!  
   Home   Help Search Login Register  
Pages: 1 2 3 4 5 6 7 8 [9] 10
 81 
 on: March 01, 2017, 09:09:04 pm 
Started by RiCo - Last post by PeterSt
Thank you Mani.
... which doesn't really solve Rica's problem I suppose. So we must all realize that you and me (and many others) boot in a wimp into that other OS - just like me testing this all. But this is very very different from someone not owning the RAM OS Disk. So say that this message is just a heads up for Rica and that I don't want to belittle Rica's problem (nor yours of course).

Regards,
Peter

 82 
 on: March 01, 2017, 08:27:33 pm 
Started by RiCo - Last post by manisandher
And I'd say that if one these days wants to use WASAPI he just as well can use 10586.0, which very many do anyway.

It's not that I want to use WASAPI, but rather that I'd like to use Roon in my office. And in order to do this, I have to get HQP working with the NOS1a.

But you're right, no reason not to use 10586.0 for this purpose, which is exactly what I'll do. So a solution of sorts Happy

Mani.

 83 
 on: March 01, 2017, 08:03:46 pm 
Started by RiCo - Last post by PeterSt
I forgot to tell ... regarding what I see, I think I can get it to work at some stage. But at this moment this really can't have priority. Sorry for that.
And I'd say that if one these days wants to use WASAPI he just as well can use 10586.0, which very many do anyway. It is of course for a reason that seriously everybody uses Kernel Streaming (oh sure, a few may say "me not !").

Peter

 84 
 on: March 01, 2017, 07:56:03 pm 
Started by RiCo - Last post by PeterSt
PS: It was already known that other devices work, so really no need to connect a dozen more for proof. Google for sound device problems and Windows 10 will "help" more. Happy
Don't get drowned in them.

 85 
 on: March 01, 2017, 07:44:44 pm 
Started by RiCo - Last post by PeterSt
No.
That leaves W10 at fault.

You seriously think that this driver, working for years, is going to be revisited because some stupid W10 version (which from its start *always* has problems with sound) suddenly does not work with it ?
Just look how wackey it works with that loudspeaker icon staying red and all. Or how the enhanced tab (which is quite crucial regarding the "Exclusive Mode stuff on it) of the device's properties can appear or disappear.

You can try 1.03 if you like (works with XXHighend properly only (don't forget the driver103.tst)) and may notice that it does not work just the same. I did not try it, but I take it there will be no difference. This makes it go back all the way to Vista.

Peter

 86 
 on: March 01, 2017, 12:20:56 pm 
Started by RiCo - Last post by manisandher
Peter, I just loaded the iFi driver and connected the iFi Nano DAC to the Mach II (W10-14393), and:

1. HQP/WASAPI works perfectly
2. XX/WASAPI works perfectly

So that leaves the NOS1a driver at fault, no?

Mani.

 87 
 on: February 28, 2017, 07:04:40 pm 
Started by RiCo - Last post by PeterSt
PS: Another indication for 14393.0 is that the loudspeaker icon remains "red" (not available) until you explicitly change the output channels (and back). So this is all once again W10 sh*t ...

 88 
 on: February 28, 2017, 07:02:13 pm 
Started by RiCo - Last post by PeterSt
Answer : not me. But I am also not sure how to solve it, and I feel it requires a normal monitor connection first. I mean :

The error message and whole situation is exactly the same as if the "Remote Audio" device would be (accidentally) selected. See 10586.0 where it all works perfectly, unless that Remote Audio is redirected (I hope I need not further to explain). But also : the audio problems can not be solved (see button for it) when at an RDC connection. Thus, error message the same, and that too smells fishy.
And I am not going to get out my monitor, which, well, is connected to that other pile.

Anyway, 10586.0 is fine with it. 14393.0 indeed is not and most 100% probably HQP's problem as well.

Peter

PS: Watch out : There's a bug in 2.07 (or longer) which requires the Sound Engine to be killed when the Sound Device in XXHighEnd is changed. This is most misleading of course (I only found out about this yesterday).

 89 
 on: February 28, 2017, 06:10:26 pm 
Started by RiCo - Last post by PeterSt
So ... before I try myself ... who are we going to blame if it does not work ?

 90 
 on: February 28, 2017, 05:41:50 pm 
Started by RiCo - Last post by manisandher
Yep, XX on Mach II and NOS1a (#5 up).

Everything in Normal OS (of course  yes)

Mani.

Pages: 1 2 3 4 5 6 7 8 [9] 10
Powered by MySQL Powered by PHP Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Valid XHTML 1.0! Valid CSS!
Page created in 0.252 seconds with 15 queries.