Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Mayibongwe

Pages: 12 3 ... 42
Ahhhhh! I see what you mean...

You are absolutely correct.
What's suggested here could function in the same breath as the "sort as" feature.
In the preferences setting, MusicBee already maintains some list of sort as values there, and it automatically writes them to tracks that matches the criteria.

I also don't see myself having to use something like this in the near future (if ever).
I don't think I have any useful information that I'd ever want shared uniformly across tracks from the same artist.

With that said, I also do see some potential in such a feature evolving into something that a number of people would appreciate the existence of.
So, if someday I ever felt like taking on the exercise or project, this is how I'd offer it (as a plugin):

If such an offline* database was going to be maintained manually,
Then I wouldn't see how it would have been more advantageous over a process where you would save that value to one of the artist's tracks.
And then applied some plugin-defined command to write (or append) that one track's tag to the same tag on the other artist's tracks.

*existing outside of MusicBee or the music files
The AT&RT plugin sounds like it could already do the process I described though

Questions / Re: Copy vs Move behaviour
« on: May 25, 2023, 05:28:20 PM »
As per the piece of info linked here and on another thread that I can't find at the moment:

MusicBee follows Windows's standard behaviour for moving files within or across different drives.
I could be wrong but I seriously doubt there's a setting anywhere in MusicBee that will do what you want.

Was about to post the above when I got notified of a reply - I'm gonna post that anyway.

you can tweak this behavior with Winaero Tweaker
Will MusicBee also conform to that tweaked behaviour?
It's not something I've tried, but my initial expectation would have been that MusicBee's behaviour for the above would be independent of any tweaks done to the OS itself.

Virtual tags can manipulate just about every shred of information located in your music files.
So, assuming that the database you mentioned is actually referring to some "year artist" tag stored within your track files:
The virtual tag formula should be something as simple as:

$Sub(<year release song>,<year artist>) whatever tag names reference the info you require

Questions / Re: Edit VIEWED format of tags?
« on: May 25, 2023, 04:55:28 PM »
Yeah, there is.

MusicBee's virtual tags were designed exactly for this purpose.
You'll find these two links helpful. Shout if you're stuck:

Questions / Re: Can MB 3.5 sort/group multi-disc tracs vertically?
« on: May 20, 2023, 06:35:24 PM »
In case Mayibongwe does not find any other solution, I will follow your suggestion to create a wishlist item. Unfortunately, there doesn't seem to be much hope in that case.
Sorry, try the wishlist champ.
You must really like the old look if you still haven't managed to get used to the new behaviour after all this time...

Questions / Re: Any Way To Resize Album Covers??
« on: May 20, 2023, 12:26:09 PM »
This can't be done within MB.
While there isn't any straightforward way to do it within MusicBee, it definitely can be done through a process which involves syncing.
One would need to perform a sync to their mobile device or some pc folder using virtual devices (I'm not too familiar with how they work but there are explanations on the forum).

A sync is required in order to access the option resize artwork to...
After the syncing, all that would be left is to overwrite the original files with the new ones containing the resized artwork.

I did explain it a while ago here. The use case is a little different to yours but the idea is still the same.

phred's method and The Incredible Boom Boom's that is mentioned on the linked thread is probably less of a headache though.
Just wanted to make it known that MusicBee does have a resize option - perhaps it can be split into one that doesn't involve a sync?

Questions / Re: Plugins
« on: May 20, 2023, 11:49:21 AM »
after uninstalling and reinstallingi got most of the plugins to work besides dsp plugins and 3dbee. 3dbee always  comes back with error 
"System.ArgumentOutOfRangeException: Index was out of range. Must be non-negative and less than the size of the collection."
dsp plugins disappear when moved to the appropriate plugins folder in x86   
Adding on to say, this is the point where you then have to direct the errors to the specific plugin threads if you have any hopes of getting them to work.

Is it possible to add more sources to Musicbee when search for album covers??
Don't think I saw a mention of "yes, it is possible through plugins" - whether those plugins exist or not atm is another story though.
What other sources in addition to MusicBee's built-in providers did you have in mind that also have the image resolution you specified?

Questions / Re: File deletion behavior
« on: May 20, 2023, 11:32:28 AM »
I can only assume the behaviour is intended, and speaking for myself, it really sounds ideal.

Deleting a track from the library only (whether intentional or accidental):

it sounds good knowing MusicBee is able to preserve that old data and continue where it left off if one were to add it back.
So, at the moment, there are options for both users - one who'd want to the data back later on and the other who'd want it permanently gone from MusicBee.
The suggestion would take away the first option without affecting the other anyhow.

On the flip side, deleting a track from both the library and the computer:

It makes sense that the data is automatically deleted since the track is basically "gone forever".

Questions / Re: Fade out a song within a playlist
« on: May 15, 2023, 09:14:38 PM »
Welcome to the forum, bg428

There's a 'crossfade' setting in the Preferences that sounds like it could do what you want. Note that the setting is global though, I doubt you can limit it to just playlists only.

Some reading here and a forum search should guide you accordingly:

Questions / Re: Can MB 3.5 sort/group multi-disc tracs vertically?
« on: May 15, 2023, 08:58:11 PM »
The view in ur screenshot is the expanded panel of the Album Covers View. So, the two settings that you tried out relate to views that are irrelevant to the one you are displaying.

I won't be able to have a closer look until Friday earliest. In the interim, I can only suggest that you dig up the customise panel for the Album Covers view and then play around with the settings over there.

To find the customise panel, click on the 'Albums' header menu - have a look at the Wiki if you cannot locate that panel.

Questions / Re: 'composer' incorrectly parsed in virtual tags
« on: May 13, 2023, 05:47:59 PM »
Not to be misunderstood: I welcome the introduction of <composers>.
It's the suggested change of getting <composer> to not parse <display composer> that I feel would be consequential to <artist> & <artists> as they both currently use the same behavior.
The suggestion is valid, the way I see it too, but if taken up, won't it necessitate a change in the result/output of <artist> as well? (for uniformity/consistency)

For me, then <Composer> will be a singular value (it could be "Composer1, Composer2" though, note the use of a comma instead of a semicolon)
<Composers> will contain all 'composers', which in my case (using Picard) will automatically get populated with all the people that had some significant role in how the composition came to be.
Will <composers> be a writable tag? I got the impression that it would only be for display purposes in the virtual tag editor and other concerned areas.
I'm most probably confused or uninformed on how composers actually work - I can't understand at the moment why you don't prefer <composer> having multi-values.

If <composers> is to work the same as <artists> (as I've understood it), it will merely be a readable tag that contains all the individual <composer> tags.
The same multiple tags that you plan to add onto <composers>, I don't get why you haven't added them as individual <composer> tags yet.

I have a feeling that I missed the mark completely, but I wouldn't like for you to derail the purpose of this thread by explaining the concept of composers to me.
This wouldn't be the topic for that. Ignore my statements if they are truly missing the point.

Questions / Re: 'composer' incorrectly parsed in virtual tags
« on: May 13, 2023, 05:02:42 PM »
1. Can it be changed so that the actual 'Composer' tag is always used when a virtual tag uses <Composer>, and does not switch to using Display Composer if that happens to be populated too?
    (perhaps <Display Composer> could additionally be made available for use in virtual tags so to have that option available too? But then again that may not be needed when 3.6 gets <Composers> )
2. Are there occasions where MusicBee will auto-populate the Display Composer tag by itself? (similar to Display Artist)
The introduction of <composers> will make it possible to access the actual <composer> value(s) - which wasn't possible prior to you bringing this up.
I'm not so sure if that change should be done now so far in the development as:
<artist> (outputs display artist) and <artists> (outputs the actual value(s)) have also worked on the same basis since inception by the looks of it.

In my testing, <display composer> is only written to the file when the composer field in the Tag Editor is different from the actual value(s) in <composer>, if that make sense.

For now I am deleting all existing Display Composer tags from my library, which solves the current issues, but I am concerned MusicBee might populate them again at some point without me knowing.
Not knowing anything about the classical side of music, are you sure that's a good idea...
Looking at ur screenshot, I don't see C. Richard F. Maunder as a separate <composer> tag.
Do you have that value saved elsewhere? Won't you lose a record of that person in the file once you clear <display composer>?

Plugins / Re: LyricsReloaded (Latest)
« on: May 13, 2023, 03:31:02 PM »

Again, well done though on the provider. I will be adding it to the list of optional providers in the download link when I get to it.
Will also do some tests on it and revert with comments.
This is done now. No room for improvements in the yml. It's impressive how got everything perfect on your first try. Well done!

Pages: 12 3 ... 42