Tweet
I'm planning on running multiple machines to handle a really large collection- essentially I want to set up a few hundred disks and walk away from it. So that I can keep them in order (to make it easier to find the cases afterwards!) I asked earlier about naming convention for creating a folder (or inserting into the files) what drive it came from ([SETLEN]1,,,[origpath][], which is brilliant, btw. Thanks Spoon!). So, now I'm thinking that since I'm getting several errors per 100 using 5 drives with my current setup, I'll be REALLY bummed when I have to scrutinize the logs to figure out which disc had the error so I can try it again in another drive.
The best thing I could come up with so far is:
Change the log so that the notes header or footer includes [discunique] to make it easy to find the folder number
Set naming to include[SETLEN]1,,,[origpath][] as the primary subfolder (so I can tell what drive the data is coming from, keep them in order, and know which drive had the error even if Batchrip crashes or some other nonsense happens)/[discunique] as the secondary subfolder (to keep them in order for that drive, and make it easy to find the disc with the error after adding my own)
Then, check the log
Control F in the log and look for the error, which should have info about what disc number it was
Then use a batch renamer (ReNamer, excellent tool) to add my own project disc number (00001, 00002, and so on) for the that drive (easy, since they'll be in order by [discunique])
Figure out what [discunique] corresponds with that disk number (batch *879 which had the error would then have the disk number in the folder name, from above)
Go to the location of that disk error, delete the original data
Dig through the 100 stack that finished from that batch, find the error disc (now that I know the disc number based on the corresponding [discunique]), and try it again
There's got to be an easier way...
Any thoughts?
The best thing I could come up with so far is:
Change the log so that the notes header or footer includes [discunique] to make it easy to find the folder number
Set naming to include[SETLEN]1,,,[origpath][] as the primary subfolder (so I can tell what drive the data is coming from, keep them in order, and know which drive had the error even if Batchrip crashes or some other nonsense happens)/[discunique] as the secondary subfolder (to keep them in order for that drive, and make it easy to find the disc with the error after adding my own)
Then, check the log
Control F in the log and look for the error, which should have info about what disc number it was
Then use a batch renamer (ReNamer, excellent tool) to add my own project disc number (00001, 00002, and so on) for the that drive (easy, since they'll be in order by [discunique])
Figure out what [discunique] corresponds with that disk number (batch *879 which had the error would then have the disk number in the folder name, from above)
Go to the location of that disk error, delete the original data
Dig through the 100 stack that finished from that batch, find the error disc (now that I know the disc number based on the corresponding [discunique]), and try it again
There's got to be an easier way...
Any thoughts?
Comment