XXHighEnd

Hi,

Peter knows already from previous XXHE version(s) and with 2.03 this 'problem' is wider: Whenever I have a file name containing diacritic character
like "ñ" or "ö", perhaps several others and with some characters from local language (Serbian Latin - previously was one character only, now few others)
I get the message "Not enough space on Playback Drive". Playback drive is ImDisk RAM disk of course. Tried to install different ImDisk version, same again.
I'm always installing standard, US language, US keyboard Windows, be it W7-W8-W10. Is anyone else having this playback error?

After clicking away above error message, clicking on next or any other song in playlist, I get another one (both pic attached hblw)

Not only George, but me too are desperately hoping for someone to respond.

Please don't hesitate, anyone who recognizes this !

Thanks a lot,
Peter

George,

It could be a good thing if you describe what you think what could be all different from everybody else.
Context : If I try your tacks all is fine.

Suggestions :

Operating System which is natively not English but another Lange (like official German which can be bought and which is different from e.g. W8 Pro which can install different languages but which is English in the base).

The selection of another language (in the Pro version) other than the one which was shipped natively.

Whatever locale (country) settings you apply and of which you might recognize people usually won't do that.
(maybe it is about someone else but I recall that you guided me/us to stuff like that for comma/dot notation ?)

Is it actually so that this only goes wrong with IMDisk ? I doubt that ...

A special type of Harddisk. Notice that all what is USB and NAS can already be special.

A special means of formatting (like you could apply EXFAT while NTFS is standard).

And so on.

Peter

Hi Peter,

The only recognizable trace in your questions would be: I use exFAT formating (since this was in (me thinks) in your very short bat script)
All other remains original, perhaps just change Time Zone and run further to installation of NOS1 drivers, SW needed and XXHE of course.
So, exFAT as disk format, yes.

I am not talking about the Playback Drive re exFAT. Just the music drives ...

No Peter, standard NTFS, 2x2TB WD Red.
Eventually I change date format to dd-mm-yy on "AudoPC". Tried Notherlands locale on it :)
PC holding the music library is very similar, just changed numbering to EU style (dot for thousand, comma for decimals)

What I can add is tt XXHE on "AudioPC" (or any other app actually) has no write permission to music HDD's (on other PC) so I get errors in XXHE when adding a song to a Library.

Ahaaaa ...

But you say it as if this was done on purpose by you ?

In sharing options I did granted full access (@ 'workPC') and in reality there's no write allowed through local network. So I continued like that.

Small language problem perhaps;
Now I still don't know whether you do that on purpose or whether you rather had that solved.

I'm already for 99% convinced this is the problem. I only need to find out "how exactly". But look at that error on the .DAT file ... and didn't I point at that before ...
(puzzle starts to close)

Peter

Sorry, had to go out for a while (will have to again, soon)

As said, I left it as it is - no write permission from other PC, in this case no write from "AudioPC" to "WorkPC" where music files reside. This has
to do with my need to re-build XXHE Library since I moved some albums/folders from one to other HDD so XXHE metadata are not correct anymore.
I need to delete all meta info and let XXHE build new main Library file/directory, whatever is needed.

This second error message we did mention in e-mails and it was "the most unexpected error" as you said :)
And it points to A: disk, RAM HDD of course.

So is it allowed that this no-write "issue" is going to be solved ?

Yes, I will 'fix' this 'not allowed writing' on HDD's containing music :)

And I'll make a quick test: I'll copy whole album (seen above) to the partition on 'MusicPC' an try playing the song #4, named "Sueño Latino", a 'problematic' one, directly from AudioPC.

Same error. No space available  :(

Edit: above 'MusicPC' should read 'AudioPC'

Replaced "ñ" to "n" and file plays normally...

Understood about the 'MusicPC'.

Copying like you just did is a bit dangerous when it is about rights (this is all "since Vista" stuff).

Can you try it the other way around :
(but this is not waterproof for proving)
Have a normal file name(d album), copy that to the Audio PC and now change an n in an ñ.

If it now plays it tells about a "rights" thing.
If it does not play it doesn't tell so much because you still copied the file from that other source.

PS: Don't give up as I hope you'll understand that thare are more users *with* such characters than without. Only English (/ American) will be without it for the native language, while they still may like e.g. French music.
Read : it *has* to be something on your side and when we found it finally, we'll have a laugh over it.

And a drink of course !

I don't think you answered this ? Easiest to try for you could be a USB pen of which you don't need the contents.

I had another idea and the results:
- Copied album to some memory stick and load it to XXHE directly on AudioPC (using free connector on PCIe USB card)
 (AudioPC is headless, controlling it through RDC). Gues what? File plays without any complaints from XXHE!
- Now copied album from MDD to HDD on AudioPC
Guess what? Again, the same complaint from XXHE - Disk Full :)

So, it is rights related but how, shoot me :)
Rights for one music HDD:

:thankyou:
But now what eh ? ...

It is difficult to recall correctly, but at first with Vista things happened, which nobody understood. And, I don't even remember that it got out of the way - we got used to it or so (coming from XP). This was a.o. about this :

Copy a file with copy-paste (but actually drag & drop) and some times the "forbidden" remark appeared.
What happened was that the source had less rights than the target. Ehm source ? yea, source FOLDER (and target FOLDER). So that depended on how they were created.
But I really forgot the how or what.

Anyway I feel this can be similar and then still it will be the most indirectly leading to this "conversion" (think Unicode), which is what it should be about (a Windows internal thing - I don't do anything with  about it).

So I saw this coming, but also saw coming that I'd had to say too : BEATS ME HOW.

Peter