addie_reiss
New member
Okay...
Just came back from a lovely day at the beach here in Tel Aviv. And wow...! so many replies... in such a short time...
I must admint that i got what i wanted. I started this thread to tell the story, which is an educative one. I guess I like drama, therefore i chose the phrasing the way i did. after all - i did want to get responses and different angles and opinions from fellow camera people, and i wanted to get attention to the problem from RED technicians. after all if the post had a dry title like "CODEC FAULT" or "RED DRIVE FAILURE" and the presentation of the issue was a list of dry facts, not so many people would bother responding.
and after all - we are here to make drama...and to tell the story...
Its a shame, though, that the Thread, which was so active and lively was closed... (the problem is not solved yet...)
I am happy to see that the forum here is alive and responsive.
I was shocked that some people here "took it personal". my appologies.
I'd also like to thank the kind souls here, voluntairily demonstraring their SCHADENFREUDE (http://en.wikipedia.org/wiki/Schadenfreude).
And also thanks to all those guys who chose that the best way to defend their beloved is to attack my professionality.
Between all the responses it seems there was one guy "Andrew" (http://www.reduser.net/forum/member.php?u=805) who was on to something quite disturbing...
but before that, just to clear things out:
- It was against my judgment to work on Hard drive (in the studio we worked on CF).
- it was against my judgement to work without swaping drives.
- I never trusted this technology. it always seemed immature to me. The producer tought i'm paranoid.
the producer was aware of my recommendations and precautions. but obviouly trusted this technology more than you guys. Schadenfreude. spare the finger pointing please.
back to Andrew. if there is a chance that the disk was damaged when connected to the computer, then there is a missing link in the product. red should supply a proper download/backup solution. Something like the Portable P2 reader (panasonic AG-HPG10). and by no means allow accidental loss of data because of computer interface issues (a scenario that could happen also in the field).
The basic thing is that you need to trust the camera. tripple backups means people dont trust the workflow. tripple backups also means production overhead.
when i look at the Arri D-21, i feel safe. a robust and trusted tape mechanism to store the data that i know was tested over and over again by Arri in extreme conditions. They dont ask me to open a portable delicate IT office in the field. they "say": trust us - we are Arri. RED "sais": dont trust us - we are RED. watch us real close. one moment you look away and we will bite you.
Schadenfreude.
Thats the way to treat a trusting customer.
but regardless of the data loss, the real annoyance is the CODEC FAULT. this is unforgiven. almost no reply about that. are you guys living happly with a camera that may not always be able to shoot? do you like double guessing what kind of images this CODEC is capable of dealing with and what images you just arbitrarily cant take?
when you have to shoot - shoot. dont talk.
lets admit the truth. its not ready. not yet.
Just came back from a lovely day at the beach here in Tel Aviv. And wow...! so many replies... in such a short time...
I must admint that i got what i wanted. I started this thread to tell the story, which is an educative one. I guess I like drama, therefore i chose the phrasing the way i did. after all - i did want to get responses and different angles and opinions from fellow camera people, and i wanted to get attention to the problem from RED technicians. after all if the post had a dry title like "CODEC FAULT" or "RED DRIVE FAILURE" and the presentation of the issue was a list of dry facts, not so many people would bother responding.
and after all - we are here to make drama...and to tell the story...
Its a shame, though, that the Thread, which was so active and lively was closed... (the problem is not solved yet...)
I am happy to see that the forum here is alive and responsive.
I was shocked that some people here "took it personal". my appologies.
I'd also like to thank the kind souls here, voluntairily demonstraring their SCHADENFREUDE (http://en.wikipedia.org/wiki/Schadenfreude).
And also thanks to all those guys who chose that the best way to defend their beloved is to attack my professionality.
Between all the responses it seems there was one guy "Andrew" (http://www.reduser.net/forum/member.php?u=805) who was on to something quite disturbing...
but before that, just to clear things out:
- It was against my judgment to work on Hard drive (in the studio we worked on CF).
- it was against my judgement to work without swaping drives.
- I never trusted this technology. it always seemed immature to me. The producer tought i'm paranoid.
the producer was aware of my recommendations and precautions. but obviouly trusted this technology more than you guys. Schadenfreude. spare the finger pointing please.
back to Andrew. if there is a chance that the disk was damaged when connected to the computer, then there is a missing link in the product. red should supply a proper download/backup solution. Something like the Portable P2 reader (panasonic AG-HPG10). and by no means allow accidental loss of data because of computer interface issues (a scenario that could happen also in the field).
The basic thing is that you need to trust the camera. tripple backups means people dont trust the workflow. tripple backups also means production overhead.
when i look at the Arri D-21, i feel safe. a robust and trusted tape mechanism to store the data that i know was tested over and over again by Arri in extreme conditions. They dont ask me to open a portable delicate IT office in the field. they "say": trust us - we are Arri. RED "sais": dont trust us - we are RED. watch us real close. one moment you look away and we will bite you.
Schadenfreude.
Thats the way to treat a trusting customer.
but regardless of the data loss, the real annoyance is the CODEC FAULT. this is unforgiven. almost no reply about that. are you guys living happly with a camera that may not always be able to shoot? do you like double guessing what kind of images this CODEC is capable of dealing with and what images you just arbitrarily cant take?
when you have to shoot - shoot. dont talk.
lets admit the truth. its not ready. not yet.