I was able to get the Windows Media Player player interface working, except for selecting an alternate audio output device.  Not sure what's going wrong with that part of the code.  This has been released with version 4.16.0.
One of these days, I will get back to it and see if I can figure out why the audio output cannot be selected.
In conjunction, cross-fading has been implemented, only for the Windows Media Player interface.
			
			
									
						
										
						Development Status 2025
Re: Development Status 2025
Version 4.17.0 has an important fix for Windows.  MP3 tags were not being processed for audio files with international characters (the simple accented characters were probably ok).   Unfortunately this bug may have been around since 2024-11.  
A bad copy of the configuration file for the libid3tag support library was present when it should not have been there. I only happened to run into this bug when I was doing installation testing, as the bug did not present itself while working in the usual development folder.
In better news, the Windows Media Player player interface now works when a specific audio output device is selected. The Windows Media Player player interface is now the default for new installations, and VLC will not be installed.
Windows users that currently use the VLC player interface may continue using VLC, or may switch to the Windows Media Player interface if desired (and VLC may be uninstalled).
The Windows Media Player is relatively new, it has not had as much real world testing as the VLC interface. The Windows Media Player does have support for cross fading if that functionality is desired.
			
			
									
						
										
						A bad copy of the configuration file for the libid3tag support library was present when it should not have been there. I only happened to run into this bug when I was doing installation testing, as the bug did not present itself while working in the usual development folder.
In better news, the Windows Media Player player interface now works when a specific audio output device is selected. The Windows Media Player player interface is now the default for new installations, and VLC will not be installed.
Windows users that currently use the VLC player interface may continue using VLC, or may switch to the Windows Media Player interface if desired (and VLC may be uninstalled).
The Windows Media Player is relatively new, it has not had as much real world testing as the VLC interface. The Windows Media Player does have support for cross fading if that functionality is desired.
Re: Development Status 2025
Version 4.17.2 fixes a problem with the new cross-fade function.  When cross-fade was enabled for a music queue and the last song in the queue was played, the player was trying to do a cross-fade, causing BDJ4 to hang.
For Linux, the GStreamer player interface now supports cross-fading. I am going to see if I can get GStreamer working on MacOS, which would make cross-fading available for MacOS users.
			
			
									
						
										
						For Linux, the GStreamer player interface now supports cross-fading. I am going to see if I can get GStreamer working on MacOS, which would make cross-fading available for MacOS users.
Re: Development Status 2025
Version 4.17.3 fixed the mobile remote control, which got broken a while back.  I also found a bug that prevented WMA audio files from being processed on Windows.   I had located a function that turns out to be in only one library on Windows, and two libraries on Linux/MacOS, and the library that didn't work on Windows was being used.
Version 4.17.3.1 has fixes for Linux only. I noticed that a Linux KDE user installed BDJ4, so I put in the work to make sure "presentation mode" got turned on for KDE. This also involved some minor re-arrangement of the code.
I am currently running the automated tests on 7 different operating systems using 3 physical computers and 4 virtual machines. I can only run 2 virtual machines at one time.
I started running the automated tests at 5:30. The automated tests finished at 8:50. Packaging and releasing the software takes another 30 minutes.
			
			
									
						
										
						Version 4.17.3.1 has fixes for Linux only. I noticed that a Linux KDE user installed BDJ4, so I put in the work to make sure "presentation mode" got turned on for KDE. This also involved some minor re-arrangement of the code.
I am currently running the automated tests on 7 different operating systems using 3 physical computers and 4 virtual machines. I can only run 2 virtual machines at one time.
I started running the automated tests at 5:30. The automated tests finished at 8:50. Packaging and releasing the software takes another 30 minutes.
Re: Development Status 2025
Version 4.17.3.3 is upcoming.   It has a few minor user interface changes in the configuration.  It was pointed out that some of the user interface text spinboxes were difficult to use, as there were many selections to choose from.  The Locale, UI Theme, and Marquee Theme have been changed to use drop-downs instead of text spinboxes.
I also made the configuration topic selections scrollable. This is useful for smaller screens, when the configuration window is reduced in size, and useful in the future when adding new configuration topics.
In the process, I ran into a GTK bug, and had to figure out a way to work around that. Very annoying.
It was also pointed out that the forum registration was not working. I had to configure ballroomdj.org's DKIM, DMARCS, get a google API key (I think I delete all my API keys without thinking), and re-configure the forum.
			
			
									
						
										
						I also made the configuration topic selections scrollable. This is useful for smaller screens, when the configuration window is reduced in size, and useful in the future when adding new configuration topics.
In the process, I ran into a GTK bug, and had to figure out a way to work around that. Very annoying.
It was also pointed out that the forum registration was not working. I had to configure ballroomdj.org's DKIM, DMARCS, get a google API key (I think I delete all my API keys without thinking), and re-configure the forum.