Print

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

[pseudoelvis]

OK moved some albums around tonight and found a bug in the move/copy function when encountering long filenames and unusual unicode characters.

It appears that when there is a special unicode character (as in Blue Öyster Cult or Beyoncé, for example) that the move occurs mostly correct, but the DB doesn't get properly updated to the new location. There are a few issues:
1. The songs are moved, but treated like there is another file of the same name in the destination, i.e. a '(1)' is added to the filename, even though there is not a file in the directory. For example, the file 'Blue Öyster Cult - Blue Oyster Cult - d1t10 - Redeemed.flac' was moved to the new location as 'Blue Öyster Cult - Blue Oyster Cult - d1t10 - Redeemed (1).flac'
2. This spits out the following log:
Tagging error: /Volumes/Multimedia/Music/Blue Öyster Cult/Blue Oyster Cult/Blue Öyster Cult - Blue Oyster Cult - d1t10 - Redeemed.flac
 3. A pointer is created in the media library, however it is not updated to the proper location, rather it strips the '(1) off, expecting the proper filename I suppose.
4. The old pointer in the media library is not deleted.
5. Possibly related, there is a file that contains no special characters that chokes too, presumably due to length.
Tagging error: /Volumes/Multimedia/Music/The Beatles/Abbey Road (Super Deluxe Edition)/The Beatles - Abbey Road (Super Deluxe Edition) - d1t38 - The Long One (You Never Give Me Your Money - Sun King - Mean Mr Mustard  - Her Majesty - Polythene Pam - She Came In Through The Bathroom Window - Golden Slumbers - Carry That Weight - The End).wav

When I run the import function, it does fix the broken pointers, however I now have a bunch of '(1)' artifacts, and I dare not move the files again with f6.

Enclosing log output after move and after re-import for reference.

[RoderickGI]

I think you are correct. I've helped others with issues created by this problem.

[pseudoelvis]

Confirmed for sure to be in the 'Move' function, I did a rename and that did not create the same naming anomaly (putting (1) after filename) as the move function does. Don't know about Copy.

[bob]

What is the filesystem on the device
/Volumes/Multimedia ?

[pseudoelvis]

It is a QNAP NAS accessed over a Thunderbolt IP connection, I presume using an underlying Windows 10 mount (SMB/CIFS type) for my windows box, and MacOS SMB for the MacPro. If you would like to look at the machines directly, I'd be glad to connect with you and set up a mechanism to let you poke around on the machines.

[bob]

It is a QNAP NAS accessed over a Thunderbolt IP connection, I presume using an underlying Windows 10 mount (SMB/CIFS type) for my windows box, and MacOS SMB for the MacPro. If you would like to look at the machines directly, I'd be glad to connect with you and set up a mechanism to let you poke around on the machines.

I have a QNAP here.
It's likely to be something like the charset mapping done on the mount.

[pseudoelvis]

OK, looks like something has gone wrong with the handling of the Thunderbolt interface in this build of Windows, it occurs on the Thunderbolt mount with Explorer and TeraCopy. I'll open a bug with the windows dev team and see what gives.

I remapped using the Ethernet interface and got 70MB/s and JRiver worked like a charm after that 

-Shane