Sort Order issue when exporting from DRM

The sort order hierarchy (Parent/Child) in DRM is correct, and appears in the right order. When the hierarchy gets exported, some of the nodes are out of order in HFM.
There are shared nodes in the hierarchy. There is a Custom Sort order that is set correctly for the hierarchy in DRM.There is also a Query that was created to export nodes that does not contain the word Shared.
Ex
DRM
Parent 1
Child 2700
Child 2701
Appears in HFM
Parent 1
Child 2701
Child 2700
The sort order is not correct in Smartview. Why would the nodes show correctly in DRM, but export out of order, and not show correctly in HFM?
Any suggestions or comments would be greatly appreciated.

Can you evaluate the DRM export results with the Hiearchy structure, also make sure the Default Hierarchy Sort on the Hierarchy has a value assigned to it, whether it is core or custom based on node ID, DRM should export nodes as they appear in DRM.

Similar Messages

Sort order switches when changing from List to Thumbnail View

I can't seem to get the Thumbnail view to "lock" to the same sort order as the list view. I arrange by file name (or ingest date, or reverse media duration, or any of the other sortable metadata fields) in list view, but then when I click to the thumbnail view, the order seems to arbitrariliy change to some sort of preset. What's worse, it appears to be changing to something that's in a jumbled order.
This isn't a big deal if I only have 10 clips. If I have 100, or 1,000 clips though, they have to be in a sortable order for the thumbnail view to be of any use.
Thanks,
Eli

Hi,
Thanks for your post. Our current design doesn't support keeping order between list view and icon view. It would be good if you can drop that as a feature request / bug into the the forum.

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?

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

Has anyone else noticed that: "The OS X Lion v10.7.3 Update includes Safari 5.1.3 and fixes that: Resolve a Wi-Fi connection issue when waking from sleep" didn't work?

I installed OS X Lion v10.7.3 because of the following claim.
The OS X Lion v10.7.3 Update includes Safari 5.1.3 and fixes that:
Resolve a Wi-Fi connection issue when waking from sleep
It continues to be a real pain having to reconnect to the network each time I wake my MacBook Air from sleep.
Does anyone have a suggestion for the resolution to this problem?

It seems the update fixed old problems for some and caused new problems for others. Sorry to hear you're in the latter group.
Here are some things to try.
1. Go to System Preferences > Network, and click the gear icon under the network interfaces like so:
Whatever service order you have set, drag Wi-Fi either to the top (assuming it's not already there) or someplace else in the list. Click OK and then Apply. Sleep the system then wake it again to observe any changes.
2. Click Wi-Fi in the above then click Advanced. Select all the networks your computer has ever joined and delete them with the "-" button. OK then Apply again. Select your network under the AirPort icon to re-join it. Sleep and wake again to see if that did anything.
3. Try creating a new, temporary user account. Log in under that account to see if its behavior is any different.
You may have done all of these already but perhaps there is something you have not thought of. If nothing helps we may just have to wait a bit longer for Apple to release a fix.

Green frames when exporting from CC 2014

Hello. I just updateted to the newest edition of premiere pro(aswell as all the other CC software i have installed which includes phoshop,speedgrade,audition,ame, and after effects). So the versions of the software are the very latest.
My computer is late2013 macbook pro with nvidia graphics card, and i have all the system updates installed, nothing special going on.
Heres the issue:
When exporting the project, i get random green frames, full green frames. Complitely randomly, no pattern whatsoever.
My workflow have been this: Footage shot with two Sony cameras and i have encoded all the materials to mxf format with one step earlier AME version. I started the project with one step earlier premiere, and i have already done 19 out of 23 sequences that project contains, no problem at all with earlier version of ame&premiere. Now i updated to the latest 2014 cc and these green frames started to pop out randomly. I have not used any plugins or effects, only premieres own threeway colorcorrector and bightness&contrast. Parts of the clip have transparent black video as textbackground with crop effect applied and basic textlayer from premieres own text editor. I have exported few grpahics from aftereffects (both the lates and the one step earlier version) to proress 4444 format as RGP+alpha. And im exporting with using youtube SD widescreen 360p settings, nothing changed. Again, everything worked perfectly before update.
things i have tried sofar:
delete caches both manually and from each software
normal boot
pram reset
safeboot
update check
export XML from 2014 cc and import to earlier premiere -> no luck, things got messed up somehow
made a copy of both project files, i compared and changed some version number from 27 -> 26 so i could open the project in earlier premiere -> no luck (this worked back in cs6 time when i had to import cs6 project to cs5.5)
Kinda running out of time, so rest of the night im going to spend re-editing those sequences i have done today with newer version of premiere. Will adobe pay for me for these extra hours, i think my client wont approve one extraediting day(night becaus of the schedule, these must be ready tomorrow with no green frames) because of software problem?
Ask anything you want, i'm 100% sure this is not user error since everything was fine with one step earlier premiere version. I will copy&paste this to the bugreport too.
Thanks

Temporary solution for this was "export xml" after all. I had to disable all graphics and textlayers and delete colorcorrections, and flatten multicam, so i had to redo all grading ja graphics stuff in older premiere after importin FCP xml. But got the work done in time. Won't use cc 2014 in near future unless someone figures out what is wrong with green frames. (well actually now im exporting from older AME, will she if the green frames pops out there too, wouldn't be too much surprised....)

When exporting from Imovie I get the following error? OSStatus error -2009

when exporting from Imovie I get the following error? OSStatus error -2009

Hi
Apple Support pages says.
Error 2000-2009 (2001, 2002, 2005, 2006, 2009, and so on)
If you experience this issue on a Mac, disconnect third-party devices, hubs, spare cables, displays, reset the SMC, and then try to restore. If you are using a Windows computer, remove all USB devices and spare cables other than your keyboard, mouse, and the device, restart the computer, and try to restore. If that does not resolve the issue, try the USB issue-resolution steps and articles listed for Error 1604 above. If the issue persists, it may be related to conflicting security software.
Yours Bengt W

Getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

getting red frames when export from cc 2014.2 codec used panasonic mxf format long GOP 50p. If any solution please help on that

i solve my red frame problem. originally my project was done in premiere pro cc 2014.2 & i render in Encoder cc 2014. in newer version i get lots of red frames. i complain a lot to adobe customer support . they said they know the issues but they couldn't solve. I was so tired from adobe customer support. one of the worse customer services i had. My friend got the mac pro & e got premiere pro cc 7.2 version. i convert all my footage mxf to mp4 in encoder cc 7.2 version and i succeed. i don't get any red frames.
So i think the problem is in adobe encoder cc 2014.2 version. newer version.

No audio when exporting from mpeg to flv

We have two PCs with Premiere Pro and AME installed, and just upgraded to CC. On one computer exporting works fine, on the other one, I'm losing the audio when exporting from mpeg to flv. I have used the same preset as on the other computer (that works) and also tried other presets that came with AME.
I can't figure out why this wouldn't work on one but works fine on the other? Anyone who knows?

How are you determining that the FLV has no audio? Are you playing it back in VLC Player or importing it into Flash?
Also, do you see a full range of formats on the system where you don't hear audio? If some formats are missing this might be a licensing issue. Also check if AME recognizes audio on the MPEG source (hover over it in the queue and look for audio info in the tool tip).

JMS issues when migration from weblogic 9.2 to 10.3.5

We are facing some issues when migration from weblogic 9.2 to 10.3.5
In weblogic 9.2 :_
BMP Entity EJBs used in our project are read-only in nature using entity cache, below is the configuration details
<!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 6.0.0 EJB//EN" "http://www.bea.com/servers/wls600/dtd/weblogic-ejb-jar.dtd">
<weblogic-ejb-jar>
<weblogic-enterprise-bean>
<ejb-name>
Company
</ejb-name>
<entity-descriptor>
<pool>
<max-beans-in-free-pool>300</max-beans-in-free-pool>
<initial-beans-in-free-pool>150</initial-beans-in-free-pool>
</pool>
<entity-cache>
<max-beans-in-cache>3500</max-beans-in-cache>
<idle-timeout-seconds>100000</idle-timeout-seconds>
<read-timeout-seconds>0</read-timeout-seconds>
<concurrency-strategy>ReadOnly</concurrency-strategy>
</entity-cache>
Entity beans will get refreshed using the JMS messges. with in the MDB descriptor files(weblogic-ejb-jar.xml) we are using the provider URL directly and XA enabled connection factory is set to false.
migration to Weblogic 10.3.5_
With the same configurations MDB are not not getting deployed in weblogic 10 with some exception, so we removed the provider URL from weblogic-ejb-jar.xml and changed the JMS configuration to use foreign JMS and XA enable connection factory is set to true. Now when ever the JMS message is triggered Entity bean is not getting refreshed with the updated values. i.e values are stale.
Can some one look into this and provide your inputs to resolve this issue.

I think the Entity bean refresh problem appears to be unrelated to MDBs. The MDB is only responsible for getting the message to your application (which in turn interacts with Entity beans). You might want to try posting your question to an EJB newsgroup.
Tom

Media Encoder crashes when exporting from Premiere Pro

Media Encoder crashes when exporting from Premiere Pro. I am queueing multiple files for export and Media Encoder will crash. The computer system has 32GB of RAM and the videos export fine in Premiere, but that requires exporting each one individually. Each video file is being down converted and some can be quite long (upwards of 3-5 hours). Nothing else is running on the computer that would take up memory.
Any idea why Media Encoder will crash?

Try turning off GPU acceleration.

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" 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.

"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

Sort Order issue when exporting from DRM

Similar Messages

Maybe you are looking for