Activity › Forums › Apple Final Cut Pro Legacy › Single file to go “online”
-
J. Tad newberry
August 4, 2007 at 6:06 pmi’m pretty sure they have all software up to date, and therefore FCP 6, but i’ll check.
do i gain anything by going with ProRes? also, what is the diff between HQ and non? and should i go 1920 or 1440?
thanks again!
mh
-
J. Tad newberry
August 4, 2007 at 6:14 pmsorry it has happened (albeit mysteriously!) to you, but i’m glad to know it’s not just me. sometimes i think i’ve been struck by lightening or something as it seems my fingers seem to short circuit some of the high tech stuff i touch. either that, or my brain stopped developing about 7 years ago…
anyway, i did a few more tests. short tests, just the first 30 seconds or so of the sequnce. did one where i first went and made sure Easy Setup was where i wanted it (DVCPro HD), then exported the clip with “Current Settings”. it imported fine, no rendering needed, 1280 x 1080, just like the original sequence. then did one with Settings chosen at DVCPro HD 1080i60 (which SHOULD be the same as “Current Settings” anyway). well, both of these short tests needed no rendering…so i started wondering if it might have something to do with the length (c. 5-6 minutes) or size (5-6 GB) of these files…but then i hear your story and maybe it can just be chalked up to electronic flakiness (or “funkiness” depending on your preferences)…or maybe it is electronic terrorism that we all just accept now as “normal”.
if so, the terrorists have won!
thanks again!
mh
-
John Pale
August 4, 2007 at 6:22 pm[mortimer heathcliff] “upon checking the file info on these clips, one rendered at 1280 x 1080 (the “Current Settings” version, which is what the sequence is), and the one where i chose the DVCPro HD rendered at 1920 x 1080. obvious discrepancy here, and just trying to nail down what will cause me the least amount of time and headache at the post house. again, starting with 1440 x 1080 HDV and 1280 x 1080 DVCPro HD (from HDCam original footage), also wondering if i really “gain” anything by rendering at 1920 x 1080 or should i leave it at 1280???”
I had this happen recently too. I was able to track it down to some animation files in the timeline….if I added a broadcast safe filter to them, thus causing FCP to read the render file instead of the original media, the timeline would export at the correct size. Not sure what was wrong with the original media..probably some weird Quicktime metadata bug…they were the correct size and codec.
-
J. Tad newberry
August 4, 2007 at 6:27 pminteresting…this could very well be the problem, and explains why the first few seconds rendered fine, but the longer version did not. i have several embedded QT movies (from Motion files) within the sequence so this could be it…
i’ll try the broadcast filter route…
thanks again!
mh
-
J. Tad newberry
August 4, 2007 at 7:29 pminteresting stuff here…as for my sequences, they are like this:
i created a mini-segment in it’s own sequence that is comprised of 4 video layers. i put this mini (as a sequence) in the main timeline. of course, from within the main timeline i can’t just throw a filter on the mini segment, since it will then automatically upon up that mini-segments’ native sequence. i suppose i could then apply the broadcast filter to all 4 layers, and all clips, within that native sequence? or, is it best to render that mini-segment, from it’s native sequence, as it’s own separate QT file to then put into the main sequence? as a QT, i could then also just put the Broadcast filter on from within the main sequence before rendering out the whole thing as a final QT.
but, then i start thinking i will have a QT of a QT at certain places within this larger segment (does that make sense?), which SEEMS like it would be doubly-compressed files. am i nuts, or is that what would be happening…(or both?)
thanks again!
mh
-
J. Tad newberry
August 4, 2007 at 7:49 pmwell, i found that from within the main segment timeline, i could just drag the broadcast filter to the embedded sequence (the mini-segment) and it “appeared” to have been applied. rendered out a test, but same thing: had to still render this QT when putting it back on the timeline. also, went to the sequence of the mini-segment and see that the Broadcast filter was only applied to layer 1 rather than all layers and all clips…
anyway, for now, moving on as i need to still shorten this whole show before onlining…
thanks again!
mh
-
Jeremy Garchow
August 4, 2007 at 10:48 pm[mortimer heathcliff] “also, forgot to aks in the previous flood on this topic, is there a way to batch process Exporting a QT Movie??”
With your sequence selected, File > Batch Export
When the batch export window pops up you’ll see a button at the bottom to choose settings and other options.
-
J. Tad newberry
August 5, 2007 at 10:11 ammaybe i should try “recompress all frames” in the QT window?
thanks again!
mh
-
J. Tad newberry
August 5, 2007 at 4:57 pmwell i’ve tried several things…but i still get a nice 5-6 minute 5-6GB file…that still needs about 30 minutes of rendering when i put it on the timeline…and this is even after FCP alerts me that the clip i’m dropping onto the sequence is of a different format, would i like to change the sequence settings to match the clip? i say yes…but it still needs rendering….
well, at this point, i guess i’ll still do the single files of each of my four segments, then also do the render of them on the timeline, SAVING the render files and taking all that to the post house. seems like it SHOULD work with no additional rendering before going to tape. (keyword: SEEMS).
of course, i will also take my drive with ALL the clips for the show just in case Murphy’s Law persists. this seems to be an interesting subject that many might be having mysterious troubles with, please post if you have any more suggestions here. thanks again to all.
thanks again!
mh
-
Kiwi
September 7, 2007 at 6:37 amI had the same problem – “export->Quicktime Movie” was giving me 1920 X 1080 instead of 1280 X 1080 for a DVCPRO HD 1080 60i sequence. And checking “recompress all frames” in the export window did indeed fix the problem, so that’s another work-around, just took a little longer …
Reply to this Discussion! Login or Sign Up