XXHighEnd

I found a bug in XXHighEnd.

If a filename has certain funny special characters, XXHighEnd brings a "Out of Memory" Error and does not play the file.
Renaming the file corrects the problem.
This is very irritating, because the error message is totally unrelated to the underlying problem which is that XXHighEnd cannot deal with certain characters in the file name.

Something to put on the todo list for a next release.

Regards, Michael

Hi Michael,

Do you have an example of that ? Include the whole path please.

Thanks,
Peter

Btw small hint :

Such characters (whatever they are) are generally supported. So it won't be all that easy to find something which goes wrong for those characters in general. In other words, please check also what it exactly is that makes it go wrong. Hence check other tracks of which you may think they will go wrong just the same, but possibly do not ...

Peter

Hi Peter

Here 2 examples:

04 - "Wachet Auf, Ruft Uns Die Stimme" BWV 645.flac

05 - Hello (Why Are We Whispering? remix) - Martin Solveig.flac


The path is not the problem, unless it also contains these chars.

With this filename, the error is "not enough space in playback drive", so out of memory I reported before is not correct.
However the error is still misleading.

Regards, Michael

Michael,

I think the message is still a bit different (consists of two parts and the last (you mentioned) is a question. All IIRC.

Stupid question perhaps, but what are those characters not allowed in your opinion ?
Otherwise the double quotes look very suspicious to me to begin with.

Also your 05 track does not comply to good structuring because of the " - " separator for Artist and Album. This is official for XXHighEnd but also logical. And now it depends on the path ...

So please show the paths as well (not make up something - copy paste it !). Also show me the first message appearing from this.

Regards,

Peter

Hi Peter

Will paste the full path this evening.

The error message does not appear if I remove the ? and the " " in the shown examples. BTW, those are actual practical examples I found to cause this in my music collection

I have seen it happening also for other characters but I would have to dig further.

My conclusion is that if I get this funny error, something is wrong with the filename. Changing the filename always corrected the problem. The thing is just that the error message is very misleading and it took me a long time to identify the root cause (filename incompatibility).

Regards, Michael

Thank you very much Michael.

These characters are not legal. At least not for Windows. See below where I tried to put in a ? in the filename and where you can see what is not allowed.

There's not much to so about this because we are after the fact. So I don't know where you got these file names from, but they can't have been created under Windows.
Also, supposed these are from a Mac etc. and there they are allowed, then the means of mounting the volume is not correct. This "so to speak" because there won't be another means I'd say, unless you use something which does not check for this in the first place while it could by normal means (no idea what I'm really saying here). But for example, if you'd copy these files under Windows to another location, most probably it errors out. And if not this would be wrong in itself.
But I never tried such a thing because I wouldn't know how to create such a file (name) in the first place.

Peter

Hi Peter

These filenames were actually created on a Linux / Mac system where they are prefectly legal and working.

There are no such restrictions there.

As you say, these are illegal in the Windows System
It is not possible to create such names in Windows but somehow when you copy the files over, no error message is displayed and it seems to work.

Funny that I am the only one with this problem so far.
But then, I always bring things to their limits somehow. ;)

Regards, Michael