What settings when exporting from motion?

What settings do I use when exporting scrolling credits from Motion.

Exporting to where?
If you are going back to FCP, save the Motion project and import that. It can be treated exactly the same way you would a video clip.

Similar Messages

Trouble Exporting from Motion

I've been having problems exporting my Motion Projects out of Motion. I've been working on a 30sec spot 100% animated (no 3D), the project is set for DVDCPRO HD 1080i60 and I just cant get it out properly.
Fades that worked in the project are missing in the exported file, pictures somehow become corrupted/distorted in the exported file, and I have also noticed the top bar in leopard often turns partially or completely black after export, and motion crashes soon afterwards.
When exporting from motion I notice my processors aren't being used much. I have tired dropping the motion project directly into compressor but I get even more errors and strange green distortion on the exported file.
It takes about an hour and a half to export the 30 sec spot under maximum settings, (motion blur, frame blending, and all that) and I have an ATI RadeonX1900 with 512 VRAM.
Is my computer to underpowered, or my graphics card, or both? Suggestions please?

Hope you get some better advice soon. Meantime, try to copy and then paste some layers into independent projects, render them out as self-contained movies. See what happens to them. What you want to try to do is separate out pieces you can pre-render and then bring back in as movies. This eliminates tons of layers processing and might clear up some issues. Also helps you isolate issues with possibly corrupt media.
Can't help you on the Leopard stuff. We've had dozens of Motion/leopard conflicts posted over the last several months.
bogiesan

What is the best settings to use in the export manager when exporting from Aperture 3.5 to Photoshop cc. tiff? psd? 16bit? dpi?

What are the best settings to use in the export manager when exporting from Aperture 3.5 to Photoshop cc for editing?
Should I use tiff or psd?
8bit or 16bit?
How many dpi?

That will depend on the photometric resolution of your originals. For jpegs it would be a waste of space to convert them to a higher resolution than 8bit, but if your images actually have already more than 8bit, you will want to preserve this quality. Then he 16bit format will help to prevent color clipping.
Both tiff and psd will preserve the lossless workflow. With Photoshop as external editor I would use he psd format for better support of layers and transparency, e.g., when you want to create watermark files.
The dpi will only matter, when you export the file for printing.

I have a problem. When exporting from PDF to PPTX error "unable to process the document in the module Save As file is not created." What to do?

I have a problem. When exporting from PDF to PPTX error "unable to process the document in the module Save As file is not created." What to do?
Windows 7 64
PC

everything works on a laptop (

When exporting from Photos, the panel for naming the file no longer shows up. Why and how do I change so I can name the file what I want?

When exporting from Photos, the panel for naming the file no longer shows up. Why and how do I change so I can name the file what I want?

You don't need to maintain all versions of the upgrade chain, but many of us do in case we need to work on a legacy file. If you want to rmove a version, though, ti should be done BEFORE installing the later one. Just reinstall CS5 and things should get back to normal.

"Milky" or faint results when exporting from AE to FCP

(Accidently posted to FCP Express forum-- whoops!)
I've been using After Effects for years now to create graphics for our Avid projects, and the QT results have always been great. Clean, sharp moving graphics. But now that I've been using FCP, I'm not exactly happy when I export my Quicktime graphics from After Effects to FCP: they're extremely "milky" and faint/fuzzy when viewed from FCP over an NTSC monitor. I have tried various codecs when exporting: DV/NTSC, Animation, Component-- all with the same results.
I have read other threads with similar comments (even the thread that mentioned "milky" results when exporting from FCP to AE and back) but none of the suggestions/remarks helped in my situation.
I'm sure others have experienced this. Any suggestions?
Settings:
After Effects comp: NTSC/DV Preset (720 x 480, lower field, etc.)
Export Codecs: DV/DVCPro-NTSC, Animation, Component (all with the same milky results)
Final Cut: Sequence Preset "DV/NTSC 48 Khz"
Also tried using, as one thread suggested, the "Uncompressed 8 bit NTSC 48 Khz" preset and no difference
Side note: I'm using Final Cut in this system outputting to both DV video and Betacam video, using an Aja card for the Beta. Both DV and Beta results look the same (going straight thru the decks-to-NTSC monitor) and they both use the same "DV/NTSC 48 Khz" sequence preset-- except where I changed it to "Uncompressed 8 bit". If I use Animation or Component as my export codec from AE, naturally, I have to render to play the clip back in the timeline. It even looks milky or faint on the FCP source/viewer screens!
And yes, I've checked the NTSC monitor-- a Sony Trinitron PVM-20 monitor. And I've looked at the results on other monitors and even regular TVs. Milky/faint video all around.
Any suggestions would be appreciated!!

Is this on files with alpha channels? Have you tried
changing the Alpha type? Are you having
pre-multiplication problems?
No, they don't have alpha channels. But I did try, when rendering with Animation, changing the colors to "Millions +" which was something I read on another thread. Same results.
Basically, these are After Effects projects with simple backgrounds and moving text. I'm not doing any layering with alpha channels-- like lower third supers.
However, whenever I use Apple programs like LiveType or Motion, the NTSC results look like they did while I was creating the projects with these programs before I rendered them.

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5

My new iMac with FCPX crashes when rendering complex templates and crashes when exporting with Motion 5
Using Motion 5.0.6 and Final Cut Pro X 10.0.7 on New iMac (December 2012) Mountain Lion,
Intel Core i7 quad-core a 3,4GHz, Turbo Boost fino a 3,9GHz
32GB di SDRAM DDR3 a 1600MHz - 4 x 8GB
Fusion Drive da 3TB
NVIDIA GeForce GTX 680MX 2GB GDDR5
During the rendering of complex FCPX mac crashes and I have to force a restart.
I also happens when I try to export movies with Motion 5.
Does anyone have the same problem with my new iMac?

Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
First, empty the Trash.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Triple-click anywhere in the line below to select it, then drag or copy it — do not type — into the Terminal window:
find . $TMPDIR.. $ -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 -o -acl $ 2> /dev/null | wc -l
Press return. The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
The output of this command, on a line directly below what you entered, will be a number such as "35." Please post it in a reply.

Large PDF file sizes when exporting from InDesign

Hi,
I was wondering if anyone knew why some PDF file sizes are so large when exporting from ID.
I create black and white user manuals with ID CS3. We post these online, so I try to get the file size down as much as possible.
There is only one .psd image in each manual. The content does not have any photographs, just Illustrator .eps diagrams and line drawings. I am trying to figure out why some PDF file sizes are so large.
Also, why the file sizes are so different.
For example, I have one ID document that is 3MB.
Exporting it at the smallest file size, the PDF file comes out at 2MB.
Then I have another ID document that is 10MB.
Exporting to PDF is 2MB (the same size as the smaller ID document)... this one has many more .eps's in it and a lot more pages.
Then I have another one that the ID size is 8MB and the PDF is 6MBwhy is this one so much larger than the 10MB ID document?
Any ideas on why this is happening and/or how I can reduce the file size.
I've tried adjusting the export compression and other settings but that didn't work.
I also tried to reduce them after the fact in Acrobat to see what would happen, but it doesn't reduce it all that much.
Thanks for any help,
Cathy

> Though, the sizes of the .eps's are only about 100K to 200K in size and they are linked, not embedded.
But they're embedded in the PDF.
> It's just strange though because our marketing department as an 80 page full color catalog that, when exported it is only 5MB. Their ID document uses many very large .tif files. So, I am leaning toward it being an .eps/.ai issue??
Issue implies there's something wrong, but I think this is just the way
it's supposed to work.
Line drawings, while usually fairly compact, cannot be lossy compressed.
The marketing department, though, may compress their very large TIFF
files as much as they like (with a corresponding loss of quality). It's
entirely possible to compress bitmaps to a smaller size than the
drawings those bitmaps were made from. You could test this yourself.
Just open a few of your EPS drawings in Photoshop, save as TIFF, place
in ID, and try various downsampling schemes. If you downsample enough,
you'll get the size of the PDF below a PDF that uses the same graphics
as line drawing EPS files. But you may have to downsample them beyond
recognition...
Kenneth Benson
Pegasus Type, Inc.
www.pegtype.com

IDVD Stops Responding when Exporting from iMovie

I'm using iDVD and iMovie (from iLife 06 and fully up to date) on a MacPro (also up to date on all software, MacOSX, Quicktime etc).
This proceedure has worked before several times but now results in a non-responding iDVD every time I try it, including an archive and re-install and a complete new install of OSX and all software on a new partition.
What I'm doing.....
[1] Recording a TV programme on EyeTV (410) and exporting it to iMovie - sucessful every time
[2] Edit the iMove project and add chapter markers and save project - no problem.
[3] Export to iDVD - iDVD shows exporting in progress and whilst this is still showing iDVD launches
[4] iDVD starts playing the music from a std theme for a few seconds and then stops. Then resumes the music after resizing the window and then after a couple of more seconds freezes. From the Dock I can see that iMove and iDVD are "not responding"
[5] Eventually iMovie completes it's "export" and then starts responding normally. iDVD continues to show as non responding although I can move the window around the screen. I have to force quit iDVD to get it to close down.
I have tried:
Re-exporting the project from EyeTV
Deleting the preferences files for iMove and iDVD
Deleting the iLife suite and re-installing
Doing an OSX archive and re-install
Installing a fresh OSX (10.4.8) on a different drive and installing fresh software
Running Disk Utility - clean bill of health on both drives
Repaired permissions
The Console reports the following errors when exporting from iMove to iDVD:
===== Tuesday, 24 October 2006 22:56:45 Europe/London =====
[KN,10:57:08:852]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 0
[KN,10:57:08:852]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 1
[KN,10:57:11:968]/SourceCache/iDVD/iDVD-791/./PBProjects/iDVD/RemoteControlContr oller.m:348 : switchTheme: mIsPlaying = 1
2006-10-24 22:57:53.394 iDVD[424] NSExceptionHandler has recorded the following exception:
NSInvalidArgumentException -- * -[NSCFArray addObject:]: attempt to insert nil
Stack trace: 0x954ee243 0x9264f2cb 0x9264f110 0x925dd399 0x000df708 0x000df806 0x00215e6d 0x002167ef 0x0021470b 0x001a0b4f 0x00184105 0x92627d78 0x92627222 0x92626fa9 0x92626811 0x92621ae0 0x00166dc7 0x9261e861 0x925f2ef1 0x925f2d1b 0x9151d6c5 0x9151d5f6 0x9151d4c2 0x92dda340 0x9325c63d 0x9325c056 0x93255ddb 0x93249d2f 0x0000ad5d 0x0000ab36 0x0000aa51 0x00000002
Result - problem persists. I'm at a loss as what to do next. Any suggestions greatfully received.

Yes, tried that when I deleted the preferences. Disk Utility did not report any permissions needed repairing.
What really mystifies me is that this export to iDVD did work once and I expected it to resume once I'd created a fresh OSX install along with all the iLife apps on a new partition, but it remained the same!
Perhaps there is some sort of other software conflict going on? I have Adobe CS2, MS Office, Toast and FMP installed all are latest editions. On the utilities front I have installed Stuffit Deluxe, Internet Cleanup, Contour USB controller for video editing and a LogicTech wireless trackball. Again all the drivers are the latest releases.
Does anyone know if there are any preferences associated with the other not responding applications listed in my other post that I could try the delete-reboot trick on?

Mac Projector Crashes When exported From Flash CS5.5

Something strange that i noticed, when i had exported a presentation for a Mac,
on a 64 bit windows 7 using flash cs5.5.
the applicaton gets the paths of a few swfs from an XML file
and loads them one after the other.. there is a small bit of interactivity.
.. tested this projecter on various versions of MAC, it crashes often,crashes earlier if i switch applications. what follows here is a part of a report that was generated on an OS X 10.7.3,
works fine if the projector is exported from flash cs5.
i need it to work when exported from flash cs5.5.. any suggestions on what i need to change in my application so that it works when exported from flash cs5.5?
Your help would be appreciated Thanks in Advance
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000500d98eb
VM Regions Near 0x500d98eb:
Memory tag=240         000000000ebd0000-000000000ec90000 [ 768K] ---/rwx SM=NUL
-->
__TEXT 0000000070000000-0000000070142000 [ 1288K] r-x/rwx SM=COW /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
Application Specific Information:
objc_msgSend() selector name: orderOut:
objc[9434]: garbage collection is OFF
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libobjc.A.dylib                 0x92115d47 objc_msgSend + 23
1   com.macromedia.Flash Player.app 0x00467d96 main + 240950
2   com.macromedia.Flash Player.app 0x0047efda main + 335738
3   com.macromedia.Flash Player.app 0x002feae2 0x1000 + 3136226
4   com.macromedia.Flash Player.app 0x0033a77b 0x1000 + 3381115
5   com.macromedia.Flash Player.app 0x00462718 main + 218808
6   com.macromedia.Flash Player.app 0x004628b2 main + 219218
7   com.apple.CoreFoundation        0x98e0b3df __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
8   com.apple.CoreFoundation        0x98e0ad96 __CFRunLoopDoSources0 + 246
9   com.apple.CoreFoundation        0x98e34c68 __CFRunLoopRun + 1112
10 com.apple.CoreFoundation        0x98e3447c CFRunLoopRunSpecific + 332
11 com.apple.CoreFoundation        0x98e34328 CFRunLoopRunInMode + 120
12 com.apple.HIToolbox             0x9289117f RunCurrentEventLoopInMode + 318
13 com.apple.HIToolbox             0x928984e7 ReceiveNextEventCommon + 381
14 com.apple.HIToolbox             0x92898356 BlockUntilNextEventMatchingListInMode + 88
15 com.apple.AppKit                0x98fe8a9c _DPSNextEvent + 678
16 com.apple.AppKit                0x98fe8306 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
17 com.apple.AppKit                0x98fe4675 -[NSApplication run] + 911
18 com.apple.AppKit                0x99278261 NSApplicationMain + 1054
19 com.macromedia.Flash Player.app 0x000032a2 0x1000 + 8866
20 com.macromedia.Flash Player.app 0x000031c9 0x1000 + 8649
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib          0x97d3f90a kevent + 10
1   libdispatch.dylib               0x99a75c58 _dispatch_mgr_invoke + 969
2   libdispatch.dylib               0x99a746a7 _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
2   libsystem_c.dylib               0x9232482a pthread_cond_wait + 48
3   com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
4   com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
9   libsystem_c.dylib               0x9237c6de thread_start + 34
Thread 3:
0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
2   libsystem_c.dylib               0x9232482a pthread_cond_wait + 48
3   com.macromedia.Flash Player.app 0x003ff62f 0x1000 + 4187695
4   com.macromedia.Flash Player.app 0x0001a06c 0x1000 + 102508
5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
9   libsystem_c.dylib               0x9237c6de thread_start + 34
Thread 4:
0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
2   libsystem_c.dylib               0x9237cf7b pthread_cond_timedwait_relative_np + 47
3   com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
4   com.macromedia.Flash Player.app 0x001c58fe 0x1000 + 1853694
5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
9   libsystem_c.dylib               0x9237c6de thread_start + 34
Thread 5:
0   libsystem_kernel.dylib          0x97d3e83e __psynch_cvwait + 10
1   libsystem_c.dylib               0x9237ce78 _pthread_cond_wait + 914
2   libsystem_c.dylib               0x9237cf7b pthread_cond_timedwait_relative_np + 47
3   com.macromedia.Flash Player.app 0x003ff5f8 0x1000 + 4187640
4   com.macromedia.Flash Player.app 0x00305328 0x1000 + 3162920
5   com.macromedia.Flash Player.app 0x003ff70c 0x1000 + 4187916
6   com.macromedia.Flash Player.app 0x003ff73a 0x1000 + 4187962
7   com.macromedia.Flash Player.app 0x003ff847 0x1000 + 4188231
8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
9   libsystem_c.dylib               0x9237c6de thread_start + 34
Thread 6:: com.apple.audio.IOThread.client
0   libsystem_kernel.dylib          0x97d3cc22 mach_msg_trap + 10
1   libsystem_kernel.dylib          0x97d3c1f6 mach_msg + 70
2   com.apple.audio.CoreAudio       0x9cd8e9fe HALB_MachPort::SendMessageWithReply(unsigned int, unsigned int, unsigned long, unsigned long, mach_msg_header_t*, unsigned int) + 122
3   com.apple.audio.CoreAudio       0x9cd8ea6a HALB_MachPort::SendSimpleMessageWithSimpleReply(unsigned int, unsigned int, int, int&, unsigned int) + 60
4   com.apple.audio.CoreAudio       0x9cd86e5f HALC_ProxyIOContext::IOWorkLoop() + 1145
5   com.apple.audio.CoreAudio       0x9cd86926 HALC_ProxyIOContext::IOThreadEntry(void*) + 136
6   com.apple.audio.CoreAudio       0x9cd86898 __HALC_ProxyIOContext_block_invoke_6 + 20
7   com.apple.audio.CoreAudio       0x9cd8681d HALB_IOThread::Entry(void*) + 69
8   libsystem_c.dylib               0x92378ed9 _pthread_start + 335
9   libsystem_c.dylib               0x9237c6de thread_start + 34
Thread 7:
0   libsystem_kernel.dylib          0x97d3f02e __workq_kernreturn + 10
1   libsystem_c.dylib               0x9237accf _pthread_wqthread + 773
2   libsystem_c.dylib               0x9237c6fe start_wqthread + 30
Thread 8:
0   libsystem_kernel.dylib          0x97d3f02e __workq_kernreturn + 10
1   libsystem_c.dylib               0x9237accf _pthread_wqthread + 773
2   libsystem_c.dylib               0x9237c6fe start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00dbe0e0 ebx: 0x00dbe0e0 ecx: 0x99985548 edx: 0x500d98cb
edi: 0x0000036e esi: 0x00aad0e0 ebp: 0xbfffe4f8 esp: 0xbfffe488
ss: 0x00000023 efl: 0x00010202 eip: 0x92115d47   cs: 0x0000001b
ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
cr2: 0x500d98eb
Logical CPU: 1

Looks like it was a memory problem with the jvm.ini file.
Pumped it up to 256 and it works now.
Hope this helps anyone else in the future if they come across it.
Thanks.

"Milky" Results When Exporting from AE to FCP

I've been using After Effects for years now to create graphics for our Avid projects, which have always been great! Now that we're using FCP, I'm not exactly happy with the results of my QT graphics exported from After Effects to FCP: they're extremely "milky" and faint when viewed from FCP over an NTSC monitor. I have tried various codecs when exporting: DV/NTSC, Animation, Component-- all with the same results.
I have read other threads with similar comments (even the thread that mentioned "milky" results when exporting from FCP to AE and back) but none of the suggestions/remarks helped in my situation.
I'm sure others have experienced this. Any suggestions?
Settings:
After Effects comp: NTSC/DV Preset (720 x 480, lower field, etc.)
Export Codecs: DV/DVCPro-NTSC, Animation, Component (same milky results)
Final Cut: Sequence Preset DV/NTSC 48 Khz
Also tried using, as one thread suggested, the "Uncompressed 8 bit NTSC 48 Khz" preset and nothing better
Side note: I'm using Final Cut in this system with both DV video and Betacam, using an Aja card. Both DV and Beta results look the same (going straight thru the decks-to-NTSC monitor).
And yes, I've checked the NTSC monitor-- a Sony Trinitron PVM-20 monitor. And I've looked at the results on other monitors and even regular TVs. Milky faint video all around.
Any suggestions would be appreciated!!

You might want to post this in the FCP forum next door; this for Final Cut Express

Formatting of text fields when exporting from InDesign to Acrobat Pro

How does one preserve the formatting of a text field when exporting from InDesign CS6 to Acrobat Pro? It loses both the font and the alignment formatting in the PDF.

Use a font that allows embedding/ check the font embedding settings in the PDF output settings.
Mylenium

Can you have a PDF fit on the viewer's screen automatically when exporting from InDesign CS4?

Can you have a PDF fit on the viewer's screen automatically when exporting from InDesign CS4?

If you were to upgrade to InDesign CS5 or CS5.5 and if you exported as Adobe PDF (Interactive), you could set the View settings for Page Layout and Zoom.
While, as Jongware points out, its possible for individual users to override that option (Preferences > Page Display > Default Layout and Zoom), the number who will actually do that is actually very tiny.

Filename when exporting from ReportViewerBean

I'm using Crystal Reports for Eclipse 2.0 in a desktop application and ReportViewerBean is used for previewing reports. The export-dialog have several file formats and they all work fine but one annoying thing is that the filename is blank, so one have to write the filename/filextension manually before exporting to file.
Is there a way in the code to specify what filename a report should get when exporting?
I'm probably missing something here...
I've searched through the forums and code examples but have not found anything about this.
Thanks in advance
// Uhlen

To be clear, are you looking to have the Save As field in the export dialog box populated with a report name when you export the report?
When exporting from the viewer it isn't possible to do this, however if you export directly using the SDK, you can set the report name and path to whatever you like and automatically export to that location.

Can't open quicktime movie that I exported from Motion 5 and can't import to FCP

Can't open quicktime movie that I exported from Motion 5 and can't import to FCP 7.
I exported (with current settings) from Motion 5 now i can't view my movie with QT Player an FCP
won't recognize it.
That's the message I get ?
I'm running Mac OSX but still on FCP 7 (upgrading to FCP X is NOT an option)
Thanks a lot for any sugestions
luxbud

Thanks TOny
i think it was just a problem during the export. i tried a second time and it just worked fine

What settings when exporting from motion?

Similar Messages

Maybe you are looking for