Messages

1

Bug Reports / Re: Flickering display since the last updates

« on: Today at 12:45:31 PM »

i cant reproduce any issues but will have another look later in the week
you could try removing mb_Spectrogram-Display.dll or at least renaming it to .dll2 so it doesnt load at all

2

Bug Reports / Re: Flickering display since the last updates

« on: Today at 11:54:55 AM »

could you send a link to your settings file (help/support/view settings)
and if you use a custom layout or view, a zip of the AppData\Saved Settings folder

3

MusicBee Wishlist / Re: vgmstream support

« on: Today at 07:40:17 AM »

https://github.com/X-Hax/sadx-mod-loader/tree/master/extlib/bass

it doesnt work either - the bass_vgmstream.dll just doesnt load as a bass plugin
Your best bet may be to try to get the winamp plugin to work

actually i am almost certain its not written as a bass plugin - just something that uses bass itself

4

MusicBee Wishlist / Re: vgmstream support

« on: Today at 06:04:20 AM »

https://github.com/X-Hax/sadx-mod-loader/tree/master/extlib/bass

it doesnt work either - the bass_vgmstream.dll just doesnt load as a bass plugin
Your best bet may be to try to get the winamp plugin to work

5

MusicBee Wishlist / Re: vgmstream support

« on: Today at 04:43:34 AM »

bass_vgmstream wont work but if someone sends me a vgm file i can have a look

i cant get bass_vgmstream.dll to load, even with the addition of the 3 dependency files. There must be other dependencies

6

Bug Reports / Re: Flickering display since the last updates

« on: Today at 02:30:18 AM »

can you try temporarily disabling the plugins you use, including any dsp plugins

7

Bug Reports / Re: Flickering display since the last updates

« on: May 18, 2024, 11:57:24 PM »

this is the build from 12-may, so could you try that to confirm its something in MB that has changed
https://getmusicbee.com/patches/MusicBee36_Patched12May.zip

8

Portable Devices / Re: Copy Failed-Year, Month, Day parameters describe an un-representable DateTime

« on: May 18, 2024, 10:13:23 PM »

If any file in the library has an "original year" set to "0000" then any playlists using "original year" fail.

thats fixed now:
https://getmusicbee.com/patches/MusicBee35_Patched.zip
unzip and replace the existing musicbee application files

9

MusicBee Wishlist / Re: vgmstream support

« on: May 18, 2024, 09:24:45 PM »

bass_vgmstream wont work but if someone sends me a vgm file i can have a look

10

MusicBee Wishlist / Re: Bandcamp as an alternative to iTunes in Music Explorer

« on: May 18, 2024, 09:23:45 PM »

does bandcamp have an api that lets you search artist/albums/tracks?

11

Bug Reports / Re: musicbee doesn't find "The Beatles" in my network folder

« on: May 18, 2024, 05:04:34 AM »

This is a very strange problem. I did notice in your screenshot that the "The Beatles" folder in windows explorer is set to a future date "15.06.2024" so perhaps somehow it is corrupted in some way that MB cant read it

12

Questions / Re: No edit popup, can't edit metadata

« on: May 17, 2024, 05:27:53 AM »

if you have multiple screens run at different dpi resolutions, and change the resolution of the screen the tag editor was open, it can cause the tag editor to go off screen. If thats the case try setting the dpi scale back to how it was before
otherwise delete "DialogStateSettings.dat" in the musicbee application data folder

13

Bug Reports / Re: Flickering display since the last updates

« on: May 16, 2024, 10:50:26 AM »

i cant reproduce any issues and i cant think of anything thats changed as compared to v3.5 that might cause such issues. So i guess it will remain unsolved for now

14

Bug Reports / Re: Stange Error Log Entries

« on: May 16, 2024, 10:32:22 AM »

its related to the replaygain analyser. Do you have it replaygain analysis enabled in Tags(2)/ in the tags section?
If you just run it manually, do you sometimes cancel the analysis mid-way through?

in any case the usual downloads link is updated with a change to address the issue

15

Bug Reports / Re: Some kind of multi-instance cross-contamination

« on: May 15, 2024, 10:47:43 AM »

if the C: instance is monitoring a specific C: folder then I dont see how tagging files on the E: drive would trigger the folder monitor unless Picard is configured the write temporary versions of the tagged file to that folder (which seems very unlikely)
You dont ever run the E: instance and switch to the C: library (using File/ Open Library) ?