Topics

1

MusicBee Wishlist / Start / End Times

« on: October 15, 2022, 02:42:11 PM »

I just discovered the "Start Time" and "End Time" settings in the track editor. Perfect timing as I was looking for a way to cut out the studio chatter from some of the alternate tracks included with the new super deluxe edition of a Charlie Brown Christmas. That said it triggered a few suggestions I wanted to share:

- If I set, save and then uncheck the start and/or stop time the values should remain. So, if and when I check them again, the previous values are assumed as a starting point. It took me some time to find exactly where I wanted these set and it was frustrating to lose them just because I unchecked them for a listen or two
- Allow multiple start / stop times - a bit of a stretch but I found some songs (medleys) I wanted to break into pieces. A way to indicate track 2a (start/end) 2b (start/end) etc. Would be nice, if possible.
- cut out a section of a track, vs just the start/end. Again, would allow someone to clean out studio chatter, etc.
- Another stretch - it would be nice to indicate start/end times only when not listening to the album in order. In other words, when listening to the album I want to ignore my start/end times BUT if listening to a track in isolation, an album on random or listening to a track as part of a playlist it would be nice to recognize the start/end times. This would allow someone to keep the flow of an album, including listening to studio chatter, etc. but still use a "cleaner" cut of a track in a playlist.

Thanks!

2

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

3

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?

4

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.

5

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.

6

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

7

MusicBee Wishlist / Seperate/Categorize Albums by Type

« on: January 18, 2021, 02:14:46 AM »

I like how some services / apps separate albums by type:
- Album
- EP
- Single
- Live
- Compilation
- Box Set
- Bootleg
- Appears On

It would be great if MusicBee was able to do this as well. I think it might require a new tag to implement but if you are a big fan of a few older artists, as I am, I expect you will quickly find that their catalogue becomes a bit of a mess otherwise - see Blondie, Radiohead, Bowie, U2, Kiss, etc...

8

MusicBee Wishlist / Read Only Tags

« on: January 11, 2021, 07:33:45 PM »

It would be nice to have the ability to display tags like UPC, ISRC, etc. as read only - knowing they won't accidently be changed or deleted. I can't imagine ever wanting to alter some tags. That said, if the need for change arises I am good with it be slightly awkward (using a 3rd party editor or having to change the field settings.)

Thanks

9

MusicBee Wishlist / Customize Now Playing Track Details

« on: January 11, 2021, 07:28:35 PM »

Allow the now playing track details that appear around the progress bar in the player controls to be customized. While we have the ability to customize them in multi-line view it would be nice to be able to tweak them when displayed as a single view - I prefer <title> - <artist>, for eg.

10

MusicBee Wishlist / Customizable Footer and additional subheader(s) on "show tracks below" view

« on: January 11, 2021, 07:14:17 PM »

When showing tracks directly below an album it would be nice to have more room to play with:

- The option to show a footer would be nice for metadata like copyright, organization, track count, comment(s), replayGain, etc.
- Additional sub-headers would also be nice. right now I am using bullets to separate multiple fields - date, genre, track count, running time, alerts (metadata checks I run), etc. Having the ability to spread this info over multiple lines would make it a far more readable/flexible view for me.

Thanks