Messages

1

MusicBee Wishlist / Re: Ability to Add PDFs to Library

« on: October 20, 2022, 03:37:24 PM »

I love this addition! An additional suggestion:

In addition to the "album covers" view -> "show the tracks..." -> "directly under the selected album..."  -> "enable all artwork to be selected and displayed"
It would be great to include an option to display a link/icon to each PDF there. Something like:
In addition to the "album covers" view -> "show the tracks..." -> "directly under the selected album..."  -> "enable all PDF booklets to be selected and displayed" (or whatever language makes sense)

 Ideally, it would display icons for PDFs and images in the same way, as a single strip of clickable icons. This would allow me to drill down into images and PDFs in a single, seamless and consolidated way. While I realize displaying a thumbnail might not be possible, an icon would be enough, imo. Hopefully, that description makes sense...

2

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!

3

Plugins / Re: Musicbee Chromecast Plugin

« on: October 15, 2022, 02:28:20 PM »

I initially had an issue where I could see Chromecast devices and select them but couldn't stream to them. It turns out Windows defender wasn't properly configured. I needed to go to "Windows Defender Firewall" -> "Allowed Apps" and enable both Public and Private access to "MusicBee Chromecast"

4

Plugins / Re: Musicbee Chromecast Plugin

« on: October 02, 2022, 03:48:42 PM »

Curious to know the status of native MusicBee support for Chromecast?

I started something that made quite a bit of progress but have no plans to continue. Happy to send the code if you want to look at it for ideas

Hi Steven. That would be great! Thanks! It's been a busy week but I am hoping to spend some tinker time playing around this week/weekend.

5

Plugins / Re: Musicbee Chromecast Plugin

« on: September 22, 2022, 11:47:48 PM »

Thanks for a great plugin!

Curious to know the status of native MusicBee support for Chromecast? I would like to see a few things updated:
- The font size for the device list on the selection dialog is too big on my system
- I would like to see the display broken out as an isolated option (ie play on one speaker and display on another device, such as a TV)
- transcoding. This is a big one, as the plugin appears to send the audio in it's native bit/sample rate. My devices seem to choke on anything more than 24/48. So, I would like to see a lower bitrate option or see the stream bit/sample rate capped by default

I am considering taking TroyFernandes up on his offer and forking the build but if native support is on the horizon I would rather wait it out as I suspect my progress would be slow...

6

Questions / Re: Special Characters in Custom Web Links

« on: September 21, 2022, 10:08:45 PM »

I agree that it would be nice if it was handled internally & that $Replace seems as though it should be able to handle the use case. I was actually surprised the <origin> tag wasn't setup as a web link by default, it seems tailor-made for that purpose. Oh well, I guess that means MusicBee is only 1000x better than all the other music apps out there (rather than 1001x) 

7

Questions / Re: Special Characters in Custom Web Links

« on: September 21, 2022, 07:07:59 PM »

That did the trick! Thanks!

8

Questions / Re: Special Characters in Custom Web Links

« on: September 21, 2022, 06:38:44 PM »

I have tried several variations, as far as setup goes, but my goal is pretty straightforward:

I use the origin tag to track the origin of a track, a link to the album in the Qobuz web store, in this case:
https://www.qobuz.com/us-en/album/revolver-the-beatles/0060254767013

Then I setup the customize web link via the Track Information panel settings (to your point, you can also view/edit the custom web link list via preferences -> Internet):
name="Origin"
web-link=<Origin>

I then check the "show web links:" option for "Origin" on the Track Information panel settings form, save and attempt to open the link from the track information panel.

That's it...

Of note:
- I can see the origin tag in the tag editor when an individual track is selected as well.
- I use the field to help determine the source of a track - Qobuz, HDTracks, whatever... Hopefully, I am using it as intented.

9

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

10

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

11

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.

12

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.

13

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?

14

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

15

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.