Welcome to our community

Be a part of something great, join today!

Register Log in
  • Hey all, just changed over the backend after 15 years I figured time to give it a bit of an update, its probably gonna be a bit weird for most of you and i am sure there is a few bugs to work out but it should kinda work the same as before... hopefully :)

Shotput Pro VS R3D Data Manager

G

Greg Gutierrez

Member
Joined
May 18, 2011
Messages
6
Reaction score
0
Points
0
Location
Arlington, VA
I know there is a thread from 2009 discussing this however, it seems now that Shotput Pro has MD5 Checksum capability. That being said anyone who has used both of the current versions have a preference? I'm leaning towards Shotput since it does more than just R3D files....
 
I've been wondering about Shotput myself. I would like to get it but I would really like to hear anyone's opinion on the program or any other alternatives.
 
I already own the R3D Datamanager and the Alexa Datamanager but was forced to also buy ShotPutPro, because I was hired for a Sony F3 featurefilm. After 3 days of terrible nightmare with SPP and serious delays (3h+ after wrap each day) I contacted SPP and tried to get rid of the bugs. I made some recommandations for a better workflow and Dan gave me a new Beta every few day that got better and better. In the end it even got faster than the Datamanagers.

Long story short:
I'm owning all 3 data managing softwares, but exclusively use SPP for all Alexa, Red, Epic and else shoots. Very happy with the performance !
 
Leif Thomas said:
I already own the R3D Datamanager and the Alexa Datamanager but was forced to also buy ShotPutPro, because I was hired for a Sony F3 featurefilm. After 3 days of terrible nightmare with SPP and serious delays (3h+ after wrap each day) I contacted SPP and tried to get rid of the bugs. I made some recommandations for a better workflow and Dan gave me a new Beta every few day that got better and better. In the end it even got faster than the Datamanagers.

Long story short:
I'm owning all 3 data managing softwares, but exclusively use SPP for all Alexa, Red, Epic and else shoots. Very happy with the performance !
Click to expand...

Glad tro hear this.
WHen did this happen?

I have only bad experiences with SPP...
 
We arent standing still on the speed race. Of course all systems will be limited by the speed of their devices, but for those with decent speed (i.e. NOT firewire) and decent systems, we will soon release a major improvement that will decrease time by about 25%. Thats a total of 65% speed increase over our first version, apples to apples.
 
That was in August this year. Now I'm using 412 and am very happy.

I'm happy that R3D still evolves and is getting faster. I also love the camera specific features that R3D and Alexa Datamanager offer. I'll still use R3D whenever I need a specific feature, but on my current jobs only speed matters. I still am and will be a R3D Datamanager customer.
 
I'm looking into SPP vs R3D DM, but currently I'm using Al3xa DM, and there seems to be some very serious bugs with it, and was wondering if anyone had any similar situations with R3D DM.

Basically, say you are on reel A030, and you mount it up, and start the auto copy, only to realize that whoever formatted the card in camera, didn't check the reel number and it's formatted as A028. Even when Al3xa DM has settings to create new folder if source media exists at destination, the program does NOT create new folders and starts overwriting the Reel A028 that I've already verified and sent back to set (even if the reel folders are locked in Finder). Now I understand it's my job to check everything before-hand which is why I've never had any problems on an actual set, but these issues force me to find a different method of copying these files over, since the software offers no solution other than resetting all your output directories to a temp location for that specific card. I've done a few little tests in the time I had available and it seems to be an extremely dangerous bug, that defeats the sole purpose of the software. Has anyone else noticed a problem like this with R3D, or is it only the Al3xa DM version? The software does everything else fairly well, but with a bug like this, it makes me extremely nervous for how automated it is.
 
No, it simply relabels the containing folder to append a time stamp of when the copy was started. This is the way the R3D version works. This way it works in your scenario, or if you really are trying to copy the same footage again (like after a copy error). And it doesn't sit there waiting for user intervention when you set up 6 cards to copy and walk away for coffee.
 
That'll be fantastic, I'll be looking forward to this update, I'm just a little bummed that there was no warning of a bug this dangerous that is in a current release. Aside from that, the only other thing I've noticed that gets a little finicky is halting copies mid-copy causes crashes from time to time. Not a big issue, just something I've noticed (could be related to the Sonnet Qio which isn't running perfectly stable on my system at the moment). I like the software a lot, and will stick with it once this issue is fixed though.

It would be really nice to have a feature to start multiple instances of the program for simultaneous copies. I.E. copying from slow source media to RAID, and then wanting to start copying sound at the end of the day while footage is still working, where the simultaneous copy won't slow anything down going to fast destination drives. Just a thought. Thanks for being active in the forums, it's nice knowing that developers are listening to feedback.
 
You must log in or register to reply here.
Back
Top