Recognising different bitrate value after replacing MP3

[jsr7096]

Cross DJ 2.3.0

Example: if I had a track called ABC.mp3 that was 128kbps, is in several playlists and has a played history of say >20 times.

If buy a replacement track that is essentially identical but is 320kbps. I replace this on my PC, but I now want Cross DJ to recognise it has a different bitrate and maintain the file's presence in applicable Cross DJ playlists/history.

How do I do this?

[Support@MixVibes]

Should have the exact same name, and re-analyze the file should refresh everything from it.

[jsr7096]

Should have the exact same name, and re-analyze the file should refresh everything from it.

Sorry, but this doesn't work.

I've just done another test. Existing file was a 128kbps MP3 (3.12 MB). I have replaced it with a 320kbps MP3 (7.81 MB).

Exact same filename causing Windows to prompt what I want to do. I allow it to replace it.

I go to the track in Cross DJ, right-click and select "Analyze All".

It completes that, but still shows a sad face for the quality icon, and when I go into the info, it claims the file is 128kbps and 3.1MB

This is a pain because although I know for this particular track I should be playing a better quality, I don't get a visual reassurance from Cross DJ that I am.

I have a lot of MP3s at 128 and 160 kbps that I am currently re-ripping from my original CDs and would really like to easily replace the files but without losing the playlist/playcount history within Cross DJ.

[Support@MixVibes]

My bad, this isn't written at the stage analyze but when parsing the file. So removing the entry and put the file back should work.

[jsr7096]

My bad, this isn't written at the stage analyze but when parsing the file. So removing the entry and put the file back should work.

Thank you for the response. I can wait if it's something that will be fixed in the next version?

Before I do anything I assume you mean "Remove from collection"?

This will keep the tally of how many times played, but it will remove the entry from History and any Playlists that I have the track added to?

[Support@MixVibes]

Before I do anything I assume you mean "Remove from collection"?

Yes, this will clear the entry.

This will keep the tally of how many times played, but it will remove the entry from History and any Playlists that I have the track added to?

No removed file should only be marked as missing into Playlist/History so if you replaced it, nothing should change really.

[jsr7096]

Sorry I don't understand. Please clarify what it is you meant me to do.

1) My aim is to replace the files on my harddrive. Essentially the same song, just a different bitrate.

2) Then I would like Cross DJ to then recognise this new bitrate and file details.

3) Whilst doing this, I don't want it to be lost from History or any Playlists.

Using "Remove from collection" means I do lose it from History and Playlists.

Sorry, I don't see an easy way (especially if I am replacing lots of files at once) but I can be patient if this is a bug that can be fixed with the next version?

[Support@MixVibes]

1) My aim is to replace the files on my harddrive. Essentially the same song, just a different bitrate.

As said it will use the newer version without issue.

2) Then I would like CrossDJ to then recognise this new bitrate and file details.

This is not possible as the file have changed.
A file is defined by name, extension, size and location. If any of these change it is not the same file.

3) Whilst doing this, I don't want it to be lost from History or any Playlists
Using "Remove from collection" means I do lose it from History and Playlists.

So you're right, you cannot remove the file from the collection to put the new ones and also you cannot acces to the relocate feature as long as the file are not missing.

Sorry, I don't see an easy way (especially if I am replacing lots of files at once) but I can be patient if this is a bug that can be fixed with the next version?

This is not a case handled by the application, could be a misfeature but is certainly not a bug.

Can't tell for what version, me might chime in to see what can be enhanced there.