Strange lines when exporting from Illustrator

I am having an issue that's driving me crazy, I've tried everything and I still can't figure out why it's doing this.
I created a template in Illustrator,  very basic,  just some 1 inch circles.   The goal is to color them in different color palettes and then save it as a PDF.   In Illustrator,  they show up completely fine,  the pattern fills sometimes have those little seam lines but those don't show up at 100% so I'm not worried about that.
My issue is that when I bring these graphics into Photoshop,  these little white lines appear in random places,   these are not pattern seam lines and there's no reason I can think of for them to be there.  I figured it may have been a corrupt file,  so I started from scratch and the lines are still there.  I've tried  copying it directly from Illustrator and pasting it into Photoshop,  same issue.  Saving as a TIFF,  same issue.
Here's an example of the line I'm talking about,  it's faint but noticeable on my screen,   any idea what might be causing this?
http://img.photobucket.com/albums/v648/hazelsmrf/line.jpg
The only thing I can think of is that when I turn off all pattern fills and only use solid color fills,  these lines don't show up.  I'm not sure why a pattern fill on a circle two circles away would cause a line to show up on a solid colored circle that's completely unrelated to the pattern fill though.   I am using CS5.

My Illustrator is fully up to date so that doesn't seem to be the issue.
I loaded the PDF into Acrobat reader and those lines don't show up there,  they only show up in Photoshop,  strange?
How I've brought it into Photoshop:  save as,  PDF,  or Tiff,  these didn't work.
Copied it directly from AI into PS,  did not work.
Saved as .AI and loaded that into PS,  did not work.
I just tried it as PSD and it worked!  However I've not been able to duplicate that because every time I've tried to export it to PSD since then it says I don't have enough memory,  argh.   Not sure why it worked the first time and not after.
Oh and the pattern fills were created with a blank no fill square on the bottom,  then a color filled square on top,  and then a few circles in a diagonal to make a polka dot pattern. Nothing goes past the square,  there's nothing in outline mode to show why it would do this.

Similar Messages

  • Significant quality loss and jagged diagonal lines when exporting from FCP

    I've been working on this problem for several days and I'm going insane! Every time I export my movie from Final Cut, there is a significant quality loss. It is most noticeable in two ways: diagonal lines become very jagged (looking somewhat like diagonal lines in an older video game -- more a diagonal sequence of blocks); also, in some areas such as faces, the colors get a little blurry and there seems to some "pooling" of colors around the edges of the face.
    I'm pretty sure the problem's not in capture: the Quicktime clips that I captured from the camera are all pristine. When I play them in Quicktime, I can blow them up several times their original size, and they maintain their sharp lines. (I also Reverse Telecined them all with Cinema Tools, if that's relevant.) I also know the problem's not just my computer monitor; when I play these movies on my external monitor and TV, they look bad too. The clips look bad after I bring them into Final Cut, and while I'm editing, but at first I figured that was because Final Cut sometimes doesn't show full resolution in the timeline. Still, when I export, the quality of the original captures just isn't there.
    Some details:
    Captured from 24A progressive, Sony HVR V1U HDV.
    Using Final Cut 6.0.1, Compressor 3.0.1, Quicktime 7.2.0, OS 10.4.10 (all the most recent versions I believe).
    I've exported in many different ways: using Compressor (and have tried a number of different settings: the DVD Best Quality 90 Minutes default Setting, as well as using a variety of bit rates from 3.0-8.0, One pass CBR, Two pass CBR, Two pass VBR, Two pass VBR best; Video Formats NTSC, HD 1440x1080...I have tried many combinations. Regardless of the size of the m2v created, the files seem to have the same problem over and over. I've also tried exporting from Final Cut as a Quicktime Movie and with Quicktime Conversion. Same result. I also tried using different compressors with my Final Cut sequence: Apple Intermediate Codec (which I used when capturing -- you have to with the Sony HVR), HDV 1080p24, HDV 1080i60, Apple Pro Res 422, H.264...
    What's happening? Why is Final Cut turning my nice pristine captures into jagged foulness? What can I try that I haven't yet?

    Welcome to the forums!
    Unfortunately, you seem to have tried everything I can think of, and I don't have the latest versions of FCP to know if it is a bug. However, in the off chance that you haven't given this a shot:
    Take a problematic 10 second section of your timeline (set in and out points) and the Export -> Quicktime (not QT Conversion) and make sure that you have it on Quality settings that you captured, and select the "Make Self Contained" box.
    Look at that in Quicktime and see if it's bad. If it's not problematic, use that video file in Compressor for your render.
    Hope that helps!
    ~Luke

  • Missing elements when exporting from Illustrator to .dwg

    Hi,
    I am exporting our Illustrator files into .dwg -- as our client will accept them in .dwg format only.
    There is one element that doesn't seem to transfer when exporting.  It is a red circle in Illustrator, but when exported, it shows up as a black outlined circle.  Any way to fix this in Illustrator so that it appears correctly in .dwg?
    We have the same red circle in other projects, and when exporting, they show up in the .dwg perfectly.  I tried to copy that red circle from another project and pasted it into my current project.  I matched the properties with the eyedropper tool, but still, no red circle in .dwg.
    I've included a screen shot of what is happening.  This is the .dwg.  You can see there is a black outlined circle next to the 'D' in the stairwell on the image.  It is supposed to be a red circle.  Below, in the empty space in the lower right corner, I copied and pasted another red circle from another project that is appearing fine in the .dwg.
    Any help would be greatly appreciated!!  Thank you!

    Thread moved from Adobe Captivate forum.

  • Scaling Error when exporting from Illustrator CS to AutoCad 2002

    When I export an Illustrator CS file to AutoCad 2002, I end up with a part that need to be scaled down by .03937 to be 1:1 in AutoCad. I changed my preferences to inches on all units and still have this problem. What setting do I need to change to have this convert straight to AutoCad without secondary operations.

    Hey, guys,
    Thanks so much for the responses. I discovered that one of the issues was that my browser window was set to 125%, causing things to appear a bit blurry. However, I'm still having issues with the "save for web" window. It seems like the left side (the original) should look exactly like what's on my artboard, but as you can see from this screenshot, it's blurry when I zoom up (Both the artboard and save for web window are at 300%). I have the text on the right set to gif, but it still looks the same as the "original" on the left. Shouldn't my orignal in the save for web window look exactly like the text on the artboard? Would this be affecting the files I'm exporting? Thanks so much for the help!
    Peter

  • Lines too dark in PDF exported from Illustrator

    Hi there!
    When I export from Illustrator to PDF, all lines in the design looks black, when they are light grey in the original file.
    Here the examples:
    Any ideas?
    Thanks a lot!

    Did you use Export in Illustrator or the Acrobat process. The Acrobat process would need to have the display resolution and such set to an appropriate setting. If you did the export, then you may have to look at the properties of the export process in Illustrator, not Acrobat.

  • Lines too dark in PDF exported from Illustrator, any idea?

    Hi there!
    When I export from Illustrator to PDF, all lines in the design looks black, when they are light grey in the original file.
    Here the examples:
    Thanks a lot!

    Do you feel that this is a swetting that you would like to be able to set per document so that when it is opened by someone else this feature is turned off?
    Or would you prefer to have this setting turned off by default?
    Would you perhaps think that a warning stating that the document contains thin lines and to see them more accurately the user has to turn it off in the preferences would bve sufficient in case the user would not be so concerned acccurac but is more worried about their vision?
    And yet perhaps a way to set this up in the preferences on the authors side so that when such a document is opened the user is given a choice of how they would like this setting configured in the future?

  • 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

  • Transparent edges in psd exported from Illustrator

    Hello Community,
    I have something going on when I export from Illustrator as a PSD using the artboard. It ends up with a line of transparency around the edges, and is larger than the size of the art exported. It gains about .01 inch around the edges, and when I use 'trim transparent pixels' in Photoshop, it trims it down so it has only gained .07 inches around the edges, but doesn't lose the last line of pixels that are semi-transparent. I am using a script that exports it, then re-imports it and places it in the Illustrator file, effectively swapping the vector for raster. It's part of a larger process I have no control of, so the process is not something I can change, otherwise I wouldn't do that.
    Why is it exporting with this line of transparency on the edges? It's causing white lines to show up in the file that it gets reimported to. Until now it was ok because it only shows in the bleed, which gets trimmed off. From now on, though, this process is supposed to be used for non-bleed items, and the white lines are showing up. Attached is a closeup of an example.
    Does anyone have any ideas how to stop it from happening?
    Cheers,
    Emmy Williford

    Ok I got it you have two choices to get rid of this problem this is what I found out.
    if you export the file with the choice of art optimize or type optimize you will get this antialias artifact if you choose none as the optimize option then you will not get this anti alas artifact since there is no anti alias being applied.
    The second choice is to turn on align to pixel grid and then you can export with art or type optimze as an anti alias option and this artifact will not be present.
    You have a third option and that is to keeep your optimization options and set the color background shape to align to pixel grid on the object level and not the document level using the align to pixel grid option in the transform panel you have to show options in the transform panel to see this option.
    Here is  no align to lixel grid with none for optimizing
    Here it is with Art Optimized
    Here it is with Type Optimized
    Here it it with art optimized and align to pixel grid document wide
    Here it is with the background object only set to align to pixel grid
    I hope this gives you the options you need

  • Glitches during Export from Illustrator

    I recently went from CS2 on an old G5 to CS5 on a newer, more powerful IMac.
    Now, when I Export from Illustrator to Photoshop, the resultant files have small glitches: horizontal white lines one pixel high by several or many pixels in width.
    The only recourse I have is to manually retouch or try to revive CS2 on my old computer.
    There must be a better way?

    I hope you can see this. I had to save the psd as a png.

  • Weird Lines when Exporting PNGs - help!

    I'm getting some funky lines in images I export from Illustrator as PNGs. Anyone else have this issue, or have a solution?

    Looks like transparency issues when saving PNGs with the Interlaced option... Since you seem to be opening them in Photoshop for further editing, I wouldn't bother. Simply export as PSD or TIF and save as PNG from PS when realyl needed...
    Mylenium

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

  • Export from Illustrator as PSD

    Hello
    I updated to 16.2.1 and now when I export from Illustrator as a psd with antialias option unchecked it opens in Photoshop with the edges antialiased.

    I hope you can see this. I had to save the psd as a png.

  • 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?

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

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

Maybe you are looking for