[Brian Houle]

Hi Brian,

I just wanted to follow up on this thread.
I’ve had a chat with 2nd level FCX support. I’ve done a series of capture tests and screenshots which I’ve sent to them at their request. They had the same issues and are looking into.

I’m putting my money on QT 10.1 being the culprit along with FCX. QT 10.0 plays the files perfectly as does FCP 5 and 7. A file captured in FCX reads as DV/DVCPRO NTSC in QT 10.1, but in QT 10.0, it reads as DV NTSC (as does QT 7 Pro) – those files all import into FCP 5 and 7, but not FCX.

Will keep you posted.

Cheers,
Brian

[Brian Houle]

Wow! Thanks for taking the extra steps! I appreciate it.

I’m using FCP 5.1.4 and FCP 7.0.3

Maybe I should mention that I use a Canopus (or Grass Valley now) ADVC300 connected via FW. I don’t think that would necessarily matter though, but I wanted to mention just in case.

Interesting that you files worked just fine.

Also, I captured the same tape on FCP7 on my 2010 Mac Pro and FCX wouldn’t import it either. The support rep had asked if FCS 3 was installed prior to FCX because he was thinking the codecs should be installed. I even installed QT Pro 7 and that didn’t help (aside from being able to see the file using QT 7).

hmmmm…

Cheers,
Brian

[Brian Houle]

Thanks Brian – neat app!

But now I want to shed another tear lol

I checked one of the original capture files and the format is indeed DV (NTSC) so I checked one of the files I converted in MPEG Streamclip in both mediainfo and QT 10.1

QT 10.1 = DV/DVCPRO NTSC file

In Mediainfo = DV (NTSC)! it reads the same as the original file. This adds another layer of confusion.

I’m with you – these are files created by legacy FCP software so there’s no reason it shouldn’t import. I told the support fellow that too after he told me what I was doing was using ‘older technology’ whereas FCX is a new way to do things. Explained that I wasn’t asking my older machines to rip HD footage or anything. lol These are basic yet important functions for which these machines are perfectly suited. 🙂

Plus I want the new machine to harness it’s horsepower and not handle menial tasks if I can avoid it – maximize time 🙂

I sent a detailed feedback page to the FCX team. Not sure what else to do. I truly believe it’s a minor oversight on their part.

Cheers,
Brian

[Brian Houle]

Hi Craig,

Thanks. I did update as soon as it was installed.
To me, it seems that the DV NTSC 720×480 format wasn’t built in. They went with DV/DVCPRO NTSC 720×480 as their ‘base’ SD format.

I tried explaining that to the FCX pro apps support as it’s the only difference I’m seeing, but he said as long as the app works, that’s the support they provide. Of course, I politely disagreed with him b/c as far as I can see, it’s not working with their own other apps (being FCP 5 and 7). I don’t expect them to import project files which we know is an issue, but their own basic video format shouldn’t be a roadblock 🙂

Cheers,
Brian

[Brian Houle]

Hi Brian,

Thanks for your response. You’re close – and this is where it’s confusing – I think the new machine does have the right codec. I think it’s FCX which won’t read or use it.

FCX seems to use DV/DVCPRO NTSC for capturing (or it will import those files as well) whereas FCP 5 and 7 uses DV / NTSC for SD footage.

I have FCS 3 (FCP7) installed on the same machine and if I use that to capture the tapes, FCP7 reads them no problem, as does QT 7. The more confusing part is that QT 10.0, on my 2009 Mac Pro (with Snow Leopard), can also read the files. I have FCX and FCP7 on that machine as well.

So it’s QT 10.1 on my 2010 MP with Lion and FCX on either machine which can’t read or use that codec.

I was hoping to maybe use another sequence setting to capture them?

Sorry if I wasn’t clear in my original thread. I’ve done so much troubleshooting… 🙂

[Brian Houle]

Thanks Shane.
I only see options to move this into another forum but the only fCPX is the to FCPX or not: the debate forum.

Should I just copy and paste? Trying to follow proper etiquette.