Welcome to our community

Be a part of something great, join today!

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 :)

COOL CAMERA GEAR R2E to ESATA - SHAM OR DOES IT ACTUALY WORK

As a fellow R2E owner I can only look back fondly on the few months of happy usage I enjoyed for my $225 investment. I still break it out on every gig and try it with each RedDrive at least once and occasionally it actually works, but not often. Cool Camera Gear hit a moving target and evidently moved on, not impressed with their business ethics post facto but they can't be expected to have a crystal ball either.

In any case, I am getting the impression that the spinning media RedDrives are an EOL item and we may never see any effort by RED to provide a RedStation module dedicated to offloading them at eSATA speeds. I would be thrilled to see Jarred jump on this thread and refute that...

The meaningful takeaway on this is that RED, despite all their other R&D priorities, did develop the RedStation to address time and reliability issues at the download step. CF users are taken care of right away and one would assume that the form factor of the media for Epic and Scarlet will be elegantly supported with purpose built modules as well. Moreover, now that RED is engineering the RedStation as well as the on-board recording media they can make sure it all works together seamlessly. Sounds good to me.

Cheers - #19
 
cool camera gear gets my vote as one of the most NON-ATTENTIVE RED affiliates. Had a good product and folks want more and willing to pay more to keep the product line, but they have yet to respond. Too bad. Guess that's the end of CCG. They've branded themselves quite well here.
 
Hi Conrad.
This is regarding the problem I was having of checking the destination checksums post copy problem I was having a few weeks ago.

I am using a new gen MBP late 2008 release, the few that were released with an express card slot, 4GB RAM 1067MHz. A Stardom raid set to raid 1 with 2X 1TB 7200 Barracudas in it connected via Esata to a Silicon Image Esata to express card adapter in the express card slot. In addition to this I will have a second Esata drive connected to the second Esata slot on the adapter either a Lacie 1TB or Soho raid 1 - 2X2TB HDD or Nexstar raid 1 - 2 X2TB HDD. Copying from a Reddrive connected via the FW800 or a CF in a Lexar reader connected via FW800.

I have ever since discovered that the checksum files were being written to only one of the destinations I was copying to. I was able to run a check on the destinations that had the checksum files but not on the others as they didn't have the checksum files in them. So when I added the formally destinations to the source window that did not have the checksums the “verify all checksums” button remained greyed out. I couldn’t find in the preferences any options relating to the destination checksum writing.

How can I make R3D Data Manager write the checksums to all destinations?

Thanks,
Nir.

[edit]
Posted this in the wrong discussion please ignore.
 
You must log in or register to reply here.
Back
Top