[Ann Clark]

Here’s a variation on that theme:

I use a Sony HDV deck, and usually FCP recognizes it when I start FCP.

Today, after rolling in DV footage with this Sony deck, I noticed that FCP was not recognizing the Sony deck. After lots of trashing of preferences, restarting FCP, restarting the Mac, plugging and unplugging (amid lots of head-scratching), I discovered that the deck was convinced it was set to HDV 1080i. I used the deck’s menu to change from “Autoselect HDV/DV” to just “DV” and then FCP finally caught on and recognized the deck again.

The only puzzling thing is how I was able to roll in footage just moments before, only to have the deck change its mind about the input.

So, I think if a deck or camera goes unrecognized like this, the best approach is to check if the deck or camera is set correctly (in this case, to DV).

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Thanks, Mark.

I didn’t realize what was wrong until I visited the Compressor folder and saw the naming convention for my other custom settings.

Apparently, the cable net sent us the right file, and the filename had the word “setting” at the end, but not “.setting” — so Compressor wasn’t recognizing it. D’Oh! (smacks forehead)

Once I added the dot, all was well. 🙂

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Audio compression is one of those many things that have TV commercial producers vexed. FCP 7 doesn’t have a great way to measure whether you’re exceeding the C.A.L.M. requirements, and broadcasters aren’t putting their own limiters on the output from their stations. They simply reject any TV commercial with peaks that exceed their requirements. Audio software with easier to use compression filters can be a big help there, but I’m sure not everyone has access to just the right tools.

As media buyers, ourselves, we often air commercials for other producers, but nowadays we run each of these outside ads through our “Evaluation” process, which includes checking for Luma levels and audio peaks. We send our evaluation to the producer, they make corrections, and then send us their cleaned up ad — assuming they have the tech savvy to accomplish the task. The VAST majority of these small producers really don’t know what they’re doing though, and a few just get angry at the critique and don’t air the ad at all.

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

As it turns out, I elected to follow some instructions from the Goog’s website regarding how to output from FCP via Compressor into an H.264 formatted file. (Hold your nose, punch in the numbers in the fields and hit Go.) The MPEG2 conversion they offered didn’t yield a result I was happy with, so I used the H.264.

[Ann Clark]

[Jeremy Garchow] “As far as getting FCP7 project support, that might not happen. It certainly isn’t possible today.”

Bingo.

When they solve this big requirement, then I’m perfectly happy to try it out. Till then, there’s no real motivation for us to experiment with the new regime just because it’s from Apple. (Plus, they don’t pay the editors to experiment, they pay to get the job d-o-n-e.)

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Jeremy,

I think you’re taking me out of context. Simpler is better – as long as that’s streamlined. Also, I said that the common opinion seemed to be that the software was a bit low-end.

The interface, as I understand it, for FCPX, requires learning/relearning a few, maybe many, things.

I don’t need the 30-day test drive. My hardware, according to my tech guy, is on the non-compatible list. He said I’d need an upgrade to try the test drive.

Maybe when FCPX gets a few more of the features I need, such as support for my gazillion FCP 7 files, I’ll take the financial plunge. For now, I don’t intend to fix what ain’t broke…

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Jason,

When it comes to money and performing a custom job like video, a contract will save you a lot of grief, if it is written correctly. My feeling has always been that a client who balks at the contract will eventually balk when it comes time to pay.

Recently, I had a client who paid us for a service, but somehow our team missed getting a signed contract along with the check. First, he sent just a check – but unsigned. Hm. When we asked about a replacement check, he acted sheepish, then finally sent a signed check. But in all the shuffling, we didn’t get a signed CONTRACT (which would have limited what we agreed to do for him, for that money). Nevertheless, like good sports, we proceeded to do the work, as if he had actually signed the contract. (We didn’t want to turn down the business, you know.)

Then he raised a big stink later on, demanding things that we wouldn’t have been contractually obliged to do, had he actually signed the contract. Long story short, he eventually quit calling, then had an aggressive buddy call us to try to bully us into a refund on the custom work that had been performed, then eventually they both quit calling. But not without making us miserable with their harassment.

Anyway, that’s what we got for trying to help this guy, without having the paperwork.

Having a contract is just good policy for keeping your business solvent, and the phones quiet.

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

John — I know you responded to this thread in ’09, but I would like your thoughts.

It’s 2011 and Perian still doesn’t support the f4v format. ;-o

Going from MOV to f4v is apparently easy, just change the suffix to f4v (so I’m told).

Going the other direction, it doesn’t seem to work. I can play a f4v in Quicktime, but can’t save it in any other format. MPEGStreamclip doesn’t like this f4v, neither does VLC. Flash itself doesn’t even want it.

Bad file, maybe…? Dunno, since I didn’t create it. Seems like I would need to ask the client for the clip in another format.

Any additional suggestions for a cheap/free translator from F4V to MOV?

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Good point. One anecdote does not make a trend. My experience is that most who have their own productions don’t really like hearing that “your baby’s ugly.” They’re twice as offended when you tell them what it will really cost to fix it (even if we offer them some really awesome deals on edit time, etc.). Based on the many clients we talk to here, they’re very emotionally invested in their handmade productions, and not inclined to see anyone apply any finishing services. It’s hard to even explain to them that a YouTube vid is not necessarily in broadcast format, much less get them to pay to have it fixed. I don’t really see a trend there yet. Maybe later, but not right now.

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7

[Ann Clark]

Craig, You’ve clearly got a lot of time on your hands. I’m not sure why you’re so interested in countering me line by line. Tiresome.

@Don — if you’re still following the thread you started — any ideas?

MacPro 2 x 2.8 GHz Quad-Core Intel Xeon 14GB memory – OSX10.6.4 FCP7