Why does the video clip get split?

[Darrell Essex]

I was doing a test where I let the camera record for 5 minutes with out moving the camera.
When I went to look at the clip on the computer, it was split in 4 gig segments.
Anyone know why it did this?

Also, everything has a 1999 date on it.

Thanks

 

[Bob Gundu]

Thats the way FAT32 partitioning works.

 

[Terry VerHaar]

I was doing a test where I let the camera record for 5 minutes with out moving the camera.
When I went to look at the clip on the computer, it was split in 4 gig segments.
Anyone know why it did this?

Also, everything has a 1999 date on it.

Thanks

Totally normal as far as the split goes. As for the 1999 date, is the date in your camera set correctly? Post a screen grab of the file names and we can help more.

 

[ericyoung]

The 4GB chunks are a good thing. If the camera loses power or has a problem at anytime, you should only lose the last 4GB being recorded at that moment. If it was all one big file, you could lose the entire clip.

 

[Marc Wielage]

It's a pain in the ass for editorial. The Canon C300/C500's did this for some time, but I dunno if this problem was ever overcome or not.

 

[Maik Müller]

It's a pain in the ass for editorial. The Canon C300/C500's did this for some time, but I dunno if this problem was ever overcome or not.

No pain at all. All software that can handle RED-files will treat the splitted files as one big file, seamless editing and playback as if its one big file.

About the file-date/times. There is something wrong. If the camera is set right and looses the date/time after being turned off, then probably the little battery died.

 

[Terry VerHaar]

It's a pain in the ass for editorial. The Canon C300/C500's did this for some time, but I dunno if this problem was ever overcome or not.

Why is this? I've never had any sort of issue but that doesn't mean there can't be one. What is your experience?

 

[Bob Gundu]

It's so invisible. Not really an issue at all.

 

[Marc Wielage]

Why is this? I've never had any sort of issue but that doesn't mean there can't be one. What is your experience?

I worked on a project last year where the editor was still on Final Cut Pro 7. FCP7 only sees the broken files as separate chunks, not as one single take. I would much rather that Canon just invest in a newer operating system that can deal with files much bigger than 4GB. FAT32 is so "1999." I mean, c'mon.

 

[Eric Santiago]

In regards to file management, same as Avid.

The date stamp bugs me.

Ran into this a few times on big projects.

 

[Tony Mac]

I worked on a project last year where the editor was still on Final Cut Pro 7. FCP7 only sees the broken files as separate chunks, not as one single take. I would much rather that Canon just invest in a newer operating system that can deal with files much bigger than 4GB. FAT32 is so "1999." I mean, c'mon.

FCP7 doesn't take .r3d files natively, so wouldn't it had to be transcoded at some point? I don't see why transcoding it would break up the files, especially if you're using Redcine-x.

 

[Are Luke Muggerud]

It might be worth mentioning that FAT32 or ExFAT (not sure which REDMAGS use) enables you to read and write from both Windows and Mac

 

[Marc Wielage]

FCP7 doesn't take .r3d files natively, so wouldn't it had to be transcoded at some point? I don't see why transcoding it would break up the files, especially if you're using Redcine-x.

Canon.

 

[Jürgen Klenk]

Recoding in "chunks" is standard almost everywhere. XDCAM, P2, Canon MXF (which is also XDCAM), AVCHD, XAVC ... you name it. But with proper software (and sometimes a free plug in from the manufacturer) you will never see these chunks, they are automatically stitched together by the NLE. Also fcp 7 could very well see and import Canon files correctly. Seeing "chunks" in post is always due to human error (like ignoring manuals).

 

[Gunleik Groven]

I worked on a project last year where the editor was still on Final Cut Pro 7. FCP7 only sees the broken files as separate chunks, not as one single take. I would much rather that Canon just invest in a newer operating system that can deal with files much bigger than 4GB. FAT32 is so "1999." I mean, c'mon.

As to FCP7, this doesn't make much sense.

FAT32 works on all platforms, and is thus a good way to format the cards.
As some have mentioned, there is a bit of redundancy in the chunk'ing, too.

Me like (and we're probably doing the same thing in a little project I am working on)

 

[Justin Campos]

It must be FAT32, as ExFAT can handle greater than 4GB

 

[Jan Balster]

We had a Scarlet a while back that kept "forgetting" what date it was. We ended up sending the camera to RED to be fixed. They never told us what was wrong but we're thinking that it was some sort of internal clock battery that failed.