Print

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

[marko]

Thinking more about that, JRemote communicates via MCWS, I think, and if I'm correct, that's not the same communication channel a theater view client would use... Am I still correct here?

If I am, I don't think there'll be any issues here if authentication is enabled.
The other issues are with true library clients that are merging changes back into the library via "delta" archive files, which wouldn't be the case with something like JRemote 😊

[AudibleImagery]

I was very hopeful that disabling read-only authentication would fix this problem but it happened again today. I backed up in preparation for the new update, installed it, and then left my residence. While I was driving, I decided I would listen to some music but when I looked at JRemote I noticed that 75% of my playlists had been deleted.

[JimH]

You have a very unusual problem.  Leave the drama out of the reporting and we'll try to help.  JRiver doesn't delete anything unless you tell it to.

Security software often does very unexpected things.

[zybex]

I was very hopeful that disabling authentication would fix this problem but it happened again today. I backed up in preparation for the new update, installed it, and then left my residence. While I was driving, I decided I would listen to some music but when I looked at JRemote I noticed that 75% of my playlists had been deleted.

I think there's some misunderstanding? Disabling authentication will *for sure* cause all changes made in Clients/Remote to be LOST. The only way to keep them is to have Authentication enabled.
Even so, as Marko said above, it's better to do all playlist changes on the server directly.

[AudibleImagery]

I think there's some misunderstanding? Disabling authentication will *for sure* cause all changes made in Clients/Remote to be LOST. The only way to keep them is to have Authentication enabled.
Even so, as Marko said above, it's better to do all playlist changes on the server directly.

I edited my reply. I meant to say “disabling read-only authentication”.

[AudibleImagery]

JRiver doesn't delete anything unless you tell it to.

As I've already clarified with you and mentioned in multiple replies, I'm not telling JRiver to delete the playlists but JRiver is randomly deleting them on a frequent basis. That's the point of this post.

[bob]

Thinking more about that, JRemote communicates via MCWS, I think, and if I'm correct, that's not the same communication channel a theater view client would use... Am I still correct here?

If I am, I don't think there'll be any issues here if authentication is enabled.
The other issues are with true library clients that are merging changes back into the library via "delta" archive files, which wouldn't be the case with something like JRemote 😊

Correct.
JRemote only uses MCWS and MCC commands to talk to the MC server. It never loads the DB so it doesn't do deltas.

[AudibleImagery]

I think it's unlikely too, but it may be triggered by some specific character that AudibleImagery may have in his filenames or fields. There were recent changes to the handling of composed/decomposed chars in macos.

Do you think this old post might have some solutions?:

https://yabb.jriver.com/interact/index.php?topic=99583.0

[bob]

Do you think this old post might have some solutions?:

https://yabb.jriver.com/interact/index.php?topic=99583.0

I don't think so. The accented character issues only come into play with filenames stored on a non-apple filesystem. I can't see how they'd have anything to do with playlists.
If there were composed utf-8 issues, you can use the tool
Tools->Library Tools->Convert UTF-8 filenames
to fix them however this is normally done automatically when loading an old database (<MC30) on a current version.

[AudibleImagery]

I don't think so. The accented character issues only come into play with filenames stored on a non-apple filesystem. I can't see how they'd have anything to do with playlists.
If there were composed utf-8 issues, you can use the tool
Tools->Library Tools->Convert UTF-8 filenames
to fix them however this is normally done automatically when loading an old database (<MC30) on a current version.

Okay I guess I'll try to convert UTF8 filenames for good measure. I'm trying to go through and cleanup/remove some old playlists to see if reducing the number of playlists in my library might resolve this issue.

[AudibleImagery]

I don't think so. The accented character issues only come into play with filenames stored on a non-apple filesystem. I can't see how they'd have anything to do with playlists.
If there were composed utf-8 issues, you can use the tool
Tools->Library Tools->Convert UTF-8 filenames
to fix them however this is normally done automatically when loading an old database (<MC30) on a current version.

Do I check or uncheck "Convert to precomposed UTF-8"?

[bob]

Do I check or uncheck "Convert to precomposed UTF-8"?

Check it.
It won't affect anything other than entries that are still decomposed (if any).
Be sure to have a DB backup whenever you do something like this.

[AudibleImagery]

Check it.
It won't affect anything other than entries that are still decomposed (if any).
Be sure to have a DB backup whenever you do something like this.

I was reading in an old Interact post that this conversion should only be applied to the “Name” library field. Is that still true or is it okay to convert all library fields?

[bob]

I was reading in an old Interact post that this conversion should only be applied to the “Name” library field. Is that still true or is it okay to convert all library fields?

The only fields that SHOULD contain those characters are the FILENAME and IMAGE FILE
If the original tags were copy/pasted or entered with a different program incorrectly the others MAY contain those characters.

[AudibleImagery]

The only fields that SHOULD contain those characters are the FILENAME and IMAGE FILE
If the original tags were copy/pasted or entered with a different program incorrectly the others MAY contain those characters.

Okay I’m going to convert all fields to precomposed UTF-8 just in case. Like you said, this probably isn’t going to fix the problem so what else should I do?