Print

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

[Gumby]

I am currently experiencing an unusual problem with album booklets in JRemote.  I have one album of Beethoven & Mendelssohn Violin Concertos that shows all the album booklets from all other albums that start with the name Beethoven.  Over 40 album booklets show up as assets on this one album.  I deleted all of the album booklets from my NAS and they still showed up.  I tried deleting the album and putting it back and rebooting everything in the process.  No luck.  All of the other Beethoven albums show only the booklets or assets located in the directory of the music.  Any ideas?

I am running JRiver 19.0.163

One other minor issue with Asset is that it appears the booklets need to be located in the director where the music is.  If an album as multiple disks and there are subfolders for each disk, JRemote will not find the album booklet if it is in the root (album) directory.  Copies of the booklet must be placed in the folder for each disk.

[Gumby]

It appears the issue I have is related to the use of an ampersand in folder names.  “Assets” of albums become associated if those albums folder have an ampersand in their name and they are located in the same folder, an artist folder or composer folder for example.  Also, it appears, album assets can become associated if those album folders are all located in a folder with an ampersand in its name.  This does not appear to be related to the name of the album itself (the album tag) or the file name of the asset.

Not sure if this is by design.  If so, it might be covered better in the WIKE somewhere.  Otherwise, be advised that using an ampersand in folders introduces some interesting folder math.

[marko]

Gumby.... activate the asset!

[Gumby]

All assets are deployed, under fire and taking heavy casualties!

[marko]

Top man. No help at all with the issue at hand, but whenever someone mentions assets, I think of Jason Bourne, and I couldn't resist...

Apologies for not being able to help with the actual topic though.

[Lespaul]

It appears the issue I have is related to the use of an ampersand in folder names.  “Assets” of albums become associated if those albums folder have an ampersand in their name and they are located in the same folder, an artist folder or composer folder for example.  Also, it appears, album assets can become associated if those album folders are all located in a folder with an ampersand in its name.  This does not appear to be related to the name of the album itself (the album tag) or the file name of the asset.

Not sure if this is by design.  If so, it might be covered better in the WIKE somewhere.  Otherwise, be advised that using an ampersand in folders introduces some interesting folder math.

Thank you for digging into the issue Gumby. I`ll look into why the ampersand mess up the paths, it`s certainly not by design.

Regarding the other issue, the booklets do need to be located in the directory where the music is.
This is a limitation of the way assets are found, and can`t really be fixed in the current implementation.

[Gumby]

Thanks Lespaul.  It was so perplexing and difficult to describe.  Also, I think the use of commas in the folder name may be doing the same thing.  For example, Beethoven Symphonies No. 1, No. 2, No. 3...etc.  Did not have time to play with that this weekend.  I will hold off renaming all my folders to see if an update is forthcoming.