Page 3 of 4

Re: BDJ4 Development status 2023

Posted: Tue May 02, 2023 11:53 am
by bll
BDJ4 4.3.2 has been released.
Various bug fixes.
Export for BDJ4 and Import from BDJ4 are working.

I will be working on the wiki documentation to get it all up to date with the various changes and new features.

Re: BDJ4 Development status 2023

Posted: Tue May 30, 2023 10:06 am
by bll
BDJ4 4.3.2.4 is released.
Some improvements on how BPM/MPM are handled internally, with some minor changes to the bpm counter.
The dance selection algorithm is a new rewrite. I think it works a bit better. It's really difficult to make a perfect dance selector.

I am now starting work on using the ffmpeg libraries to handle audio file tagging. I haven't researched everything yet, it is currently a work in progress, but I think it will work out.

Re: BDJ4 Development status 2023

Posted: Fri Jun 02, 2023 10:05 am
by bll
Working on evaluating the various possibilities for audio file tagging.
Looking for a better and faster replacement for python-mutagen.

taglib - does not seem to support "unsupported" tags at all.
ffmpeg - has a couple of minor bugs that could be a problem, but could be usable in some cases.
tagparser - just found this, and still need to evaluate it.

My other option is to use separate libraries for id3, vorbis, m4a, etc. and call the appropriate one. This would be a lot of work.

Re: BDJ4 Development status 2023

Posted: Mon Jun 05, 2023 12:11 pm
by bll
None of the taglib, ffmpeg, nor tagparser libraries seem to have the functionality I need for audio tags.

I'm going to work with smaller individual libraries. I found a good one for id3 tags. Vorbis comments won't be a problem.
I will be trying to find a library to handle .m4a (mpeg4/aac) tags.

Re: BDJ4 Development status 2023

Posted: Mon Jun 26, 2023 8:44 am
by bll
Still working on the new audio tag interface.

Using a test database with 15937 files (all mp3), and running a complete database rebuild.
The python-mutagen audio tag interface: 130 seconds to finish.
The new audio tag interface: 14 seconds to finish.

I am getting closer to finishing this first phase.

Initially, I will be releasing the new audio tag interface with MP3, Ogg and FLAC support.
Opus support should follow shortly.
MP4 (.m4a, .aac, etc.) support will be more difficult, and will take a while to complete.

The audio tag interface to use is selectable in the configuration.
The python-mutagen interface will not be removed any time soon.

The new interface doesn't just promise more speed.
All audio tags, known, unknown and custom will be preserved.

Re: BDJ4 Development status 2023

Posted: Wed Sep 06, 2023 10:11 am
by bll
I am still working on the new audio tag interface, it is much closer to being complete.
The mutagen audio tag interface will not be removed in the near future, there will still be a choice of which audio tag interface to use.

MP4 (.m4a) audio file tags are working (read and write). This is available with the latest BDJ4 releases.

.wma audio file tags can be read, but not written. I just finished this today.
I think there is one more piece I need to check on.

If anyone wants the ability to write .wma audio file tags, please let me know.
As this is no longer a popular audio file format, I am planning on leaving .wma audio file tags as read-only.

I will be working on reading .wav audio file tags. Again, these will be read-only.

Re: BDJ4 Development status 2023

Posted: Tue Sep 12, 2023 12:25 pm
by bll
I am starting work on "Audio Identification" which will use one or more of the audio identification services to identify the music. I plan on having support for 'AcoustID', 'ACRCloud', and 'AudioTag' (if you know of others, please let me know). 'AcoustID' will work out of the box. Any other services will require the the user to sign up for an account.

At this time, I am trying to figure out how the user interface will look. There's quite a bit of information to display. I'm a little worried that if I try to fit it all into one screen, that it will be too much. But the alternative, having two separate tabs for the Audio Identification Listing and one for the Audio Identification Retrieval Display seems like it wil be too hard to use. I think there is still enough vertical space, so I may be worrying too much.

Re: BDJ4 Development status 2023

Posted: Sun Oct 01, 2023 6:25 am
by bll
Adding the Russian translation to BDJ4 necessitated some changes to the user interface, as it turns out Russian has some very long words and phrases. This made the management window very wide. I split the playlist management screen into two separate tabs. Working on Russian also uncovered some localization bugs due to the long text, and these bugs were easy to fix.

The "play" button that plays a selected song from the song listings has been changed to an image. I had not wanted to do this, as it will be confused with the play button in the player. The "filters" button has also been changed to an image.

The management window when using the Russian language is still 1631 pixels wide. That is on Linux with the default font size. English is 1210 pixels wide. I will be looking into further changes to see if the width can be reduced.

I will be working on documentation to get it up to date with the latest changes.
After that, I will get back to implementing the ACRCloud interface for audio identification.

Re: BDJ4 Development status 2023

Posted: Mon Nov 13, 2023 10:12 am
by bll
2023-11-13

In the next release, the marquee countdown timer will be fixed.
Also some of the folder/file selection buttons in the configuration were broken.

Currently working on making the Windows version work with international characters in the account name.
I should have done this long ago.

Also fixing any other Windows bugs I run across.

Re: BDJ4 Development status 2023

Posted: Fri Nov 17, 2023 7:56 am
by bll
bll wrote: Mon Nov 13, 2023 10:12 am Currently working on making the Windows version work with international characters in the account name.
I should have done this long ago.
Good news, I figured out how to get past the problem blocking progress, and should be able to get windows international account names working within a week or two.