Paul Taylor

SongKong 8.1 Scar released 7th of January 2022 https://community.jthink.net/t/songkong-8-1-scar-released-7th-of-january-2022/10400 Performer Credits SongKong could already retrieve track level performer credits from MusicBrainz. But MusicBrainz can also store performer credits at release level and these apply to all tracks on the release, this new release can now retrieve these release level credits and add them to each track. When a track has multiple credits for a particular role (such as two engineers) they are not stored by MusicBrainz in any particular order, so the order they were added to SongKong was random, this mean't that the order could change when the the Albunack database was rebuilt. Now to ensure consistency and remove needless modification to your SongKong music files these roles are always stored in alphabetical order SongKong correctly splits a single credit of multiple instruments into multiple credits, so a credit for Paul McCartney Vocals, Guitar is added to your music files as Paul McCartney (Vocals), Paul McCartney (Guitar), but it was also splitting single credits such John Lennon, Addtional Guitar incorrectly, this is now fixed. The vocal performance of Vocal performers was previously being added to the Instruments field, this is not what most customers would like so now the instruments field is restricted to actual instruments Original Release Date When looking for the earliest or original release date SongKong was always selecting later release with country to earlier than one with unknown country. So this means it may not get the earliest release and it could actually be later than the release matched if song has been matched to a release with no country events, this is now fixed. Improved Matching When double checking album matches we now allow for existing data storing the featured artists in title rather than artist. This is quite common but MusicBrainz preferred formatting is for featured artists to be stored in artist credit so that when we double check artist/title for each match it was sometimes leading to valid matches being rejected. So when matching we now check for artists in original metadata and strip out and when checking artist credits we should allow a match from name to just the one main name credit in artist credit. Bug SONGKONG-2275 1 Performer with instruments that use additional guest or solo just shows a credit as addtional guest solo SONGKONG-2272 Performer role of additional vocals just shown as additional SONGKONG-2271 Discogs Albunack Match double counts Discogs and album matches SONGKONG-2267 Discogs Only Update can change SingleTrackNo field to zero SONGKONG-2236 Composer Artist Credit can return different sortname variant for composer relation to trackartist from Albunack SONGKONG-2134 Albunack: When looking for earliest/original release date will prefer later release with country to earlier than one with unknown country SONGKONG-1723 Albunack:SongKong should consider MusicBrainz release level performer credits not just track level ones Improvement SONGKONG-2277 Store multiple composer/conductors/arrangers/performers for track ordered by name SONGKONG-2274 Add Performer field alphabetically SONGKONG-2273 Remove vocal performers from instrument field SONGKONG-2270 When double checking release match check for metadata storing the featured artists in title field rather than artist field

Sorry not possible, it is not possible for me to support multiple versions. But a small upgrade payment of £10 allows you to download all the new versions released in the next year. We do release a new version of SongKong every couple of months and you get a much better product if you keep up to date with the newest version

SongKong 7.2 Cassdaga now available We are please to announce the release of SongKong Cassdaga, named after the 8th album by Bright Eyes This release is a complete rewrite of the SongKong’s renaming feature. There are no new options and only minor changes to the Errors and Warnings tab but it should do renaming considerably better. Especially when SongKong has to shorten the name because the Windows 259 character limit is enabled, and when you have duplicate copies of the same song so that the duplicates have to be renamed. Full details at https://community.jthink.net/t/songkong-7-2-cassadaga-released-march-8th-2021/9882

Hi, that is not possible with Docker version, but should not be necessary.

SongKong 6.8 Rumours released, full details at https://community.jthink.net/t/songkong-6-8-rumours-released-29th-january-2020/8540

Sorry for the delay in replying, I forgot to check and we have new forums at https://community.jthink.net/ I guess this problem only occurs when you use SongKong to rename or move files, and the default permissions created are incorrect. We tried to fix this previously with umask but it didnt work - https://jthink.atlassian.net/projects/SONGKONG/issues/SONGKONG-1757 so I will try again in the next few days

SongKong 6.7 Closer is now available http://blog.jthink.net/2019/11/songkong-67-closer-released-november.html

SongKong 6.6 Red is available http://blog.jthink.net/2019/10/songkong-66-red-released-october-23rd.html

We have just released SongKong 6.5 Doolittle Music Tagger with over thirty fixes and improvements - http://blog.jthink.net/2019/10/songkong-65-doolittle-released-october.html

SongKong 6.4 Treasure now released, named after the seminal Cocteau Twins album. This release contains more than twenty bug fixes, but we have also added a number of nice improvements.

SongKong 6.3 Psychocandy now released, discount still available using code UNRAIDSPECIALX This includes fix for permissions problem described in this thread. Now includes Browse by Artist/Album and Browse By Folder sections in report, making it easier to manage your metadata

Thanks, never saw that. Although the initial question was very much just an unRaid user question rather than Programming.

The files are moved to a different location, and I have just realized the issues is not with the file themselves they preserve their original owership and permissions, the problem is that the directory structure that was created to move the files to is owned by root with only rx permission for everyone. so this means the files contents can be edited but the files cannot be deleted or renamed, and new files cannot be added to these directories. Setting umask to 000 will provide permissions to everyone, but Ideally I want to work out in my docker ap how to create the folders as the correct user.

So this was done with my own SongKong app, Im looking to improve it to avoid this issue but first of all I need to better understand how unRAID permissions worked in the first place. Terminal matches Windows Yes i only said that Windows shows the correct users/groups, not the correct permissions. I have no intention of trying to modify permissions from the client. I was just trying to understand it (before I knew about Terminal), and that is why I viewed on Mac as well. I still dont really understand why Mac is so much worse than Windows since we are going unix -> unix.

If I just right click oo the folder and select Security tab it shows me user/group/other. But I cant see permissions, that's why I was using my Mac instead. Screenshots below show initial folder permissions and then after file moved with Docker app)

I looked at unRAID from a Windows PC, and that does correctly show the users and groups ( nobody/users versus root/root), however I can never understand how Windows shows permissions which I viewed from Mac as I am familiar with the UNIX style rwxrwxrwx permissions. You lost have me regarding SMB , if that is a Windows thing why would a Mac connecting to unRaid use SMB since neither are Windows based systems

So in normal circumstances everything is nobody/users , unRaid doesnt let you create new users ectera so root is the only other likely owner, right ? When you say controlled by Samba, do you just mean when you mount the drive from PC/Mac you can decide whether to connect as guest or other user (root), or do you mean something else? Is connecting as guest the same as connecting as user nobody or not ?

My original Docker container (for SongKong) was created for use with Qnap (http://www.jthink.net/jaikozforum/posts/list/20064.page) , created a songkong User and Group RUN addgroup -S songkong \ && adduser -S -G songkong songkong But this did not work well because then SongKong did not have permission to read/write some files So I removed the user so SongKong defaults to running as root However we see on unRaid this means that although it can now modify any files if it moves them they get created as user root, group root umask 000. Whereas the original files are owned by nobody, group everyone umask 755 which means they cannot be modifed/deleted outside of unRAID. Can anyone suggest an approach whereby SongKong Docker has access to all files but create them as the nobody user with full permissions, will this be compatible with non UNRAID systems such as Qnap ?

SMB is a layer between OS and SMB, did you mean this ?

Thankyou, that solves it, I was not aware of the Terminal option. Can also use ls -alR /mnt/user/ to recusrively get listing. But I am a bit surprised that you have to use Terminal to see the permissions, not very user friendly for users not familiar with UNIX.

I look at files on an an unRAID user share that i connect to from my Apple Mac as guest. Using Terminal permissions shows as paul staff -rwxrwxrwx i.e owner by paul (my MacOS username) with full permissions for everyone. But that isnt actually the case because if I try to delete the file I get Permission denied I have navigated to the files via the unRAID shares browser, but nowhere can I find anything that shows the file permissions So: - Why does macOS not show me the real permissions ? - Where can I see permissions from within unRAID itself ?

Okay, didn't think of that.

Okay, havent heard anything so I assume its okay so have posted on

SongKong 6.2 Hunkpapa has now been released, this includes major performance improvements - http://blog.jthink.net/2019/06/songkong-62-hunkpapa-performance.html And we are offering 15% discount for unRAID customers on SongKong Pro for a limited time, just enter UNRAIDSPECIALX as promo code at checkout

I think this must be for a particular file format since usually SongKong modifies existing file rather than create new one and so ownership of existing file should not usually be changed. But I have already raised an issue for this https://jthink.atlassian.net/projects/SONGKONG/issues/SONGKONG-1757 and I will be looking at this next, what audio format are your files ?