I am wondering why is it that every single time I tried exporting an AMA sequence to quicktime (sources are h264 and export settings are also h264) I keep getting this error message: "Exception: Movie export from procedures FAILED!, errorcode:4294965262". Hoping someone can share some lights on this for me.
Happy holidays y'all,
EDIT: I should mentionned that I am using MC6
How quickly into the export does it happen?
What if you take a small section to export?
Have you tried a video mixdown and then exporting that?
Broadcast & Post
Production Consultant / Trainer VET
T 07581 201248 | E email@example.com | W www.vet.co.uk |
Media Composer V8.2 Review Background Render
Follow me on Twitter Pat_H_VET
how long is the sequence? what are your exact export settings? what kind of storage are you using? what are your system specs? are you exporting to the same hard drive that contains AMA linked media?
Stop answering questions with questions. If any of the questions you have asked could be the cause of the fault then it would be useful for the thread to know how to rectify each one. Otherwise this thread is useless. Like many that try and find answers to things on this forum I have found this thread really pointless, I don't usually respond to these things but I felt I needed to after finding nothing that gives any answers at all.
An answer could be that you have first to export to QT movie or ref (after a transcode) and go from there to H264. The results will be much better.
Desktop Corsair RM750X/Asus P8Z68 Deluxe(Gen3)/i7 2600K@4.4/Corsair 32G DDR3/PNY Quadro 2000D(375.86)/Samsung 850 Pro SSD(OS) 256 GB/ 2x2TB WD RE4@RAID 0/LG BH16NS40/W7 Pro 64bit/Media Composer Software 8.8 with Symphony • PhraseFind • ScriptSync Option/2xHP 22'' Monitors/M-Audio AV30 Speakers.
Larry as long as I live I will remember you.
3 Heads Digital Media • Vienna Frames
paulgordon:Stop answering questions with questions. If any of the questions you have asked could be the cause of the fault then it would be useful for the thread to know how to rectify each one. Otherwise this thread is useless. Like many that try and find answers to things on this forum I have found this thread really pointless, I don't usually respond to these things but I felt I needed to after finding nothing that gives any answers at all.
Well, gee, Paul, thanks for participating. It's always nice to see a new face with a fresh perspective.
Perhaps if the original poster had answered any of the questions - which were aimed at narrowing down the cause of the problem - an answer would've been found. As it turns out they disappeared after one post. That happens sometimes.
"There is hardly anything in the world that some man cannot make a little worse and sell a little cheaper, and the people who only consider the price are this man's lawful prey." - John Ruskin (1819-1900)
Carl Amoscato | Freelance Film & Video Editor | London, UK
Perhaps if he'd have said he was outputting to the same drive then there'd have been the suggestion to go to another drive and see how that works.
Perhaps he'd done another search on google and found the answer, that's currently what I'm trying to do. I hope once I've found it i can remember my login details to come back and post the answer (that helped me)
Wow...you do realize this is a user-supported forum. None of us are paid, we spend our own time out here trying to help others where we can.
I'm sorry if you are bothered by the fact that in addition to my day job, I do not have time to provide you with all of the possible answers depending on your situation. We ask that users provide as much information as possible when they first post. We ask questions to narrow down the scope of what the issue might be. If I answered every question with ALL of the possible solutions, you'd be reading forever and I would be fired because I'd be spending all day on the forums.
If you're not finding help here, then I am sorry. But sometimes, you get better help when you ask (and converse) nicely.
I had this issue too! It seems when having this issue you will need to export to the disk your working off of. Not sure what's causing it or how to fix it. Good luck.
No responses from the original poster so not able to narrow down the issue or suggest any solutions that may help.
As stated with such a generic problem with so little information on what actually happened making blanket "try" this suggestions can often cause more issues. So we try and help posters define the issue more carefully so we can make the most accurate suggestions.
Exporting to the same disk you are working off isn't really relevant. The disk must have enough free space for the export. It must be a file system that supports the expected export size (so FAT32 is often an issue) but other than that exporting to a drive you are working off is normally ok if not a little slower as it is now busy doing readng and writing.
Was anyone able to find a solution to this issue? I'm currently unable to export any canon 5d footage on MC 7.0.4. All the files were linked via AMA and transcoded to DNx36. The AMA files are able to export fine but the transcoded DNx36 footage is yet to work I receive the same error as the original Poster.
My system is a late 2011 iMac i7 with 12gb ram running MC 7.0.4.
We have 10 systems that all crash (the export fails but MC does not crash out) during export. It often makes it about 10 minutes before crashing. We using same as source settings though, not H264 which I have found in the past to be trouble some with MC.
I just wanted to post that version 220.127.116.11 resolved some of these crashes but because of some other issues we have to stay on 7.0.4.
I do have a solution to the failed exports.
If we do an expert render on our sequences (rendering to a local thunderbolt drive) it exports without fail and very quickly I might add. However, unlike the initial post in this thread we are not using AMA. We are using all DNxHD36 24p on shared storage.
Trouble shooting ideas:
Please try rendering the sequence before exporting.
Be sure there is enough room on the export drive.
Be sure you have write permission the the export drive.
Hope this helps.
This is a rather old thread but I recently had the same problem. Very tedious.
This is how I resolved it: When rendering the sequence before export there was an unexpected error sign saying that some effects could not be rendered. I found the effect in question by narrowing down the selection using "Render in/out".
It turned out that a simple sound fade was the problem. After removing and re-adding the effect everything worked well again.
Hope that helps,
FWIW...Just wanted to pipe in here even though it's an old thread. i just ran across this issue (for three straight days). Turned out that the culprit in the sequences was a superimpose effect applied to a psd on my templates, on the track above a color matte built in the title tool. From those templates I built 80 sequences, doing a replace edit on each matte, changing it out for a matte of whatever color I wanted for the sequence. Almost all of those sequences crashed on export, with the dreaded 4294965262 error and about ten segmentation faults behind it. Then the program would lock up.
How I fixed it: Ended up replacing the psd texture file with jpegs and applying a new superimpose effect to each one. Solved it. Not sure if it had anything to do with the psd or not, appears to be more the superimpose effect, and it's worth noting that one other sequence had a similar issue with a slightly different "superimpose" placement.
© Copyright 2011 Avid Technology, Inc.
Site Map |
Find a Reseller