[Gary Adcock]

[james Lackleter] “Yes audio is not video but it does FPS for playback. With your logic I can record 48000 samplerate and play it back with 240 fps video and it will match.
“

No that is not correct- Audio does not record in FPS and never has. Audio on early dual sound recording was done on Nagra style tape decks that recorded the files in ft and inches. Later using minutes and seconds as the metric.

While there may be timecode associated with the audio, there is not any frame indicators on any audio file that I know of.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[james Lackleter] “Audio at 24 fps, and video at 23.98 syncs.
Audio at 24 fps and video at 24 fps does not.
“

James

It react this way because there cannot be Frames per Second in an audio file, (there are no frames) while there can be timecode, audio files captured as Dual System Sound independent from the camera would match the the camera frame regardless of how the audio was recorded (actually had this happen with a 25P camera and 29.97 tc on the audio)

In the tape era, audio was recorded in ft and inches, in a digital world while we give the audio TC in actuality many of the audio formats do not support a time code track to reduce bleed / crosstalk.

Audio records in minutes and seconds, not FPS and that is why the 2 match.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Carlo Ferraro] “I am starting to do time lapse at 4K and playback is critical to spot any flickering or image jumps. I work with USB3.0 raid (Buffalo). “

No USB 3 Drive can really support a full 4K workflow, you might be able to handle ProRes Proxy or LT from that drive but you get what you pay for.

4K is not for the timid.

4K is not something you want to edit on anything but the fastest drives possible, if fiber is barely fast enough for 4k workflows, there is no way your inexpensive USB drive will be able to compete, it was not designed for that level of performance.

You need to be editing on a RAID volume to maintain the speed that 4K needs, I would not recommend any drive with less than 4 disks minimum, with 8+ being optimal.

Thunderbolt is the only connection technology that has enough power to handle 4K without a hassle, accept it and you will enjoy a lot less hassles.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Bret Williams] “Gives you write and playback speeds in the high 300-high 400mb/sec range.”

Bret

That’s really slow for that setup. 400mbps (that’s megabits)

I would expect that read/write to nearly 2x faster and should be closer to 600MBps (megabytes)

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Don Walker] “and it has 426 GB empty space remaining.”

For a 4T Volume that’s less than 25% of the available space is remaining open on the drive. Not many drives work very well when that full and most apps will not create content on a volume that is that full.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Dinis Rodrigues] “Those individual block failures must also have happened post copying, as we would have detected them while copying during those couple seconds of playback.”

Why? its not like you can see what is going on while the file is writing. You are writing Gigabytes there is no way you would see a bite error that small- thats why you write data with verification by MD5 or CRC32 checksum tests.

“Also, do you know how to recover footage from cards formatted on camera?”

Most Formatting only destroys the header/ directory on the media, the data is not damaged in most cases, and ARRI uses the same UDF formatting that Sony does for that media the process is not that difficult.

I will say that some of the tools are off the shelf and some are not.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Dinis Rodrigues] ”
I also found out today that when the alexa formats a card (not “erase card”), even though it takes just a couple seconds, it is a destructive format, unlike when you format a normal harddrive or card through the operative system”

First- I am regularly able to recover media from re-formatted Alexa SxS cards in a reliable fashion so that is not your issue. THIS IS NOT A CAMERA ISSUE

Again. I am more than sure the error you see is failure of the storage media chosen to store the Camera data on, not in the media or the transfer from SxS.

Those lines appear to be from the individual block sectors failing failing on the drive itself – and since EXFAT does not allow for error correction compensation on media, the drive mechanism does not know not to write on the bad segments of the media

There is no excuse for not making a backup copy when handling data, it’s somewhat akin to handling film in the light-DONT DO IT.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Dinis Rodrigues] “It just doesn’t make sense how, as mechanical-wise, the hard drive seems to function fine.”

Drop outs. those are small individual partitions on the drive.

Have you tried coping the data to some other media?

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[Dinis Rodrigues] “Shot on Alexa 2k 444. All the clips got this, 6 different cards, interior shot.
The clips were viewed from the hard drive the cards were copied to, a 2TB WD drive.
“

OK.
First off this is not any type of error that would happen in-camera, Alexa Sensor errors tend to have multi-colored pixilation due to the nature of the CMOS sensor. The camera would also be indicating is something this drastic had happened.

You also do not mention what format the content is which 2K frame size, and what frame rate.
Did you record to SxS ProRes 444 or ArriRaw 444 ?

SO.

What app’s are you viewing the file in?
Are you viewing them all from the same media on both computers?
How are the drives formatted?

Have you checked a backup copy of the media? Having this on 6 different pieces of media makes me think that the error is on the harddrive holding the content and not in the camera originals.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock

[Gary Adcock]

[John Lee] “o my question is that possible to edit arri raw natively or do i need to convert to pro res or something else?”

did you use one of the arriraw presets that have been in Premiere since CS6 and in the CC version?
if you use the preset ( there is one for 1080 and one for full frame) the files just playback normally.

gary adcock
Studio37

Post and Production Workflow Consultant
Production and Post Stereographer
Chicago, IL

Follow my blog at https://www.garyadcock.com

Or follow me on Twitter
@garyadcock