FCP quicktime conversion export problem

issue exporting still image instead of video
FCP quicktime conversion export problem
within the last 2 weeks i have exported from FCP studio 7.0.3 as quicktime conversion, the settings are:
export as QuickTime Conversion:
> Options> quality> set to Best>
Standard Video Compression Settings
Compression Type: H.264
Motion:
Frame Rate: Current fps
Key Frames: Every 24 frames
check Frame Reordering
Compressor:
Quality: Best
Encodeing: Best (Multi-pass)
Data Rate:
Automatic
Filter… none
Size>
Dimensions:
NTSC 720x486 16:9
>ok
Sound: (don't change anything)
Format: Integer (Little Endian)
Sample rate: 48.000kHz
Sample size: 16-bit
Channels: (L R)
>Export
the results i get a odd. - the video exports fine, except for the beginning titles, instead a still frame image from somewhere else in the video occupies that intro, until the first transition- in this case- dip to white, then the rest of the video is fine. the portion of the beginning that does not show are composed of: livetype text credits in V2 - in which i have done a manual opacity fade up and down - so the livetype text fades in, over matte color solid in V1. in the exported video -i do not see any of this, all i see is a seemingly random still from somewhere else in the video. i can however hear the audio as it is supposed be.
cant figure out why this is happening. anybody know?
i think the livetype files are 1920 x 1080.
my FCP sequence is 720 p
this has only recently started happening and doesn't seem to be consistent.
im wondering if it has to do with the live type files, or the white solid?…
or the conversion settings above?

Alistair
Earlybird is exporting H264 ... the Key Frames setting is determining the GOP length. This value should really be determined based on the complexity of the video, to my understanding, the actual frame rate has no bearing on it. If you have very complex fast moving content then a low Key Frame rate is advisable to ensure good image quality (although it will adversely affect the filesize) whereas if you have slow moving or static content (like an interview subject) then a higher Key Frame rate will still produce a good image but at a smaler filesize. The default of 24 should be pretty much fine as a catchall starting point.
Earlybird
Corrupted render files (and render references) can be a pain because FCP will use those files and references in place of the original media when building the export. And so it should as it does't want to waste time re-rendering sections that are apparently already rendered. Unfortuantely, as noted, if the render file has gone bad and/or starts referencing the wrong media then you'll get these wierd flashes of completely unexpeced and unwanted footage showing up where it shouldn't be. When you trash those files then QT / FCP will just go back and re-reference the original media ... so it's usually a worthwhile step to take just in case thats the problem. The worse case scenario is that it only that doesn't work and you spend some time unecessarily re-rendering.
As to why these files go bad? That I don't know. Why do Preferences get corrupted? That I don't know either but it definitely happens :-(
Cheers
Andy

Similar Messages

Fcp quicktime conversion export colour problem

Since upgrading to Snow Leopard, i have noticed that whenever i want to export a file using Quicktime Conversion from Final Cut Pro 6, the output file has lost its colour depth and seems flat.
For example, i have a DV-PAL timeline and want to export a mov file using QT Conversion and the DV-PAL setting, the file's colour is different to fcp.
What could cause such a problem? i never encountered such a problem running on an older system.
Please help!

i have tried checking and unchecking 'Enable Final Cut Studio color compatibility', and i do not see a change. i have even tried opening the file using the old Quicktime player, but both the new Quicktime x player and the old one look identical.
i appreciate your help!

FCP7 Quicktime Conversion Export Resetting

Hi,
I'm trying to export a 46 minute HD project from FCP 7, which is due to TX on national TV in 4 days time.
I'm trying to export as the following:
Pro res 422
Quicktime Conversion
1920x1080
6 channels of audio
25p
49Khv 16bit Linear PCM
However, the Quicktime conversion export keeps reaching 100%, and then resets straight back to either 0 or a different random percentage. Why is this? It's been going for 5/6 hours...

This is FCPX forum. Try FCP Studio

KNOWN PROBLEM BUT NO SOLVING: FCE CRASHES ON QUICKTIME CONVERSION EXPORT

Hi to all,
i'm an italian new user. I already use FCP on my Mac Pro 2007,and i purchased FCE for my new MacBook 2008 3GB Ram.
I use Snow Leopard for both machines. FCE is installed only on MacBook. The issue is:
When i put ANYTHING on timeline (effect,clips of ALL formatsetc) indipendently from Sequence presets,FINALCUT EXPRESS CRASHES IMMEDIATLY WHEN I TRY TO EXPORT TO "QUICKTIME CONVERSION". No messages,no report,nothing.
I searched and read many pages of this forum,i found a similar thread where the suggestions were the erase of preferences in Libray and reinstalling. I DID THAT but FCE crashes again.
I'd like to resolve the problem on this machine,because i will use FCE on this computer.
Follow, there is a sample video of my problem,i captured it for this thread. I hope will help you to understand exactly i want to repair:
http://www.zshare.net/video/658799979072b569/
FCE CRASH.mov - 34.38MB
Thanks in advance
Lamberto from Italy
Message was edited by: LamProds,Inc
Message was edited by: LamProds,Inc
Message was edited by: LamProds,Inc
Message was edited by: LamProds,Inc

Tom,
This is an excellent tip. I really learnt something I wasn't aware of. FCE always seemed to render anyway but it takes longer if you did not render first. But you are right. The manual mentions it as well.
Anyway, it does not explain really why, with Quicktime X installed, I and others experience FCE crashes. Before with Leopard , FCE really never crashed.
Contrary to what I mentioned, I still experience crashes, also after full rendering. Strangely enough, it does not happen all the time. It seems difficult to reproduce the circumstances when FCE crashes on export. Any suggestions?
Jan

Final Cut Pro 5.1.4 crashes when using QuickTime conversion export

Our copy of Final Cut Pro 5.1.4 has started to crash when exporting using QuickTime Conversion. It gets about 66% complete, then dumps out. I have updated FCP using Software Update and QT to the latest version. Any ideas why this happening? Pro Kit 4.5 installed. QuickTime Pro 7.4.5
My previous post had the wrong version of FCP. Dyslexia sets in.

Erik:
quite often during render I get the error messages "The specific file is in use by another application"
Check this Apple doc:
http://docs.info.apple.com/article.html?artnum=302790
I think that was solved with 10.4.10.
About the crash problem, you would post the system configuration of that computer.
Hope that helps !
Alberto

FCP quicktime "iphone "export diff then quicktime "export for iphone web"??

so what i dont get, is when i export out of quicktime using "export for web" and i choose the "iphone" 900 kbit option, i get 480X270 beautiful true widescreen clips. But when I export using quicktime conversion in final cut pro 6 and i choose" iphone"....i get 480X360. Why does this happen? I want true widescreen, just like everything i get from itunes.....not this 360 size (which i know is the phones screen res, but who cares)?

Alistair
Earlybird is exporting H264 ... the Key Frames setting is determining the GOP length. This value should really be determined based on the complexity of the video, to my understanding, the actual frame rate has no bearing on it. If you have very complex fast moving content then a low Key Frame rate is advisable to ensure good image quality (although it will adversely affect the filesize) whereas if you have slow moving or static content (like an interview subject) then a higher Key Frame rate will still produce a good image but at a smaler filesize. The default of 24 should be pretty much fine as a catchall starting point.
Earlybird
Corrupted render files (and render references) can be a pain because FCP will use those files and references in place of the original media when building the export. And so it should as it does't want to waste time re-rendering sections that are apparently already rendered. Unfortuantely, as noted, if the render file has gone bad and/or starts referencing the wrong media then you'll get these wierd flashes of completely unexpeced and unwanted footage showing up where it shouldn't be. When you trash those files then QT / FCP will just go back and re-reference the original media ... so it's usually a worthwhile step to take just in case thats the problem. The worse case scenario is that it only that doesn't work and you spend some time unecessarily re-rendering.
As to why these files go bad? That I don't know. Why do Preferences get corrupted? That I don't know either but it definitely happens :-(
Cheers
Andy

Can you make a custom quicktime conversion export be your default?

When I go to export a quicktime conversion, I change the perameters to a custom setting for my need. Next time I go back into quicktime conversion, it goes back to the FCP defaults and I have to set my custom settings all over again.
Is there a way to create a custom export in quicktime conversion AND MAKE THAT the new default for quicktime conversion?
Alternatively, is there a quicker way to always get to my preferred export settings?
Thanks.

Why not just construct your favourite QT EXPORT setting in Compressor and then drag that setting into the box every time you want that type of movie?
K.

Instead of Compressor went Quicktime conversion (still problems)

Hi,
Thanx for all the suggestions regarding compressor. I didn't even consider doing Quicktime conversion for my DVDSP2. I did this last night with a two pass knowing it would take along time. After about 9 hours with some 18 to go ( the piece is 78 minutes) I got two errors, one from my system and one from FCP. FCP simply said "Out of memory". And what I'm assuming was from my system with the yellow triangle and exclamation point. "Your startup disk is nearly full. You need to delete some files."
What I don't understand about these is that I had "video" as my destination. This is a drive within my firewire drive that I had earmarked for just video and it has 23GB of memory in it which should be enough for this piece. Am I wrong?
I know that the other internal drive that I have just for graphics such as video does have a lot on it. A 200GB drive, it only has about 5GB left of memory. Can anyone enlighten me or point me to some articles.
Thank you in advance,
John

Your system drive functions as a virtual memory device. When the software you are running requires more memory that the physical ram you have, the hard disk pages in and out of RAM as needed. Since your spec doesn't mention ram below, I don't know how much you have, but once it filled, overflow started to fill up your system drive. If that becomes full, the system itself could shut down.
You can think of the disk as a pantry and shelf space and RAM as the kitchen table and counter top. When you run out of space for food preparation, you can put stuff back in the pantry or put partially prepared recipes on shelves for later completion.
And please don't call disk space MEMORY - it is not memory. Memory is RAM. Disk space is storage. Also, I should mention that the efficiency of your hard drive drops off SIGNIFICANTLY once it gets over 90% full.
make sense?
Patrick

QuickTime Conversion Exporting HDV

Hi,
The camera I used was a Sony HDV 1080i60 and my movie is about 10 minutes in length. Just a simple video with fade in and fade outs with audio.
It seems that when I convert by exporting to QuickTime Movie, there is no issue. However, when exported through certain settings under QuickTime Conversion, the 'cross dissolve' effect does not seem to appear properly.
Can anybody suggest a standard setting for this?
Thank you.

Hi Muglho,
You should really use QT movie, same settings self-contained and not QT conversion as the latter causes further coompression to your video and possible loss of quality (HDV is an heavely compressed format).
gogi

QUICKIE - default settings for quicktime conversion export

Hi All...
Is it possible to set the default settings to still image when choosing export via quicktime conversion?
I do a lot of frame grabs and at present whenever i do an export via QT Conversion i have to change the default from movie to still image...can still image be set to the default and therefore be selected when QT Conversion is selected from export options?
I think that is comprehensive enough a question!
Thanks for any help or guidance..it will save a lot of mouse clicking if it is possible.
ta...Mike

Michael Grenadier wrote:
Here's what I do. Park on the frame I want to export. Mark In AND out, Make subclip...
Wow! I sometimes need to do a few frame grabs, and this is a great way to do it.
Good thinking.
there are a few other editors and often it is difficult to persuade them out of their comfort zones.
Gee and they still get work?
If I didn't get out of my "comfort zone" my style wouldn't change, I wouldn't be able to handle OS and suite updates, let alone move away from linear suites.
I understand that some people might want a quick and easy solution, a single button press, but this solution sounds like it isn't so hard to make editors run and hide.
If they do baulk and cry, I would suggest you find some new editors; cause they are never going to adapt and give your clients top quality stylish work.

QuickTime Player export problem

When I save in QuickTime Player (10.0) as Movie everything works fine, but when I select another format, I get an "Export Progress" window, but after that finishes there is no file.
The problem seems similar as reported in this 1 year old thread:
http://discussions.info.apple.com/message.jspa?messageID=10326043
which doesn't have a solution.
Any idea what is going on?

...no problem Michael.But the question exist.Because is not accetable that a professional sw like FCP has these type of problems....if you making an application like Compressor I not understand why the export module inside program itself has these(very evidents....) problems. Question: Final Cut Studio
stand alone has COMPRESSOR inside???
This is like rallenty problems. Everyone tell me :" use rallenty in motion..is very good " Rallenty in Motion has the same identical problems (es : strobing...) that are in FCP (IDENTICAL !!). I use this SW and partially all applications of FCS 2 until 3 months but I have find problems like "banding" that people that use FCP from many many time have never see...is possible this??
It's a great suite but these things are inaccetable...this is my opinion.
silvio bonomi

Strange QuickTime conversion audio problem

QuickTime on my G5 will no longer export Final Cut files properly as H.264 - the video is perfect, but the audio just stops after about 1'30.
This never used to happen. I have tried with FCP container files and with FCP self-contained files, and the problem is the same. It started before the QuickTime upgrade, but even after upgrading, it is still happening.
Yet when I moved the exact same FCP file over to my MacBook Pro, and tried an export with the same settings as I used on the G5, it worked fine.
I can also do this export fine on the G5 with software such as MPEG Streamclip - just not QuickTime.
What on earth could be wrong that QuickTime's audio is failing at 1'30?

I confirmed that it's either a QT 7.2 issue, or OS 10.4.10 issue (guess which I think is more likely :-)).
I moved the iMovie to my wife's macbook, who thankfully usually hits cancel when the software update screen appears so it was still on 7.1.6 and OS 10.4.9. The movie exported fine. Not a great test, since I was changing processor types, iMovie versions, and OS versions, but it did work. Then I upgraded her to 7.2 and 10.4.10 (in retrospect, should have just done 7.2 to only change one thing, oh well), did the exact same export procedure, and the audio was corrupted the exact way that my computer broke it.
So it's in one of those components for sure. I opened a bug, #5345205, for what it's worth. Hopefully they'll be able to replicate somehow and issue a fix. too bad there's no easy way to rollback an update.

Quicktime Conversion Export Takes Way Too Long

I am using FCE2.
I have a 28-minute project that I am trying to export to a quicktime movie. (h.264 640x480 29.97FPS)
Every time I export, it takes 6 hours to complete! When I play it back, the quality is bad. It skips like there are not enough FPS.
I have tried adjusting the compression, size, FPS everything...but it just doesn't come out right. I have the latest versions of quicktime pro, and FCE2.
Something is wrong. Isn't 6 hours way too long? My computer gets real hot and the fan is constantly on while it's crunching.
What do I need to change? Any suggestions?
Thanks

Ah I think I figured it out.
I did another test project with the same source DV file, but didn't do ANY editing to it.
It took 2 minutes to export a 70mb reference mov file from a 7 minute DV sequence.
Then I cropped & resized the sequence by changing parameters in the "motion" tab.
Then it took 20 minutes to export a much larger reference mov file from the same 7 minute DV sequence.
Then I clicked "render all" after selecting every render option in the drop-down menu.
Then it took less than 1 minute to export a 70mb reference mov file from the same 7 minute DV sequence.
So I guess I was having problems because I didn't render "everything", because I didn't select "FULL" on the drop-down menu for rendering. I thought only RED segments in the timeline needs to be rendered prior to export, but apparently the "FULL" render must be selected as well so that the entire timeline is nice and purple. (or some shade of blue)
Also, a cropped and resized video is very large in size (GB) if it is exported as a reference file only without prior rendering. * Can someone else confirm that this is the normal behavior in FCE? *
Oh well, lesson learned.. This movie is going to take a very long time to export, and result in a very large file. But I can't use it without cropping & resizing it!
Message was edited by: Yongwon Lee

QuickTime 7 export problem

I have just discovered that QuickTime 7.66. on a 2gHz core duo intel iMac and QuickTime 7.6.4 on a 1gHz DVI TiBook no longer export. Any attempt to export a movie immediately closes QuickTime.
The iMac is running 10.5.8 and the TiBook is on 10.4.11. They both used to export to whatever setting was selected. The only option that works is 'Sharing'.
Anybody know why QuickTime has lost the export function on two completely different computers?

Well I discovered the cause of my problem. It was entirely self-inflicted. I have a little app called Monolingual that gets rid of all the unwanted OSX language translations that take up so much space. Having saved a couple of G's I got all enthusiastic and moved onto to input methods and removed all the Far East options.
Then there is ANOTHER window for 'Architecture' listing Power PC G3 etc. Well, I couldn't stop now could I? Bin it all.
And voila, Quicktime was suddenly missing some its vitals. A costly (timewise) rebuild of both computers has brought everything back

Final Cut 7 CRASHES during Quicktime conversion export

Does anyone else have this problem. The error message says it might be the FLV plugin? It doesn't even het to the options window... just crashes.

I don't know if this will make too much of a difference, but if you can, try using Compressor. It's a bit slower and more clumsy than a direct QT conversion or Export, but it should do the trick. As a bonus, if anything does go wrong, Compressor might offer a more detailed error report.
Hope this helps!
Titan

FCP quicktime conversion export problem

Similar Messages

Maybe you are looking for