Premiere Pro CC crashes upon XML import from Final Cut 7 Export

Hello all,
I have recently tried to import a FCP7 XML into Premiere Pro CC 2014, and a few seconds after initiating the export Premiere Pro crashes. Any solution to this???
I Exported on a Mac Tower running FCP7 and then imported the XML on a PC Running the latest Premiere CC v8.1. Could that be a problem in itself?
Also I'm considering a workaround where I move the FCP7 to FCPX, generate the XML then try importing again. Worth a shot?
Also trying this strictly on an Apple computer to import and save before moving to my main PC station. Thoughts?
The sequence I'm trying to import is fairly massive too, not sure if this is why, but it is mult-layered, both in audio and video and is running about an hour in length with several other blocks of video files after that, probably running up to 2 hrs. This should not be a problem, right?
Help! It would be greatly appreciated to get out of the clutches of final cut finally.

I am having the same issue.
Your best bet is to logon to Adobe website and go to customer support. If you chat with someone they can go on your computer and trash all your preferences. Your computer will be stable again. It worked great for me, but I just imported an XML from Resolve and it is crashing the system again.
Good luck.

Similar Messages

Premiere Pro CC Crashes upon video import

I just installed CC on my computer. All the programs seem to be running fine, with the exception of Premiere Pro. Whenever I go to import video (either by dragging video over or importing) the program crashes. I went to 'Event Viewer>Windows>Logs>Application' to try and see what the problem was. I could really use someone's help as one of the biggest factors in purchasing CC was for Premiere Pro. This is was the log said:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: MXF_SDK_GenericContainer_DV_4.4.33_vs10.dll, version: 4.4.33.0, time stamp: 0x534d774c
Exception code: 0xc0000005
Fault offset: 0x00000000000116a0
Faulting process id: 0x1a70
Faulting application start time: 0x01d0577d4ee51810
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\MXF_SDK_GenericContainer_DV_4.4.33_vs10.dll
Report Id: a92de2cb-c370-11e4-b686-ecf4bb1e4a36

I am having the same issue.
Your best bet is to logon to Adobe website and go to customer support. If you chat with someone they can go on your computer and trash all your preferences. Your computer will be stable again. It worked great for me, but I just imported an XML from Resolve and it is crashing the system again.
Good luck.

Import from Final Cut Pro not working correctly

I have a very simple project in FCP. (Ver 6) It is a HD clip that is about 5 min long with 7 chapter markers.
I exported the project as an XML file and imported that into Premiere Pro empty project.
I wind up with two assets, a .mov with same name as the .mov in FCP and a sequence with the same named sequence in FCP.
Right clicking on the .mov and selecting "New sequence from clip" creates a new sequence with the .mov on the timeline.
There are no markers.
Right clicking on the sequence asset and selecting "New sequence from clip" creates another sequence with the same name and the .mov on the timeline.
The markers are inside the .mov and audio tracks, not up on the top ruler line where markers appear when manually adding markers.
The keystrokes to move to markers do not work.
The "Clear all Markers" function is greyed out , like it is when no markers exist.
If a "Dynamic link to Encore is performed, there is no markers in Encore.
If you enter chapter markers manually and look at the project file (an XML file) you will see indexes with the chapter points , durations and names as children named "Markers" with attribute"ObjectID='22'.under "//PremiereData"
Following , in sequential order, are subsequent objects "Markers", ObjectID='23" through "ObjectID=n
However, if you look at the project file after importing a FCP project, this same function occurs, except that it is "Markers" "ObjectID=30 with the indexes and marker data 31 through n (further down in the file). This area is empty when adding the markers manually in Premiere Pro.
FYI , the project file is littered with the word "Marker" and "Markers" throughout the file, only their attributes make any node unique.
I am at 99.9 &% finished with a VB program to create / modify nodes, values and attributes, except that the XML date changes format at the node named "//WorkspaceSettings" so I am not able to edit values to make a file that will not crash when opening.
I would very much like the import from Final Cut Pro to work, or someone explain how to work with the nodes under "//WorkspaceSettings"
Thank millions for a solution.

It's a 2007 iMac with 2.4 GHz Intel Core 2 Duo. I had been using Final Cut Pro without any problems right until I upgraded to Yosemite. I'm hoping that upgrading to Yosemite doesn't mean I can't continue using Final Cut Pro - that would be extremely frustrating.

Importing XML files from Final Cut

Keep trying to import XML file from Final Cut into Adobe Premiere CC, and I get the Error Message:
The project appears to be damaged, it cannot be opened.
Not sure what I'm doing wrong.

I have an FCP generated XML file that I'm trying to open in Premiere CS6.0.2. It fails on import. The sequence of messages is below.
Premiere Pro has encountered an error.
/Volumes/BuildDisk/builds/slightlybuilt/shared/adobe/MediaCore/Backend/Make/Mac/../../Src/ Component/AudioPanProcessor.cpp-214
Next I get a window saying "File Import Failure"
/users/josh/library/caches/temporaryitems/ollombo.pproj
Error message: The project could not be loaded, it may be damaged or contain outdated elements.
When I check the translation results, it says: Generator Item (Outline Text) not translated for clip , Transparent Video used as a placeholder
Help, I need to get this project open!

Premiere Pro CC crashing upon export

Anyone having issues with Premiere Pro CC crashing when you try and export off the timeline? I have a 2010 MBP running OS X. Seems to be an intermittent problem but crashes about 50% of the time. I've got the latest version of Creative Cloud too.

I am on Windows, but have a few saved Mac discussions that may help (or, may not... but free to read) Some 10.9.3 links
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
Mac & nVidia Driver http://forums.adobe.com/thread/1075592
-and http://www.nvidia.com/object/mac-driver-archive.html
Troubleshooting guide for Mac freeze
http://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-mac.html
http://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-ef fects.html
External speakers stop playback http://forums.adobe.com/thread/1370072?tstart=0
OSX Crash http://helpx.adobe.com/creative-cloud/kb/ame-premiere-crash-launch-export.html

Audio popping between clips with timeline imported from final cut xml file

So i imported a final cut timeline that was synced with pluraleyes into adobe and between all the cuts there is an audible popping noise. I've tried using audio cross fade but it seems to make it worse. How can I fix this??

If anyone else has this problem - you fix it by making sure you pan the audio to the center, not left or right.

Premiere Pro CC crashes when browsing/importing video files.

I've got a trial version of Premiere Pro CC installed today, running on a late 2012 iMac.
No problems during splash screen or project startup, but when I try browsing for a video file in the import box or attempt to drag and drop files from my local disk, a Premiere prompt says a fatal error has occured and shuts down. I haven't experienced this problem on other PCs/Macs.
The files I've tried all run smoothly when opened by VLC or QuickTime. Extensions tried so far: .avi, .mkv, .3ggp.
NVIDIA GeForce GTX 680MX 2048 MB
3,2 GHz Intel Core i5
8 GB 1600 MHz DDR3
OS X 10.8.5 (12F45)
If there are codec issues, trial version limitations or these types of files are not supported I would hope PP would say so instead of crashing abruptly?
Any help appreciated, I'm not an editing guru.

Premiere does not have trial limitations.
If vlc plays the files is no garantee Premiere will.
Premiere does not support mkv.
Premiere only supports dv-avi and 3gp.

Premiere Pro CC crashes when I import CS6 project files

I recently upgraded to CC, but every time I try to import my project file from Premiere Pro CS6 into Premiere Pro CC it crashes, or stops working if you like.
This is very irritating as I wanted to make use of the SpeedGrade workflow in the CC packaged between Premiere Pro CC.
My project file is no longer than 1 minute, however is does contain After Effects CS6 compositions, could this possible cause the crash? I have tried to import without these but it still stops working for some reasons.
Also I have no idea where to find the error log for crashes on Adobe software.

I have experienced similar crashes and timeline playback failure when importing a CS6 project into CC or CC 2014. I had to rebuild two projects by hand before I realized it was a bug in CC converting the CS6 project files to CC project files. I don't think this has been addressed yet, but I have had better luck starting projects from scratch in CC, not cross-converting a CS6 project. Although I'm still experiencing issues with multicam projects in CC 2014.
Curious to hear others chime in on this.

Adobe Premiere Pro CC Crashing Upon Startup

Hello, this is my first post on this forum and I am doing this because I have a reoccurring problem:
Whenever I start up Premiere Pro CC, it does one of two things: 1. Stops responding at the startup screen and I am forced to close it. or 2. It gets to the "New Project" screen, and when I click anything, it stops responding and I am forced to close the program.
- I have a Windows 8 Intel Core i7-3630GM CPU @2.4GHz. 8 GB RAM. x64-based processor.
- I installed Premiere Pro CC (newest version directly from the Creative Cloud application) from the Creative Cloud (which I purchased within the past week).
- I tried reinstalling the program three times, each time trying to save it to a different location, and the problem still persists.
- The error message just says "Abobe Premiere Pro has stopped working" and then just suggests the normal pointless "If Windows finds a solution to the problem...etc"
I would like to recieve help for this problem because I need to use this software very soon in the future.
Thank You!

1st, Go to http://forums.adobe.com/community/premiere and, in the area just under Ask a Question, type in
crash on startup
You may now read previous discussions on this subject... be sure to click the See More Results at the bottom of the initial, short list if the initial list does not answer your question
2nd, What is your exact brand/model graphics adapter (ATI or nVidia or ???)
What is your exact graphics adapter driver version?
Have you gone to the vendor web site to check for a newer driver?
For Windows, do NOT rely on Windows Update to have current driver information
-you need to go direct to the vendor web site and check updates for yourself
ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

Premiere pro cc crashing ONLY when opening from file shortcut

When I'm opening PP from the taskbar, it works fine and I am happy girl.
But then I'm not so happy if I'm trying to open the files from my desktop, because PP crashes as soon as it opens
I'm with windows 8 and premiere pro 7.2 cc
I've already replaced my preferences file, so please don't tell me to try that again please!
THANK! anja <3

Try deleting the Desktop shortcut and creating a new one.

Premiere Pro CC crash on video import

updated drivers, etc.
Started crashing after I installed Audition. Worked before that
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: Adobe Premiere Pro.exe
P2: 8.1.0.81
P3: 5426694c
P4: devenum.dll
P5: 6.6.7600.16385
P6: 4a5bded7
P7: c0000005
P8: 00000000000016a0
P9:
P10:
Analysis symbol:
Rechecking for solution: 0
Report Id: f428a246-8499-11e4-8645-8086f2dc13cd
Report Status: 1

I am unsure of the origin of the source file.
It is video from a conference shot from two different camera angles...not sure what applications created the file, or if mp4 was the native saved format from the camera(s) that shot it.
Like I said though, it worked fine (both camera angle files), was editable...I saved the first clip I needed down, went to lunch while Audition downloaded because I needed to remove some background noise, came back and get nothing but crashes.
The only specifics I have for the file are as follows.
3.21gb file
43:48 length
1920x1080
data rate: 10361kbps
total bitrate 10521kbps
29 frames per second
159kbps audio bit rate
stereo
44kHx
no encryption

Premiere Pro CC crash when dragging media from project window

I have had so many problems with CC (2014) since the 8.1 update. The latest problem is interacting with media in the project window. In any version of PP (7, 8.0.1, 8.1), when I attempt to drag media from the project window to the timeline i get the "Premiere Pro CC has encountered a serious error..." crash. I am running a Macbook Pro i7, 16gb of ram, Nvidia GT 750m graphics card, on OSX Yosemite. I have tried clearing the media cache and clearing settings on startup with alt+shift. I have been using 8.0.1 because of previous problems with serious ui lag on 8.1. I have had more problems with PP in the last 3 months, than in the previous 7 years I've used it.

Hi Huzzahbeard,
Just out of curiosity. How is it that your software is hindered by a plugin in Chrome. I .... I have no words. This solved my problem and thats great except. Push Bullet is the issue! No, what is premiere even doing with my browser that push bullet would cause problems.
I looked at our bug database and there is no real "reason" listed as to why this particular issue occurs (and it does affect a couple of our other non-video applications—InDesign and Illustrator, as well).
A common troubleshooting step for when things go wrong with an application is to remove any recently installed applications or plug-ins. As I understand it, certain applications share resources which can affect each other. Since Chrome extensions are created using Javascript, I assume that is the area of conflict.
Thanks,
Kevin

Premiere Pro CC Crashes upon opening a Project file

Get error: [/sirreel64/releases/2013.02/shared/adobe/MediaCore/MediaLayer/ImporterHost/Make/Mac/../. ./Src/Audio/AudioWaveform.cpp-173]
Then it crashes.
I have tried: Re-Installing, clearing the Cache, changing my region to USA (Computer), turning off various features, changing scratch disk
I'm using a 2012 iMac, Mavericks, up to date.
Have been using CS5, 5.5, & 6 on this system just fine.
My system:
3.1 GHz Intel Core i5
16GB 1333 MHz RAM
AMD Radeon HD 6970M 1024 MB
I'm a professional editor and very tech saavy, save the 'did you turn it off and on again' responses please.
Thread 22 Crashed:: Dispatch queue: com.apple.root.low-priority
0   libsystem_kernel.dylib                  0x00007fff8c456a52 __semwait_signal_nocancel + 10
1   libsystem_c.dylib                       0x00007fff8f9b4a7c nanosleep$NOCANCEL + 189
2   libsystem_c.dylib                       0x00007fff8f9de5fe usleep$NOCANCEL + 54
3   libsystem_c.dylib                       0x00007fff8fa0abc4 abort + 135
4   com.adobe.Frontend.framework            0x000000010006728a FE::ApplicationErrorManager::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) const + 202
5   com.adobe.dvacore.framework             0x00000001002a1962 dvacore::config::ThrowError(dvacore::config::ErrorLevel, char const*, unsigned int, int, bool, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&, dvacore::config::ReplacementValue const&) + 226
6   com.adobe.ImporterHost.framework          0x0000000104df6879 ML::AudioWaveform::SetSingleChannel(int) + 185
7   com.adobe.Backend.framework             0x0000000101c41a3d BE::Media::SyncToMediaInfo(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 7069
8   com.adobe.Backend.framework             0x0000000101c48880 BE::Media::SetMediaInfo(ASL::InterfaceRef<BE::IMediaInfo, BE::IMediaInfo>, dvamediatypes::FrameRate const&, bool) + 4288
9   com.adobe.Backend.framework             0x0000000101c4734a BE::Media::RelinkMediaInfo() + 1466
10 com.adobe.Backend.framework             0x0000000101c468ea non-virtual thunk to BE::Media::CheckMediaInfoRelink(bool) + 58
11 com.adobe.Backend.framework             0x0000000101c4fb86 BE::(anonymous namespace)::HandleOneRelinkRequest() + 326
12 com.adobe.dvacore.framework             0x0000000100326642 dvacore::threads::(anonymous namespace)::SubExecutorImpl::CallFunctionWithExceptionHandler(boost::function<void ()> const&) + 66
13 com.adobe.dvacore.framework             0x00000001003250a8 dvacore::threads::(anonymous namespace)::SubExecutorImpl::OnThreadExecute(boost::shared_ptr<dvacore::threads::(anonymo us namespace)::SubExecutorImpl> const&) + 232
14 com.adobe.dvacore.framework             0x00000001003383d4 dvacore::threads::WrapExecuteTopLevelFunction(void*) + 68
15 libdispatch.dylib                       0x00007fff91cef2ad _dispatch_client_callout + 8
16 libdispatch.dylib                       0x00007fff91cf109e _dispatch_root_queue_drain + 326
17 libdispatch.dylib                       0x00007fff91cf2193 _dispatch_worker_thread2 + 40
18 libsystem_pthread.dylib                 0x00007fff8c43bef8 _pthread_wqthread + 314
19 libsystem_pthread.dylib                 0x00007fff8c43efb9 start_wqthread + 13

BUt that's a different error.
I am getting this one aswell.
[c:\ppro772\releases\2013.10\shared\adobe\mediacore\mediafoundation\api\inc
Please fix it.
I really want my Premiere Pro to work :\

10.9.2 + Premiere Pro CC Crashing upon open!

So I am using a mid-2011 iMac and these errors keep popping up as I try to open Premiere Pro CC. I should not have updated to 10.9.2 at all
all this has done is give me errors, I have uninstalled and reinstalled many times and I just got Photoshop to work. If anyone has any fixes please
help!
Process:         Adobe Premiere Pro CC [4144]
Path:            /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
Identifier:      com.adobe.AdobePremierePro
Version:         7.2.1 (7.2.1)
Code Type:       X86-64 (Native)
Parent Process: launchd [228]
Responsible:     Adobe Premiere Pro CC [4144]
User ID:         501
Date/Time:       2014-03-16 21:45:26.561 -0500
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Anonymous UUID: D6748548-1F7B-A473-BD6D-826698978E6B
Sleep/Wake UUID: 68EB9A37-7C3C-468B-B49D-F598CC0979CB
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
    __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/MacOS/Adobe Premiere Pro CC
Application Specific Information:
/Library/Frameworks/CUDA.framework/Versions/A/CUDA
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation                0x00007fff91d27c5f CFStringGetLength + 15
1   com.apple.CoreFoundation                0x00007fff91d3ae58 CFStringCompare + 24
2   CUDA                                    0x00000001164d1fff GetNVDADriverModelString + 287
3   CUDA                                    0x00000001164d5823 cuda_driver_initializer + 99
4   dyld                                    0x00007fff6a3dfc2e ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) + 268
5   dyld                                    0x00007fff6a3dfdba ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
6   dyld                                    0x00007fff6a3dca62 ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 308
7   dyld                                    0x00007fff6a3dc9eb ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&, unsigned int, ImageLoader::InitializerTimingList&) + 189
8   dyld                                    0x00007fff6a3dc8f6 ImageLoader::runInitializers(ImageLoader::LinkContext const&, ImageLoader::InitializerTimingList&) + 54
9   dyld                                    0x00007fff6a3d2b0e dyld::runInitializers(ImageLoader*) + 89
10 dyld                                    0x00007fff6a3d97cf dlopen + 538
11 libdyld.dylib                           0x00007fff95a867ee dlopen + 59
12 com.adobe.GPUFoundation.framework          0x000000010912ef18 cuInit + 40
13 com.adobe.GPUFoundation.framework          0x00000001090e26fd GF::Initialize(bool, void*, void*) + 333
14 com.adobe.DisplaySurface.framework          0x0000000110c29126 DS::ExecuteGPUSnifferAsync() + 22
15 com.adobe.Mezzanine.framework           0x0000000105ddbe70 MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 192
16 com.adobe.Mezzanine.framework           0x0000000105ddb3a4 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
17 com.adobe.Frontend.framework            0x00000001000a8557 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
18 com.adobe.Frontend.framework            0x00000001000a7768 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
19 com.adobe.Frontend.framework            0x00000001000c886d FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 237
20 com.adobe.Frontend.framework            0x00000001000cfa65 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
21 com.adobe.AdobePremierePro              0x00000001000018cc main + 524
22 com.adobe.AdobePremierePro              0x00000001000016b4 start + 52
=================================
Crash report trimmed down to essentials by moderator.

Hi JesseHunter,
Thanks for posting on Adobe forums.
Application Specific Information:
/Library/Frameworks/CUDA.framework/Versions/A/CUDA
Please check if you have any NVidia Graphics card installed on the iMac.
if not please Go To following location :
Computer> Main HD > Library > Frameworks
and delete or rename CUDA.framework
Please update if this works out.
Happy Editing,
Sandeep

Importing from Final Cut Pro-improving rendered quality

Is it possible to render an exported movie in FInal Cut so that it can be immediately written to the DVD rather than be rerendered/ compressed? FC allows you to create MPEG2, the same as iDVD or DVDs generally?
Failing that. my guess is that the export from FC should be with as little compression as possible (Animation, None, others ?). I have been quite disappointed with the end result quality in the burned disc seen on a TV, it doesn't look nearly as good as on the computer monitor. Perhaps this is a function of the limited resolution of TV/ versus the 720x480 DV. But I'm also getting color noise on black backgrounds, elements that I suspect are created by compression.

Hello,
Rendering and compression are two different beasts. If you are working in the DV format then you want to stay (render) in the DV format. Rendering to another format (HD, Animation, etc...) is not going to give you any more quality than what is already there: DV in this case. Compression takes your current format (DV) and turns it into an MPEG 2 (for most cases) for burning to a DVD. Keep in mind that 1-hour of DV is 13gigs while a DVD can only hold 4.7/4.3 gigs so the material must be compressed. Next, as you have surmised, these codecs were designed for SD Television display which has a much lower resolution than you computer monitor & also only displays one field at a time, alternating between two fields very quickly. The difference between interlacing fields and progressive scan. When editing in FC, you can hook a deck (or your camera) up to the computer and also send a signal via the analog outputs of the camera to a TV (I use an el cheapo 13" Philips but it serves my purposes). This allows you to have an idea of what the material will look like on a TV rather than the computer monitor.
FC will use Compressor to create the MPEG 2 files (compression) for a DVD. iDVD uses the same compression engine but does not give you control over the variables of the compression. However, iDVD cannot use an MPEG 2 file created by Compressor, iDVD wants to do it's own Compression. When exporting out of FC, you can either save the file as a reference file or as a self contained movie (using the same settings you captured with, DV in this case). You can drag either of these files to iDVD for compression/burning. The following is by stock answer on iDVD & quality:
Quality and iDVD- Quality is subjective; what one person finds as good another may not. Quality is also highly dependant upon input. In other words: quality in, quality out; garbage in, garbage out. It is helpful to have a basic understanding of what makes a DVD a DVD. When you record on mini-DV you are recording to an already compressed format. Arguably a very good compressed format but compressed nonetheless. This means information is being tossed at the point you are using the camcorder. iDVD, or any DVD authoring app on any computer, Windoze or Mac, compresses this material even further into the MPEG 2 format for playback via a tabletop DVD player. Now mini-DV has about 30 frames per second (NTSC). MPEG (in a very basic nutshell) takes a picture about twice every 30 frames and uses this as a reference frame and then only records the motion difference between that reference frame and the next time it creates a reference frame. So you go from 30 frames/second to TWO, with motion difference! This is how one hour of DV which is 13 gigs, can be compressed to fit onto one DVD. Two hours would be 26 gigs of DV compressed to one DVD! Hence the general quality difference between one-hour and two. And keep in mind that is compression will show artifacts that may have always been there but you didnt see until the other 28 frames where tossed out.
Having a basic understanding of what makes a DVD can help you make better DVDs. As example, if you see that your recordings have a lot of motion that is bad. Remember, when compress to DVD it only records the motion difference so you want to keep the camera steady and use slow controlled movements (pans & zooms). Quick pans or zooms or jerky movements are the bane of any MPEG compression scheme.
That is just one example. There are thousands more. Sometimes, merely recording to a different blank media yields better results. iDVD has a unique way of discovering bad RAM, so if you have added any RAM lately, this may affect your quality. The list goes on. /End my standard reply.
Black also poses difficulties for compression (fades to and from black, black with no motion and so on) since the Compression is looking for motion. The first step in "fixing" this is understanding it. What are your black backgrounds? Can

Premiere Pro CC crashes upon XML import from Final Cut 7 Export

Similar Messages

Maybe you are looking for