Nicole Haddock
Forum Replies Created
-
I rarely have problems FTPing files to various sites, but occasionally you do hit upon a server that doesn’t like certain type files. That might be what Monsieur Bogiesan is getting at.
What are your sequence settings? If it’s a DV sequence, you can just go file/export quicktime (not conversion!!) and spit out a DV file. At 1 minute, it’ll be less than a gig. If it’s HD, or you’re editing in a specific codec, it gets more interesting.
-
We’ve got 2 G-Speed ES’s humming along here, and they are pretty great, but they aren’t super quiet. I’ve got a 3GB one next to me right now and the fan noise is definitely audible. It’s nowhere near as loud as some of the firewire drives I have, and it’s not particularly distracting. I think if it were under the desk, I probably wouldn’t really take note of it, but it’s on my desk about 3′ away from me. The AC unit in the room is louder. Hope that helps 🙂
-
If you don’t choose the Quicktime Conversion option, just go Export/Quicktime, FCP will (more or less) automatically export a file at your chosen sequence settings. For archiving purposes of a finished piece, I’ll export a self contained via that method, ergo I’ll have a file that’s at the editing specs I chose to work in. MOST of the time this is what the footage was shot at, or at least a majority of what it was shot in. As long as you’ve put some thought into your sequence settings if you have mixed footage, exporting just to Quicktime and choose make movie self-contained, you should be fine.
You may also want to consider exporting different versions of your piece- one as is, one without graphics, one without music and fx, etc.
-
Well the unable to connect to background process is a different problem requiring a different solution (do a search and the fix will show up).
But the bigger problem is the compression you chose- why are you going to HD DVD files? From the beginning, it sounded like you were trying to get this up to the web. And you’re also compressing an already compressed file which really isn’t the best way to go. I would export a self contained file and then in the Compressor presets, go to Apple/Other Workflows/Web/Download/Quicktime 7 Compatible. You’ve got 5 choices there to get you started. Do not change the file extension in Compressor, wait until it’s done with your file, THEN change the extension. It should be fine then, but first you’ve got to fix the background error.
Digital Rebellion has gizmo that makes this easier (most of the time)- https://digitalrebellion.com/blog/posts/compressor_repair_1.1.4_released.html
-
What are your sequence settings at and what are the settings on your media (especially compressor, pixel aspect ratio, etc)? Chances are something’s hinky there. Do the files playback fine in the Viewer?
-
Try exporting a self contained QT and converting that file. If you’ve got the Creative Suite on your system, the Adobe Media Encoder can crunch it to an FLV file for you.
As a general rule, compressing straight out of FCP is often an exercise in crashing and futility. It’s really not made to do compression- that’s what Compressor and other utilities rock at.
-
When you drag your sequences into the Export Queue, highlight the batch or sequence, hit settings, and the popup window will give you a check box at the bottom to “make self contained” files. Uncheck that and you can make reference files.
-
Muchos nachos.
The secondary camera operator made an offhand comment while we were scratching our heads over this- “Oh, we recorded in the one without the N”, which is a format we have NEVER EVER SHOT IN.
The main operator said it was PN. Everyone know where their right hands are? How about lefts?At least Tuesday has been interesting.
-
I *just* had this problem and was absolutely boondoggled by it.
What happened was I got a film submission (I work for a festival) in Quicktime, he said it was shot 720p24 on an HVX-200. Great, I see that stuff all the time. I copy the QT over and it was the same specs you listed. I have never seen the 1248×702 nonsense before. I brought it into FCP, sank it into a DVCProHD timeline, and it was all distorted. I let FCP determine the settings, looked fine, but of course this had to go out to HDCamSR, so bizarre 1248 settings would do me no good. Every time I brought it into a proper DVCProHD timeline, it came in distorted, and even when I fixed the distortions, I would either be letterboxing the file in the timeline (so it looked kinda 70mm ish) OR pillarboxing it. Then the guy mentioned he had to cut it in AfterFX. Riiight. I took it into AFX, same problem.
And then I found a solution. I popped the file into a DVCProHD 720p AFX timeline. Under the view options, I hit “correct for aspect ratio” AND VOILA, the film went full frame, looked fine, despite it’s weird pixel size, and so I re-rendered out the film to the DVCProHD 720p60 codec (which is what it was originally), brought that back into AFX and bam, looked fine, went out to tape fine.
I really have no idea what made the pixel sizes go all weird other than an operator error when he rendered his film. Btw, rendering this 6ish minute film on an octacore 2.8 with 6GB of RAM probably took 8-10 minutes. But once it was kicked out, it was fine.
But, to get the film out of FCP properly, click in your timeline, then go File/Export/Quicktime, use the current settings and make sure “make film self contained” is checked. You should be good after that.
-
I’m going to ditto what Jason said because, hah, we used to work together at the same lab!
Another solution to consider is a tool like Digital Rebellion’s Preferences Manager or Final Cut Rescue. You can save settings for FCP and with the click of a button, can trash the preferences and restore to your approved backup.
I lobby for all labs of any kind to have a preferences trasher tool since it solves seemingly 90% of the problems you see on a lab level and they’re generally a pain to find unless you really know what you’re looking for.