Error during playback initialization

[smilemakr]

I've been happily using XXHE v. 1.186a for a couple of years now (yeah, I know, I need to upgrade!), on a computer that Peter built.  I'm using the NOS 1a DAC.  But a couple of weeks ago, when I hit "play" with a track cued up, I got no music--only the Windows error chime and the following message:

Error during Playback Initialization
ENDPOINT CREATE FAILED -> The DAC does not accept this byte sequence.
Try switching DAC Needs from 32 to 24 (or the other way around)

A second message, behind the first, says:

4|32|176400|2822400|16

Switching "DAC Needs" to 24 did no good, of course, nor did rebooting the computer.  I don't think I inadvertently made any changes to settings before the problem began--it came "out of the blue", so to speak.  The housecleaner was here earlier that day, but I can't imagine that she would have messed around with it, and I'm out of other suspects!  My wife definitely avoids touching the stuff.

I'm not particularly computer savvy, so this may be a problem that most of you would have solved by now, but I'm stuck.  Any ideas?

[jhmvl]

Hi,

I had the exact same problem some weeks ago. My setup is a bit different, I don't have nos1a (yet), but the problem appeared the same way. I solved by uninstalling the driver for my dac, rebooting, and reinstalling the driver again.

I still don't know wherethe problem came from but this procedure solved it for me.

Regards

Hans

[PeterSt]

Hi there Mark,

It feels like the NOS1a not being recognized at this moment. Hence, if you'd go into XXHighEnd Settings and drop down the available devices, nothing of the NOS1a shows and only Motherboard audio devices. Is that so ?
But if you see it, select it.

Btw, apparently you are in Normal OS Mode. Maybe you did that on purpose.

If the NOS1a shows after all, you may fire up the NOS1 Driver Control Panel (the yellow-ish X) and see whether there's life in there (should show "Streaming is up and running" at the bottom). If this is not the case, check these things briefly :

Power cord thoroughly in (both sides);
USB cable in (both sides);
Power switch at the back is on (down);
Sw#2 is on (down);
Sw#5 (the one most far from you) is on (Down).

Lastly, proove that the NOS1a is on in the first place. With the NOS1a this is not so easy. But if you, in the dark, look in the middle section (through the slits) at the left wall, there's a small mirror reflecting the green led which these days is under a PC on top of the DAC board. You will see it shine, when in the dark.
There's also a more easily visible green led in the left leg (~ middle) but if USB fails (like no cable connected) that led will be off anyway.

If this all fails, check the fuses;
Under the power inlet there's a bracket which can be removed by means of pushing the little thingy you'll see automatically. The bracket will jump out a few mm by itself. The bracket will hold two fuses and both must be OK to let the DAC work.
Is one blown (or both), we delivered two spares. If you can't find them, you'll need 1A medium slow blow fuses, and obviously of the same size.



Let us know what happens ...
Best regards,
Peter

[smilemakr]

Hans and Peter,

Thanks for your replies.  You both seem to feel that the NOS1a is the problem (either the driver or the DAC itself).  However, the Windows chime or *bling* sounds are coming through to the stereo just fine.  If the NOS1a or its driver is at fault, wouldn't these sounds coming from the PC not make it through to the preamp?

I'm perfectly willing to follow your earlier suggestions, of course, but I want to make sure it's sensible to do so in light of the above facts.  Also, Peter, it will be many hours before it's dark enough to look for a miniscule LED glow in the innards of the NOS1a!

Mark

Mark

[PeterSt]

Uhm ... Mark ...

haha

I guess you must be right. But now I must (for once) think ...

Peter

[PeterSt]

Must be the wrong Device selection, Mark. So in that drop down I mentioned.

In itself it can happen that a wrong Device is auto-selected by XXHighEnd, that is, in the 1.186a/i version.
And *that* is encouraged for when in Normal OS Mode (just because more devices are available in there).

Skip the "led analysis".

Peter

[smilemakr]

Hi Peter,

OK, when I get into XXHighEnd settings and look at the Output section and then the "Device" drop-down menu, there are several choices (some of them appear truncated due to the width of the box):

Primary Sound Driver
Realtek Digital Output (Realtek High Definition
Speakers (Realtek High Definition Audio)
Phasure NOS1 Out1 L/R (3-Phasure NOS1 W
Phasure NOS1 Out2 L/R (3-Phasure NOS1 W
KS: Phasure NOS1Out1 L/R>>#pcmrendere
KS: Phasure NOS1 Out2 L/R>>#pcmrendere

One of the two Phasure NOS1 Out options was indeed selected (I didn't pay attention to which one was active--oops-- but I've tried both).

No matter which of the above options I choose, I get the same error.

Should I try reinstalling the driver, as Hans suggested?  If so, give me a hint as to how to do this.  Thanks!

Mark

[PeterSt]

Mark,

Maybe you are trying to load Hires files with 16x upsampling while the fx button is not active (any more). Look for the fx button in the left pane under the input and output sampling rate.
Slide the [ 1 ] button in the top sufficently to the right in order to see that pane.

Theoretically you can also get the fault when Device Buffer Size (in Settings) times Q1 times xQ1 (under [ Q ] near the bottom) is too low. Set respectively to 4096, 14 and 1.

Regards,
Peter