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 - karbock

Pages: 1 23 4 ... 25
Skins / Savanna & Wisteria (skins)
« on: May 24, 2024, 01:26:25 PM »
Savanna & Wisteria skins

Two light skins based on Cheetah DNA 1.4 by hiccup.
  • Savanna: light warm tones based on a brown palette.
  • Wisteria: light tones based on a mauve/violet palette.
They are in .XML format (editable), so that you can adapt them to your liking.

Download links


Savanna skin
Wisteria skin
Album view
Album & Tracks view
Now Playing

Changes, compared to Cheetah DNA

Gradients used for:
  • player panel background
  • column headers
  • highlighted tab
  • scrollbar buttons
  • setting buttons
Alternating colours added for:
  • now playing
  • thumbnail browser

Fonts used in the screenshots

Font name
Supported scripts
Default fontUbuntuLatin, Greek, Cyrillic
Sub-grouping headerLiterataLatin, Greek, Cyrillic
Now playing trackLiterataLatin, Greek, Cyrillic
LyricsMonomakh UnicodeLatin, Cyrillic, early Cyrillic (for Slavonic)

General Discussions / Re: MusicBee v3.6
« on: May 14, 2024, 05:39:51 PM »
I use MB portable patched May 13th. I would like to try the 3.6 portable version. Is it possible (and advisable) to share the library with both versions? Thanks for the replies.
I've been using both 3.5 P and 3.6 P for weeks without a glitch.
The two .EXE are stored in the same directory, with a suffix to distinguish them (MusicBee_3.5.exe).
They share the same configuration + library.

Skins / Re: question about skinning
« on: May 14, 2024, 02:30:40 PM »
If you install Sample Skin by hiccup, you will be able to locate each ID.

  • Install and select "Sample Skin".
  • Use any colour picker to get the r,g,b value of the desired colour.
  • Search "Sample Skin.xml" for the r,g,b code.
    Each colour is used only once in the .XML.

If you don't have any colour picker, I recommend Instant EyeDropper (free).

EDIT: Instant EyeDropper (no space).

Skins / Re: Sample Skin
« on: May 12, 2024, 08:26:08 AM »
All correct now, thanks Steven!

Skins / Re: Sample Skin
« on: May 09, 2024, 06:16:01 PM »
I tried Segoe UI 14, and the button doesn't get misaligned for me.
It might be of help if you can figure out why that is happening for you.
The vertical misalignment of "MusicBee" in the button is only visible with some fonts (*), even with row padding = compressed,
but not with Segoe UI 14 for example.
Anyway, it doesn't affect the presence of the black line over the track title.
(*) Such as: Ubuntu, Papyrus, Comfortaa, Commissioner, Kristen ITC (not shipped with Windows).

From the tests performed so far, the only factor triggering the black line is the size of the default font.
And the larger the default font, the thicker the black line.

Skins / Re: Sample Skin
« on: May 09, 2024, 05:06:40 PM »
Is it only the player panel font that you have set to a custom one, or others also?
The problem occurs with larger sizes for the default font:
* 14 and above with Segoe UI, Trebuchet, Ubuntu
* 16 and above with Arial, Candara

The reason why that ProTunes skin doesn't show the issue for you is probably because it has "UseModernMenuButton"> set to "true".
I am guessing that if you use:
<element id="UseModernMenuButton">true</element>
in the Sample Skin, it will also display the black line for you?
No change with that setting, though.

Skins / Re: Sample Skin
« on: May 09, 2024, 09:38:54 AM »
So maybe I should add a comment element to the Sample Skin that says: "file a bug report" when RGB "0,0,0"is picked?  ;-)

Well, when I posted, I wasn't 100% sure that it was a bug, since while testing I had come across one (and only one) .XML without the issue: ProTunes.
I was still trying to find what difference between SampleSkin and ProTunes could cause it.
I have extracted lists of the IDs present in either file (pruned of their parameters and sorted), if you are interested.
A tool like KDiff3 can highlight the differences, example:

Skins / Re: Sample Skin
« on: May 08, 2024, 12:35:09 PM »
Ok, thanks Steven!

Skins / Re: Sample Skin
« on: May 08, 2024, 12:04:57 PM »
Font Literata, bold italic 18
Windows scaling 100%

The font is available here:

Skins / Re: Sample Skin
« on: May 08, 2024, 10:22:18 AM »
(1) Great tool!

(2) I've stumbled on a really tricky colour issue, which is only visible when the player controls are docked at the top:
a black line above the track title (1-px thick, rgb=0,0,0).

Zoomed capture showing the line with "Sample Skin.xml":

It is striking with skins using lighter tones, such as Cheetah DNA:

The black line doesn't top the whole rectangle containing (tile+time+progress bar), but only the part used to display the track title.

The artefact shows up with a series of .XML I've tested:
  • Absolute Zero
  • AeroBee
  • Midnight
  • Phred on the lookout
  • Sky Blue
  • Threshold flat
  • Cheetah DNA
  • Chameleon DNA
  • Blue
  • iBee
With skin "MusicBee3", it is visible with both the .XML and .XMLC.

I haven't found any setting explaining this so far
* in RotemK's guide
* in the wiki
* when browsing through the .XML files (especially the PlayerTopFlat and PlayerFlat settings).

Any idea of the possible cause?

Plugins / Re: Additional Tagging & Reporting Tools
« on: April 29, 2024, 06:08:56 PM »
An All-in-One, Forty-Two bar R&B vs. Neo-progressive Rock Medley: A Journey (Uma Viagem) (Moby remix)
Tricky questions are posed here.

  • According to the MLA Handbook:
    Forty-Two, Neo-progressive (because neo- is a prefix)
  • According to the Chicago Manual of Style:
    Forty-Two, Neo-Progressive

To address this topic, TitleCase would need a fifth parameters indicating after what characters a subtitle starts.

I don't think it's necessary to overload the coding (and the coder  :)) for minor cases like that.

There are already cases impossible to solve without AI anyway. Example:
  • Lifting off the Ground
    'off' is a short preposition, and should not be capitalised.
  • Taking Off, No Looking Back
    'off' is an adverb, and should be capitalised.

Moreover, English and French for example have totally different title case rules.

TitleCase4 is already a wonderful tool.

Plugins / Re: Additional Tagging & Reporting Tools
« on: April 29, 2024, 05:08:17 PM »
@boroda, have you considered having only one $TitleCase function instead of 4 versions?
I was about to propose the same.

Plugins / Re: Additional Tagging & Reporting Tools
« on: April 28, 2024, 08:11:10 AM »
no, it's not intentional. and i see from your example that this is a glaring bug. i'll fix it tomorrow.

For the documentation of the TitleCase functions, I suggest the following parameter pseudos, which seem clearer to me:

i've tired of the ugly "New" text label on the forum instead of the old icon, so i've created css style for the "Stylus" browser extension (available for all modern browsers). this css style replaces the missing "New" site icon by the icon directly embedded to the style.

this is how the forum is now looking for me:

the extension link to google chrome store:

css code:
/* ==UserStyle==
@name  - 29.06.2023, 20:38:40
@version        1.0.0
@description    A new userstyle
@author         Me
==/UserStyle== */

@-moz-document url-prefix("") {
        content: url("data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAQCAYAAAAf8/9hAAAACXBIWXMAAAsSAAALEgHS3X78AAADMElEQVR4nG2TaUhUURTH//e9N4uj1YyzNSNttkiWfqiwzJCixq2FiCCzaLOF6kNRWARKX/JLZQlCZJkRaUhUX8xsihZsMVokSnNaqUwnm1GbZhyXmfduxxGiwseDx73vnN/5n/89V+KcY6Tn3FIWo3AYGTDIBHzPvz5yoPT34vwKJsghrNJoscliN84arZd04RDkHq/fU7mU3STC6fw67hoRULmcmRlH2Yx5yWsSM9cixjQRoGwmCFB4OLaj+VFCU1113plMVrDdyS/8A6DkaJHhQnrexuxJaSvgf1MDz8tjGPB3Q5REaIxTYUtah5yD5eaG8sMV1bl6eV3Nz6o/ACWMnXNyFlFyNjpv7UXwRxtEFUP0uPkI//qKQLsLQXcRTLPzkL6tUKot3l3yqfbog/jlB75IFTlsQqxZuyPRkY/uxhIEPW1gkgBRzWCatwvBd1fQ3/0N1Au8Ly4hzpyE5IyVFtfdqq0EKJKo+rLxyWnxIv+BwNfnYGQ7lxXwMEkLBUldL60jOjF0Dr6WaoyfvQ8tDXeyaLNIEgWkGOOsQr/3M+QQR+z0dKhGWwhEJE0ctHELYZV0IEnwfXiIPs9HGFQaRKn7zMMeUKuSikMOE55etXUOtJZEKkgLyQBJPxOi1kAADXnxDqHeroga8kiMABQZrT5vCLbJeghkqfdJaSRAUgmwZZ1F8NNVdL2+AUbHNKQwKnYssUX0BoTAsAIBzg7X490zM1Yb1HozBno84CSfjp/+qkiUODQOEBQGReaIic9Gd9trMLW+KQIQVWhs/9BR537TuN40dw/ctwshUyDnAvrdrxDyeyPGKmRsjH0KdFOW4dGJvbI9yVERAWyp5TLNfXHj5YrF2ftLbDbHEWqjDIO+TrjvHY8kC2oBoyYtgCFlD1zOKnS2eysX7My9/2eQhuabIJvrT+yrTF2zwz42oxTKr7fo9/WQWSK0xngMKqPQdLkEL+88vqIzmgqiEhz8n7tAECdBljhPnTxkn2zNtCakWcYY1NQ/Q1fD09C35ifve7rC5eRZee5Fz8CIt5EgrfTZcDaLpX5pveYgI6dRmYCi4JmgQv3Wet7x/3X+DXi+Slb6F430AAAAAElFTkSuQmCC");

To ensure that the above code also works for the PM inbox:
@-moz-document url-prefix("") {

@-moz-document url-prefix("") {

Plugins / Re: Additional Tagging & Reporting Tools
« on: April 27, 2024, 04:08:31 PM »

    excepted_words: list of words separated by spaces, which will become lowercase (except for the 1st and the last words)
    word_splitters: list of characters separated by spaces, which must be treated as word splitters. i'd recommend to enclose the list into quotes (e.g. "& . -")
    exception_chars: list of characters separated by spaces after which the words become lowercase (e.g. ' for something like "Someone's")
exception_chars is not taken into account for the last word of the string. Is it intentional?

$TitleCase4("Title (remixed) (remixed)","a an the and but nor or at by in of on to for","& - .","(")
Title (remixed) (Remixed)

Pages: 1 23 4 ... 25