XXHighEnd

Hi Peter,

When I run in Unattended I get the "Failed to set sample rate" error message at the end of a track and then music stops. To get XX working again I have to unload Engine4 from memory and then run on Attended for a short while. I can then use Unattended again but only until the end of the next track when I get the error msg again.

It does not happen in Attended. Changing to higher latency settings i.e. SFS 400 makes no difference so it seems it is not a resource issue. Any ideas?

I do not get this problem at all running in Attended

Reboots make no difference

Cheers

Paul

Paul,

All I recognize is that this looks to be a W8 issue.
But how can you complain about that using W8 for a longer time by now ?

So I don't get this ...
Help.

Peter

It did not happen very often to start with now it happens more frequently.

And now having listened to one album in Attended I can now play OK in unattended - at least for a while. Very strange.

Don't blame yourself. Blame me or Bill Gates (uhm).

You don't want to know how much I have been puzzled the past few weeks.
Anyway blame me to be on the safe side.

:drinks:
Peter

Peter - the odd thing is that this error message is intermittent. Could that point to the DAC maybe hardware or driver - just wondering?

Paul

Paul,

I didn't look into it yet, but I was going to dive into something which looks too slow. It is not only about this "failed to set the sample rate" but one other message as well. It also feels like too much memory is consumed, which I *did* notice in the end, though from Windows herself (that "memory leak" I talked about in the other topic).

At this moment I am not sure whether a reboot would have helped, but at some stage I more got the error than I did not. It is there where I hopped back to W7, so I didn't proceed on it.

It has my attention (is in To Do list), but if you have further data that could help, don't hesitate.

Thanks,
Peter

When I had the problem I did reboot but it made no difference I still got the error message after the reboot. Then, after I reported the problem and had run Attended for a while for the rest of the evening no problems it worked in Unattended fine.  :scratching:

If I look at this, it can only be about additional disk activity needed to get that track.

That said ...

What if this about the RAMDisk ? point is, I myself did not receive these messages at first. It is only from the last 10 days or so (using the RAMDisk). I did change XXHighEnd though, but you "did" not obviously.
Do you use one in this case ? Which ? how ?

Another strange thing : after the last track played in the evening, the next morning the message (failed to ...) was on screen. I don't even see how it could have gotten there, because it needs something to play. And Santa is out of the country by long now ...

but

When that RAMDisk plays tricks, it could have happened.

Ah now that happened to me last night. I pressed "Stop" on XX and went out of the room to do something. When I returned the "Failed to ..." msg was on the screen. I do not use RAMDisk and I have to say I thought I was seeing things but now you mention I am sure I was not. I will watch out for it happening again though.

Also I was just wondering if this linked somehow to the problem I have where XX stops randomly.

P

So that is the same what happened to me.

I can tell you ... these kind of things happened to me up to the painful level; now I have been using W7 for the third day and no single problem to be seen. Same XXHighEnd version.

... Which doesn't tell all, because in W8 I can have tweaked too much "down".

Paul, if it is easy for you to copy the situation, try without Phase Alignment and tell me whether it makes a difference. Not that I expect it to make a difference, but if it does I know better where to look.

But as you can understand yourself by now ... no Stop is to change or set any Sample Rate. Still the program goes that route.
In Windows 8 only ?
:scratching:

I will try without PA but will have to be tonight - also the law of sod always applies to me so it is very likely everything will work OK when I try to test it but anyway .................

The good thing is that at least I know now that this is not just happening to me !!

What about others ??

I really thought it happened to me only because of my strange setup as of now.

I was wondering if it was something to do with my failed Bluetooth install that ended up doing something nasty to the OS and although I restored the o/s to an earlier time I just wondered if there was some residual problem hence the clean install yesterday.

I've had W8 installed in my office system for nearly two weeks now. Although I've only used it only a few days in this period, I really have used it for pretty much the whole day. And no problems at all. However, I can't remember how much of this time has been in Attended vs. Unattended - I suspect mostly in Attended.

It's playing right now in Unattended and I'll keep it this way to see if I can replicate the issue.

Weird sound though - almost as if all leading edges have been accentuated. Weird, but strangely attractive...

Mani.

Last night I had a chance to finish a(nother!) totally clean W8 install and setup XX. Afterwards I managed about 3 hours listening and - no problems at all. No error messages, no random stopping and the o/s is now notably faster than before particularly during file conversions etc. Certainly before I would have had some problem during 3 hours even on a dgood day.

But it is too early to draw conclusions the same problems could crop up again. Tonight (if I remember) I will leave XX running overnight to see if it keels over during the night.

With the previous two W8 installs I had the "Stopping" and "Failed to set sample rate problem". With both those installs I had attempted to install the Bluetooth remote control s/w and both had run into problems with the o/s requiring a restore to get working again.

Paul

tonight I left xx running in Unattended for 4 hours continuously and no problems - no stopping and no error messages. It does look as though the Bluetooth installs previously could have been responsible for the problems.

Paul