Jump to content

Problem with file renamed but still appears with both new and old name in new Album feature


Recommended Posts

Flux02400
Posted

Hi,

I've rename audiobook files but even after many database scan, vacuum etc... The old file still appears in my Album field (not in the folder field)

Thanks for help

 

Flux

ALBUM.png

FOLDER.png

Posted

Hi, try running a library scan of all libraries and see if that helps. Thanks.

Flux02400
Posted

I do it it's the same

Posted

What exactly did you do?

Flux02400
Posted

Launch scan with the scheduled task, launch scan with right click on the library and put vacuumdatabase on true before restart.

I've also delete the library lanch the schedules task and next recreate the library and relaunch the task, these old file are still here.

Carlo
Posted

Hi, If you bring up the detail page or meta data editor for one of these songs you should be able to see the location stored on disc.
I would do that to find the culprit files and then check the tags in those files.

Flux02400
Posted

I already do that, the path doesn't exist but file still in album section ( no problem in folder section ) 

Carlo
Posted

Any chance we could do a remote session so I could get a better view and understanding of what's going on with this?

Flux02400
Posted

Yes how do you want to proceed ?

Posted

Please see my comments here: 

 

Flux02400
Posted

I've delete the concerned library (audiobook) already and rename the folder and after that recreate the library, still appear...

But, if i understand you well i've to remove all music libraries and do a full rescan or just wait for a patch ?

 

In that case, i'll wait for patch because my late full rebuild after 4.6.0.50 was a mess with audio file and i had to restore from a backup :)

 

Thanks for your support :)

 

FluX

 

Deathsquirrel
Posted

I had the same problem with three songs.  All I needed to do to clear them was rename the file, scan my library, and then delete the record for the remaining entries.  the file wasn't deleted as the duplicate entry was still pointing at a path that didn't exist.

Posted

Thanks for the feedback. Apologies for the disruption.

Flux02400
Posted

4.6.2 solved this issue, thanks :)

Posted

Thanks for the feedback.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...