Help please with tagging problem with rsync

English Network/Internet
1

I am using rsync to upload flac files from master data set on workstation to a music server on NAS. I rip and edit the tags on workstation before I upload. Sometimes I need to revise the tagging which I do on the workstation.

I have found that although the file access flag is changed, the modified time and date is not changed even though the metadata has been changed.

Is there an easy way to flag the file so that it is uploaded again by rsync. As things are now, because the modification time stamp is unaltered, the file with revised tag is not copied to NAS.

Grateful for any help on this.
Budgie2

2

Looks like your tag editor deliberately retains the same mod time. You could try using -c to make rsync also compares the content checksums so that it won’t skip based on mod time alone.

3

And your tag editor may have an option or configuration to tell it not to retain the old timestamp.
Or write a short script that calls your tag editor and then touch and call that instead of the tag editor directly.

Just some hints.

4

Hi and many thanks.

Yes I had thought about the -c option but was concerned about the time it might take.
In fact the speed of the whole process is of concern as both machines have gigabit nics and are connected to the same gigabit switch but the rsync process runs and 1.4Mb/sec. True I have -v set so this will slow things down but I do not understand why it is so slow.

I shall try the -c option. Can’tslow things down much more.
Thanks again,
Budgie2

5

Hi Henk,
Many thanks. Yes touch is what I was hoping for to set the time stamp. What I have to sort out however is how to apply it only to the files I actually edit. I shall also have a careful look at Easytag as well to see if there is an option. If not I shall raise it with Jerome to see if he can include it in future release.
Thanks again,
Budgie2

PS I have just checked Easytag and the option to preserve time was checked. I have now unchecked it and think that will solve the problem. Will report back if not.

6

-c causes more processing at each end since a checksum has to be computed for comparison. It shouldn’t affect communication cost.

7

Hi Ken,
yes I understand and at on end ther are two quad core processors which might be used if rsync has been set up for multi threaded work but but at the other there is one rather feeble embedded processor, hence my concern. Meanwhile the change to tag edits seems to have done the trick.
Many thanks again,
Budgie2