Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[chrisjj]

1 With:

 Playlist location: R:\Playlists\!test.m3u
 Track location: R:\Spacers\02480002928928-1-1.wma
 Playlist line: \Spacers\02480002928928-1-1.wma

do File | Open Media File...

Expected: track plays
Observed: dialog saying "Warning There is nothing to play."

This

 Playlist location: R:\Playlists\!test.m3u
 Track location: R:\Spacers\02480002928928-1-1.wma
 Playlist line: R:\Spacers\02480002928928-1-1.wma

and

 Playlist location: R:\!test.m3u
 Track location: R:\Spacers\02480002928928-1-1.wma
 Playlist line: \Spacers\02480002928928-1-1.wma

succeed as expected.

Matt, I think there's a loophole is the relative path resolution here.

[Matt]

Could you mail a test package (playlist + a file or two) that will show the issue to matt at jriver dot com?

Thanks for your help.

[chrisjj]

Could you mail a test package (playlist + a file or two) that will show the issue to matt at jriver dot com?

Sure. Doing so now... EDIT: Done.

Thanks for your help.

Thanks for your interest in this issue! I'll be very happy to see it fixed.

[Matt]

Thanks for the sample package.

First, I was going to say you should switch:
\Spacers\02480002928928-1-1.wma
to
..\Spacers\02480002928928-1-1.wma

But then I asked somebody else here and they said "if it starts with slash, that means the path is starting on the current drive."

So I learned something new.  We'll make the program support that syntax in a coming build.

[chrisjj]

"if it starts with slash, that means the path is starting on the current drive."

Indeed. That's been so since MS-DOS.

We'll make the program support that syntax in a coming build.

Excellent! Thanks.

[chrisjj]

Matt

We'll make the program support that syntax in a coming build.

Seems you did - thanks - but with faulty Filename:

 

and this prangs e.g. Locate On Disk (external).

[Matt]

Thanks for the heads-up.

Next build:
Fixed: A relative path that starts with a backslash could incorrectly end up with a filename that had two backslashes after the drive.

[mbagge]

Since the good old DOS days there were two built in folder names, "." and".."
If you are to construct a relative path with these names, then ".\filename.ext" refers to a file in the current folder, and "..\filename.ext" refers to a file in the parent folder. When using"\filename.ext" it refers to a file in the root folder of the  current drive, as mentioned above.

[MrC]

Since the good old DOS days there were two built in folder names, "." and".."

off topic historical footnote: this predates DOS by at least a dozen years.

[JimH]

CP/M?

[MrC]

My belief was that it was invented in '69 w/Unix and directory hard links.   Perhaps the idea was borrowed from a previous invention though.

[chrisjj]

Next build:
Fixed: A relative path that starts with a backslash could incorrectly end up with a filename that had two backslashes after the drive.

Thanks Matt.

[chrisjj]

Fixed: A relative path that starts with a backslash could incorrectly end up with a filename that had two backslashes after the drive.

Verified in MC19 Build  54.