Messages

16

Questions / Re: Special Characters in Custom Web Links

« on: September 21, 2022, 05:14:56 PM »

Hi phred,

The "Origin" tag is a standard MusicBee tag. It is displayed/editable from the properties tab of the track editor. It is stored as an embed tag: <ORIGIN WEBSITE>, at least on FLAC files.

A sample url that I am able to repo the issue with: https://www.qobuz.com/us-en/album/revolver-the-beatles/0060254767013

17

Questions / Special Characters in Custom Web Links

« on: September 21, 2022, 04:25:22 PM »

I have been trying to use the <Origin> tag as a "Custom Web Link" without luck. The tag is stored properly in my FLAC file - I am able to read it, display it, update it, cut and paste it into my browser and link to it successfully. However, when I try to use the tag as a Custom Web Link I get an error: "Unable to open web link: <Origin>" and, in the error message, the following changes have been made to the <Origin> tag):
":" is replaced with "%4A" and
"/" is replaced with "%2F"

I have tried to address this with a function:
$Replace($Replace(<Origin>, "%3A", ":"), "%2F", "/")

but end up with the same error. Any suggestion?

Thanks

18

Bug Reports / Re: "Encoded with" value of FLAC files

« on: September 06, 2022, 06:08:41 PM »

Thanks for the info Bee-liver. I'm not crazy about the thought of a tagger library playing around with a file's header data. I'll have to look into that a bit more and see if there is a way I can turn it off.

No worries hiccup. I am clearly in over my head as well. I appreciate you taking the time to better understand my issue and doing what you can to help.

19

Bug Reports / Re: "Encoded with" value of FLAC files

« on: September 05, 2022, 10:04:33 PM »

I wrote some scripts to tag some of my flac files and noticed the "encoded with" value of these files shows up as "Mutagen 1.45.1" in MusicBee.
For context Mutagen is a python library that I used to edit the tags, it's not an encoder. I can't imagine a tagger would alter the encoder value for any reason (or at least I hope not).

What software did you use to write these tags?
It must have used Mutagen, and Mutagen is used for the text encoding of the metadata.
So technically it is not wrong that MusicBee displays that Mutagen 1.45.1 was used as an encoder

(posting this in 'Bug Reports' seems a bit premature to me)

Hi Hiccup,

I wrote the software myself. And, as I mentioned in my post, I did use the Mutagen library to write the tags. That said, Mutagen is a tagging library, not an encoder. I don't see anything in the documentation that would allow me to set or edit the file's encoder data.

I reported it as a bug for a few reasons:
- The issue could be a me issue, it could be a mutagen issue or it could be a MusicBee issue. If it is a me issue, I have run out of ideas (tagging a file is pretty straightforward so there is not much to debug.) Between Mutagen and MusicBee - the next couple of bullets cover why I chose to start with MusicBee
- I am fairly certain MusicBee was working as expected in the past (ie it reported the encoder properly)
- MusicBee is pulling nothing as the encoder in many of my other flac files. I could have sworn that similar files were not only pulling the right encoder info in the past but they were also writing it to tags on updates. Because of this I assume something may have changed in MusicBee (or it's supporting libraries) specific to reading/displaying/writing the encoder data at some point

That said, I am open to further troubleshooting on my end but without knowing where to look for the encoder data in the file or knowing how musicbee is reading the data I am not sure how to proceed. If I was an issue at my workplace this is typically the stage of troubleshooting that I would involve one of my developers and ask them to work with the tester, to help isolate the issue, so I took the same approach here.

20

Bug Reports / "Encoded with" value of FLAC files

« on: September 04, 2022, 10:43:22 PM »

I wrote some scripts to tag some of my flac files and noticed the "encoded with" value of these files shows up as "Mutagen 1.45.1" in MusicBee.
For context Mutagen is a python library that I used to edit the tags, it's not an encoder. I can't imagine a tagger would alter the encoder value for any reason (or at least I hope not). That said, I noticed MusicBee seems to leave the "encoded with" value empty for some files I have yet to tag. Wondering if this might be a MusicBee bug? Could it be pulling the "encoded with" value for flac from the wrong place?

21

Bug Reports / Re: <Track Count> and multi disc albums (accessing <Album Complete?> data)

« on: September 04, 2022, 10:22:30 PM »

Thanks Steven. Is there an exposed value that gives you what <Album Complete?> is comparing <Album Track Count> too? I'm guessing there is a calculation that compares <Album Track Count> to the total of each disc's <Track Count>? or something similar? In other words - I would like to be able to access the numbers <Album Complete?> is using to determine if an album is complete.

Thanks

22

Bug Reports / <Track Count> and multi disc albums (accessing <Album Complete?> data)

« on: September 04, 2022, 12:58:58 AM »

I have a script that I swear was working correctly at some point but it appears I have broken it and I am not sure how to fix it. I have the below script embedded in a larger custom tag:

$If(<Album Complete?>="Y",<Album Track Count>,<Album Track Count>/<Track Count>) Tracks

the goal of the tag:
- If the album is complete (ie all tracks are accounted for) it should display something like "31 Tracks": <total number of album tracks available> Tracks
- If the album is NOT complete (ie there are more or less tracks than expected) it should display something like "30/31 Tracks": <total number of album tracks available>/<total number of album tracks expected> Tracks

The problem seems to lie in: <Album Track Count>/<Track Count>

The <Track Count> does not give me the total expected track count of multi-disc albums. It only seems to account for the first disc.

So If I have a 2 disc set where the first discs looks like this:
TRACKNUMBER=<1-16> TRACKTOTAL=16 DISCNUMBER=1 DISCTOTAL=2
and the second like this:
TRACKNUMBER=<1-15> TRACKTOTAL=15 DISCNUMBER=2 DISCTOTAL=2

"31 Tracks" is displayed

But if i delete one of the disc 2 tracks i get: "30/16 Tracks"

ie only the TRACKTOTAL of DISCNUMBER=1 is accounted for...

Long story short - I am trying to display the <expected track count> that <Album Complete?> is using to determine if a album is complete or not and <Track Count> doesn't appear to be it...

Hopefully I have explained that clearly enough. Any thoughts/suggestions would be appreciated. Thanks.

23

Questions / Re: <Album Complete?> Data

« on: August 31, 2022, 07:12:12 PM »

Do you perhaps have set Disc# in Preferences > Sorting/Grouping as a criterion to define an album?

I haven't played with this section before, but now that it has my attention...    Right now it is set to what I assume are the defaults: the following fields define an album: 1. Album Artist 2. Album Name

And, have you rescanned the files (and perhaps restarted MB) during testing this?

Many times. I have rescanned the album more than once and I even removed the album from my library and rescanned it.  As far as restarting the app goes - I have restarted it countless times since discovering the issue.

24

Questions / Re: <Album Complete?> Data

« on: August 31, 2022, 01:57:24 PM »

Hi Phred,

All of my albums are flac and have:
TRACKNUMBER
TRACKTOTAL
DISCNUMBER
DISCTOTAL

tags. MusicBee reads all 4 and I suspect uses them to determine if an <Album Complete?>

25

Questions / <Album Complete?> Data

« on: August 31, 2022, 01:27:35 PM »

Hi,

I have a script that I swear was working correctly at some point but it appears I have broken it and I am not sure how to fix it. I have the below script embedded in a larger custom tag:

$If(<Album Complete?>="Y",<Album Track Count>,<Album Track Count>/<Track Count>) Tracks

the goal of the tag:
- If the album is complete (ie all tracks are accounted for) it should display something like "31 Tracks": <total number of album tracks available> Tracks
- If the album is NOT complete (ie there are more or less tracks than expected) it should display something like "30/31 Tracks": <total number of album tracks available>/<total number of album tracks expected> Tracks

The problem seems to lie in: <Album Track Count>/<Track Count>

The <Track Count> does not give me the total expected track count of multi-disc albums. It only seems to account for the first disc.

So If I have a 2 disc set where the first discs looks like this:
TRACKNUMBER=<1-16> TRACKTOTAL=16 DISCNUMBER=1 DISCTOTAL=2
and the second like this:
TRACKNUMBER=<1-15> TRACKTOTAL=15 DISCNUMBER=2 DISCTOTAL=2

"31 Tracks" is displayed

But if i delete track 3 of disc 2 i get: "30/16 Tracks"

ie only the TRACKTOTAL of DISCNUMBER=1 is accounted for...

Long story short - I am trying to display the <expected track count> that <Album Complete?> is using to determine if a album is complete or not and <Track Count> doesn't appear to be it...

Hopefully I have explained that clearly enough. Any thoughts/suggestions would be appreciated. Thanks.

26

Bug Reports / Re: Image Description

« on: August 29, 2022, 01:16:33 PM »

Wow! Thanks for the quick response Steven! Much appreciated!

27

Bug Reports / Image Description

« on: August 28, 2022, 10:07:34 PM »

I just noticed that MusicBee overwrites/erases the description of an embedded image when updating a flac file's tags. I have been using the image description to store the image source url. Qobuz also includes info in this tag with purchased files, if I am not mistaken. Mp3tag allows you to add/view/change image descriptions.

Thanks,
Mee

28

Questions / Re: What external applications are available for MusicBee?

« on: April 09, 2022, 11:15:20 PM »

I use MP3TAG. I tried AudioTester64.exe but it seemed to struggle with batch jobs. It would be a great one to have available though.

29

Questions / Re: What external applications are available for MusicBee?

« on: April 09, 2022, 11:13:04 PM »

Actually not specifically looking for copyright but instead the label/organisation. The reason I included the term is because iTunes doesn't write label/publisher/organization only copyright. It includes the publisher as well as the copyright information, sort of extended version of label/organization.

I'm looking for a tagging application which scraps iTunes for tags, yet to find one. I like their format, full release date instead of just year, Release Type (for sorting) etc etc

I tried kid3 with MusicBrainz and it doesn't appear to write the composer tag. Deezer API also writes composer, author tags, haven't found any application scrapping Deezer, Qobuz, Spotify either.

I'll give Picard a go.

MP3TAG has a third party source script that scrapes apple music and manages to pull pretty much everything - organization, composers, ids, upc, isrc... Deezer, Qobuz and Spotify - I'm not sure about those...

30

Questions / Re: official chromecast plugin

« on: April 09, 2022, 11:06:57 PM »

+1

I'm hoping that transcoding for chomecast as an option. Goggle chokes on hi-res, especially if you are streaming to a group. The only option at this point is to keep duplicate libraries - hi-res and a lower res option. Less than ideal and a royal pain in the butt, especially if you use tags to store ratings..