A few regressions in MM 2024

[Vlad1]

I just upgraded from MM 4 to MM 2024. There are few things I noticed:

1) I have a collection of old mp3 files. When I try to update their tags in MM 2024 , I get an error "Tag update failed. File <filename> has wrong format". This is not a single bad file, all files from one particular collection produce this error. MM 4 was able to update tags in these files just fine. Also, both MM 4 and MM 2024 can parse tags in these files when scanning them.

2) Some dialogs in MM 2024 (for example confirmation dialog for file deletion) exhibits very strange behavior. Their right boundary is slowly moving to the left, making dialog window smaller, until (after about 10 second) reaching their final state.

3) This is a minor nitpicking, but I will still mention it. When I right click a folder and choose Add/Rescan to the library, MM shows directory tree, asking to choose the folder(s) to scan. As I right clicked a particular folder, it should be obvious that I want to scan this folder. In MM 4 the current folder was pre-selected. In MM 2024 it is not, so requires additional mouse click to select it before starting the scan.

Thanks!

[Lowlander]

1. Did the tags on the files actually get changed in MMW4, or is it a case of no error shown in MMW3, but nothing being tagged?
Can the files be played, if so, could they be read-only, have overly long file Paths (more than 240 characters) or contain characters not supported by Windows or the OS the files reside on (in case of NAS)?

2. Please retry with the latest MediaMonkey 2024.2 release.

3. In 2024.2 it will be listed, but not pre-selected. In other scenarios user kept having to de-select needlessly.

[Vlad1]

Did the tags on the files actually get changed in MMW4, or is it a case of no error shown in MMW3, but nothing being tagged? Can the files be played, if so, could they be read-only, have overly long file Paths (more than 240 characters) or contain characters not supported by Windows or the OS the files reside on (in case of NAS)?

Yes, MM4 actually changes the tags. The files are not read only. They are playing fine. They do not have long paths, and nothing unusual in file names (just latin letters and numbers).

[Vlad1]

2. Please retry with the latest MediaMonkey 2024.2 release.

Yes, the same behavior in MediaMonkey_2024.2.0.3178.

[Peke]

Did the tags on the files actually get changed in MMW4, or is it a case of no error shown in MMW3, but nothing being tagged? Can the files be played, if so, could they be read-only, have overly long file Paths (more than 240 characters) or contain characters not supported by Windows or the OS the files reside on (in case of NAS)?

Yes, MM4 actually changes the tags. The files are not read only. They are playing fine. They do not have long paths, and nothing unusual in file names (just latin letters and numbers).

Can you please open support ticket and supply us one of files? Are files play normally in MM?

[Vlad1]

They play fine, and MM can read the tags too, the error occurs only if I try to update them.

What is the best way to send you mp3 file ?

[Lowlander]

1. Attach a smaller file to a Support Ticket or include the link to a Cloud share with the file in the Support Ticket.

2. Please rename persistent.json to persistent.json.old and start MediaMonkey again.

[Lowlander]

1. Files are .WAV files with a .MP3 extension. This is causing the issue. Fixing the file extensions from .MP3 to .WAV should fix the issue.

[Vlad1]

1. Done.
2. Same behavior.

[Vlad1]

Files are .WAV files with a .MP3 extension.

Interesting. I would say that observable file size (compared with play duration) is more indicative of a compressed format than of wav.

But I agree that something may be wrong (or at least unusual) in file format. This is what MediaInfo tells.

General
Complete name : 0033.mp3
Format : Wave
Format settings : WaveFormatEx
File size : 1.61 MiB
Duration : 2 min 0 s
Overall bit rate mode : Constant
Overall bit rate : 112 kb/s
FileExtension_Invalid : act at9 wav

Audio
Format : MPEG Audio
Format version : Version 1
Format profile : Layer 3
Format settings : Joint stereo / MS Stereo
Codec ID : 55
Codec ID/Hint : MP3
Duration : 2 min 0 s
Bit rate mode : Constant
Bit rate : 112 kb/s
Channel(s) : 2 channels
Sampling rate : 44.1 kHz
Compression mode : Lossy
Stream size : 1.61 MiB (100%)

It shows general format as Wave, but then Audio format as mp3. I am not an expert in audio formats. Maybe wave is a container format allowing different encodings ?

[Lowlander]

2. Which Skin? Anything else particular/noteworthy about your setup?

[Vlad1]

Metro M skin.

The only unusual thing about my installation is that after installing MM 2024, I copied the library and ini file from my old MM 4 installation on a different computer. (At first I tried to copy only DB file, but parts of the library somehow disappeared. When I copied both db and ini files, I was able to see the library completely).

In fact more exactly. On my old computer I upgraded to MM 5 first. MM5 library and ini were copied to new computer. Also I wanted to change directory structure of my music, and experimented with the best way of doing it (moving files in win explorer vs in media monkey, etc). So I did several try runs (copying DB, or DB with ini, moving music files, then deleting the results and doing it again). In the end I got the library in the state I wanted. I do not imagine however that this affected in any way MM program itself.

[Lowlander]

Try a separate Portable Install (select during installation) and with just the database and with the default Material Design Skin. Does the issue persist.

[Rob_S]

Regarding point 3 above, I dont understand the current logic either.

If I have right clicked and asked to scan a particular folder, why would I need to select it again?

I thought the issue originally was that when users did this not only was the current folder selected, but all other existing scanned folders were also pre-selected, and so they ended up scanning everything or having to unselect those???

It seems the right-clicked folder only should be pre-selected, and all others pre-UNselected for such a scan. After the specific scan is completed, all the folders should be pre-selected again for future scans.

[Lowlander]

It now always pre-selects the folder of the selected file/folder, not just when initiating right click scan.
This means there often is no intent to scan the location.