[Ryan Biller]

Hi Jeremy-

The objective is a streamlined workflow for finding clips whose source resolution and frame rate differ from the sequence’s using the browser.

Whether we’re tripping over nomenclature or whatnot, I don’t care if the clip is a master clip, sub-clip, affiliate, duplicate independent… I want browser to display source media resolution and frame rate like it used to for me in FCP 6.
That was not impossible then, I’d hate to imagine that it’s impossible now.

I employed your method of revealing the master clip- it pointed to the clip in my browser that displayed a column value of 1920 X 1080, 29.97fps.
If I then reveal the item properties of that very same, highlighted clip, I get two columns in the pop-up: one ‘Clip’, one ‘V1’. The clip lists, 1920 x 1080, V1 lists 480 x 270, 30fps- the latter is the same result if I open in editor/quicktime and hit control-I. That’s the info I need, that’s the info I wish the browser would display.
If you can steer me in that direction, that’s my promised land.

I appreciate your spirit in trying to help.

[Ryan Biller]

Jeremy-

I appreciate your suggestions- here’s the breakdown:

Revealing master clip points to the clip in browser- that clip in browser still displays the offending info I’m looking to correct.

I have a couple hundred clips to deal with in my sequence- opening a Item Properties window for each would be a mess/time consuming.

And where it comes down to is I need the browser to display the info properly (at least what I consider properly) so I have easy functions of labeling, organizing by parameters, reconnecting media, etc.

So I agree, sending Apple a little what-what might help.

[Ryan Biller]

Let me clarify:
I need to drag all clips from the entire sequence into a browser window/bin to do my weeding process.

My example should have used an indefinite article:
‘If I display the item properties for a clip…’

Jeremey,
Please define ‘match frame to the browser’-
I don’t know any function for match framing directly to or in browser.

As a test, I did match frame a clip and drag that from viewer to browser, but it still displays sequence properties not the source.
Further, I don’t know of the ability to match frame multiple clips; I need this to be a macro-solution for all clips comprising the sequence.

Just as a vent on the ontology of this problem:
This method worked fine in FCP 6: drag clips to browser, get source info.
I do not understand the benefit of FCP 7’s displaying clips frame size and vid rate in/from a sequence if it’s only gonna copy the FS and VR info of sequence properties. It seems like redundant information- I can just look at the sequence settings for that info.
The actual source properties of the media is what would benefit me.

Happy Festivus

[Ryan Biller]

I am not certain about the footage being non-drop though my suspicion is yes.

There were two shoots for this project: on the first, I thought the cameraman and I agreed to do 29.97 DF as the TC rate just in case it may have a broadcast future.
But then on the second shoot I was told that the Panasonic Vari-Cam (which was an AJ-HDC27H, not the AJ-HDX900) always records at a rate of 59.94. But again, that is saying sampling frequency, not necessarily TC rate, correct?

That is part of my line of questioning: what are the parameters regarding timecode with Vari-Cam that define the settings for the Tascam’s LTC to follow?
Is there a constant to always follow, such as 29.97 or 30 NDF- or does the cameraman define the TC Rate (which is what I thought from the first shoot discussion)? Is there any dependence on shutter speed and sampling frequency?

Further- yes, I ingested 720p footage at 1080i. We’ve been capturing at ProRes422 1080i based on another project that mixed both 1080i HDCAM and 720p DVCPRO HD Vari-Cam. The decision was made (not mine) for sticking with 1080i and living with the slight softening in the 720p footage.
So it was our default setting for captures and I did notice halfway through digitizing the second shoot that 720p would have been ideal for digitizing… but at 3/4 through, I chose consistency in 1080i.

It’s something I’ll keep it in mind for the future and have been well deprecating myself. Still I don’t believe that would bear relevance on the time code issue… And all the above is auxiliary to my main concern of why FCP’s info for the WAVs’ Media Start is off from the TC Start listed in Wave Agent.

[Ryan Biller]

The Tascam was set for 48KHz/24bit at 29.97 DF- Broadcast WAV’s of course. Dragging the WAVs right into FCP shows a TC Rate of 30.

Now, it was a Vari-Cam Panasonic and I could use some enlightenment-
The way I think I understand Vari-cam is that the sample frequency for the camera always runs 59.94 and the operator chooses a frame-rate and the camera takes care of pull-up/pull-down.
(If I’ve got some wrong concepts there, I don’t mind so long as someone lets me what right is.)
That said, the cameraman was using 24p for his frame rate and the footage was digitized using Apple ProRes422 1080i and FCP lists the vid rate as 29.97 and the TC rate as 30.

So with regards to the camera and syncing: are frame rate, sampling frequency, and time code rate somewhat independent entities?

Would there have been a better setting for the Tascam? If I had it to do over, I’d have chosen 29.97 ND… but the Tascam has options for 30 DF and ND (and 24, 25, etc) and pull up and pull down for ’em all; seeing the TC Rates in FCP as both 30, I’m left with a lot of wonder.

And does any of this affect the Start TC/Media Start disparity I’ve run into with FCP and the BWFs?

[Ryan Biller]

I’m having the same problem- Final Cut worked fine yesterday, and today, the icon jumps once and nothing else; Final Cut won’t start.

Here are a few details that maybe someone can use to help us troubleshoot:

I got done ingesting material around 6:30p, saved everything, and shut down Final Cut. The computer was left on over the course of the night to upload some files to an ftp but I did come back around 9:00p just to check on the transfer and nothing seemed out of the ordinary (Final Cut wasn’t run then, so who knows).

I came in this morning and our intern said they tried to use Final Cut directly from being left on last night and it didn’t work- same scenario, icon jumps once and no start. So they tried a restart and that had the same result, and further tried an entire shutdown, same thing.

Here’s a note that may yield understanding to a greater mind: I switched to another user account on the computer and the Final Cut icon on the dock was grayed out with a circular line-through symbol and gave the message ‘You can’t open the application “Final Cut Pro” because it is not supported on this architecture‘ if you tried to start it there.

That should mean something and provide a diagnostic route? I did searches here and on the web and didn’t find anything too enlightening.

I did have this happen once before on this particular machine about six months ago and tried the trashing preferences solution others sometimes recommend- but ultimately had to resort to a Final Cut reinstall- which I’d prefer to avoid since that’ll put me a day behind and blow my weekend.

So any clues or insights on how the ‘architecture’ would have changed over the course of the evening or even what said architecture consists of?

Solutions would be nice too- but the reinstall has worked before and if it has to be, it has to be. But knowing why it went wrong and preventing it from happening again would work for me… this randomly happening a third time in the future would deliver too much angst.

Thanks ahead of time for any helpful input.