[Bill Kimzey]

Any updates on getting the GTX 780 working on your Mac 3,1? I see that card is now officially supported on a PC with the latest CC update. Does the October update fix it on a Mac?

[Bill Kimzey]

Did you, perhaps, make multiple copies from the card? If so, check other copies. One transfer may be bad, the other good.

Does the problem appear if the file is played directly in Quicktime? If not, you might be able to export the problem areas from QTPro into a more robust codec, such as Prores.

Depending on the severity of the problem it may be possible to manually composite good footage into the problem areas of your bad footage.

But, ’tis best practice to use ClipBrowser or some third-party tool with copy-error detection (such as ShotPut) for at least the initial transfer from the SxS card to your footage drive.

[Bill Kimzey]

7.6.6, but I did try X; no success.

Thanks

[Bill Kimzey]

https://support.apple.com/kb/TS2853

[Bill Kimzey]

I’ll humbly submit that you are right.

By standard, I had meant that this is what we saw often suggested as the way to do it. Not a good word choice – I should have said common. I could point you to posts and tutes that state this as the procedure, but I don’t want to embarrass or criticize what was meant as helpful. Since this was so oft suggested, seems like there’d be more complaining.

I’d be very interested to see what percentage of users use the ClipBrowser always to copy their footage vs. the straight copy, if anyone else would want to fess up.

I’m also curious why a file copy, which works mostly flawlessly on other files, would fail to copy byte for byte for this particular format. I’m guessing there is a reason; since Sony included the CRC, they must have suspected there’d be problems sometimes.

Thanks for your help. Guess we won’t be able to use the G5 for offloading from here on out.

We’ll keep our eyes out for pic breakups, but hopefully this will solve the problem.

Thanks

[Bill Kimzey]

Not quite – unfortunately this was shot a while back, and is only being discovered in the editing stage. So, the first copy from the card was done as a straight copy of the BPAV folder from the card to a couple of hard drives, as stated above. Sorry if I wasn’t clear about that.

So, I can only use the ClipBrowser to move files post that initial copy.

This seemed to be a standard way at the time, using the ExpressCard slot on a laptop to trasfer it to a couple of drives.

One other note is that we’ve only noticed this on long records, over 30 minutes or so; may or may not be relevant.

Is everyone else always using the ClipBrowser to copy the file from the card initially?

Thanks

[Bill Kimzey]

The general procedure we’ve used is to copy the BPAV folder off the SxS card to 2 hard drives; then from FCP, select XDCam import which calls up the XDCam Transfer Tool (2.8), and import the footage. The re-importing is marking in and outs from the clip where the breakup occurs, then importing again. This doesn’t always fix the problem; often only makes it less obtrusive, and often does nothing.

Using the Clipbrowser 2.5 to import the footage (w/CRC) does not seem to fix the problem.

Several cameras were rented, as were the cards, so I cannot vouch to their care. We have seen it also with our own EX3 on our own cards, which we do take good care of. With the rentals, I believe we reformatted once before shooting, then simply erased the files off the card from that point. (It seems as if – though did not count the breakups – we have more on the first use of the cards than in subsequent non-reformatted uses.)

I’m uploading a few example pics to show the problem. Often it’s more subtle than these examples. The blue boxes are for obfuscation 😉

Thanks

example1.jpg

example2.jpg

[Bill Kimzey]

This fixes the problem of 720p60 audio ticking. 😉

[Bill Kimzey]

This is a repost, since the first time I posted this, it disappeared (after appearing briefly).

Sounds good.

One other thing of possible significance – we can’t hear the clicks in the Clip Browser, but only after it has been turned into a QT file.

So, we are inclined to think that the recorded audio may be fine, but the conversion creates the problem. In other words, the camera may not have a problem, but the software might be the culprit.

By the by, we did not do any testing in the PC world, so I don’t know if this problem exists only on the Mac side of things or not.

Thanks, and if you hear anything about a solution from the Sony guy we’d like to know it, as we are interested in the EX3s.

Thanks.

[Bill Kimzey]

Yes, clicking is definitely there. Some updates from my previous post on this topic.

With 2 rented cameras, the problem was present on both, even when no audio was recorded, that is, mic off.

The clicks are absolutely visible in waveforms.

Recording in other modes (can’t say definitively all other modes, but all other modes we tried) did NOT give this problem. In other words 1080i seemed just fine. This may explain why not many are noticing it – I don’t know how many are shooting in this mode.

Since 720 p60 HQ was what we wanted to shoot, we had to use double system sound to get a clean recording.

Also, since the clicking either appears or disappears at the 4GB boundaries, unless doing long form recording, it may or may not be present. You may have to record longer than 13 minutes to get it. In tests, I recorded for 30 minutes at a time so as to have 2 boundaries.

The firmware on the cameras, was, I believe, an earlier version, so I can’t say if this is a persistent problem on later editions.

I’m also curious if the problem remains in the EX3, so if anyone has that info, I’d be happy to hear that this is fixed.