Minor problem with flac2mp3.pl

[strindberg]

I have been using the excellent flac2mp3.pl with good results. However, there is a small anomaly that I thought I'd better report.

The problem is that for some albums, flac2mp3 reports that it is updating the tags, although these albums have not been touched since the last run. The script will report that it is updating the tags, and then it runs through the files in the album really quick, it seems to me it isn't really updating anyting (which it shouldn't, since nothing is changed).

It is always the same albums which trigger this behavior, and it triggers every time I run the script. No real harm is done, of course, but I thought I should still report it, since the functionality of the script depends on it correctly identifying which files need to be updated, right?

This is v0.3.0rc1 on Windows.

[JJZolx]

I have been using the excellent flac2mp3.pl with good results. However, there is a small anomaly that I thought I'd better report.

The problem is that for some albums, flac2mp3 reports that it is updating the tags, although these albums have not been touched since the last run. The script will report that it is updating the tags, and then it runs through the files in the album really quick, it seems to me it isn't really updating anyting (which it shouldn't, since nothing is changed).

It is always the same albums which trigger this behavior, and it triggers every time I run the script. No real harm is done, of course, but I thought I should still report it, since the functionality of the script depends on it correctly identifying which files need to be updated, right?

This is v0.3.0rc1 on Windows.

Where are the flac and the mp3 files stored?

I see something similar when I back up my flac library each night from my Windows server to a network share on an Infrant NAS. I use robocopy to update only files that have changed, based on the last modified timestamp. I have robocopy produce a report and every night the exact same files get copied to the backup, even though they haven't changed. I think the problem lies with the difference between Windows timestamps and those used in the Linux file system on the NAS.

[strindberg]

The directories are on two different (usb-connected) external hard drives, both with ntfs under Windows. I edit all flac files on Windows.

I do run the Slimserver on (Ubuntu) Linux, with the external hard drive with flacs attached to the linux server, but since it is mounted read-only under linux, I don't believe this could be the reason.

[Robin Bowes]

strindberg wrote:
> I have been using the excellent flac2mp3.pl with good results. However,
> there is a small anomaly that I thought I'd better report.
>
> The problem is that for some albums, flac2mp3 reports that it is
> updating the tags, although these albums have not been touched since
> the last run. The script will report that it is updating the tags, and
> then it runs through the files in the album really quick, it seems to
> me it isn't really updating anyting (which it shouldn't, since nothing
> is changed).
>
> It is always the same albums which trigger this behavior, and it
> triggers every time I run the script. No real harm is done, of course,
> but I thought I should still report it, since the functionality of the
> script depends on it correctly identifying which files need to be
> updated, right?
>
> This is v0.3.0rc1 on Windows.

There are still a few outstanding issues with tag comparisons.

Try running it with the "--debug" switch on a single directory that is
always "updated". Send me the output (robin-flac2mp3 <at> robinbowes
<dot> com ).

Thanks,

R.

[strindberg]

OK. Will do.

[Robin Bowes]

strindberg wrote:
> OK. Will do.

Actually, the "--tagdiff" switch might be sufficient. Try this first.

R.

[Robin Bowes]

Robin Bowes wrote:
> strindberg wrote:
>> OK. Will do.
>
> Actually, the "--tagdiff" switch might be sufficient. Try this first.

This is fixed in r109:

http://robinbowes.com/projects/flac2mp3/changeset/109

R.