0dB cracks at -24dB volume ?

[hybride]

Damn! (sorry)
From the 3th to the 4th track; no track data, XX stops playing...
Then pointing the mouse at nr4 and click play...
CONTINUOUS CRACKS/NOISE AT 0 DB!!!  AAARGHH

Peter how can this 0db screaming come out of my speakers with the slider is at -24db

[PeterSt]

I explained this elsewhere (release notes on 0.9u-0 I think) :

This is not 0dB, but (as I say) clips the DAC. The byte order will be wrong, and e.g. +2V jumps to -2V in one step. The DAC can't handle that.
Try to set the volume at 0dB and notice that it's way louder then ... 

Btw, in that file the data will be wrong.

[Gerard]

Hi Hybride,

Maybe try a different Q1 setting.... 14.... Worked for me before....

 

[PeterSt]

I don't think that can create the loud cracks hybride is talking about Gerard.

[Gerard]

I don't think that can create the loud cracks hybride is talking about Gerard.

OK 

[hybride]

HOLY sh*t!!!!!!!!!

THE CRACKING BLEW UP A TWEETER IN ONE OFF MY (€4000 piece) SPEAKER!!!!

Peter, alarm!!!

YOU HAVE TO WARN ALL THE PEOPLE WHO USE ENG#3 WITH NO PRE-AMP.

 

[PeterSt]

First response : you are allowed to shout as much as you want. Special occasion.
No, I won't put smileys, because this is far from funny.

A second response is coming up.

[PeterSt]

So, second response ...

hybride, this indeed is serious. Ok, not to withdraw any of my sad feelings, but this is literal part of the Release Notes :

Serious warning : Follow below procedures precisely, or you may end up with smoked speakers. Please don't hold me responsible if it happens anyway !

so on that matter I tried my best. However ...

The "why" is important here. And I know, not for you ... not this time. !

In between lines : I had it myself in three occasions or so, the last time yesterday at going from one format (like 96/24 to 96/16) to another the player can't deal with, and for which I did my stinking best to capture the situation. I wrote about it yesterday ...

Does this help you ? no, still not obviously.

The real (kind of) response is that one should be over-careful not to try this on material you actually don't know, or don't know how it works out within XX. And I can't emphasize more on the FACT that Microsoft herself does not comply to the RIFF (blahblah) Audio (Red Book) rules, with the example of WMP rips on one side and playback via WASAPI Exclusive Mode on the other.
And then there's also errors on my side ...

In the area of playing without a preamp there are dangerous dangers. One of them is the loud clicks, which were discussed yesterday I think, at the DAC settling at 88.2 or 96 KHz. At least with my DAC this is so, that most probably always have been so, but never came out as the loud unattenuated click because of ... well, it just being attenuated analoguely.

I want to write more, but it doesn't help you.
I can only hope a wire went loose ...

[PeterSt]

For now, and for others KEEP ON KEEPING THIS IN MIND !

... and maybe for more reasons than indicated here :

[PeterSt]

For now this doesn't leave my mind;

Thinking of the +2V/-2V story, I think I am able to build in a check for too large voltage steps happening.
Yes, I will test it myself.

[PeterSt]

It is strongly advised to not use your system without a preamp (or the pre-amp at max volume for that matter) if you or your speakers won't be able to handle a situation that e.g. the file contains wrongly formatted data or otherwise - because of which cracks may emerge with an energy beyond imagination.

I added this text to the Release Notes on each of the versions that support the Digital Volume. The least I could do.


To emphasize the potential danger : you may have heard of the Densen CD. This CD contains a special track that "demagnetizes" the equipment. The track contains rather rubbish tones. Throughout times I smoked both of my Infinity R90 tweeters TWICE by playing this track too loud. "Too loud" meant : the volume at 10-to while normal music played at 15-past easily or at full for that matter.
It's the harmonics which are dangerous, and the cracks as can be experienced are full of squares, producing those harmonics.

Ever heard of UDIAL ? this is a kind of SRC test file and there too 19KHz harmonics (inaudible) exist. That smokes speakers easily.

Somehow I suddenly lost the energy to continue on XX development

[hybride]

I have the Densen cd, but didn't know the risks.

Peter, thanks for the extra warning for 'newbies' like me.

You suggest that files can contain wrong format data and that explains this behaviour.
But with Foobar of Eng#1  i never have (had) such failures; every file makes music or it is rejected with a windows file error (very rare).

What makes you so sure?

 

[PeterSt]

Hard to explain for someone not deep into it, but it comes briefly down to this :

Vista Exclusive Mode is *very* formal when it comes down to accepting formats. Say, it only accept formats which are defined by standards officially. An example of unofficial formats is what WMP produces at ripping. So, this already can't be played with Vista's own audio playback means.
But it works the other way around as well :

If you have followed this forum for that last 2 or 3 weeks, you may have noticed the difficulties with DACs just not wanting to play where they should. Their format is rejected by Vista Exclusive Mode (and all other means of playback just allow for it). So it needed tweaking which in the end comes down to, you could say, allowing too much. Too much in a technical sense because Vista actually doesn't allow it. Not that such can cause cracks, but all the variations must be dealt with by me now. Including holding back those actually not allowed.

Lastly, please note that XX does more than e.g. Foobar to the sense of exploiting bits in the DAC which just the same can just be thrown away. The 96/24 which can be played by Foobar with the April Music (like Stello) DAC is an example. So, Foobar allows it, but it really plays at 44.1/16. This by itself caused by Vista Shared Mode (!) which can make it that. Say, a hoax.

All 'n all, sadly, that other players allow things doesn't say much for this environment.

In the end all can be solved, with the WMP rips as the example again. XX can deal with them, after me for some days working out that format, and convert it back to normal RIFF/ Red Book. FIRST though, we must recognize that things are not right, and how to know it ? There is no way that a bunch of bytes can tell whether it's music data or a coverart photo. Okay, except for what I said before : I could examine the voltage leaps. They can only be normal/legal to a certain extend.

Please keep in mind : even something like Wavelab (which is, rather well known software) doesn't do it right. It destroys the header data according the official format.

I know, all look like excuses, but it is really Vista WASAPI flawing. The only thing I can say is that I can work it out if time allows *BUT* / *AND* if we first know what the wrongies are.

[hybride]

As you say i am not deep into this theorie.
I can understand your explanation about Vista's formal exclusive mode.

Maybe a (to) simple thought for a possible solution;
Can you create a code that verifys - and maybe repair- the -flac extracted- WAV file in a formal (Vista) way?
Only when this 'verify' is 100% then the file is going to Eng#3

[PeterSt]

This already happens for the part that can be checked, although I can expand the checks here and there. Example :

If you'd delete the first byte from the music data part, exactly what you experienced would happen. The byte order now is wrong, and the plus and minus voltage indications are not read and instead random data for that is read. A solution to this which I can apply : check for the file if it has a number of bytes that can devide by 4. Still not waterproof, but better again.
For 96/24 this check doesn't work, and instead now the data bytes must be devideable by 6.

This is just an example of things which can be applied, and many more exist (while all the normal are already in there).

I will do my best ...