RTS delayed start

Posts: 2 · twisted1 11 Sep 2014, 04:24

Cleaning up my music info with Mp3tag, I have an RTS with a 15 min. delay set up to automatically mirror those changes to my NAS.

Is it possible to add something extra into the RTS batch file so that it will actually delay starting until Mp3tag closes, or is this an item for 'Feature Requests'?

Posts: 7281 · Zenju 13 Sep 2014, 09:32

First, RTS doesn't have a delay, but an *idle time*. This means setting it to 15 min is risky, since it will trigger FFS only after a full time period of 15 minutes *without* detecting any changes on the monitored directories.

That said, is there a problem with Mp3tag that is not handled by the RTS idle time?

Posts: 2 · twisted1 14 Sep 2014, 00:36

First, RTS doesn't have a delay, but an *idle time*. This means setting it to 15 min is risky, since it will trigger FFS only after a full time period of 15 minutes *without* detecting any changes on the monitored directories.

That said, is there a problem with Mp3tag that is not handled by the RTS idle time?Zenju

15 minutes *idle time* is good in this context, as it takes about 10-12 min. to fully tag an album. This allows me to have moved onto the next album before sync occurs. I'm doing it this way as I have found, on extremely rare occasions, if the timing is just right when I save in Mp3tag and a sync occurs, FFS reports that it has copied these last second changes to the NAS but it in fact, it hasn't.

Ideally, for me, would be having a 30 second idle time, but RTS would wait until I finished all the edits and closed Mp3tag. Guess it's back to manual synchronizing for this one.

Posts: 7281 · Zenju 16 Sep 2014, 21:58

> 15 minutes idle time

It's fine as long as you don't have some applications writing every few minutes to the monitored folder with the effect that RTS never triggers.

> FFS reports that it has copied these last second changes to the NAS but it in fact, it hasn't.

Can you describe in more detail what goes wrong?