Messages

1

Questions / Re: Sorting by original year if existing, if not use release year

« on: February 06, 2025, 01:01:02 PM »

Super helpful thanks! I modified the code slightly as for me I have mix of dd/mm/yyyy and just yyyy entries so did:

 $IsNull(<Original Year>,<Year (yyyy)>,<Original Year>)

That sorted everything for me to sort just by year ignoring days and month entries which messed up my ordering without.

2

Questions / Re: MusicBee app closes when album finishes using WASAPI Exclusive mode

« on: April 18, 2023, 01:40:39 AM »

Thanks for the replies, to answer the above...

I've got a few plugins installed, I've tried disabling them, restarting and the issue persisted, it didn't seem to matter which ones were enabled or disabled to replicate the problem.

Also tried choosing different outputs, like SPDIF and Headphones but it still just occurs in WASAPI exclusive mode. Just checked WASAPI Shared mode and that works fine.

I can't see version 3.5.8501 publicly linked on forum, is it a beta/developer version?

Upon further testing I've downloaded a clean portable version alongside my portable version and cannot replicate the issue even after duplicating the settings so am having a look into it when I get some more free time and will report back if I find anything out...

3

Questions / MusicBee app closes when album finishes using WASAPI Exclusive mode

« on: April 14, 2023, 03:49:57 PM »

Been using the app for years but never noticed this behaviour before... On my machine playing an album or playlist or queued songs using WASAPI mode everything plays but when the last song of the list has finished MusicBee closes. Nothing is reported in the error log and this behaviour does not happen if I play in DirectSound mode. It took me a long while to go through the settings but it is certainly WASAPI causing this issue on my machine. Any ideas or can the issue be replicated, am not sure if this is a bug or some setting I am missing? Am using a portable install with the current latest version from patch update in forum v3.5.8447 on Ryzen 5900x system, Windows 11.

4

Questions / Re: Forward button behaviour when editing track number

« on: November 17, 2022, 09:41:23 PM »

Ah after all this time, I've never explored that tools menu! What you say makes sense, I'll attempt it next time I have the need.

5

Questions / Forward button behaviour when editing track number

« on: November 08, 2022, 04:46:17 PM »

Firstly I'm not sure if this is a bug, but I am trying to understand the behaviour of the forward and back buttons while editing/changing track information manually. I am adding some cassette audio and importing to MusicBee where they are just labelled by the track name and load as an album with the track titles sorted alphabetically and no metadata. Let's say my 4 tracks are labelled Track A, Track B, Track C, Track D, I edit Track A and type the number '1' in the track number box and then press the right arrow to save and move on to edit the next track. Now several things happen at this moment visually. In the library view my Track A resorts itself to the bottom of the album with the track number 1. Track B is now at the top, but Track C is currently highlighted. In the edit view Track B is loaded as expected so I enter '2' into track number and press the right arrow key again. This time in the library I see Track B moves below Track A with its correct track number 2 but now Track A is highlighted again. In the Edit screen it has loaded in Track D and not Track C as logically expected. I've tried to visually explain this in the image below of the 3 screen captures.



My usage case is that for albums without track metadata like this, I like to enter the track number, press right key, enter next sequential track number, rinse and repeat. I believe this behaviour has been the same across versions for as long as I can remember and assumed it was a limitation, but I just got around to addressing this bugbear in case there is a fix. It's by no means a dealbreaker as I find this software outstanding in comparison to others out there. If anyone has any input on this behaviour it would be greatly appreciated.

6

Visualizers / Re: Milkdrop Visualiser Support

« on: January 14, 2020, 01:55:15 AM »

This is how I got it working from scratch.


I have a portable SSD to where I installed my Music Bee Portable Version.

On My main Windows 10 PC I ran into all the problems getting Milkdrop to work but eventually with a lot of copying and pasting and back and forth it all now works. What is curious is that when I plugged my external SSD into a different Windows10 Laptop, milkdrop ran first time. This leads me to believe only the 3 files are needed to be copied to the Plugins directory. I also copied the script posted on the previous page into milkdrop2.ini file but not tried without it.

I ran the Directx web installer and copied over the 3 files (D3DX9_31.dll, D3XD9_43.dll & D3DCompiler_47.dll from my syswow64 folder to my MusicBee/Plugins folder. I believe these versions are correct and resolved milkdrop not starting as I had previously downloaded those files from random sites. I suggest checking those .dlls are exactly the right version and you should be able to start MilkDrop without the Directx Message or the Graphics Driver message. (I've had both errors on my journey to get it working!) Finally if it throws up a message about any missing files from /data then check your Data folder is in MusicBee/Plugins/Milkdrop2/Data. Hope this post helps someone somewhere. I set up an account just to share this info!