Error compiling file?!

Hello,
For the third time I tried now to render a Quicktime (photo jpg and also h264) but somewhere on the last frames it skips the render with the message "error compiling file" - unknown error...
Does anybody has any idea why and what to do ?
Thanks :)
pearl

AAMinistries which Adobe software or service is your inquiry in relation too? What are you currently attempting to accomplish?

Similar Messages

Error compiling JSP packages

Please help.
I have downloaded the J2EE package - Server, Tutorial, etc. I am trying to get a BASIC jsp page with a single class to compile, but haven't had any luck.
Server error message is:
org.apache.jasper.JasperException: Unable to compile class for JSP
No Java compiler was found to compile the generated source for the JSP.
This can usually be solved by copying manually $JAVA_HOME/lib/tools.jar from the JDK
to the common/lib directory of the Tomcat server, followed by a Tomcat restart.
If using an alternate Java compiler, please check its installation and access path.
     org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:127)
     org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:348)
     org.apache.jasper.compiler.Compiler.generateClass(Compiler.java:424)
     org.apache.jasper.compiler.Compiler.compile(Compiler.java:464)
     etc, etc, etc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The Server log shows:
[#|2004-04-20T15:13:27.286-0500|SEVERE|j2ee-appserver1.4|org.apache.jasper.compiler.Compiler|_ThreadID=12;|Env: Compile: javaFileName=/C:/Sun/AppServer/domains/domain1/generated/jsp/j2ee-modules/default-web-module-server//org/apache/jsp/ch06\ch06_jsp.java
classpath=C:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\default-web-module-server;/C:/Sun/AppServer/lib/install/applications/__xa/
cp=C:\Sun\AppServer\lib\commons-launcher.jar;C:\Sun\AppServer\jdk\lib\tools.jar;C:\Sun\AppServer\lib\admin-cli.jar;C:\Sun\AppServer\lib\appserv-admin.jar;C:\Sun\AppServer\lib\appserv-upgrade.jar;C:\Sun\AppServer\lib\appserv-ext.jar;C:\Sun\AppServer\lib\j2ee.jar;C:\Sun\AppServer\lib\appserv-cmp.jar;C:\Sun\AppServer\lib\appserv-jstl.jar;C:\Sun\AppServer\lib\j2ee-svc.jar;C:\Sun\AppServer\lib\commons-logging.jar;C:\Sun\AppServer\lib\activation.jar;C:\Sun\AppServer\lib\mail.jar;C:\Sun\AppServer\lib\jaxr-api.jar;C:\Sun\AppServer\lib\jaxr-impl.jar;C:\Sun\AppServer\lib\jax-qname.jar;C:\Sun\AppServer\lib\jaxrpc-api.jar;C:\Sun\AppServer\lib\jaxrpc-impl.jar;C:\Sun\AppServer\lib\relaxngDatatype.jar;C:\Sun\AppServer\lib\xsdlib.jar;C:\Sun\AppServer\lib\saaj-api.jar;C:\Sun\AppServer\lib\saaj-impl.jar;C:\Sun\AppServer\lib\appserv-rt.jar;C:\Sun\AppServer\lib\tools.jar;C:\Sun\AppServer\jdk/lib/tools.jar;C:\Sun\AppServer/lib/install/applications/jmsra/imqjmsra.jar;C:\Sun\AppServer\imq\lib/imq.jar;C:\Sun\AppServer\imq\lib/jaxm-api.jar;C:\Sun\AppServer\imq\lib/imqadmin.jar;C:\Sun\AppServer\imq\lib/imqutil.jar;C:\Sun\AppServer\imq\lib/fscontext.jar;C:\Sun\AppServer\imq\lib/providerutil.jar;C:\Sun\AppServer/lib/ant/lib/ant.jar;C:\Sun\AppServer/pointbase/lib/pbclient.jar;C:\Sun\AppServer/pointbase/lib/pbembedded.jar
cp=C:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\default-web-module-server
cp=C:\Sun\AppServer\lib\install\applications\__xa
extension dir=C:\Sun\AppServer\jdk/jre/lib/ext;C:\Sun\AppServer\domains\domain1/lib/ext
work dir=C:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\default-web-module-server
srcDir=C:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\default-web-module-server
include=org/apache/jsp/ch06/ch06_jsp.java
|#]
[#|2004-04-20T15:13:27.286-0500|SEVERE|j2ee-appserver1.4|org.apache.jasper.compiler.Compiler|_ThreadID=12;|Error compiling file: /C:/Sun/AppServer/domains/domain1/generated/jsp/j2ee-modules/default-web-module-server//org/apache/jsp/ch06\ch06_jsp.java     [javac] Compiling 1 source file
[javac] C:\Sun\AppServer\domains\domain1\generated\jsp\j2ee-modules\default-web-module-server\org\apache\jsp\ch06\ch06_jsp.java:6: package ch06a does not exist
[javac] import ch06a.ch06class; I have also tried "import ch06a.*" with the same results.
[javac] ^
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Autoexec.bat reads:
SET PATH=C:\Sun\AppServer\bin;C:\Sun\AppServer\jdk\bin;c:\Sun\AppServer\share\bin;c:\Sun\AppServer\jdk\jre\bin;
SET JAVA_HOME=c:\Sun\AppServer\jdk;
SET J2EE_HOME=C:\Sun\AppServer;
SET CLASSPATH=C:\Sun\AppServer\lib\j2ee.jar;c:\Sun\AppServer\jdk\lib\tools.jar;c:\Sun\AppServer\domains\domain1\lib\classes;
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I am developing the jsp in c:\Sun\AppServer\domains\domain1\docroot\ch06 (I know that I shouldn't, but I am trying anything at this point).
ch06 structure is
|-WEB-INF
|-classes
| |-ch06a
| |-ch06class.class
|-lib
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ch06.jsp:
<%@ page import="ch06a.*" %>
<HTML>
     </HEAD>
          <TITLE>Using a JavaBean</TITLE>
     <HEAD>
     <BODY>
          <H3>Using a JavaBean</H3>
          <% ch06class messager = new ch06class(); %>
          The message is: <%= messager.msg() %>
     </BODY>
</HTML>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ch06class.java:
package ch06a;
public class ch06class{
     public ch06class(){
     public String msg(){
          return "Hello from JSP!";
Please let me know if I can supply anymore information.
Thanks

Make sure have the latest version of the application server. The previous release had a bug as described in this thread:
http://forum.java.sun.com/thread.jsp?forum=136&thread=473280
Here is a reply from that thread from one of the Web container engineers:
The error message about the missing Java compiler is misleading, and is being caused by a bug in the way compilation error messages are being propagated.
This problem has been fixed in the latest Appserver 8.0 PE release.
I think your JSP fails to compile because of an error in your JSP. Your appserver log should contain the real compilation error. Can you check?
BTW, the date example describe in this chapter does contain a class file:
http://java.sun.com/j2ee/1.4/docs/tutorial/doc/JSPIntro2.html#wp84418

Formatting Failed: Compiler File Error

Hello...
Yesterday I got my crossgrade disks from Apple, so I upgraded my G4 Powerbook with the full Studio Pro upgrade, then made sure I had all current patches.
When I opened up one of my DVD Studio Pro projects and clicked Burn, It failed with a dailog box that said "Formatting failed, Building was not successful, See log" so I looked at the log and it said in red "Compiler File Error"
This project worked fine before I upgraded... So, for grins, I started from scratch and rebuilt the project and reimported the assets. Now I had just recompressed the video/audio with the new compressor as well... Anyway, same result. Also, when it fails, the OS-X window pops up that you normally get once you insert a blank DVD and you can choose an app or hit ignore.
Can't figure this out... Any help would be greatly appreciated.
Dave
Powerbook G4 Mac OS X (10.4.3)

Once I upgraded, I recompressed the video (its about 14 min, and uses Dolby, not AIFF)... When I opened DVD Studio Pro, it prompted me that assets had changed, I said ok, then tried to burn and go the error. I then tried deleting the PAR folder, no help. So, I just closed the project, hit NEW and recreated the project (it was rather simple) and then tried to burn... Same error.
I burned this same DVD two days ago under the old pre-universal version and it worked fine. I only recompressed because I heard that the new version performed much better.
Sorta lost on this one... I don't see any reason why it shouldnt work. The log only says the one line and gives no other help.

LabVIEW 6.0.2 Compund Arithmetic function in XOR mode Inverted generates Compiler error when file saved

I am posting this as a problem for NI to look at.
I am using the Compund Arithmetic function in XOR mode Inverted with 5 inputs. File is also set up in reentrant mode. When I attempt to save the file I get the following error:
Compiler error. Report this problem to National Instruments Tech Support.
int inv mode=0x40000
Advertising Section:
Alliance Member
William Simmons
Simmons Software Engineering, Inc.
714 Germantown Pkwy Ste 5-341
Cordova, TN 38018
(901) 679-3513
[email protected]
LabVIEW, TestStand, Automated Test
environments, On-Site, Off-Site
Attachments:
NXOR_error.vi ‏73 KB

XOR is a new addition to compound arithmetic node. LabVIEW developpers just overlooked the fact that the outpout could be inverted. The compiler fails to generate the proper code because the inversion is not expected.
Just do what the message says. Report the problem to NI Tech Support (and use a separate inverter node).
LabVIEW, C'est LabVIEW

Discover: error: The file /a.out was linked by an older link step. Please use the latest compiler to do the link.

Hi,
I have installed Solaris studio and wanted to use the memory analyzer from there. I am trying it on a sample program, but it returns the above error and does not instrument the executable. Could you please help me tracing where am I going wrong.
# which cc
/opt/SolarisStudio12.3-solaris-sparc-bin/solarisstudio12.3/bin/cc
# /opt/SolarisStudio12.3-solaris-sparc-bin/solarisstudio12.3/bin/cc -V
cc: Sun C 5.12 SunOS_sparc 2011/11/16
# cc -g -O2 test.c
# file a.out
a.out:          ELF 32-bit MSB executable SPARC32PLUS Version 1, V8+ Required, dynamically linked, not stripped
# ldd ./a.out
        libc.so.1 =>     /usr/lib/libc.so.1
        libm.so.2 =>     /usr/lib/libm.so.2
        /platform/SUNW,Sun-Blade-1500/lib/libc_psr.so.1
# /SolarisStudio12.3-solaris-sparc-bin/solarisstudio12.3/bin/discover -w - ./a.out
discover: error: The file /a.out was linked by an older link step. Please use the latest compiler to do the link.
Regards,
Vikkal

ok. Thanks for the info.
Could you check if a small test works on your system ?
You could use this test :
% cat a.c
#include <stdio.h>
#include <stdlib.h>
int main()
        int *x = (int*)malloc(100);
        printf("x[0]=%d\n", x[0]);
        return 0;
% cc a.c -g -xannotate
% discover -w - -o a.out.disc a.out
% ./a.out.disc
ERROR 1 (UMR): accessing uninitialized data "*x" at address 0x8090008 (4 bytes) on the heap at:
        main() + 0xc2 <a.c:8>
                 5:    {
                 6:     int *x = (int*)malloc(100);
                 7:
                 8:=>   printf("x[0]=%d\n", x[0]);
                 9:
                10:     return 0;
                11:    }
        _start() + 0x71
    was allocated at (100 bytes):
        main() + 0x5e <a.c:6>
                3:
                4:    int main()
                5:    {
                6:=>    int *x = (int*)malloc(100);
                7:
                8:      printf("x[0]=%d\n", x[0]);
                9:
        _start() + 0x71
x[0]=0
***************** Discover Memory Report *****************
1 allocation at 1 location left on the heap with a total size of 100 bytes
    LEAK 1: 1 allocation with total size of 100 bytes
        main() + 0x5e <a.c:6>
                3:
                4:    int main()
                5:    {
                6:=>    int *x = (int*)malloc(100);
                7:
                8:      printf("x[0]=%d\n", x[0]);
                9:
        _start() + 0x71
DISCOVER SUMMARY:
        unique errors   : 1 (1 total)
        unique warnings : 0 (0 total)

Flash limitations, Invisible Compiler Errors, swc files...

This question is for expert users of Flash CS4/CS5 and actionscript.   Please do not comment or offer suggestions if you have no experience with these errors or their causes.
===================================================
Question:
=======
Publishing an extremely complex file can sometimes result in a blank swf being created, and no compiler errors being shown even though some may exist.   Are there any suggested methods for dealing with this?
=======
Details:
=======
Those who have written flash files with large actionscript components will be familiar with needing to set the JAVA_TOOL_OPTIONS evinronment variable in order to prevent the Flash compiler from crashing due to memory limits. The majority of the files in question require this as a bare minimum in order to be compiled at all.
The project in question involves several main "launcher" components, in addition to hundreds of "modules". The modules themselves are being developed in a distributed manner by several programmers. Each module can be executed as a standalone swf, for testing and production purposes. Each module has a companion swc file which holds its assets and exports them. All of the modules make use of a shared custom code library that sits on top of actionscript.
The launcher program also uses the shared library code, and runs the modules (never more than one at a time, and clearing previously loaded ones before loading a new one) inside of itself. The launcher contains a reference file(the class names typed in an include file, referencing all of the available exported assets from the swcs) that makes all the necessary assets available to the modules, such that any module can be run at any time.
===========
The Error:
===========
Seemingly random in occurence, every now and then a file will "compile blank". Essentially, the compile time is very short, the swf pops up as a blank white box, and there is absolutely nothing listed in the "Compiler Errors" tab, nor in the output tab. Sometimes closing flash and relaunching it will bring the Compiler Error messages back, though usually not. More often opening the file on another computer in a different copy of flash and compiling it again will show the errors.   The original computer will still not show anything, but the other computer can be used to fix the error, and then the file will start reporting errors again properly.
However, sometimes, the file will "compile blank" on all computers, and all copies of flash. Then the only resort to find the hidden errors and fix them, is to comment out the entire file, and slowly uncomment out sections one at a time. In this manner, the area where the hidden errors are occuring can be determined, and the error found manually.
Obviously this is an extremely frustrating situation, but one that can be "worked around".
However, there are two more serious incarnations of this which cannot be as easily side stepped.
1.) Sometimes certain computers/copies of flash will "compile blank" a file that doesnt actually have errors in it. The same file will compile and work perfectly on one machine, and not on another.
2.) The most severe of all...The two more complex components compile fine in cs4, but always "compile blank" on cs5, no matter what. The module files all compile much faster on cs5 and work great. However, the shared code library and the launcher program cannot be compiled in cs5, though they compile fine in cs4.   Both compile blank every single time on cs5, with no errors reported.
--Just as a side note here are the compile times on two different types of computers, for cs4 and cs5, for the three types of compiled files:
=====================
CS4 Compile time averages:
=====================
Dual Core - Pentium 4:
        Module File = 1-4 minutes
        Shared Code Library = 10+ minutes
        Launcher Program = Unusable
6 Core AMD w 16 GBs of RAM:
         Module File = less than 10 seconds
         Shared Code Library = approx. 1 minute
         Launcher Program = 15-25 minutes
=====================
CS5 Compile time averages:
=====================
Dual Core - Pentium 4:
        Module File = less than 20 seconds
        Shared Code Library = 2-4 minutes
        Launcher Program = Compiles blank
6 Core AMD w 16 GBs of RAM:
         Module File = less than 10 seconds
         Shared Code Library = less than 30 seconds
         Launcher Program = Compiles blank
========================================
Summary:
========================================
1.) Large and complex files in cs4 or cs5 can sometimes false compile, showing a blank swf, and no errors.
2.) Large interlinked projects containing many swcs that can compile on cs4 always compile blank on cs5
The issues involved "appear" to deal with interlinked swcs and swfs, memory, and compiler messages.
The best solution i can think of would be some sort of verbose mode setting, where the cs4/cs5 compilers can be set to trace all the actions they are taking, either to a log file, or to the screen. Rather than simply giving a summary of the results, a real-time display of what is occuring might lead to the actual bugs/issues.
Eisley79

For the future people who come searching this forum and find my thread.
http://kb2.adobe.com/cps/405/kb405257.html
Above is a link to adobe's official version of admitting this situation exists(and its true for cs5 as well).
If you are reading this, and simply have a single large file that won't compile. Attempt their solutions suggested. Also, click the link in the comments by the user refering to a blog that helped him.
That will explain the JAVA_TOOL_OPTIONS memory issue (which you can find many explanations on google as well).
If however, you are working with a large number of separate swf's that load each other, and share assets and are getting the REAL problem, neither adobe's solutions, nor the JAVA_TOOL_OPTIONS will correct the problem for you. My best suggestion to you is, have one SWF launch the next one, and break your project into pieces. Whatever the parent SWF needed to have, can be either copied into all the children SWFs, or into several "brother" SWFs which share the loaded children SWFs, (and can actually be successfully compiled). Then as you move from brother to brother, they can be made to appear as if they were actually ONE file, loading the children, instead of several launching each other, and sharing the loading duties.
and as far as adobe is concerned, if i told you what i thought of you, i would get this post deleted...and myself banned.
Anyone considering doing Enterprise level projects in Flash, DONT. I wanted to use JAVA, but my company went with flash. I am stuck working around it constantly, and would have been better off coding foundation classes to mimic whatever functionality we needed from flash into java.
Maybe when actionscript 4 comes along, it will magically bring with it true object oriented programming, and Adobe will spend the time and money to make a real working compiler. Somehow i doubt it.

What is a Compiler File Error?

I'm getting this error message when I try to burn my DVD.
"Starting DVD Build ALLINTHEFAMILY...
Compiler File Error"
It happens right away. What's wrong?

I think there is a bug in DVDSP4 and Apple needs to address this ASAP. The workable fix is to delete the DVDSP4 preference files.
I was having the described problem, and I've seen numerous discussions of the issue on blogs and groups all over the net. In any case, when you have this "Compiler File Error" message, exit DVDSP, navigate to user->library->preferences->com.apple.dvdstudiopro.plist and toss that puppy in the trash. Empty the trash. Restart DVDSP and burn without further problems...at least until next time!
Hey APPLE! Wake up and fix this for us!!! Thank you!
In Service of Mankind,
-Ruth

How do you fix a "compiler file error" in DVD Studio Pro?

I've tried to burn a DVD from a project file in DVD Studio Pro a couple times now and get a "Compiler File Error" each time. What does it mean and how do I fix it?
Thanks.

where are you assests from? did you use compressor to create a mpeg2 and dolby audio file? did you export self contained and bring into compressor? or a reference movie? What were your orginal seq settings? More details.

Compiler File Error

I am unable to burn DVDs in DVDSP2. I get the same message each time: Compiler File Error. I have tried compressing as MPEG2, I have tried moving media to boot drive and I have tried re-loading Compressor and DVDSP and upgrading before opening. I have tried everything suggested here to solve this issue but have been unsuccessful so far. Any thoughts?

I used the "DVD: Best Quality 90 minutes" presets in Compressor (Dobly Digital Pro 2.0 and MPEG-2 2.6Mbps 2-pass). By "gaps in the timeline" do you mean the FCP timeline? If so, no, there is only one movie.
The project does not build at all. I click BURN, the INITIATE dialog box appears and closes immediately. The log then shows COMPILER FILE ERROR.

Continuous 'Compiler File Error'

I've tried to burn various projects recently and each time I am getting a 'Compiler File Error' message. Can anybody advise what I should do to get rid of this. It's a real pain!
Basically I have various projects which I'm unable to build it at all. Here's a run down on what's happening from the log...
Starting DVD Build...
Compiler File Error (in red)
Build Cancelled
Formatting Finished
Building was not successful. See log. (in yellow)
And there's nothing about this error message in the Help guide either.

I had the very same problem. I simply moved the DVD Studio Pro prefs file found in system library>prefrences to my desktop. DVDSP will automaticly create a new pref file. If it fixed the problem you can trash the old pref file. This worked for me.

Error creating files. Compilation failed... when publishing iOS app with AIR 3.1 and Flash 11.5.1

Hello, I'm running Windows 7. I'm using Flash 11.5.1 (that's CS5.5 updated once) and AIR 3.1 to make an iPhone app.
I can export the app perfectly fine with either Ctrl+Enter or F12.
I added all the required things with AIR for iOS settings, such as a p12 certificate and icon files.
I then hit publish. After I hit publish, I got this error:
Error creating files.
Compilation failed...
I tried dragging the window to see if there was anything hidden behind the elipses. What can I do to fix this problem?

note sure if I'm much help other than to CONFIRM it is working for me by using the sdk WITHOUT the compiler. Check out adobe's little note: "Note : Flex users will need to download the original AIR SDK without the new compiler."
I am using FB 4.7 with AIR 3.6 and seems to compile correctly for iOS.
Maybe try reinstalling flash builder?
I honestly don't know if the JRE has anything to do with it... I'm using 1.7 ....to see what JRE you're using, open the Java Control Panel (I right click my java orange icon and hit properties), select the Java tab, then hit "View..."

Compiler File Error - DVDSP4

I'm having a problem with DVDSP4 and burning DVDs.
I now receive a "Compiler File Error" when attempting to burn a DVD. This is the first time I've encountered this problem. It occurs before the burn process actually starts. Does anyone know what causes this, and if there is a known work-around?
Currently running OSX 10.4.7, DVDSP 4.03, on a G5...
Thanks in advance.
G5 Mac OS X (10.4.7)

Thanks for the help all! Sorry I didn't think of using the search. I browsed through the first 5 pages or so, and didn't find what I was looking for, but it never occured to me to actually search for it... d'oh!
At any rate, the Compiler error still occurs when I use the "Burn" feature, but I was able to Build & Format successfully. There was no preference file to delete (I'm assuming this is because none of the preferences have been changed, thus a seperate file was never created), but I did repair permissions, to no avail. I tried a reboot a number of times as well.
Thanks again, I'll keep searching to try and solve my problem.
G5 Mac OS X (10.4.7)

Help ! ever seen this in DVD Studio Pro : 'Compiler File Error' ?

Help !
This is a strange problem :
Evertime I try to burn a disc, it says :
Starting DVD Build DVD_
Compiler File Error
Build cancelled
Formatting finished.
Building was not successful. See log.
Now I tried several different projects and it does it on multiple computers.
Only explenation would be something I did in my DVD menu, or assets.
If I burn it on my powerbook though, it works perfectly....
Harry Potter was busy, so please help me, I'm getting desperate...
Have the latest update, the latest OS, en DVD Studio Pro 4.2

Welcome to the boards.
Take a look at the log as it is compiling and see where the compile stops/crashes. Also download MPEG streamclip and open up the last VOB in the build folder in MPEG Streamclip. (VOB ares here, you will have different VOBs of course and numbers but look at the last one that has something in it) http://dvdstepbystep.com/vts.php It will show you the last part was compiled properly so you can look at the asset in the DVD SP project.
Some things to look for
1.) Gaps in the timeline in the audio or video. In fact I just had this happen. The project compiled fine in an older version of DVD SP (4.03) BUT would crash out at 4.2. Turns out there was a gap I had missed (doh!) somehow and cleaning it up would then cure then problem.
2.) Did you make the audio AC3? What rates were the video encode? High rates can cause the compile errors.

DVD Studio Pro: Compiler File Error

Hi there,
I'm running DVD Studio Pro 4.2.1 on Mac OS X 10.5.8, and until now, I've been successfully burning DVD projects. But suddenly, when I try to burn a DVD, I keep getting a message stating that the "build failed" due to a "compiler file error." Any clue how to solve this? My sound file is a .ac3, and my video is a .m2v.
Thanks!

It could be a number of things. Generally, you should try renaming your m2v and then re-importing it and setting it into the track it is in. Also, try trashing the PAR files (check your preferences for the location of these) which get created when you import an asset.
Finally, try simply re-encoding the footage and going from there (add a new name for it too...)

Build Error Message "Compiler File Error"

Whenever i try to burn a DVD in DVD studio pro i get this error message:
"Starting DVD Build UNTITLED_DISC...
Compiler File Error
Build cancelled
Formatting finished.
Building was not successful. See log."
This occurs no matter how big my project is, how many files i use, or what format. I thought originally the video files i were using to burn were corrupted, but i have since tried many different video files and many different formats. This message continues to come up. I have even reinstalled DVD Studio Pro and nothing has changed.
I don't have any clue what's causing this message or how to fix it???
I WOULD REALLY APPRECIATE THE HELP! THANK YOU!

keentave wrote:
Thanks for the help. I figured out the problem or at least one of the causes. I deleted the update: user->library->preferences->com.apple.dvdstudiopro.plist and it fixed it.
That does not delete the update, it is deleting the preferences (which is one of the things always to do when things go nutso

Error compiling file?!

Similar Messages

Maybe you are looking for