More > JRiver Media Center 25 for Linux

Cross Platform Paths

<< < (4/4)

max096:

--- Quote from: RoderickGI on August 08, 2019, 07:30:47 pm ---How about using a nomenclature like this?

:::Music::Artist::Album::File.ext

Where
::: means the base path, and would resolve to something like "M:\" in Windows and "/mnt/raid/" in Linux/OSX.
:: means the OS specific path separator


In the raw form, [filename,0] would contain ":::Music::Artist::Album::File.ext", but when used programatically, [filename] or [filename,1] would resolve to M:\Music\Artist\Album\File.ext in Windows, and something like "/mnt/raid/music/Artist/Album/File.ext" in Linux/OSX.

--- End quote ---

C:\\mnt\raid\music/artist/file.ext

Is something Windows could work with so I'd just use / as a path seperator. I'm not sure if windows explorer would let you go there (for open this file in windows explorer) if you gave it that path to open. Quite possible it still does still do that, but Iīd have to try. Obviously you canīt manually input / into Windows explorer. But opening file streams programmatically should work.

BryanC:

--- Quote from: RoderickGI on August 08, 2019, 07:30:47 pm ---...Oh, wait. The above wouldn't cater for my situation where I have media on multiple drives, each with there own drive letter, so there is no one "Base Path". Hmmm, more thought required. Not today.

--- End quote ---

It would be OK as long as the client doesn't have multiple drives. If the server has multiple drives it shouldn't matter (if both drives have the same folder structure) since you'd be stripping the drive letter regardless. If the client has multiple drives then you would have to determine on which drive the folder exists. This would add some overhead. The other option is to require users to pool drives on the client at the filesystem level.

mattkhan:
if this change is implemented, will it be sufficient to allow a windows client to play BDs from a linux server library via local disk access or is disk access a necessary but not sufficient condition for this feature?

Navigation

[0] Message Index

[*] Previous page