Have a feature request or suggestion? Post your idea here!

Publicação

10 seguidores Seguir
3
Avatar

File name column not updated after renaming

if I physically rename an mp3, the File Name column in the Track list doesn't change.

Any way to refresh it?

C.B.

Comentário oficial

Avatar

If you physically rename the file, that is no longer the same file within rekordbox; attempting to load that file would result in a "File not found" error. You would need to re-import and re-analyse the track, any changes to the beat grid, memory points or hot cues would be lost as rekordbox considers it a new file.

It's my advice that if you are making changes to your files because of metadata renaming (you prefer to have things a certain way based on the tags), you should do those changes prior to importing to rekordbox.

Pulse
Ações de comentário Permalink

Publicação fechada para comentários.

16 comentários

0
Avatar

After renaming hundreds of files?!? Come on, please... there will be always a need to move&rename files to organise the music database on the hard-drive. Especially when I have to play with non Pioneer Rekordbox gears. Have you never tried to play using a USB pen exported with Rekordbox into Laptop using Traktor, Serato or VirtualDJ? I cannot even see the playlists... mp3s lost in tens of sub-folders...

Look, back to my problem, I used the available raw 'relocate' function to re-assign the re-named file. Everything works well, however the file name field doesn't get updated.

Is there any reason to keep old data?

I have an example to send, showing the bug on the track list after using the 'relocate' function.

Let me know where to send it, thanks.

C.B. 0 votos
Ações de comentário Permalink
0
Avatar

Can confirm that this BUG is still present in 5.3.0.
After changing filename on hard drive, I relocate the track and it finds it successfully.
But the "File Name" column is not updated. Shows the old filename.

Suggestion for fix:
1. File Name should be updated after successful relocate is done.
2. File Name should be updated when doing "Reload Tag" command.

FatCash 0 votos
Ações de comentário Permalink
0
Avatar

@FatCash > Thanks, I'll pass that along -- it should be automatic based on the file itself after the relocation, I'm not sure why it doesn't change.

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

I can confirm this is still an issue in 5.8.5.

The column "Filename" does not update with the new filename even after relocating after rename. (BUG)

 

The Column "Location" does update with the new filename after relocating.

 

Luis Rodriguez 0 votos
Ações de comentário Permalink
0
Avatar

I am afraid this is still happening in 6.0.0.

Rekordbox autorelocates files with no issues even when the file name has been changed but the old file name appears in the library.  

Is there any walk around without re-importing?

MadCowOnAcid 0 votos
Ações de comentário Permalink
0
Avatar

Sorry, it appears it's still on the fix list, I'll flag it again.

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

Please please fix this. Not everyone has hindsight

jacksongrgec 0 votos
Ações de comentário Permalink
0
Avatar

I have just run into this problem and it is a big problem, considering that keeping things organised is so important. Please get this fixed. The original post was 6 years ago!

Thanks :) 

Dan Cresswell 0 votos
Ações de comentário Permalink
0
Avatar

It is now working for me. I have not updated my software. So it could be a bug in rekordbox or it was user error?

Dan Cresswell 0 votos
Ações de comentário Permalink
0
Avatar

Not sure, but at least it's working...? ¯\_(ツ)_/¯ 

Pulse 0 votos
Ações de comentário Permalink
0
Avatar

Still not working here, version 6.6.4

sergio bonifacio 0 votos
Ações de comentário Permalink
0
Avatar

Version 6.6.8 still not working. Please fix!

Fernando Moreno 0 votos
Ações de comentário Permalink
0
Avatar

Version 6.6.8 on Windows still has the bug :/

Michal Sadowski 0 votos
Ações de comentário Permalink
0
Avatar

Version 6.7.2 still not working!

Terrible annoying!

Can somebody finally fix this or will users have to wait another 8 years?

Frank B 0 votos
Ações de comentário Permalink