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

Similar Messages

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.

Compressor3.53 genrating dulipcate frames when exporting from H264 to Apple Prores

whn i was trying convert Animation playblast(H264 Codec) in compressor to appleprores422...genrating dulipcate frames..at 13th frame ....Orginally the animator will take playblast in NON-codec .OR Wraw codec formate ....later it will converts into H264 using Quicktime ..while the playblast playing like vedioShutters..wat i converted in Compressor
i was using same preset from long bak...........this promble occuring for few days
iam using compressor 3.5.3......QT.time 7.0 .. mac

Not surprised the 10bit uncompressed won't play back on an iMac. Is 10-bit HD....? Yes, in fact in some opinions, 10 bit IS (the appropriate bit-depth for) HD.
The other thing is that you must select your render codec and directory BEFORE you load the Render Queue. Otherwise everything goes out 'default',and to top it off, the XML export will reflect the changes you made AFTER -- which will then be, as they say, "wrong".... so yes, it matters.
Internal Hard Drive is nowhere near what you'll need. Doing a compression from it shouldn't be a problem, though. Anything that doesn't need to run in real time should be okay. Heck, you could probably do 4K -- but not much of it, or very quickly.
Seems like FCP really wants to work in bit depths in multiples of 8. Funny thing, that.
I'm also mystified about the 'render in original codec' wrinkle in your fabric... I've never had an issue with DVCProHD like that. And the ProRes422HQ thing... I'm looking at a 5 minute project right now (just Media Managing the corrected version back to hard drive as I write this) that would duplicate your initial workflow and it looks, well, lovely. You may be simply overwhelming your hardware.
jPo
Message was edited by: JP Owens

Changing frame rate when exporting from iMovie '09 using quicktime has no impact on duration. Why?

Changing frame rate when exporting from iMovie '09 using quicktime has no impact on duration. Why?
I have a file created by digitizing an 8mm film at a rate of 24 fps. I would like to create a downloaded movie at a frame rate of 15 fps. The Export using Quicktime option seems to provide that capability but the resulting file has the same duration as the original 24 fps file. How can I get the exported movie to be slowed down?

joegez,
There is a feature you can use to slow down the video. In the project, move the mouse pointer over the clip, then click the gear icon. That brings up the Inspector. Click the Clip tab. Then you will see a feature there called Speed. Move the slider to the left to slow down the clip. Or you can enter a percentage in the box on the right.
Hope this solves the problem for you.

Saturation Loss When Exporting from Lightroom.

This happens to me when exporting from Lightroom 2 or 3. It happens regardless of the color profile, file format, bit depth, image size, compression, or the method of export. I regularly profile my one-year-old iMac monitor with an Eye One Display 2. My working color space for Photoshop CS4 is ProPhoto. After exporting, I am viewing the images in Photoshop, Safari, Firefox and Apple Preview, with the same result. I have used pretty much all the available export methods in Lightroom, including exporting with Lighroom ad-ons such as SlideshowPro. And, conversely, if I edit an image to my liking ourside of Lightroom, there is a saturation increase when I import it into Lightroom. The effect tends to be most obvious and bothersome with shots taken outside on sunny days, with lots of blues and greens. I am shooting raw files with a Canon 5d II and I use the Adobe Standard profile in Lightroom.
There is a section at the back of Martin Evening's Lightroom book where he talks about the Lightroom color space and Lightroom versus Photoshop curves, which seems to relate to what I am seeing, but I have the feeling that what I seeing is more pronounced than what he is talking about there. It is a real dullng of the look, not merely a slight difference in how the colors are rendered.

Looks like Lightroom doesn't like your display profile.
Try removing the profile (don't know how to do it on a Mac) to leave your display uncalibrated. Are the colors still different in Lightroom and Photoshop?

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.

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

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 (

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

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.

Green frames when exporting from CC 2014

Similar Messages

Maybe you are looking for