As said ... Otherwise I won't be able to keep track effeciently of your various remarks !

And ... sorry about the more buggy version (0.9s-0). It took me the whole afternoon just in trying combinations ... there are many really.
And I guess I promised too much to have it ready this weekend.

Peter

I may see ghosts, but the track (name) selected in the screenshot (as the only one) does not have a space behind the dash ?
that won't matter, does it ?

Wow ...

And Chris, with "stop after one track" you mean at unattended playback, right ?


Or ?

VST users report glitches and everything with Q processors, although they blame it on the software they use.
In those cases, *not* spreading tasks over processors, solve their problems.
Besides that, various benchmarks (although from the same environment) show that total power is not more that 2 core processors.

So in theory -obviously- Q processors are good, but in practice it often doesn't work out.
In this case I'm copying orthers' opinions. But Google shows just too many of them ...

Better (please) put that on the forum ...
 

Edit : Never mind this. I thought I responded to a PM ...

Hi Gerard,

Could you please try the same track with normal attended playback ? (thus not ticking that new checkbox)

Thanks,
Peter

No ... I will try to solve that ASAP Leon.
MP3 will have the same problem I guess.

Peter

Unless you have other reasons than Audio ... don't go for the Quad cores ...
They have problems with switching procecces from core to core and bring nothing effectively. I.e. many people report problems, and I see no people with joy.
But that may be a matter of Googling. 

Hi,

What do you mean, "manually" ? (this is kind of important I think)
And how did you set it in XX ?

Hahahaha, this is probably about the "combinations" I mentioned in the Releasenotes. Not sure though ...

When you want to change something like Invert or Q1 settings, click Stop, change the settings (load your tracks), and click Play.

In upcoming 0.9s versions those things will be possible ...

Edit : Sorry, I was responding to

Hi,

Well, to be honest I vented by opinion this morning, but I scatched that because I didn't think you were interested in that, also looking at your budget issues ... So I started with "maybe I'm snobbish, but ..." 

And then I said something like a "DAC" like a Fireface (it really being an external soundcard) not fitting in the row of, say, audiophile DACs. Nor the Lynx's, nor any of the other $500 the "AA people" often rave about. They are just in another leage, and "us" who use a Fireface, only use it to pass through (and reclock) SPDIF ...
Now, is that snobbish or what ?!

Furthermore, it needs the real experience with the DACs you mentioned to have a real opinion.
Anyway, also looking at your response in this other topic (Question about direct I2S DACs) you seem to be a good candidate for my Audio Note Signature-3 double modded (tube) os-DAC. Hehe. It still would need an SPDIF connection somehow ...
I only replaced it with the (indeed very good TwinDAC+) because I specifically wanted non-oversampling.

Peter

Because of complexity and sheer unlimited combinations to test, it is expected that bug fixes for this version will follow. I few more features are planned as well.

Well, here is is ... the impossible SQ of today ... as was anounced here.
If you did not read it, please also see the Prepare for Christmas topic, where I was seeking for lacking highs in (digital) playback. Well, cover your tweeters ! 

The new means of achieving the new are of good sound was done by means of eliminating the "Controlling Section" (in fact, XXHighEnd) just at all.
Engine#3 only ...

So here are the new features :

• Unattented Playback
  
  Comprises of more than just that;
  First of all tick the checkbox "Play Unattended" in the Settings Area.
  Load a Tracks in the Playlist Area as usual, and click Play ...
  The XXHighEnd screen will disappear, and you will be in the blind now. But hey, just close your eyes ...
  
  You can restart XXHighEnd though, and it will show the track which is currently playing.
  Just click Off to let all continue as it was.
  Click Stop if you want to stop Playback.
  Or load other tracks (you might want to click Clear first) and just click Play.
  
  You will notice that FLAC and MP3 and tracks with diacritical marks will take a long(er) time to preload. Unavoideable.
  Cue files will work too, although currently right after dragging the big WAV onto the Playlist Area ans clicking Play there will be an error. Just click that away.
  
  Generally : After clicking Play a red cross may appear in the Playlist Area followed by an error. Here too : just click it away.
  
  
• A PlayerPriority "Low" has been added.
  
  
• At Unattended Playback the set PlayerPriority is now applied to your whole system (you can set it to Low), except for XXEngine3, which receives the ThreadPriority as usual (you can set that to RealTime).
  The Priorities are reset to Normal when playing is stopped by means of XXHighEnd. So note : this will not happen when Playback is just finished !
  Also note that indeed all are set back to Normal. So might any process have had another priority when things are changed by XXHighEnd ... only a reboot will set things back to the default settings.
  Critical system processes will never be touched though !
  Edit : Also see But the new Priority Scheme changes SQ just as well ...
  
  
• When Stop is clicked, the current contents of the Playlist Area is saved to the !CurrentlyPlaying Playlist (no matter sound was actually playing or not).
  At a next startup of XXHighend that Playlist will be loaded automatically. Just click Clear of you don't want that.
  Note : Clicking a track and click Play for Unattended Playback will *not* start at that track. Such playback will always start at the top (will change in a next version).
  
  
• 3 new Processor Core Appointment Schemes were added, while Scheme-1 acts the same as with the before versions.
  The explanation on how Scheme-2, -3 and -4 act differently is kind of useless, but they do, and they attempt to help people with glitches of any kind as impeeded by lack of processor power. Just try if it helps !
  Note that it may influence SQ just as well ... this wasn't tried yet.
  For a 4 core processor system, the schemes are applied differently than for a 2 core system, all in order to spread capacity at best, while maintaining the necessary "power" (hum) for XX.
  
  Edit : As found so far, Scheme-3 sounds significantly better than Scheme-1.
  Edit : Scheme-3 is mentioned two times in the combobox concerned; Choosing the second Scheme-3, actually selects Scheme-4.
  
  

Important (I think) : The first hour you might think "huh !, this is nothing for me !!". It might even take you a day to get used to the different sound. It will not be what you are used to whatsoever !
But ... try to appreciate all the cymbals and hi-hats flying around. I think you can't do without them after a while.
Then try to imagine that this all might just as well be normal ...

Oh, remember, again no DSP and just bit perfect payback.

Have fun !
... and please let know what you think of the sound.

Edit : See : How to play Unattended with 0.9s-1
And : My own settings for 0.9s

Peter

It took some longer than expected (isn't that always ?). Should be 30 minutes now ... (making Release Notes).
That would be 5:55pm here.

Hahaha Russ. Bad luck you have. And you'd be really in bad luck when I finish it after 6pm tonight ...
But no, I'm working on it. 4-5 hours maybe ...

Peter

It will be my english Andrey, sorry !

I agree with all you say, and of course the jitter we measure at the DAC is too small to incur for the jitter I implied (and I think I put a "(?)" behind that somewhere). Also, there is more too it than an already too large post can describe, e.g. my presentation of a "computer clock" which in fact is totally unrelated (so that was for visualization). And btw, also note that somewhere else (at AA I think) I pointed out that the jitter we generally talk about is to be measured at the analogue side ... (just your story).

IMO it is too complex to just write ahead (and brainstorm), because remember the subject : XX playing and influencing the pits on the burned CD. So I am (or was) just trying to find reasons for that, which all didn't hold. Note that the normal jitter (occurring at the analogue side) could NO WAY influence your burning process, unless it's the soundwaves in air doing it. Hahahaha.

Maybe we should stick to that ... it can be tested easily (by guys like you).