INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Linux JRiver Quirks  (Read 719 times)

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Linux JRiver Quirks
« on: July 10, 2024, 06:30:38 pm »

I just installed the Linux version of JRiver and pretty much right away I've noticed some little things in my pretty basic workflow:

1) Some dialog boxes will display buggy (radio choices not visible until you mouse over or move the box around).
2) "Fill Properties" will sometimes let me change the Album name with [Album] for the Folder field, sometimes, it won't do anything.  In general "Fill Properties" only seems to work half the time with any Presets.
3) Slashes for imports seem inconsistent some of my files are imported with / in the path and some with \ in the path.
4) Cover art won't apply to certain albums no matter which method I use (quick find, paste, add from file, edit cover art tag, etc).  The files are imported and play fine.

With all of these apparent glitches, all audio files appear to play through my DAC up to and including DSD.

Is this just me, or is this the normal experience with the Linux version?  I'm trying to decide whether to pay for the Master License or figure out how to stay on Windows JRiver which doesn't have any of these glitches.
Logged

JimH

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 72205
  • Where did I put my teeth?
Re: Linux JRiver Quirks
« Reply #1 on: July 10, 2024, 06:33:53 pm »

Not normal.

What Linux and what desktop?
Logged

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Re: Linux JRiver Quirks
« Reply #2 on: July 10, 2024, 06:47:57 pm »

I'm using Pop_OS 22.04 with Gnome DE.  Underlying it should be very similar to Ubuntu.
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5232
  • "Linux Merit Badge" Recipient
Re: Linux JRiver Quirks
« Reply #3 on: July 10, 2024, 08:25:59 pm »

I'm using Pop_OS 22.04 with Gnome DE.  Underlying it should be very similar to Ubuntu.

So I use JRiver on Linux every day, and have not seen 2-4 at all.  I very occasionally see 1), but it's intermittent and I can't reproduce it on demand so I haven't reported it.  The other issues are probably something special about your setup.

Some thoughts:

Did you backup and restore a media library from a Windows version of JRiver or does your JRiver for Linux machine have a completely new library?

I ask because number 3) on your list sounds like a very specific failure mode from bringing across a library from one platform to another that I've seen before.  If you're using a library that started on Windows, check the "platform.jmd" file (probably at ~/.jriver/Media\ Center 32/Library/platform.jmd), and see what the file has in it; if it doesn't say "[Platform]=Linux" that's going to cause a lot of problems on Linux.  It will specifically cause lots of slash versus backslash issues, and can also mess up other file access stuff.  That may not be your issue, but it's the main thing I've seen cause weird slash/backslash issues.

Alternatively, is the machine in question a client to a JRiver server somewhere?  If so, 4 is expected behavior (clients can't ever change cover art), but that behavior is not normal on Linux other than in a client/server context.
Logged

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Re: Linux JRiver Quirks
« Reply #4 on: July 11, 2024, 06:23:52 am »

Erm.  Platform.jmd = Windows.  I will change this and do more testing!  Thanks for this tip!
Logged

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Re: Linux JRiver Quirks
« Reply #5 on: July 11, 2024, 06:36:33 pm »

Quote
I ask because number 3) on your list sounds like a very specific failure mode from bringing across a library from one platform to another that I've seen before.  If you're using a library that started on Windows, check the "platform.jmd" file (probably at ~/.jriver/Media\ Center 32/Library/platform.jmd), and see what the file has in it; if it doesn't say "[Platform]=Linux" that's going to cause a lot of problems on Linux.  It will specifically cause lots of slash versus backslash issues, and can also mess up other file access stuff.  That may not be your issue, but it's the main thing I've seen cause weird slash/backslash issues.

This very simple change to this one file has resolved items #2, #3, and #4 above immediately!  Thank you very much!  I was really frustrated!
Logged

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5232
  • "Linux Merit Badge" Recipient
Re: Linux JRiver Quirks
« Reply #6 on: July 11, 2024, 08:23:01 pm »

This very simple change to this one file has resolved items #2, #3, and #4 above immediately!  Thank you very much!  I was really frustrated!

Gotta love an easy fix!  ;D
Logged

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Re: Linux JRiver Quirks
« Reply #7 on: July 11, 2024, 09:16:35 pm »

#1 remains, where some dialogs are a little glitchy.  I'm using X11.  I think I read that JRiver isn't compatible with Wayland.

Disk Write Error
Failed to create time-shifting file.
Error: 2
Please make sure you have write access to disk drive T:
and that you have enough space on the drive.

Obviously I don't have a drive T: on Linux. 
This happens when I open the Options dialog and attempt to "OK" settings changes.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7670
  • August and everything after...
Re: Linux JRiver Quirks
« Reply #8 on: July 11, 2024, 09:36:25 pm »

Maybe the platform issue is something that can be detected and fixed when restoring a Windows backup in the Linux and Mac versions of MC. At least, that's how I think it should be because that's kinda annoying when trying to change platforms. It could also do periodic checks to see if the platform MC is running on matches the contents of the file.

The first issue is random for me too but it exists. You'd probably have a little better experience with X11 as indeed MC doesn't support Wayland (but does work, albeit with minor issues like this, through XWayland).

You'll have to fix your used paths/directories in MC to fix that issue. That's something else maybe MC can do when restoring a Windows backup in Linux or Mac, sanitizing Windows paths to default. Using the portable library feature could cover paths to the media files when running cross platform but I don't think it applies to directories set in MC's options so you'd have to go through and fix those.
Logged
I don't work for JRiver... I help keep the forums safe from Viagra and other sources of sketchy pharmaceuticals.

Windows 11 2024 Update (24H2) 64-bit + Ubuntu 24.04.1 LTS Noble Numbat 64-bit | Windows 11 2024 Update (24H2) 64-bit (Intel N305 Fanless NUC 16GB RAM/500GB M.2 NVMe SSD)
JRiver Media Center 33 (Windows + Linux) | iFi ZEN DAC 3 | JBL 306P MkII Studio Monitors | Audio-Technica ATH-M50x Headphones

atreides

  • Junior Woodchuck
  • **
  • Posts: 81
Re: Linux JRiver Quirks
« Reply #9 on: July 12, 2024, 07:38:36 am »

After going through all the Options pages several times, I finally found the reference to the T: path.  It was under some TV settings that I’ve never used before, and I have no idea why the path was even T: to start with.  The error message from JRiver could use some clarity it would help the user to locate the problem.

For some reason, none of my hard drives show up under “Devices” - the only thing listed there is my optical drive. 

So, I looked at the “Files” view under all the other categories like Images, Videos, etc and found more Windows file paths that I had to remove or convert.

It would be nice if the Devices view would show your drives like the Windows version does, so you could navigate and see all the files in one place.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2620
Re: Linux JRiver Quirks
« Reply #10 on: July 12, 2024, 07:59:58 am »

After going through all the Options pages several times, I finally found the reference to the T: path.  It was under some TV settings that I’ve never used before, and I have no idea why the path was even T: to start with.  The error message from JRiver could use some clarity it would help the user to locate the problem.

For some reason, none of my hard drives show up under “Devices” - the only thing listed there is my optical drive. 

So, I looked at the “Files” view under all the other categories like Images, Videos, etc and found more Windows file paths that I had to remove or convert.

It would be nice if the Devices view would show your drives like the Windows version does, so you could navigate and see all the files in one place.

You can an add the mount points as handheld devices.
Logged
Pages: [1]   Go Up