Problem solved ...
Another Vista quirk; Some temporary file stayed without official notice. 

In the next version there will be anticipated on this.

1. Assuming you applied the Run As Administrator thing ... could you revert that and try again ?

2. Also, do you take the time to wait for the track with diacritical marks to load ? ... they take longer ...

3. Now I think of it, you might have .wav tracks in the \USERS\[your pc name] directory ... as explained in the Can't drag files from Explorer onto Playlist area topic.
Maybe look for this first ... which by itself would be related to the Run As Administrator thing. So if this is the culprit, either 1 or 3 would help, but 3 (and removing those wav files) would be the desired solution.

Gerner,

Offline we "determined" that there would be a problem with diacritical marks. However ... not here.
Something must have changed to your system, but I can't think of what.

Since the real thing changed is the Processor Core Appointment ... do you have the same problems with the checkbox concerned (Settings tab) NOT checked ?

Hi Leo, ... more connections. That's all (and maybe the possibility for Firewire800, control the thing from two PC's (with Firewire400)).
For Pro users this also comes down to more ADAT channels.

Peter

Interesting ...

I'd say the only reason can be CPU useage ... but then very specific. I would never had suggested that this could be a problem for Q1 values, although thechnically it would be true.

I assume you have normal (total !) cpu useage of, say, 3 % during playback, with 0% in the "XX Core" ?

Btw, I only now see that you are talking about 0.9m-1 and not about 0.9m ... is that correct, or do you actually mean 0.9m ?

To be honest ... I myself have 1 glitch in the two or three days. But I think I always had that.
Anyway, once you have 1 or more per CD (and the rip is OK), do not take it for granted. Something must be the matter.

Chris' system is a good example; no glitches only at 256 samples latency, while my (and I think all Fireface (which Chris has too)) systems can do 48.
That's why it's good to ask, and good to exchange the data.

Gerard, thank you for the sig.

I don't think this is related to Gerner's problem. I can copy the behaviour you described. All is caused by too many presses of (e.g.) next within a short time.
Will be solved in the next version  ...

Gerard, please put your setup in your signature ... (so I can draw conclusions better).

Hi Gerner,

If you could proove that this was not so with 0.9m I would be very happy to hear that. Or when 0.9m does not make a difference ... I'd be even more happy.

Peter

Hey Bert,

You know how much I appreciate it when it's coming from your mouth as a great critisizer, so thank you very much.
But I also want to thank you for making it possible to *hear* all, through a set of great amps and speakers ... yours.

A funny thing is, it was only last week when me and my wife very explicitly told to eachother that we would not know how SQ could be improved since we perceived it as "real live" or better, at comparing/listening through stage digital mangling which already sounds worse after amplifying. But then last weekend came, and it happened again; a not so minor improvement.


I'm afraid it will not end here. At least I hope so. It becomes hard what to look for though.

Peter

As the title says ... at last stop of sound and the withgoing message "Engine #3 did not start within the expected time" has been solved (it took so long because I just could not find the cause).
What comes with it is a one "glitch" sample at Gapless which was found during the process of solving the above (in 50% of cases this happened).

Lastly, the text field for entering the Music Root (Settings tab) moved out of position at dragging the form size vertically. This has been solved.

No changes in SQ to be expected.
Edit : Wrong ... SQ just will be better for those who could not reach lower Q1 levels, but can now. Also see About 0.9m-1 ...

Important : If you are new here, do not forget to read XXHighEnd Model 0.9m (Implements Processor Core Appointment) before installing this version.

Current issue (must be since 0.9l) : The coverart in the right top corner sometimes won't appear, while at the same time the empty space won't be used by the track data. This (not always ?) can be solved by restarting the player. It seems related to the search function (Library tab) and loading albums or tracks from there.
Don't forget that clicking on the tabs should restore the coverart in the rioght top corner, but this now conflicts with clicking the Playlist Area tab just for showing it.
Will be solved in the next version.

Chris,

All is relative; When you use "about nothing" from the PC, like XXHighEnd using in the areas of 0,1% CPU and together with other services, say, 3 %, you'll gain 3% on eliminating the services. This, while the fans start spinning up at maybe 30% ...

I will keep this in mind Chris. But fans won't spin slower because of the minimalistic use of things already (hence, taking things away will not do anything according to heat).

But Gerard ... although I can't (and won't) prevent you from doing those things yourself, this is not exactly the idea;
What *is* the idea, is that all happens in a controlled fashion. Example :

When someone is bothered by harddisk acces during playback (or thinks he/she is), I could shutdown the "service" which provides harddisk access. A next thing (but earlier) would be shutting down everything which urges for harddisk access, otherwise you'd get errors. And so on. Now, when the *audio* system needs the harddisk (end of track etc.) all has to be started up again, and the software can easily do that (at the appriopriate moment).

Note that this is just an example, and a not much realistic one. But it explains how far things could go, if done in a controlled fashion;
You yourself never could shutdown the service that realizes harddisk access. You'd get errors all over the place. So, the "how far things could go" is the key here. By means of software control it could go way far ...

Oh yes. It's also easy of course to shut down the whole PC. The problem would be : what could that be for *your* PC ...

The only thing I take away currently is sqlservr which creates a once per 60 seconds attack once the PC fell asleep decently (or something, but not hybernating).

I've been thinking about a suggested list of services to shut down (the user ticking that), but IMHO it could be too difficult for many people. Remember, the people I like to reach are those who stayed far away from PC playback, but now can't avoid it anymore, hehe.

Personally I don't have experience with what to shut down (when !!), jut because - as you know - I always thought it was stupid in having to do those things. But since all matters ...

Note that I can not only shut down stuff, but also bring it to live again when necessary ...
So in the end it's a matter of sorting it all out.
A list to start with would be very good of course ...