No no no, but I already expected that you'd thought I took it like that (didn't know how to make it clear). The contrary, I was really laughing outloud. I mean, if "we" are in the stage of being able to determine that it's not perfect yet, *THEN* we're talking !
And I mean that.

Saying something is wrong (and preferably why) obviously is more useful than saying it's so good.

Btw, might it help, I don't think Upsampling is good. It was at some stage (to the sense of "better"), but not anymore. Might be personal (but I don't think so).

But how can you tell when you are used to Double, which now doesn't work for you ? And don't compare with Mem checked, because that is way different !

Help ...

I forgot to check the DAC Test.

About Double ... Djeezz ... that sure worked, but one of the last things I did was activating this message in "some" case it should (and this was about native 88200 being able to select for Double). And I didn't start (2 hours !!) of checking all the combinations again. But as is obvious to me now, at the moment this check is applied (and Mem unchecked) the file *is* Doubled already, and the check is not appropriate.

I am sorry ...

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.

The following changes have been applied (all Engine #3) :

• It could happen that at the end of a track a (vinyl like) click could be heard;
  Although this behaviour couldn't be copied at will, a good reason was found for it to happen, and this has been eliminated.
  This could happen with albums with non-standard header data.
  
  
• Gapless at Attended Playback didn't work anymore for files with too long "preprocessing", thinking of the combination of FLAC and padding to 32 bits.
  Also, it can be expected that MP3 works out better too in this area, which -honestly- wasn't working satisfactory, and which was blamed to the MP3's themselves. However, a bug was found in this area, so MP3's too might work well now (untested).
  
  
• 48/24 and 88.2/24 files can be played with a 16 bit DAC.
  (96/24 files already could)
  
  
• Since the last version(s) an album may end with "XXEngine3 not working anymore"; although this was not explicitly solved it may be expected it is.
  
  
• It could occur that ChangeWP errored with a "not working anymore", and a reason for this was found and eliminated. Here too, please report if it still happens.
  
  
• With a 16 bit DAC and the Digital Volume at -0dB, a track ended in slow motion through the right channel (and the left channel being silent). For those who had the slow motion in the left channel, check your gear !
  
  

This version, like 0.9u-10, may be perceived as too dynamically. This will be solved (as an option) in the next version.

Edit : Issue : In this version Doubling (and Quad) with Mem unchecked does not work. Also, currenty the Dac Test does not work.

All of you,

I am sorry not to have spent the time on this it maybe deserves. After the current problems (clicks, gapless) have been solved (to which I seem to be very near now) I will look into this.
In the mean time, people who are bugged by this administrator message, please keep on posting.

Peter

First of al big congrats hybride !
Then, I didn't want to suggest this directly, also because of "the" situation (you know ...), but if you read my before post again you can see it's dripping all over from it.

This is hard to tell or predict (in fact, I'm thinking of building in some log).
But that is why I told to check the memory; if it remains the same, it does nothing, and the executed code is really the same.
... I think / it should. But please tell the result of the Mem box and Memory useage.

And note that I will apply the changes according to your twisted brain. I like a twisted brain too, but then from a nice pint of beer.


Now, I asked LydMekk per PM to describe the differences as well, say, in order not to get plecabo'd. The key is in his observations.
LydMekk, allow me to quote you from your PM :


Above text was never implied by me, but shows exactly what I expected (from the code) and what I experience myself. Ok, I *did* talk about it earlier but in other contexts, and some year ago it was excessivley discussed elsewhere, because it is so hard to comprehend.
Note that LydMekk is playing Double/Upsampled, where this shows more than what I like, hence what I find bearable.

I earlier referred to "energy" and stuff, but which is not measurable. In fact it is easy to recognize, once you have the experience; this is about higher dynamics. So, what theoretically is applied now is the "crazy dynamics" as how I called them one year ago, and which came from an early XXEngine3 version in Double and Double/Upsample. It kind of happened by accident, but I never forgot it and how the code was. Now, this has been applied to the normal (not Double) version as well, with the remark of it not being able to express that well there, because of (one of the) explicit "de-jitter" operations not working (like Double would do that). But it is there ...

How do you notice ? well, very easy, you can't play that loud. How do you *really* notice ? even more easy : because your wife tells you it's too loud. To give an indication of the difference : I played at -24dB since the Digital Volume, once we all got used to the level of -30dB (per night), and now I play at -36dB and maybe I switch to -30dB. It just gets too loud otherwise. Not harsh, not disturbing, but just too loud. How can that be ?

Apart from quite some pages in order to (the attempt to) reason it out which I did one year ago, it can't. I mean, take out your dB meter and measure. There is just no difference. Mind you, this is about super transients, which possibly won't be caught by my slow meter. Still I set my volume 6dB lower, if not 12 ...

I can't be sure what it takes from the rest of the equipment to show this, but I know that my SS amps I had one year ago, including my Infinity R90s from back then, showed it easily. But, the band high-mid and tweeter in the R90's are capable of producing very high energy and are very fast ...
I am not sure what happens when the equipment is fed with these higher transients while it can't cope. You just won't notice ? plain distortion ? unwanted harmonics arise (is distortion of course) ? uncomfortable feeling ?

Stupid thing is, that I know that the highst level of "this" is better from theory. Better from the theory of the things I apply in the program, and assuming this can not overshoot, probably our systems can't cope with it ? I don't have the answer to this yet.

Might you have difficulties in recognizing it, try to pay attention to suddenly generally occurring similar things everywhere. In this case it would be about rattling the (wound) strings which every guitar player seems to be keen on (or can't avoid).

For those who think this is good (on their system), I can go one step further with this, although technically I don't know how to do it yet. So that's for later, when I have become more smart.
For those who think this is not good, I will create a checkbox "High Dynamics" for the next version. As how the code is setup now, this can easily be applied without changing the SQ in the base of either. Maybe I should call it "Low Dynamics" because I keep on thinking that the latest (0.9u-10) is theoretically better and should be default.

Peter

... it still aint right. I don't think I will manage today.

GerardA, thank you *very* much for your attention and reporting. I know it didn't look like much, but I was able to solve everything with it.

Now I must test some 100 combinations if they all play, and then I will put up a new version.
Again, a big thanks.
Peter

GerardA,


Well, I must say, I can copy that behaviour. This happens with my beautiful attempt to play in the 16 bit domain, while actually the DAC is more than 16 bits. Is that so strange ? no, I don't think so. It would even be normal.

Must be me afterall. But how ? out of all I did this to 100% leave the bits alone as a special case (you actually ask for padding, but since the Volume is at -0dB that would be stupid).
Sorry I accused your soundcard.

My low pitch is through the right channel, the left channel being silent.

Btw, I now recognized that SeVeReD most probably has this too ("it's trying to catch up" or similar he said; it indeed looks a bit like that).

hybride,

I have been thinking ...
What do you hear as a main difference beteen 0.9u-8 and 0.9u-10 ? Or if not 0.9-8 which you compare to, which version is that ?

If you can describe it, I can easily put back what should make that difference, and then you can try again ...

For you too counts, that checking the Mem checkbox should go back to "the" old situation ...

(For me) This is hard to say or predict. And as you implied : how to test it since my DAC has no wordclock connection.

I think though that clocking anything by means of the wordclock connection doesn't let perform the soundcard or DAC better to the respect of jitter. The jitter we'd be listening to will be the inherent jitter of soundcard / DAC, and that isn't going to be improved by external clocking (or slaving etc.). Again, that's what I think.

What I also think is that we all need a dose of "both legs on the floor" thinking. I mean, since it is known that DACs exist of 20ps and less, they should be infinitly better than a 1ns DAC, right ? but are they ? Oh, they could, but not per definition.

This was my 0c.

I already did that, but it doesn't play in Exclusive Mode with my soundcard (and it sounded "grey" in the mean time).

I've been working for hours on it yesteday, with no solution yet. I think I can tell though that it must be "me" doing it. BUT :

It must be your soundcard/driver *showing* it.
For sure I don't do anything (wrong) with one channel only, but the pitch changing at the boundary of reading the next track is something that's prone to the means I setup the software. In a most "normal" case all should start to play at the wrong pitch (at that boundary), and it is my guess that in a not so normal way (which would be everybody but you and one channel ) sound just stops.

Funny thing is that I found for 99,99999 % sure a bug in the compiler, which is 100% related to this subject (and the stopping and the clicks I think ... in fact the unexpected behaviour). Your observiation (pitch changing) is key to this, otherwise I think I never would have found this. Praise your soundcard !