Opened 7 years ago

Closed 7 years ago

#11464 closed Bug Report - General (Need more Info)

Music scanner converted colon (:) to underscore (_), and frontend cannot find file

Reported by: Jeffrey.Ratcliffe@… Owned by:
Priority: minor Milestone: unknown
Component: Plugin - MythMusic Version: 0.25-fixes
Severity: medium Keywords:
Cc: Ticket locked: no


The appropriate line in the mythfrontend.log is:

Mar 23 13:41:03 pan mythfrontend[3393]: E CoreContext? metadata.cpp:649 (Filename) Metadata: Asked to get the filename for a track but no file found: ABBA/Gold_ Greatest Hits/05 Lay All Your Love on Me.mp3

The scanner converted "Gold: Greatest Hits" to "Gold_ Greatest Hits", but the directory still has the colon and the frontend can't play its contents.

Change History (7)

comment:1 Changed 7 years ago by Raymond Wagner

This seems like something very strange for MythMusic to have programmed into it, and a cursory scan through the code doesn't turn up anything. The colon (:) is an illegal character on Windows filesystems. Are you accessing the music over a Samba share, that might be doing some kind of name mangling for character set safety?

comment:2 Changed 7 years ago by Jeffrey.Ratcliffe@…

This is all local to a Mythbuntu 12.04 machine. I worked around it by renaming all colons and other possible problem characters, and things are now working flawlessly.

comment:3 Changed 7 years ago by paulh

I can't reproduce this in 0.27-pre. Tried both the file scanner and import music. Both worked as expected.

Import music does convert some bad filename characters when creating the filename but both the filename on disc and the filename in the DB both agree so everything works as it should.

The file scanner accepted the filename with a : without any problems.

How did you add the files using 'Scan for new Music' or 'Import Files'?

comment:4 Changed 7 years ago by Jeffrey.Ratcliffe@…

I'm fairly sure I used 'Scan for new Music'.

comment:5 Changed 7 years ago by paulh

If you used 'Scan for new Music' then all you will see is a popup box with a progress bar telling you what's happening. If you use the 'Import Files' option you will see a screen similar to this one in the wiki

You would use the first option if you manually added the music to your music directory and wanted MythMusic to find any new tracks.

You would use the second option if for example you downloaded some new music into a download directory and wanted MythMusic to copy it to your music directory automatically creating the correct directory structure and adding it to the database as it does it.

comment:6 Changed 7 years ago by paulh

Status: newinfoneeded_new

This is looking like user error of some kind but without more info it's hard to say what the cause is.

'Scan for new Music' if that is indeed what you used doesn't in any way change the file so there is no way it could have changed the file paths or names.

What file system is the directory where your music files are on using? Is it being shared by some method like cifs/samba?

Is it possible you used 'Import Files' in the past pointing it to your music directory by mistake? I'm not sure how that would cause the problem you are seeing but I suspect it may be something like this.

It would be useful if you could try to reproduce the problem with the frontend using -v file,database and post the logs. A dump of the music database tables may also be required if the logs don't show anything useful.

comment:7 Changed 7 years ago by paulh

Resolution: Need more Info
Status: infoneeded_newclosed

Please re-open if you can provide any more information.

Note: See TracTickets for help on using tickets.