INTERACT FORUM

Please login or register.

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

Author Topic: tagging issue again  (Read 230 times)

Alex_W

  • Recent member
  • *
  • Posts: 22
tagging issue again
« on: December 23, 2024, 12:00:48 am »

Hi all,

At the end of my wits here, please help.

Editing data on many many albums .flac files (like, album name, album artist, composer, orchestra, soloists, release date, etc etc), want to save the library info I'm entering to the files (tags).

The issue: for some albums I'm able to do this no problem; for some -- no matter what I do, JRiver either throws an error ("unable to do make sure it exists/is not opened by other program/is writable/blah blah") or just doesn't do it without throwing an error (like, status "finished" -- tags unchanged).

The setup:
* media files are on a Debian-based NAS, shared via CIFS/SMB;
* instance of Media Center/Media Server on an Ubuntu 22.04 VM on the same NAS; (why? because the NAS is in the closet, and always on);
* to edit/tag, I open a spice remote desktop session into the VM
* no firewalls between the clients in the subnet;

I thought inititally that maybe this is related with the SMB3 server signing that I had to turn on at some point (no more guest access, thanks Win 11 clients...) -- the media folders on the NAS were initially exposed to the VM via fstab mount line; then I added explicit user/password pair for SAMBA share access; then I changed it to the GUI-based folder mount... in all cases, I could access/read/write to the folders in question.

Strange detail: the albums that had their tags successfully updated/written into files, had much more entries in the tag dump section; the files that refused to update, had much less.

Before ppl start with the "motherhood statement"-type advice:
* yes, the permission seem fine: media folders are visible/accesible/writable from the VM (and from elswhere on the subnet);
* no, there are no media files open elsewhere: I shut down all other instances of MC elsewhere on the network, and checked SAMBA status -- no sessions/files left hanging open;
* the set is 50 CDs that I ripped following the same process over several days: ExactAudioCopy rip on my Windows PC, then copy the folder with tha album to the shared media folder;
* JRiver successfully saves tags to some albums in the set but noth others, and there is no rhyme or reason to it;
* I turned logging on -- nothing of a kind is reflected there; when JRiver throws an error, the message says "this has been copied to the clipboard" -- but there is nothing in the clipboard.

Looking for suggestions.
Logged

Alex_W

  • Recent member
  • *
  • Posts: 22
Re: tagging issue again
« Reply #1 on: December 23, 2024, 08:43:21 am »

was able to sift out from the log file:

0080435: 127039482889792: Database: CTagSaveInfo::SaveTag: Start
0080437: 127039482889792: Database: CTagSaveInfo::SaveTag: Tagging /run/user/1000/gvfs/smb-share:server=vault.local,share=bigtwo/Media/The Florilegium Series CD35/11 In nomine à 4 (No. 1); In nomine à 4 (No. 2).flac
0080437: 127039482889792: Import: JRAnalyzer::Open: Start
0080437: 127039482889792: Import: JRAnalyzer::AddFile: Start
0080437: 127039482889792: Import: JRAnalyzer::AddFile: Filename: /run/user/1000/gvfs/smb-share:server=vault.local,share=bigtwo/Media/The Florilegium Series CD35/11 In nomine à 4 (No. 1); In nomine à 4 (No. 2).flac
0080437: 127039482889792: Import: JRAnalyzer::AddFile: Start
0080437: 127039482889792: Import: JRAnalyzer::AddFile: Filename: /run/user/1000/gvfs/smb-share:server=vault.local,share=bigtwo/Media/The Florilegium Series CD35/11 In nomine à 4 (No. 1); In nomine à 4 (No. 2).flac
0080438: 127039482889792: Import: JRAnalyzer::AddFileMJ: Start
0080447: 127039482889792: General: CFileInfo::CFileInfo: Start
0080447: 127039482889792: General: CFileInfo::CFileInfo: Finish (0 ms)
0080473: 127039482889792: Import: JRAnalyzer::AddFileMJ: Finish (34 ms)
0080473: 127039482889792: Import: JRAnalyzer::AddFile: Finish (35 ms)
0080473: 127039482889792: Import: JRAnalyzer::AddFile: Finish (36 ms)
0080473: 127039482889792: Import: JRAnalyzer::Open: Finish (36 ms)
0080477: 127039482889792: General: CFileInfo::Close: Start
0080477: 127039482889792: General: CFileInfo::Close: Finish (0 ms)
0080487: 127039482889792: General: CFileInfo::~CFileInfo: Start
0080487: 127039482889792: General: CFileInfo::Close: Start
0080487: 127039482889792: General: CFileInfo::Close: Finish (0 ms)
0080487: 127039482889792: General: CFileInfo::~CFileInfo: Finish (0 ms)
0080487: 127039482889792: Database: CTagSaveInfo::SaveTag: Finished writing tags, result: 0
0080487: 127039482889792: Database: CTagSaveInfo::SaveTag: Finish (result: 0) (52 ms)

similar entries for other files.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7911
  • Long cold Winter...
Re: tagging issue again
« Reply #2 on: December 23, 2024, 08:44:48 am »

It probably has to do with the way you have your NAS mounted and the path being used, specifically the /run/user/1000/gvfs/smb-share:server=vault.local,share=bigtwo/ part with the =, : and other characters in the path name. Maybe the accented characters of the files too may also be an issue, not sure. Nonetheless I highly recommend mounting your NAS via fstab to a folder with a sane location and name, e.g. /mnt/Media would probably be a good choice. I use something similar with my NAS and my SMB shares in fstab and MC itself, and have no issues.

The main steps would be via a Terminal...

First, make sure cifs-utils or the equivalent for your distro is installed.

Then...

Code: [Select]
sudo mkdir /mnt/Media
Then...

Code: [Select]
sudo mkdir /mnt/Media
Code: [Select]
sudo chmod 755 /mnt/Media
Then you can test the mount, but you need to know the IP address of the NAS and the share folder name, but a basic example of this would be...

Code: [Select]
sudo mount -t cifs -o username=USERNAME,password=PASSWORD //192.168.1.123/Media /mnt/Media/
Of course you change everything to your liking, but make sure you use the SMB share credientials for the USERNAME and PASSWORD parts.

Then if it didn't display an error go to /mnt/Media (or whatever folder you chose) and see if your NAS is mounted there and look around and if it looks good, finally open /etc/fstab in a text editor or nano and add something like this, again change to your liking and your settings...

Code: [Select]
//192.168.1.123/Media/   /mnt/Media   cifs   username=USERNAME,password=PASSWORD   0    0
You can either reboot or use sudo systemctl daemon-reload && sudo mount -a to reload and mount, but I recommend rebooting then going to your mounted location and see if it was successfully mounted automatically.

Of course after changing the mounting location you'd have to use MC's Rename, Move, & Copy Files feature to change the paths of your files. But it'd probably be worth it in the end.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 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

mwillems

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 5242
  • "Linux Merit Badge" Recipient
Re: tagging issue again
« Reply #3 on: December 23, 2024, 10:07:04 am »

I'll second everything Awesome Donkey said, and offer a few more questions.

For the files that MC can't tag, can the instance of MC that you're using for tagging actually play those files?  That is, have you confirmed that MC specifically can access the files?  If so, does the rename move copy tool work on them if your try to move them?  I would make double sure of that to verify that MC has full file access before I went much further.

One potential weird "Edge case" I encountered that probably isn't your issue, but might be:  Linux permits the creation of case-sensitive file and directory names, but Samba/CIFS (being a windows based protocol) does not permit case-sensitivity, and just flattens case when presenting the share to another PC.  This can create serious mischief when a given directory or file exists in both forms on a Linux NAS.  For example, if you had two directories "The Florilegium Series" and "the florilegium series" on the NAS, samba would present only one of those directories at any given time and MC wouldn't be able to interact with all of the files at any one time, but might see both directories at different times!  I had an issue where I had some albums where there were those kinds of collisions and it led to some very mysterious behavior from JRiver until I figured out what the issue was.  Worth checking on the NAS directly just to confirm you only have one directory for those files.
Logged

BryanC

  • MC Beta Team
  • Citizen of the Universe
  • *****
  • Posts: 2678
Re: tagging issue again
« Reply #4 on: December 23, 2024, 10:17:32 am »

Quote
Linux permits the creation of case-sensitive file and directory names, but Samba/CIFS (being a windows based protocol) does not permit case-sensitivity, and just flattens case when presenting the share to another PC.

If you think music organization is bad, try organizing gene names on Windows when dealing with orthologs and homologs (PAX6 vs Pax6, or where dominant alleles are capitalized and recessive alleles are lowercase). And then imagine migrating everything to Linux and one of your clients syncing those directories with SMB/syncthing to a Windows machine and the level of data loss that can occur.

I will never understand this design decision, ever.
Logged

Awesome Donkey

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 7911
  • Long cold Winter...
Re: tagging issue again
« Reply #5 on: December 23, 2024, 12:37:32 pm »

Another edge case would be files and folders that begin with a period being treated as a hidden file/folder in Linux. This can cause issues if you don't enable hidden files and folders in the file manager you're using, and they won't be imported as they're hidden. I used to encounter this with albums by artists that used ... at the beginning of the album title. Fortunately I use an expression on all my freshly imported files that takes that into account and renames files/folders so there's no periods at the beginning and everything imports fine.
Logged
I don't work for JRiver... I help keep the forums safe from "male enhancements" and other sources of sketchy pharmaceuticals.

Windows 11 24H2 Update 64-bit + Ubuntu 24.10 Oracular Oriole 64-bit | Windows 11 24H2 Update 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

Alex_W

  • Recent member
  • *
  • Posts: 22
Re: tagging issue again
« Reply #6 on: December 23, 2024, 07:52:26 pm »

...... Nonetheless I highly recommend mounting your NAS via fstab to a folder with a sane location and name, e.g. /mnt/Media would probably be a good choice. I use something similar with my NAS and my SMB shares in fstab and MC itself, and have no issues..."
[\Quote ]

Thank you Awesome, that's how I had it done before. Same thing.
Logged

Alex_W

  • Recent member
  • *
  • Posts: 22
Re: tagging issue again
« Reply #7 on: December 23, 2024, 07:57:10 pm »

thank you all for the ideas.

to blanket-answer the questions: yes, all files are visible/playable.

I haven't tried to copy/move them using MC... just the file manager in the VM (no issues there).

again, the weird thing is: these are just a few stubborn ones that refuse to tag... the rest of them got tagged no problem (confirmed by looking at the tag dump)...
Logged

Alex_W

  • Recent member
  • *
  • Posts: 22
Re: tagging issue again
« Reply #8 on: December 24, 2024, 10:48:33 am »

the rabbit hole goes deeper than I thought... it seems to be permissions/ACL issue after all. now to figure out how to fix it...

thanks all for ideas.
Logged
Pages: [1]   Go Up