Thread: Copy & md5 Shell Script

Reply to Thread
Page 14 of 14 FirstFirst ... 41011121314
Results 131 to 140 of 140
  1. #131  
    Elliott,

    Thanks for the feedback about the new setcopy app.

    Did you compare with RSYNC like CODEX recomends? I have not tested that.

    I have noticed Finder is faster in single copy. We looked a little to find out what Apple was doing to make Finder faster, but our focus was on multiple destinations and checksums. Copy the same data to two or three destinations in Finder and with Setcopy or DoubleData. Finder is much slower then.

    That is interesting to hear DoubleData is same speed as Finder. So they figured it out. I guess we should look deeper and find that extra little bit of speed.

    I have attached a screenshot of an early GUI of Setcopy. Things are still changing, but it will be pretty close to this. I hope to have a testing version of the GUI ready for NAB.

    Thanks for all your feedback testing Elliot.



    Dusty
    Attached Images
    Reply With Quote  
     

  2. #132  
    For anyone interested in testing Setcopy and providing feedback, here are the features we currently have:

    Options:
    --help Print usage and exit
    --version Print the version and exit
    -v [ --verbose ] Execute with verbose output
    -f [ --force ] Force setcopy to overwrite the destination
    -d [ --delta ] arg (full|fast) Do a delta copy on a source directory to multiple targets
    -r [ --rename ] arg Tell setcopy to rename the target folder
    -s [ --source ] arg The source directory to copy from (requires quotes around source directory)
    -t [ --target ] arg The target directory to copy to (requires quotes around target directory)
    -i [ --target1 ] arg The intermediate target directory to copy to first (requires quotes around target directory)
    -h [ --hash ] arg (none|crc32+|md5|md5+) The hash function used to verify the copy (default: md5)
    -l [ --log ] arg Generate log files in parent target directories or to specified directory (requires quotes around log file directory and filename)
    -u [ --user ] arg The name of the user (requires quotes around user name)
    -o [ --owner ] arg The name of the production company (requires quotes around production company)
    -p [ --project ] arg The Name or Project (requires quotes around the project name)


    Some examples:

    setcopy -v -h md5+ -s "/path/to/source/" -t "/path/to/destination1" -t "/path/to/destination2"

    This will copy the /path/to/source/ folder and all files within to both /path/to/destination1 and /path/to/destination2.
    This will perform an md5 checksum on the source and on the destination files
    This will also print verbose information to the screen
    This will write a log file and a source and destination checksum file to each destination


    setcopy -v -h none -s "/path/to/source/" -t "/path/to/destination1" -u "Dusty" -o "Sandust" -p "setcopy"

    This will copy the /path/to/source/ folder and all files within to /path/to/destination1
    This will perform no checksums
    This will print verbose information to the screen
    This will write a log file to the destination
    In the log file it will list Dusty as Data Manager, Sandust as the Production Company,and setcopy as the Project


    setcopy -v -h md5+ -s "/path/to/source/NO NAME/" -t "/path/to/destination1" -r "Canon5d_001"

    This will copy the /path/to/source/NO NAME/ folder and all files within to /path/to/destination1
    This will perform an md5 checksum on the source and on the destination files
    This will print verbose information to the screen
    This will write a log file to the destination
    This will rename NO NMAE to Canon5d_001 on all destinations


    setcopy -v -h md5+ -s "/path/to/source/" -i "/path/to/destination1" -t "/path/to/destination2"

    This will copy the /path/to/source/ folder and all files within to /path/to/destination1
    Then setcopy will copy from /path/to/destination1 to /path/to/destination2
    It will perform an md5 checksum on the source and on both destination files
    It will also print verbose information to the screen
    It will write a log file and a source and destination checksum file to each destination
    This can be useful if you have a fast raid for destination 1 and slower drive for destination 2


    setcopy -v -h MD5+ -s "/path/to/source/" -t "/path/to/destination1" -d fast

    Will look at the source and destination checksum files on "path/to/destination1"
    This will only copy files with different checksum in destination checksum file than source checksum file
    It will perform an md5 checksum on the source and on both destination files copied
    This will print verbose information to the screen
    This will append the existing log file in the destination
    This will append the checksum files in the destination


    If you are interested in testing please send me your email address and I will add you to my beta testers distro.



    Mahalo,
    Dusty
    Reply With Quote  
     

  3. #133  
    Senior Member
    Join Date
    Mar 2011
    Location
    Southern California
    Posts
    387
    I didn't know Codex recommends rsync. I will give that a try tomorrow.
    Reply With Quote  
     

  4. #134  
    Dustin, hit me up. I'd love to test on the Mac....Ed
    Edward Hannigan
    DIT
    Chino Hills, CA
    Reply With Quote  
     

  5. #135  
    Senior Member
    Join Date
    Mar 2011
    Location
    Southern California
    Posts
    387
    Quote Originally Posted by Dustin Cross View Post
    Did you compare with RSYNC like CODEX recomends? I have not tested that.
    I can't get rsync to move faster than 150MBps, so that's the worst of the bunch.

    Dusty, regarding the GUI, I'd like to request an easy way to enter a shoot day number, to be used in paths. And abundant keyboard shortcuts.
    Reply With Quote  
     

  6. #136  
    Senior Member
    Join Date
    Mar 2011
    Location
    Southern California
    Posts
    387
    How's the GUI coming along? I wanted to request two more features, not sure if you've already covered this:
    Auto-start when a mag is inserted
    Remember destinations based on media type (so SxS has a set of destinations, while Codex packs have a different set, and Sound has a different set, etc.)
    Reply With Quote  
     

  7. #137  
    Junior Member
    Join Date
    Jul 2009
    Location
    Dallas/Ft. Worth TX
    Posts
    1
    I'd like to get in on the Beta testing if you're still looking for people.
    Reply With Quote  
     

  8. #138  
    Quote Originally Posted by Elliott Balsley View Post
    How's the GUI coming along? I wanted to request two more features, not sure if you've already covered this:
    Auto-start when a mag is inserted
    Remember destinations based on media type (so SxS has a set of destinations, while Codex packs have a different set, and Sound has a different set, etc.)
    Elliot,

    GUI is coming along well. Taking a lot more time than we expected though. We had an issue downloading multiple source mags at once. One mag at a time is blazing fast, but two mags and things slow to a crawl. It seems we have that fixed. It just took an complete rewrite!

    I do not like automatic things! In my opinion it creates laziness and that causes errors. So I have no plans of ever having Setcopy automatically copy files with zero interaction. Telling it to copy this mag to these locations with this checksum type is not much work. Plus it would be very hard to have the software predict what automatic means to everyone. I hate when Apple automates some feature I used to use and now it does not work how I did it any more.

    The GUI has multiple tabs so you can set up presets for different destinations and just jump between the tabs. If you are wanting something more automatic, see above.

    I hope to have a GUI ready for testing soon, but with this complete rewrite of everything, I am not sure how much longer.

    Here is a screencap of the GUI.


    Thanks
    Dusty
    Attached Images
    Reply With Quote  
     

  9. #139  
    Quote Originally Posted by Dan Jackson View Post
    I'd like to get in on the Beta testing if you're still looking for people.
    Dan,

    I will get you a copy for testing asap! You should have just emailed me.


    Dusty
    Reply With Quote  
     

  10. #140  
    Senior Member
    Join Date
    Mar 2011
    Location
    Southern California
    Posts
    387
    Ah I see what you mean about the tabs, that's good enough.
    I like how DoubleData starts automatically, but I realize it would be harder to set identifying criteria when you support more than 2 cameras.

    By the way, I noticed when copying image sequences (ARI from a Codex mag), CopyVerified is extremely slow at verifying checksums (like 300% slower). setcopy does not have this problem. Keep up the good work!
    Reply With Quote  
     

Posting Permissions
  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts