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

Pages: 12 3 ... 7
Steven, this issue is discussed in detail on this topic:

i'm not sure if it's important, but at least it's very strange and unexpected.

Bug Reports / Static playlist settings bug
« on: August 01, 2023, 03:07:18 PM »
while i was trying to answer to the question here:

1. i've found out that, when right-click on static playlist, select "playlist settings", and select "use custom fields for this playlist only", sorting is not kept for this playlist only (i haven't checked if the set of displayed fields is kept in this case).

2. when you click "settings" hyperlink in playlist header, sorting is kept for this playlist only (again, i haven't checked if the set of displayed fields is kept in this case).

3. playlist settings changed by right-clicking playlist and selecting "playlist settings", and settings changed by clicking "settings" word in playlist header are saved in both cases, but these saved settings are different!

p.s. it's all for mb 3.5.8610 P

MusicBee API / Permanent link to the latest MusicBee interface file
« on: July 18, 2023, 11:45:36 AM »
Steven, could you pin a topic containing a permanent link to the latest MusicBee interface files (and maybe to example projects) - C# (at least) and VB?

please add a new menu item "Local Node Only (Keep query)" to the search field in the top right corner of mb main window. it must behave the same way as the currently available "Local Node Only" option, but the query string must be kept, when the user switches a music library node (e.g. switches playlists).

for the reference, see this topic:

Firstly, both albums must contain the same number of tracks, and must be identically tagged and have identical filenames including file extensions. At least all tags you are using in your auto-playlists must be the same, if you want to keep auto-playlists working. If you consider your higher quality album already properly tagged, then skip reading to Part 2.

NOTE: Higher quality album music files must be stored in the folder different from old lower quality tracks folder.


1. Manually add (e.g. just drag'n'prop tracks from file manager to MusicBee) higher quality album to the inbox.

2. Copy mostly important tags (i.e. tags, which you are going to use in the future) from lower quality album to higher quality one. You can copy tags using "Copy tags to clipboard"/"Paste tags from clipboard" commands of Additional Tagging & Reporting Tools plugin. Make sure that track count and track order are the same for both album versions. The mostly easy way to sort tracks identically is to sort them by tracks number on the album (if track numbers are already correct for both album versions).


Rename both old tracks and new tracks, so their filenames are the same for the same tracks.

1A. Filenames of music files must have the same extensions for both old and new album versions. If they don't, then convert old tracks to file format of new tracks: select all tracks of old album version, click MusicBee menu> Tools> Convert Format. Select format of new tracks in the "encode as" field (you can set any quality because you only need to change extensions of files, it's better to choose the fastest encoding preset, because these files will be anyway replaced by new higher quality, probably lossless, ones). Select option "Replace the source file". Click "Proceed".

1B. Select all old tracks, which are already in the library, then click MusicBee menu> Tools> Organize Files. Uncheck "to folder", remove all exceptions (if any), change last part of "naming template" (which corresponds to filenames only, not to folders), click "Reorganize", or just copy this part to use it in the following step.

2. Select all new tracks in the inbox, then click MusicBee menu> Tools> Organize Files. Uncheck "to folder", remove all exceptions (if any), change last part of "naming template" to make it the same as naming template for old tracks in the library. Click "Reorganize".

3. Close MusicBee.

4. Copy new album tracks over old album tracks with file manager, overwriting old music files. You can see tracks folder (paths) right-clicking on one of the tracks of the album, then clicking "Edit", and selecting "Properties" tab in tag editor (see "Location" field at the bottom of "Properties" tab).

5. Open MusicBee and delete new album tracks from the inbox. You may want to delete music files contained in the inbox, both from the inbox and from the PC (because you already have the copy of these files in the library by this moment).


Questions / Can't reopen DSP effects setiings window
« on: June 02, 2023, 04:51:55 PM »
using 3.5.8540 P.

1st time i click (using fresh mb portable installation) Controls> DSP Effects, i see DSP effects settings window, and can adjust DSP options. but any time later, i can turn on/off DSP Effects menu item only. the only way for me to open DSP Effects window again is to delete mb settings file (MusicBee3Settings.ini and MusicBee3Settings.bak).

I've found the new free app (AudioRelay), which seems can do all that subsonic can. this app can stream any audio (received from mic or from other apps, from pc or the phone(s)) to the network, and can receive audio from the network and play it on your device(s) (pc or phone).

NOTE: it's officially claimed transferring audio from pc to the phone or from the phone to pc only, but it seems that this app can transfer audio from pc to pc(s) too (this might allow organizing multiroom playback). but this needs to checked (i haven't tested this app yet).

AudioRelay site

well, transferring audio to multiple devices is not free (it requires buying premium version).

MusicBee API / virtual device api enhancements
« on: May 10, 2023, 02:29:46 PM »
in current mb version artworks can be only either embedded or skipped/stripped (if i tick "do not copy artwork") on syncing with plugin virtual device. they can't be copied to folder.jpg or <filename template> files. also, artworks remain embedded if i select one of "copy artwork to image file" options, but this is a desirable behavior for me.

also, lyrics settings are completely missing for plugin virtual devices, and lyrics only preserved (even in case of track reencoding) if lyrics were embedded.

could you add lyrics settings for plugin virtual devices, make mb to respect artwork/lyrics settings, and send to plugin non-music artwork/lyrics files if required along with tracks?

the most desirable mb behavior for me:

1.  mb should not change source track if it's not really required, i.e. mb shouldn't remove embedded artwork/lyrics, if they are embedded, (but mb still should send them as external files to plugin) from source track if user has chosen to sync artwork/lyrics as external files, and no actual reencoding of audio data has been performed.

so that "sync links" plugin could create symbolic/hard links to source tracks instead of copying tracks, if it's possible to do not violating practically important user settings.

2. external artworks/lyrics should be sent to plugin just along with generic tracks on syncing. i can internally in plugin differentiate music files from artworks/lyrics file by file extension.

api function:


must return temp file for external artwork/lyrics if it has been extracted from track, but original file if it has been initially stored as external file in mb library, so that "sync links" plugin could just create symbolic/hard links to artwork/lyrics file, when possible.

MusicBee Wishlist / Automatic updating/uninstallation of plugins
« on: May 10, 2023, 02:11:37 PM »
i've posted it sometime ago on bag reports board, but it's actually a request of new feature (except for #1). here is the link to original topic:

General Discussions / Add FAQ to MB help menu
« on: May 07, 2023, 10:59:28 AM »
Steven, maybe it's worth to add the link (preferably localizable) to the wiki FAQ page to mb "help" menu, because this page is not displayed anymore on mb site?

MusicBee Wishlist / new placement of "configure fields" button
« on: December 23, 2022, 09:12:29 PM »
could "configure fields" button be moved one level up, next to "define new tags" button? current button placement is not logical and obvious.

it would be helpful to move the definition of virtual tags one level up also, next to the definition of custom tags.



maybe, it's better to rename "define new tags" to "customize tags", and move custom tag definitions to the current "define new tags" window (above virtual tags panel). and, rename "configure fields" button to something like "field properties".

Bug Reports / tag editor error
« on: December 20, 2022, 03:45:50 PM »
open floating tag editor, change some tag, undo changes, click "show in panel":

MusicBee v3.5.8388.32476P  (Win10.0), 20 дек 2022 18:39:

System.InvalidCastException: Не удалось привести тип объекта "#=zckcak0QrBZYgnTRbZa4zluM=[]" к типу "#=ziUjZRnOYDnu1HjLs2jh_VUo=[#=zckcak0QrBZYgnTRbZa4zluM=]".
   в #=zF4z$pSUU6B5OQ3czh3YeQ6M78YuR.#=zNL_j4JfqPvlH.#=zT$7DROkNjCDz()
   в #=zF4z$pSUU6B5OQ3czh3YeQ6M78YuR.#=zyyek3mQ=.#=zf2ut_Ro=(ApplicationCommand #=zuRaafMw=, Object #=z9ov_TIU=, IList`1 #=zFaa2Qsw=)
   в #=zYRewEU3nUrgSFjeBA3QvXZ8=.#=zEEByxHQJv94mjNr4RA==(Object #=z09rm0$E=, EventArgs #=zw9__rOQ=)
   в System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
   в System.Windows.Forms.ToolStripButton.OnClick(EventArgs e)
   в System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   в System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   в System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
   в System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
   в System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   в System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   в System.Windows.Forms.Control.WndProc(Message& m)
   в System.Windows.Forms.ScrollableControl.WndProc(Message& m)
   в System.Windows.Forms.ToolStrip.WndProc(Message& m)
   в #=zWgwAw2cKnmmEDmAE0ikc63Fbg54y.WndProc(Message& #=zDFHX0Xk=)
   в System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   в System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   в System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

the same error is thrown, when you start with tag editor in main panel, and switch to floating one.


P.S. switching from floating tag editor to docked in main panel, and vice versa, doesn't preserve changed, but unsaved tags.

1. i get error message "unable to start plugin: <dll name>.dll - Dll entry point: MusicBeepPlugin.Plugin was not found", when i try to add plugin .zip (by clicking 'add plugin' button), which contains auxiliary dlls (without "mb_" prefix) in the root of zip and "mb_*.resources.dll" (it doesn't contain any code, only resources) in "ru" subfolder of zip. mb copies main plugin dll "*.dll" instead of "*.resources.dll" to "Plugins\ru" folder.

2. as far as i understand, "add plugin" button had been added for mb store version mainly, because it's the only way to install plugin in this version. similar functionality had been added to mb for installing other mb add-ons (eg. skins). but unlike other types of add-ons there is no way to delete installed plugin in mb store version. it would be great if "uninstall" button next to plugin in prefs> plugins deleted plugin files also, along with calling plugin's Uninstall() function and unloading plugin. of course, only if plugin had been added by using "add plugin" button, not manually.

3. there is no obvious way to update installed plugin in mb store version. i get error "failed to save plugin due to the following error: forbidden data found on decoding" if i try to re-add updated plugin .zip. the only workaround is to disable plugin, then restart mb, then re-add updated plugin.

these issues concern mainly mb store version, but it would be great if they are fixed for all mb versions.

p.s. english wording of error messages may differ from what i've written, but common sense is the same.

Bug Reports / no scrollbar buttons in multiple artist splitter
« on: August 04, 2022, 01:36:47 PM »
there are no scrollbar buttons in multiple artist splitter (also, multiple composer splitter, genre splitter, etc.) using any xmlc skin:

the same window for xml skins:

Bug Reports / arithmetic functions bug ($Add, $Sub, etc.)
« on: July 26, 2022, 11:39:40 AM »
US notation for fractional numbers uses dot as decimal point, Russian (and i suspect most European) notation uses comma as decimal point. it's not the problem, when arithmetic functions use tag values, but it may become the problem, when arithmetic functions use explicit literal fractional number as one of operands. if user wants to add 2.5 to <Play Count> (it's just a senseless example to show what i mean), then mb parses corretly:

$Add(<Play Count>, 2,5)

but can't parse correctly:

$Add(2,5,<Play Count>)


$Add(2.5,<Play Count>)

i'm using the following workaround in ATT plugin for mathematical functions:

string CustomFunc_SomeFunction(string number)
            char localizedDecimalPoint = (0.5).ToString()[1];
            number = number.Replace('.', localizedDecimalPoint);
            float float_number = float.Parse(number);

so user must always use US notation for explicit literal fractional numbers, and both US or Russian (and European?) notations can be used in tags:

$Add(2.5,<Play Count>)

also, i remember that there is the entry for decimal point in localization file.
it's entry for list separator, not for decimal point

Pages: 12 3 ... 7