Messages

1

Plugins / Re: Additional Tagging & Reporting Tools

« on: July 22, 2021, 05:15:37 AM »

I've never used the ASR tool for this purpose, so you'll likely have to tweak the below.

Code

Step 1
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist

Step 2
Search: \,|\&|and in tag: Artist
Replace: ; in tag: Artist

Step 3
Search: (\sfeat\.\s[\s\S]*?$) in tag: Title
Replace: $1 in tag: (check the box) Artist (displayed)

Step 4
Search: \sfeat\.\s([\s\S]*?$) in tag: Title
Replace: (leave blank) in tag: Title

Thanks for posting this! It does correctly remove the "feat. Artist A" from the title. Unfortunately the resulting Artist fields now show the original artist and then the entire song title afterwards.

Is there any sort of guide on the coding language? I'm trying to back my way into understanding but it's been tough.

2

Plugins / Re: Additional Tagging & Reporting Tools

« on: July 19, 2021, 05:42:02 PM »

Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

Do you not have the ASR preset available that would assist in this?

Hi, thanks for the response. I have played around with the presets but haven't been able to modify them in a way to get the desired outcome. The closest I've gotten is using the "Extract featuring artists from track time and add them to the "Artist" tag. This will copy the featured artists and put them in the Artist tag, but I have a few things I'd like to change about the result and can't figure out how.

1. Remove the featured artist from the title rather than copy them
2. Have it work if there are ( ) around the featured artists or not. Right now it requires parenthesis to work
3. Move the featured artists to the Display Artist tag, including having feat. before the artists

I know I'm close, but each time I try different modifications to the code, it seems to get worse. lol.

3

Plugins / Re: Additional Tagging & Reporting Tools

« on: July 17, 2021, 06:15:25 PM »

Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

Hope it's ok that I bumped this message. I've been playing around with modifying the scripts and just can't quite figure out what I'm doing.

4

Plugins / advanced search and replace - move featured artist(s) from title to Artist tag

« on: July 15, 2021, 12:33:40 AM »

Hi guys,

Can anyone help me with the syntax in Advanced Search & Replace to move featured artists from the title and to the Artist tag?

before:
Title = Cool Song feat. Artist X, Artist Y & Artist Z
Artist = Superstar

after
Title = Cool Song
Artist = Superstar feat. Artist X, Artist Y & Artist Z

Thanks!

5

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 08, 2021, 03:42:16 PM »

I've figured out what to do to work around my problem.

It would be helpful for anyone else experiencing something similar if you posted what you did to resolve the issue.

Sure. The first thing I did was set up a custom tag using Artists as the identifier (display name I called Aritsts-multi). This tag is readable by ffprobe/Emby and take precedence over the Artist tag. Then I set up a preset in Advanced Search & Replace to be automatically applied which copies the artist names from the Artist (displayed) tag into the new custom Artists tag. So far, so good!

6

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 08, 2021, 01:05:11 AM »

no need for any further response. I've figured out what to do to work around my problem. Thanks for the help everyone.

7

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 06, 2021, 08:46:26 PM »

The Artists (virtual) tag is interesting b/c ffprobe DOES read from that tag correctly.

'artists' is not an 'official' id3 tag, but you can create a custom tag for it that should be compatible with Picard et al.
It will then read/write 'TXXX/artists' for id3, which I think should be identical to how Picard does it. (I don't know about TagScanner)

Note that while you can use 'artists' as the identifier when creating the custom tag, for the display name you'll have to choose something else because otherwise it would conflict with MB's internal use of 'artists'.

Thanks, it sounds like this might be a good work around for me. Is there a guide you could point me to? I do see the custom tag options in Preferences, but I'm not familiar with how I would go about using it for this purpose. Thanks again man. Really appreciate it.

8

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 06, 2021, 07:14:09 PM »

Yeah, Emby is definitely more focused on video and audio is just sort of along for the ride. The issue itself is with ffprobe but after reason some bug reports it doesn't seem like something they are planning to correct anytime soon. They do claim support for v.24, except as it relates to multiple artists and null separators. Emby dev said they will put it on their list to come up with a fix for it but they don't plan to move away from ffprobe, in general.

The Artists (virtual) tag is interesting b/c ffprobe DOES read from that tag correctly. I just can't set it in MB. Right now I'm using Tag Scanner to Picard to set Artists but it's manual process so I'm still looking for something a little more automated.

9

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 06, 2021, 12:25:54 AM »

unrelated question - does anyone know why Advanced Search and Replace won't allow copying to Artists? You can copy from but not to. It's missing from the picklist.

https://ibb.co/mBjxnwb

10

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 06, 2021, 12:12:31 AM »

Does this mean that if Emby would recognise the null character as separator, the issue would be solved?
Is this something Emby is aware of, and is there a chance they will address this?

Emby and at least one other popular media server (sorry the name is escaping me) uses FFProbe to scrape metadata from all files, audio and video, so it's unlikely they can do anything. In my google search there seems to be conflicting information as to if FFProbe considers this to be a bug or not, so it's possible FFProbe could make fix, however the posts I found are rather old so it doesn't seem to be something that they will change. I did read that null separator is "out of spec for all ID3 versions except for 2.4", which would seem to mean that the issue is with MB and it's use of null separator with v2.3. I don't think that FFProbe works well with v2.4, so that really isn't an option for my situation.

11

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 05, 2021, 06:04:32 PM »

If you save tags in MB, it would split the ';' into separate values. However, if you used another tag editor then you could use ';' as the separator in a single field and MB would split it into multiple values. You should double check that saving a rating wouldnt also cause MB to split the ';'. I dont think it would though but not completely sure without reviewing the code

Thanks for your reply! I do have to admit that I'm a little confused though. I have tried to run things through MB, which allows me to use the Advanced Search and Replace feature to copy artists from the Displayed Artist tag into the Artist tag  (Command copies all artists delimetered by text &, vs., feat. from 'Displayed Artist' tag to multi-item 'Artist' tag). This works well in that it visually displays the artists separated by ';' but does split the artists so that the Artist views in MB work correctly. However my understanding is that the ';' is really a null separator, which means the additional artists are not being parsed correctly by ffprobe. As a work around, I tried to load up the files post-MB tagging into Mp3tag and replace the null separator with a ';'. This does work for ffprobe, however if/when I run a rescan in MB, the Artist tags are then showing as "Artist 1; Artist 2; Artist 3" in one Artist tag and are not split correctly. If I never rescan tags in MB it would probably work though.

12

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 05, 2021, 03:26:18 AM »

Clearly the issue is with how FFprobe reads the tag(s),

That's probably a correct statement.

You never said what file format you are using.
If this is about mp3 files, are you using id3v2.3 or 2.4?
If it's 2.3 try switching to 2.4?

I'm using v2.3 so I can try to switch to 2.4, but I'm also having the problem with non-mp3 files (m4a for example).

According to an Emby dev, MusicBee is apparently using a "null separator" when using the split artist function. This null separator is displayed as "\\" in Mp3Tag and as a semi-colon in TagScanner. But that is just how those programs interpret the null separator. FFprobe stops reading the tag when it hits a null separator, which is what's causing the problem.

So the title of the thread is actually wrong. The real question is it possible for MusicBee to use a semicolon or single backslash rather than null as a separator when splitting artists?

13

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: June 04, 2021, 08:15:30 PM »

If the artists are showing in MB with double back slashes, they're not actually separated.

Using MP3TAG, use the Replace action to substitute \\ with /. You might have to use \\\\, so try on one file first and see which works.
Then use the "Split field/tag..." action and input /

Your artists will then display as Artist; Artist

Thanks for the reply. In MB, the tags look correct. When I open the same files in MP3Tag, the artists are separated by \\. When I open the files in TagScanner, the artists are separated by ;. It looks like each software just treats multiple artist tags (ie, more than one artist tag) differently. The problem that I'm having is that the media server that I use (Emby) is using FFProbe to parse the tags and it appears that ffprobe cannot handle more than one artist tag. It CAN handle a single artist tag with multiple values separated by a ; but if I make that change, the MusicBee won't display the Artists as separate artists.

I'm stuck between having MusicBee display incorrectly or having Emby display incorrectly. Clearly the issue is with how FFprobe reads the tag(s), but I'm just searching for a work around.

14

Questions / Advanced Search and Replace - writing to Artists tag

« on: May 27, 2021, 04:02:03 AM »

Hi guys,

Is it not possible to write to the Artists tag? I've been trying everything I can think of to copy the data from the Artist tag to the Artists tag but can't figure it out. Thank you.

15

Questions / Re: use single "\" or ";" rather than "\\" to separate artists

« on: April 06, 2021, 01:32:31 AM »

An artist tag with multiple artists is not what you think it is.  It is not one tag with multiple artists in it, it is multiple Artist tags each with one artist in it.

As you have seen, this will show up in various software packages in different ways.  Mp3tag displays the combination of these multiple tags as double backslashes.  But if you were to open the "Extended Tags..." panel for that file in mp3tag, you should see multiple artist tags, each with one artist in it.  If that isn't the case, then you have a tagging problem. If it is the case, then you have an Emby problem.

This is why a screenshot of MusicBee would be helpful.

Thanks, looks like it's definitely an Emby problem. Everything in MB looks good, so I'm pretty sure the tags are correct. As you mentioned, in Mp3tag they show as \\, which was causing my confusion. Interestingly, if I replace the \\ with ; (in mp3tag) and save, Emby will then show the artists correctly. very strange.

Thanks again for your help.