Tutorials for AVID Studio, Pinnacle, HFX, proDAD    .

AVID Studio, Pinnacle Studio, HFX, proDAD, Boris FX Tutorials, Tips & Tricks

Minimize
25 Latest Tutorials

DV FX RSS Flux Subscribe to Articles update by email - All Tutorials - Search - Tutorials by Category / Author / Month

Export Failure and other crashes in Studio

Export Failure and other crashes in Studio By czmax - Last updated on Tuesday, January 17, 2012
1187 Views :: 4 Comments :: Article Rating (Total Votes: 7)
Category: Pinnacle Studio Tips & Tricks, Tutorials / General, AVID Studio Tips & Tricks, Tutorials / General  -  Previous tutorials
Published on Sunday, January 15, 2012
Created on Thursday, December 08, 2011 3:30 PM
 

If you encounter an "Export Failure" when rendering your movie, you probably won't understand the content of the message shown by Studio. In the absence of this help from Studio, follow this tutorial created by an experienced user. You will find:

  • an explanation of the message and the location of the error;
  • possible causes and ways to fix them.
Step 1 : Location of the Export Failure

Occasionally Studio gives you the "Export Failure" message after stopping or freezing during rendering.

Most often this export failure is due to the fact that Studio has detected that some segment of the timeline was incorrect.

 

The error message begins with a number that indicates exactly where Studio has encountered the problem.

The error of Pinnacle Studio

This number is the number of frames created from the beginning of the video. On this screen shot you see 164/496 which means that the project includes 496 frames and the error occurred at the 164th frame.
This number can be converted into hours / minutes / seconds / frames.

Consider an example with an error at the 26,384th frame:

  • For a video created at 25 frames per second, divide 26384 by 25 to get 1055.36: this means there are 1055 seconds, (25 X 1055 = 26375 frames, then take 26,384 minus 26,375 to get 9 frames;
  • Then divide 1055 by 60 to get 17.58 which gives you 17 minutes or 1020 seconds and 35 seconds (1055 minus 1020)

Finally 26,384 frames = 17 minutes, 35 seconds, and 9 frames.

Step 2 : Possible causes and how to fix them

Next you need to position the cursor at the point of the failure, using the preview window, to identify exactly what is the problem sequence:

The timeline zoomed up
  • If it's a scene change, zoom in on the timeline to look for a missing frame that could create a blank space, if you find one, delete the space by extending the scene before or after the blank space;
  • Another possibility that I have run in to is the case of two transitions, one right after the other;
  • Pay special attention to scenes that only last a single frame, Studio doesn't like that;
  • We can't rule out having a transition that doesn't work for the two scenes, try changing the transition;
  • Sometimes it can be due to using Studio for a long time without re-booting the PC. Remedy: reboot the PC, and restart Studio;
  • It can also be due to an issue with the auxiliary files where Studio can not find the right file. The remedy is to go to the File menu and delete the auxiliary files, Studio will recreate them as needed.

In the absence of information on the precise point of the failure, one can proceed by dichotomy: make a copy of the last half of the project (use Save as with a different name) and then render that half. If that half does not cause the failure then render the other half to look for the failure there. Continue in this way, each time splitting the video in half and rendering one section to narrow down the area causing the error to a very specific location.

Other known causes :

  • Studio still does not like mixing segments that use different frame rates per second;
  • Mp3 audio is a standard that has led to many different codecs, some of which do not correspond exactly to the Mp3 standard (music found on the web for example). Studio may not understand them. Wav PCM (Pulse Code Modulation) is much more easily accepted because the audio file is not compressed;
  • There are also video codecs and extensions that Studio doesn't like and those can cause a crash or other failure.
  • It's possible that a new codec may have been created after the creation of Studio so it will not be able to recognize them. Transcoding with appropriate software can solve the problem;
  • Another type of crash can be caused by damage to Studio itself. The fix is to do a repair install of the software. Insert the installation CD or DVD and start the installation process. Select the Repair option for Studio to check that the files are not corrupt. If the problem persists, try uninstalling Studio, then run the RegDelete file (available in our download page) 2 times. Run registry cleaner and repair software if you have it and then reinstall Studio. Normally the current projects are not removed, but a backup project in a separate folder is still a good idea;
  • A complete PC crash may be caused by overheating of the CPU and Windows has stopped to protect the PC; keep the inside of the case clean and make sure there's good air flow.
  • The render stopping without a message with the progress bar looking black and blue, or Studio crashing without an error message, can be caused by a bad sector on the hard drive itself: Studio needs to store all the changes and calculations for the project and then stores all the video edit info used in the rendering and also needs some other Windows files to work. So do not be stingy with the space available on the HDD system, tens of GB of more space may be needed for a video over an hour long.
  • Auxiliary files are located on C drive by default. Move them on another drive, for this please read step 2 in our tutorial "Auxiliary files management with Pinnacle Studio" as well as tutorial "Optimize your computer before you start editing".

If you have other examples with their remedies, please let us know in the comments section to further enhance this tutorial.

{Thanks to Loosecannon for the fine tuning}

Rate this tutorial
Share/Save this article




Bookmark and Share
Comments
Joe By # Joe @ Monday, January 16, 2012 3:53 PM
Hello,
My system is Windows 7-x64 and Pinnacle Studio 15.
Recently I encountered the problem "stopping or freezing during rendering" but
without the "Export Failure" message.
I am using Pinnacle Studio since V.10 and it was the first time that the rendering process has stopped.
I went through all proposals as explained in your tutorial but could not solve the problem.
In the meantime I found the reason for the stops.
Here is what happened and what I did:
A few weeks ago I changed my system HDD.
I installed a 256GB SSD (Solid State Drive) and reinstalled the whole Windows 7 and all other programs.
Everything went fine and no problems appeared.
But then after I finished a new Pinnacle video project and started the "Make Movie Process" I got the "stopping or freezing during rendering".
It stopped randomly at different places along the timeline.
Then I went through your tutorial as mentioned above without success.
Since stops never happened before the time I changed the system-drive I thought the SSD could be the reason.
I placed the folder for the auxiliary files on my second physical drive D:\ which is a "normal" 500GB HDD.
I was very surprised to see that amazingly the malfunction was gone and the rendering process went through as usual.
I have no explanation why the SSD is to blame for the stop problem because it should work in the same way as the "normal" HDD.
As far as I know, there is an important difference:
The AHCI Modus (Advanced Host Controller Interface) is activated.
This means, that e.g. "hot swapping" and "native command queuing" are active.
In addition to that the AHCI driver provides "Trim Command" and "Garbage Collection" which is important for the SDD functionality.
Maybe somebody can give this information to the programmers of Pinnacle Studio. Those experts should have an explanation.
Regards, Joe

Graham By # Graham @ Tuesday, January 17, 2012 4:21 AM
Thank you,I tried this and found a particular clip it didn't like.I just opened a new project re-did the clip and then replaced the problem clip altogether.Next time I will try taking a closer look as you mentioned.

Déclic Vidéo FX By # Déclic Vidéo FX @ Tuesday, January 17, 2012 7:52 PM
@ Joe: Auxiliary files should always be put somewhere else than C drive...
It is explained in the tutorial "Auxiliary files management with Pinnacle Studio" (beginning of Step 2) as well as in tutorial "Optimize your computer before you start editing"

Thanks for sending this reminder, might be useful to other people, therefore I have slightly modified the tutorial accordingly, with Czmax permission.

DV FX

videoman By # videoman @ Tuesday, January 17, 2012 10:25 PM
Yes, I have suffered the same problem and discovered the location of the problem by reading the error message.
In most cases the problem was caused by a transition or an effect. One I could not find until I stretched the timeline at the error point and found a 1 frame gap.
One frame is hard (impossible) to see when viewing the whole project so close scrutiny is warranted.
Videoman


WARNING: this comment section only relates to the current article. All technical and/or general questions regarding software detailled in our article *MUST* be asked through various forums; we won't even answer to comments which do not comply to this basic rule, and we might even moderate it. Thanks in advance for your comprehension.

Comments support tags : [quote]Text[/quote], [b]Text[/b], [i]Text[/i], [u]Text[/u], [url]www.sample.com[/url] or [url=www.sample.com]Link name[/url].
You can use these tags to highlight your text or insert a link in your comment.

Name or surname (required) - publicly visible on the website

Email (required)

Website

CAPTCHA image
Enter the code shown above:

  



Home | AVID Studio | Pinnacle Studio | Hollywood FX | proDAD | Boris | Links/Liens | Download/Téléchargements | Contact
 Copyright 2004 by Déclic Vidéo FX