XXHighEnd

With 9z82 on W7 in unattended I keep getting "Failed to set sample rate" error messages using Windows 7 and the music stops. Mostly this seems to happen at the end of a track. Sometimes (but not always) this is followed by a windows message that Engine 3 has stopped which actually means that Engine4 has exited (ie when the XX GUI reappears the blue button is off).

The following does NOT make any difference to the problem:

Low latency (SFS=1 Q1=7) versus high latency (SFS=200, Q1=20 etc).
PA selected or not

This is a fresh and minimal Windows 7 install.

Basically I cannot realistically use Unattended any more and I have run out of ideas as to what to do next to find out what the problem is.

I used to get this problem before in W7 with previous versions of XX but never as bad as it is now.

With 9z81a on W8 on a separate disc there are no problems at all.

I have just re-installed 9z75 on W7 and that also has problems it stops after a few tracks with no error message.

Paul

Paul,

With which NOS1 driver is this ?

Peter

Peter - 1.0.3 which is the one you sent me.

No problems under W8 lots of problems under W7.

Paul

Ok Paul. Can you please check whether 1.02 on W7 makes a difference for you ?

To keep in mind from another topic : I just mystically have these same problems under W8 (with 1.03 obviously).

Regards,
Peter

Peter - can you please email me 1.02

Cheers

Paul

Done.

OK Peter so I have installed 1.02 and it makes no difference. Still I get the error message.

Paul

Good! At least for me, not for you... I do not have the problems you describe.

I have 1.03 installed as well.

Bert

Ha ha - I found a work around that Peter may find interesting.

I could just tell you but I thought I would provide the background by way of artistic licence as it took me so b.......y long (and two fresh o/s installs) to work this one out.

Playing Jazz or Blues albums the "Failed to set error rate" message occurs maybe once per album.

But playing say Bach Cantatas is virtually impossible. The "Failed ....." message occurs before the music even starts. Or maybe with luck just one track plays. And it is the same story with other classical music albums they are virtually impossible to play without the "Failed to ...." error message.

All this is in unattended playback attended is no problem. Also this happens for me only in W7 not in W8. And the NOS driver version makes no difference.

So why is the problem so much worse with classical music?  first thought - something to with the music content - unlikely as the cantatas are simple content.

So after an evening at a friends house listening to music (and a few beers) I got home still with the question on my mind what the heck is different about classical albums?

Then I had a really a stupid idea but anything worth a try. So I copied all 22 cantata tracks into a temporary directory and renamed each track "01, 02 etc" I tried to play them but lots of new error messages and playback would not even start. AH HA so track title is important. So then I changed the track titles to "Track 01, Track 02 .... Track n" where n=22 in the case of the cantatas ha ha. Well I was also thinking it could be something to with the number of tracks.

Eureka playback perfect in unattended - no error messages at all. And that seems to be it - classical albums tend to have long track names and that is what seems to cause the "Failed to set...." error to occur.

So the answer is simple all I have to do is go through all my albums (2Tb worth) and reduce the length of the track titles.

Ha ha.

Paul

Paul, I also have 2 disks of 2TB, but I could squeeze it into one small one when I convert them to MP3. Is it all right to send that to you so you can rename my tracks as well ? Thanks man !

Peter

And oh, when you send back the disk, stuff in ALL the booze you have laying around. It clearly is NO(t) good for you. I can let UPS collect it.

Shouldn't Cantata be played backwards ? or am I now confused with something else. Hmm.

Ha ha Peter - but why would the length of file names be implicated in this problem? or maybe it is something else I have done?

Or maybe I am dreaming?

It has to do with DOS filenames longer than 8 I guess ?

Alain

Paul, now seriously, I can't imagine a thing here. But please try this :

Create the same file names as you did (or copy the ones you already have) into a structure which matches the location where it did not work. Something like :

\xyz\MyClassicalAlbumNotworking\Original.wav
\xyz\MyClassicalAlbumWhichWorks\Track01.wav

Then reboot (!) and try again.

But be sure the issue is easily mimiced so it won't be any other coincidence that it now works. So maybe first try the reboot and play the original files and see whether it is again difficult to play them (further like you were used to). If so, then reboot and try your trick.

Curious for the result !
Peter

Peter OK I set up the file structure exactly as you say above - the result? the folder with the long file names will not play in unattended at all I get the "Failed to ...... " message before the music even starts. The folder with the Trackn files in? - well that plays perfectly no error message at all it plays all 22 tracks with no error messages.

By the way reboots do not change the result it is totally repeatable. They long file names are not difficult to play in unattended they are impossible!!

Over to you

Cheers

Paul

Ok Paul. Switch On Logging, cause that message to be on the screen, and right at that situation grab the XX, X3 and X3PB log files and post them.
Maybe we need another round of this because with Loggin On they won't play anyway with a very low SFS.

Peter


PS: Once step further with this, and renaming them to SoundsGood01.wav wil make them sound better !

Hey Peter - emailed them to you

All the best

Paul

Received Paul. Thanks. Will look into it tomorrow.
Peter

Ah interesting I am just now listening to Beethoven with long file names in unattended and no problems it plays fine. So maybe it is something else about Bach Cantatas - but there are other classical pieces I try to listen to that just will not play in unattended. The only thing in common is that they have long file names but maybe that is not the problem - mmmmm very strange.

Update: bombed out after three tracks still better than Cantatas though

Paul

Hi Paul,

I was wondering what would happen if you take the names that seem to be the culprit and rename some other songs (from another album, another artist, another genre) with these problematic names and play them like you usually do ? If it behaves the same with these songs, at least it would mean that the titles really are the culprit, presuming that the songs that you entitled with these names do not have the same behavior prior to this test ?

This test could also be applied to anyone that does not experience this. Say you send me only a list of the titles that are problematic, I could test them here...

Alain

Edit: Thinking about it, maybe you could point me to the album ? Titlle and all ? I will find it on the net and try this for myself and report back...

I don't know whether this is going to be the most puzzling issue ever, but it well could be;

For starters, this dedicated to NOS1 users. Just to make that clear.

It will be related to these long file names, but there is no normal clue as to how.

The sampling rate status of the USB Interface is obtained, and the first what happens it that it is presented not equal to what is wanted. This already seems wrong to me, assuming that Paul not just (and always) has played something with another (output !) sampling rate. IOW, the USB Device does not respond how it should.
Next, because the sampling rate is presented to be not as should, it is set. This is attempted for 1.5 seconds in a loop of 15 times. This fails (too).
And then the message is presented.

It is noteworthy that I saw this often under W8 with the special environmental thing that I in there I had the WiFi-special driver running.
If I combine the two situations, both can be about something else preventing the USB Device to respond.

Since for Paul this is about the long names, it is important so see how they may work out in wrong fashion. And ...

... After typing this I already see it. It does not work at all.
Here's one from my own log file :

Short Name initiated-1 : I:\PS\(CLASS~1\(13)RE~1\Bach\BACH-C~1\01-CAN~1.WAV

While this (virtually) comes from Paul's log file :

Short Name initiated-1 : I:\PS\(Classical)\(13) Religieus\Bach\Bach - Cantatas 140 & 51 - The Bach Ensemble, Joshua Rifkin (1987)\01 - Cantata BWV 140- I - Chorale- 'Wachet auf, ruft uns die Stimme'.wav

More literally though, Paul has it like this, and watch the "1." in there in front of the "chorale" :

Short Name initiated-1 : I:\PS\(Classical)\(13) Religieus\Bach\Bach - Cantatas 140 & 51 - The Bach Ensemble, Joshua Rifkin (1987)\01 - Cantata BWV 140- 1. - Chorale- 'Wachet auf, ruft uns die Stimme'.wav

This looks suspicious to me.

I think the actual culprit has been found (name is "illegal" so to speak), but it is the OS messing up. So, that it won't convert to a "Dos 8.3 Short Name" is one thing, but that it next messes up badly elsewhere is something else. At least that is to be the conclusion, because all what happens is that the USB Device does not (seem to) respond.

I think I will be able to build in a check for this (output from to Short Name conversion is the same as imput -> wrong).
First Paul may try to tweak the name so it works, with the attention to the dot in there, but it could be something else.

And Paul, before you notice that nothing is going to help, what about Dos 8.3 Short Names being shut off at all ? (but that wouldn't go by itself suddenly I'd say)
(How to restore Short Dos 8.3 names (http://www.phasure.com/index.php?topic=982.0)).

Let me know what happens.
Peter

Ok, the next version checks for the conversion to ever have happened.

Just got in and need to catch up on your post above Peter but I quickly tried:

1. I removed the fullstop in the filename - no difference still got error message

2. I then removed all coma's and dashes - and now it appears to work OK.

So it would appear that it is not just the length of the filename.

I will investigate further.

Paul

Peter,

I switched DOS Short Names off but I had to use this command to achieve it (disable8dot3 0 did not work as it was not recognised): -

fsutil.exe behavior set disable8dot3 0

No difference I still have the same problem error messages still being generated - but see my post above.

Cheers

Paul

Paul !!!
It looks like you are telling me that you shot OFF the short names, while they should be ON.

And now you most probably destroyed all of your files.

How to restore Short Dos 8.3 names (http://www.phasure.com/index.php?topic=982.0).

Man ... tell me that this is not true.

Peter

Just to be sure I went through all 22 tracks and removed everything that is not a number or letter (so comas dashes and fullstops all removed). So the track names are not much shorter but the album is playing just fine now - no problems.

So it appears that it is not a "short names" problem.

Cheers

Paul

Of course it is.
But I am not sure whether you responded to my last post.

Peter

I just read it now. My master music directory is on another computer where I add albums as and when and then "robocopy" mirror them over to my music computer so should not be a problem other than time it could take me to copy the whole directory over.

I also have another disc (disconnected just now) in the same music PC with the whole music directory on it.

Peter,

Surely disable8dot3 set to 0 is what I require in other words the short names are created from long names facility is on which is required because XX uses the short names.

OK so I just checked the registry entry on my music PC and HKLM\SYSTEM\CurrentControlSet\Control\FileSystem NTFSDisable8dot3NameCreation is indeed set to 0.

So then I copied the Bach Cantata album (with the long file names including comas dashes etc) from the source PC into my Music PC music directory but it does not solve the problem I still get the error messages.

Your instructions are clear (unless I misunderstand)


surely disable8dot3 1 would cause the problem of deleting all the short names?

Paul

Paul,

It is just that you are super confusing ...
You said you switched OFF the facility. That the command you used swicthed it On is something else (and trust me, I check words, not commands per se).

Next, why ever shut it On when it should be clear it's already On ?

Next, why confuse the whole thing not working because of whatever characters in there with any necessity to switch it On (or Off according to your earlier "words").

Lastly, I think you told that removing those characters helped. So ? Done.
Or ?

I guess you missed the fact that the conversion (which is a sheer OS thing) can fail.

How this compares to no problems on W8 I don't know. But maybe you did not say that. So to be clear, these Cantatas never will have worded - not in an earlier XXHighEnd version as well. But if that is is different, let me know (I am not aware of changes).

Regards,
Peter

Apologies if I am super confusing - I put the actual command in that I used to be clear.

And no Peter I did not miss the fact that the o/s conversion can fail. And I have not missed the fact that it appears to fail with the commas dashes in the file name but not when they are removed. So maybe the bit where it strips those out is not working who knows (and I am sure I don't).

And to be absolutely clear there are no problems at all with W8 (on a completely separate disc) which I have said before.

And for sure I have listened to XX in W7 with previous versions of XX and not had these problems before.

So perhaps I did not have the OS problem before even though it was loaded from the same disc in exactly the same way.

And on top of all of that it has been a really bad day because Arsenal lost to Spurs.

Paul

Paul, don't feel bad.


As you can tell by now I am not so sure at all. I won't ask you to point out that earlier version where it worked, but until you don't I remain right. I hope that is okay with you !

Do notice :
You'd need to play the exact same (which means 100%) with any older version of XXHighEnd and this includes the file type, the "intermediate" drives used and all. So for example, with a .FLAC this won't happen and I think that without any "intermediate" drive (like the Playback Drive or Copy to XX Drive - that kind of stuff) it won't happen either. What won't happen ? the necessity to make those Short Names of it. You can see it happening in the XX Logfile; search in there for
Short Name initiated-1 :
and you will get the grasp.

Enjoy your Sunday evening now !
Peter


PS: Just cut out the whole football and all your days will be better. :yes:

I don't feel bad - not at all - (I assume you mean the football) actually I much prefer rugby - football is a game played by girlies ha ha.

But one thing you say is interesting about FLAC files. I had most of my files as FLAC until recently - but as they take time to convert in the playback process I converted them to WAV and I did that recently. So maybe that explains why I am getting problems now. But what I do not understand is why others are not getting the same problem. Or maybe they are - come on others let us know if you get the same problem.

Nick was here yesterday and he has "stopping" problems in W7 but he is focused on other things so not reported it.

Maybe the last frontier is the barrier that Microsoft presents between Phasure and a repeatable secure great musical experience??????

Cheers

Paul

Hi Paul, did you get my PM ?

Alain

Peter - I have removed intermediate/playback disk references (i.e. no longer used) and there are no more problems. SQ is still as good as I could imagine so there are no drawbacks really.

The only problem now is that having pressed play I now have to run back to my chair to get there out of breath as the music starts.

I still get occasional stops with the "Data did not arrive in time message..." but at least I know that I am not the only one!!!

Cheers

Paul

We have a timer for that (counts down) at the bottom. That mini slider. I think max is 60 seconds, which would just allow you to grab a beer from the fridge underway.