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.


Topics - Messiaen

Pages: 1
1
Not sure if this has been mentioned before (there seem to be more posts about skins on this forum than any other topic), but when the borders are set to be skinned, some (not all) popup modal windows place the default mouse position exactly 32 pixels above the default button position, so the mouse pointer is no longer on the button itself.

None-too-curiously, it turns out the header-bar is - wait for it - 32 pixels high.  :)

This applies to the windows for:

Tools -> Convert Format
Tools -> Tagging Tools -> Renumber Tracks
Tools -> Artwork Downloader
etc...

Strangely, this does not happen for things like Tools -> Tagging Tools -> Search/Replace or even the main MB Options window.

So, for example, what would ordinarily be a simple two-click action like using a toolbar button to convert tracks (once to open the window and again to accept the default settings), means the mouse must be physically moved down before being able to click the Proceed button.

Occurs for all skins. If the "Skin Window Borders" option is unticked, the default mouse positioning acts as expected.

2
MusicBee Wishlist / Comments for Virtual Tags
« on: June 22, 2023, 01:47:49 PM »
In disturbingly eager anticipation of the 3.6 vtag-limit expansion...

Essentially the idea is to just allow C++ style comments to suffix virtual tag definitions to explain their what/why/how aspects to "my future self", such as why I chose to use an overly-complicated $If/$Contains/$Left/$Right combo instead of an overly complicated $RxMatch expression.  ;)

Or, in particular, a very handy way of storing "alternate" regex expressions along the road to finding the one that works the best, and why.

$RxReplace(<Genre>,"(.*?),\s(.*?)$","$2 $1") // Swap comma-separated genre-sorting elements
$Pad($RxMatch($Div($Mod(<h.Work Duration>,3600),60),"\d+"),2) // Cleanup leftover minutes
<Work><Path> // Exclusion mask to stop grouping of Works by same Album Artists, etc...

I have many small "helper sub-function" tags which are used within more than one larger more complex tag, and creating clever names for these tags can only go so far, whereas an appended comment would allow me to instantly recall what other functions reference this function, and if it's ever even used (or still used) at all.

My future self thanks you for your consideration when he has to re-edit a tag a year from now that his brain-addled contemporary self concoted at 4am.  :)

3
MusicBee Wishlist / Scrollbar for Excessive Highlighting Rules
« on: March 26, 2023, 12:59:05 PM »
Personally, this is more of a bug than a request (everyone with a problem always thinks that), but while highlighting rules for icons and such were introduced 10 years ago, apparently not too many people have noticed that as you add more and more rules, the modal window gets longer and longer until it's no longer usable.

I got to 23 rules and lost the bottom Save/Cancel buttons, but when I hit 27 rules the controls were simply inaccessible.

So, suggestion: Scrollbar, please!

In case you're wondering why I have so many rules, I was looking through old topics on customising and came upon people who had used the highlighting icons to add country-of-origin flags to the display, and it works quite well.  Unfortunately you need 1 rule per icon per flag per country, and I've got about 50 more to go.

As a workaround I started manually editing the settings.ini file, and it appears that inserting more and more <Rule></Rule> sets copied and modified from previous rules does the job, but it's a bit impractical.  At least I can identify the Latvian flag in my sleep now, so there's hope yet.

Code
 <Rule>
  <Name>Latvia</Name>
  <Query>
   <CombineMethod>0</CombineMethod>
   <Criteria>
    <Field>46</Field>
    <Comparison>0</Comparison>
    <Value1>Latvia</Value1>
   </Criteria>
  </Query>
  <Icon>_Latvia.png</Icon>
  <Colour>-8355712</Colour>
 </Rule>


4
Bug Reports / Some virtual functions only accept integer constants
« on: January 06, 2023, 10:10:46 AM »
A silly example, but:

$Left("123",$Add(1,1)) results in an error, whereas $Left("123",2) gives the expected result.

Essentially the use of any integer-returning function (especially a useful one like $Len) will error out when applied to an integer-expecting parameter in $Left(), $Right(), $CutLeft(), and $CutRight() virtual expressions.

5
In Album and Tracks view, when hovering over any of the track-layout/artwork-fields, the windows default Link-Select "pointy finger" mouse icon appears instead of whatever the user has defined in their system preferences (which generally all browsing-type programmes respect).  Whilst the pointy-finger icon is pleasingly retro, it's (if nothing else) completely prejudiced towards right-handed folk.  ;)



Also, it seems all the displayed fields are "links", which is fine for Artist, Year, etc, but this also appears to apply to custom fields - for example, I include Album Size as one of the fields, and if I click on it MusicBee dutifully shows me all the albums that are equally (in this case) 172 MB in size.  Whilst esoterically entertaining (I have 11 albums of 172 MB's each), it's a little odd.  A "feature", I guess? Is there any way to disable this "linkability" status?

6
Questions / Replacement processing in RegExp
« on: August 19, 2022, 02:46:33 PM »
Essentially I'm wondering if the "replace" text used in the tag search/replace function (as well as the $RxReplace() virtual function) is processed for anything other than the normal $nn backreference tokens?

In particular, the \U...\E switches common to RegExp replacements, where the text between \U and \E is converted to upper-case before being pasted in.

As a simple example, if I wanted to capitalize the first letter in a title after a dash mark ("-") I would use:

Code
\-(.)

with the replacement text:

Code
-\U$1\E

Testing with the title "rem-nant" should return as "rem-Nant", except in MB the returned string is "rem-\Un\Eant" which basically means the \U and \E regexp switches are ignored.

I also tested this with the virtual function $RxReplace(<Title>,"\-(.)","-\U$1\E") with the same result.

My original use case for this was more complex, but you get the idea.  For comparison, I ultimately just used the regexp replace function in MP3tag to accomplish this, so I know the syntax is correct, but as MB supports regexp in most things, it would make sense for this too to work.  Unless I'm missing something? :-\

As this could be considered anything from a bug to an oversight or even a "feature" depending on one's point of view, I ask as a general query.

7
Using 3.5.8233 P, this appears to be a regression as it does not happen with 3.4 - and, for me at least, is repeatable.

Basically I drop a folder containing a single FLAC rip and its CUE file into the inbox, select the album and convert it to MP3 (320, using "replace the source file" setting) and MB correctly produces the individual files as expected (in the folder).

However, when the conversion is complete the album simply vanishes from the inbox, and must be "re-dropped" for the usual tag editing.  And by "vanishes" I mean the files remain where they are supposed to be on the disc, it's just that the album is visually wiped from the inbox, and attempts to F5-refresh have no effect.

This only happens with single FLAC + CUE conversions... if the album is already in separate FLAC files, the album display remains as expected afterwards.

Also, (unrelated to the above), folders which have a '.' anywhere in the name ("Jarrett - Köln (44.1kHz)" can't be dragged into the inbox (the cursor changes to "blocked"); however, editing the name to remove or change the '.' character to something else such as "44-1kHz" will allow dropping as usual.  Strange.

Pages: 1