Preview is slow

Preview is very slow when dealing with PDF's, any suggestions? I am using the latest 15" Macbook pro.

Back up all data. Quit Preview if it's running.
Hold down the option key and select Go ▹ Library from the Finder menu bar. From the Library folder, delete the following items, if they exist:
          Containers/com.apple.Preview
          Containers/com.apple.quicklook.ui.helper
          Group Containers/com.apple.Preview
          Preferences/com.apple.Preview.LSSharedFileList.plist
          Preferences/com.apple.Preview.SandboxedPersistentURLs.LSSharedFileList.plist
          Saved Application State/com.apple.Preview.savedState
Log out and log back in. Launch the application and test.

Similar Messages

My Preview is Slow :(

Since the new update (Im not sure) of Adobe Muse ..... the Muse preview has slowed down ... even the browse (chrome) preview takes a very long time to load. Its definitly not my computer because i have a really powerfull machine. Can some one helpo me ???

Hey ! Zak !
Thanks for the reply !
- Im currently running Adobe Muse 7.3 and the update was from 7.2 to 7.3.
- Im using a Mac. All my machines are the top of the line models.
- When i perview my site using Adobe Muse i get something like this (http://192.168.2.10:33333/Preview/mysite/index.html)
- Here is the businesscatalyst website.......ive just started working on it......so yea : http://onefoot01.businesscatalyst.com
Since previewing within Muse was taking too long.... i started to publish my site and preview it as a website from businesscatalyst.com which was really really fast !
For example...say...If you use the built in "Muse Preview" option the site or page takes a very long time to load fully.... i even tried putting only a blank canvas with a simple colourfill, this itself took a long time.
Is there a way to fix this issue ????

FCP 6.0.1 Running and previewing extremly slow

Ever since I upgraded to 6.0.1 FCP is running extremly slow.
In my current project, I brought in a HDV QT.mov that needed to be Chroma Keyed and color adjusted. Previewing the chroma keyed file looks horrible (all jagged) unless I render it. That takes time. Then I added a piece of stock DV footage under that, blurred the background and it played back like crap until I rendered it. More time. And so on.
I can't make any adjustment and see how it looks without rendering.
When I was working in 5.1 FCP I was able to add all type of files and zip right through them pretty much. Now I can't seem to get my settings right or something...so as I apply different effects or filters I can never see on the fly how it looks without rendering it first. Then of course...if it's not right...I tweak it again but can't see how that looks until I render it again.
All my video files resides on a RAID that I created from 2 of my internal drives and it also is my scratch & render disk.
It's eating my lunch on production time.
Any suggestions Please.

You could try setting the render in the sequences you work with to ProRes. Found in that sequence setting's video processing tab.
But the real fix is to not work in HDV at all. If you have an Intel mac, a capture card like the Kona LHe card will transcode your HDV directly to ProRes... or AJA's Io HD (at the high end of this workflow) will transcode the HDV to ProRes on board the box itself... The Io will take your HDMI signal directly from the camera and transcode it to anything. It starts shipping any day now.
You're a brave soul attempting chroma keys with HDV... they are nigh on impossible to look good. But ProRes will make the rendering times go way down, and give you more real time playback of effects.
Jerry

Multiprocessing works for RAM preview, extremely slow and aeselflink crashes when in Render Queue

Hello all,
System specs:
Hackintosh
OSX 10.9
3.5Ghz (overclocked to 4.2Ghz) Core i7
Geforce GTX 580 classified 3GB Cuda GPU
AMD Radeon HD 6870 1GB Display GPU
32 GB of RAM
System SSD
5 drive internal RAID
After Effects CC 12.2.1.5
Cuda drivers up to date
I'm having a problem with the render queue and multiprocessing. I have a moderate sequence with several effects and 3D layers. When I'm working in the composition, everything goes great. I can RAM preview and all my CPU cores will kick up to 100% and render the composition in no time all; with full resolution with no skipped frames. It works fantastically.
Then when I go to render the exact same composition with the same multiprocessing settings, AE will hang at the "initializing background processes" for at least 5-10 minutes, during which the CPU will ramp up to 100% but no frames will be rendered. AE still remains responsive, as I can hit the stop or pause buttons and the queue will be cancled. But then the aeselflink processes (up to 8 of them depending on my settings, I've tried several) will still continue at 100% cpu load even with AE not set to render anything. I will have to go into the activity monitor and force quit each process. If I leave it for 5-10 minutes, it will finally stop initalizing and start the render, but the CPU will still run at 100% but the frames will crawl slowly forward at about 1 frame per minute, with an estimated 28 hours to render frames that were rendering in under a minute during RAM preview.
I have tried both reducing the number of cores AE will use, adjusting the allocated RAM, and disabling multiprocessing alltogether. When I disable multiprocessing, the render slows to a complete crawl, and it will render around 1 frame every 5-10 seconds. Again, this is on a composition that rendered in less than a minute on full resolution with RAM preview.
The only way to get this composition to render is to export it to Media Encoder, which will render it (without multicore processing, unfortunately) in about 8 minutes, still not the blazing fast RAM preview but at least it finishes it in under 3.5 hours (the amount of time that the multiprocessing disabled render in AE will take).
Here's the multiprocessing settings that have been very stable and carried me through other projects. Disk Cache is not enabled. The only other thing that is disabled is the "Disable Layer Cache" under the Secret menu as the plugins I'm using (Plexus 2 in this case) doesn't like to update when the camera moves so this option has been disabled to force it to reset each frame.
Does anyone know what is going on?
Also, please don't tell me that I should not use multiprocessing or instruct me on basic steps as to increase preformance on my machine. I have been tweaking my memory and multiprocessing settings for a long time now, and it is completely stable in everything but this setup. So please no answers saying "just don't use multiprocessing". It was made for a reason, it's effective, and it's needed. And please don't say that it's the hackintosh, either, as it's the most stable and powerful computer I've ever used. Sorry for the disclaimers, I just want to have constructive help.
Thank you in advance for your ideas!

Hi Rick, not sure if you saw the part where I said please don't reply with turning off Multiprocessing, and I did not say that it works and is effective in all areas. However, if you actally take the time to read my post, you will definately notice that RAM preview with multiprocessing takes under a minute to render a scene. Multiprocessing disabled and rendered in AE takes 3.5 hours. In Media Encoder it takes around 8 minutes. Clearly it IS working and IS effective for my case and my rig. Any vendettas against MP does not help my situation at all.

CS5 RAM preview is slow if I do other things while it's building

Good morning!
I'm experiencing a strange issue. 1080/29.97 comp on an 8-core w/ 16GB. Multi-proc rendering is off.
If I RAM preview the comp (800 frames or so) and wait while AE builds the RAM preview, it plays back fine & at speed.
If I start the RAM preview, then go work in Photoshop while it's building, then return to AE and attempt to play it down, I have the green bar like a normal RAM preview, but it plays very slowly -- almost as if it's re-rendering every frame (actually slower than if I just hit spacebar to render&play on the fly).. maybe 1fps. If I stop and play those frames that it's slogged through, they then play normally.
Is it possible that RAM previewing while I'm using another app (e.g., Photoshop) is resulting in the frames being written to swap disk or elsewhere so that they're being re-read into RAM when I actually try to play it? Disk caching is disabled in the AE Prefs, but...?
Thanks in advance for any ideas -- very annoying.

> Is it possible that RAM previewing while I'm using another app (e.g.,
Photoshop) is resulting in the frames being written to swap disk or
elsewhere so that they're being re-read into RAM when I actually try to
play it?
Yes. That is possible.
Be sure that you're reserving enough RAM for other applications.

Placing an image in Indesign CS5- Previews are slow

I have a customer with identical intel MacPros, 10.5.8 OSX, 8GB RAM and running CS5.
Whenever they go to PLACE an image in either InDesign or Illustrator the preview window that comes up takes up to 65 seconds for a preview to appear in the window. These are images(TIFFs or EPS) that are over 200MB.
What I've done so far:
Timed image preview when placing an image from server or off of desktop- No speed difference in showing the preview.
Took my MacBook Pro and tried to place the images- Immediate preview, no matter the size of the image. Desktop and over the network.
Started their MacPros up in target disk mode- Launched InDesign from their computer- No problem.
Started my MacBook Pro in target disk mode- Launched InDesign from my computer- Same speed issues with preview appearing when placing an image.
Replaced their current video cards with accelerated high end graphic cards. - No performance increase. When previewing a placed image, still very slow.
None of my other customers have this issue. Any clues????

There have been sporadic reports that changing the preference for live screen drawing to delayed from immediate has helped other issues such as this.
Try that first and let us know if it corrects the problem.
Bob

Editing pdf files in Preview painfully SLOW with mavericks! Why? How to fix?

Editing pdf files in Preview is painfully SLOW with Mavericks! With mountain lion everything was so smooth .... Why? How can I fix this?

I stopped using preview. Adobe Acrobat Pro is running fine ... this is not a solution to the problem though. The question remains open: why is preview not running as before?
Why did I upgrade?!

Preview very slow with .nef photos

My preview works well for .jpg but not .nef.
Open folder, select 'all' right click, open with 'preview'. Very slow & jerky.
Used to work fine with .nef in Mt. Lion.
Any ideas?

Same issue here, and 10.10.2 brings no solution… Haven't you heard yet, Apple is the new Microsoft?!
Anyway, here a few tips to speed up Preview at least a bit, so one can use it for work again:
tip1:
Delete /Library/Preferences/com.apple.windowserver.plist
Delete ~/Library/Preferences/ByHost/com.apple.windowserver*.plist
Shutdown OSX
Startup, immediately press and hold the P and R keys while holding down the option (⌥) and command (⌘) keys before the gray boot screen appears, which resets the PRAM
tip2:
Turn off "Smooth Text and Line Art" in the Preferences. Of course, that's really sad, because PDFs then look terrible, but at least they are easier to work with.
tip3:
For just viewing, use QuickLook: in the Finder, select the PDF and hit [SPACE]. Strangely, QuickLook isn't affected by the bug.
Anyway, those workarounds helped me a bit (thanks to those who posted them), but of course it's no proper solution. The last option would be to go back to Mavericks.
I heard the problem was reported to Apple when Yosemite was in beta, summer 2014. Nothing happened so far. Apple really has to get its act together…

RAM PREVIEW VERY SLOW (FAR FROM REAL TIME) ON NEW MAC PRO

Good afternoon
I have the new mac pro with 8 cores, 64 Gb of Ram and dual AMD 700 graphic card, but the preview on After effects is slower than in the old mac pro (from 2010). I have set the preferences as told in your website and everything stills the same. Could you please advice? is very frustrating to see that a new machine works worse than the older one.
thanks

Attached below you can see some screenshots from the settings I have on AE CC

Preview - very slow re-draw

HI all
One thing I've noticed in leopard is the new preview is very slow to re-draw when I have multiple image files loaded in. As a hit the next arrow it forms the next pic in big slow blocks unlike the previous preview that switched smoothly no matter how large the images were.
Has anyone else experienced this

I opened the pdf guide which is on the Leopard install disc. The whole machine went into a mini freeze state and then it eventually loaded. In tiger I have opened pdf's that were over 300mb in size and whilst there was an initial load it did then populate each page.
I'm sure its just a glitch to be worked out and will be addressed in 15.1 update.

Why is finder preview so slow?

When I was using the previous OS the finder preview was ultra fast. Now when I try to go thru music and audio files the preview is irritating slow. Sometimes it takes 30-60 sec to launch normal mp3 songs or WAV files. Anybody knows the reason why its degraded from the previous OS?

I have the same problem, can someone please help?

AE CC ram previews very slow - no GPU support? Newbie trying to become not newbie, falling at first hurdle...

Hello. I'm currently trialling After Effects CC though Adobe Cloud. But I've hit a snag immediately.
I have an HD video edit in Premiere Pro which I want to dynamically import into AE to work on some bits.... I have imported the project file into AE, it seems to open just fine but the playback is intensely slow!
I have an uncertified GPU - a Nvidia Geforce gtx 460 - too old? I was expecting it to help out a bit, I'm not doing anything too badass, just colour correcting a bit of HD footage.
My processor is an i5 3.4ghz 4 core.
Perhaps I'm missing something fundamental here!? Please tell me what I'm completely failing to grasp
Thank you for your time,
Tony

Yup -- you're misssing a very basic item: AE doesn't work like Premiere Pro. It's not anything like PP, and it doesn't behave like it.
One way is the method you need to play video. Space bars just don't work. You need to do a RAM Preview -- hit the zero key on the numeric keypad, let AE render the frames it can, and then it plays them back as fast as it can.

Building smart previews much slower in Lightroom 6 than in Lightroom 5

Building smart previews is much slower in Lightroom 6 than in Lightroom 5.
Creating a smart preview from a DNG (Fuji X-E1 raw file) takes about 12 seconds.
Enabling/disabling GPU accelaration does not really make a difference.
When monitoring the Lightroom process with Process Explorer the GPU usage is always 0.
Below is my system specification.
Anyone got some idea why this might be?
Wilhelm
Version von Lightroom: CC 2015 [1014445]
Lizenz: Abgelaufene Testversion
Betriebssystem: Windows 8.1 Business Edition
Version: 6.3 [9600]
Anwendungsarchitektur: x64
Systemarchitektur: x64
Anzahl logischer Prozessoren: 4
Prozessorgeschwindigkeit: 2,3 GHz
Integrierter Speicher: 8071,2 MB
Für Lightroom verfügbarer phys. Speicher: 8071,2 MB
Von Lightroom verwendeter phys. Speicher: 655,5 MB (8,1%)
Von Lightroom verwendeter virtueller Speicher: 692,1 MB
Cache-Speichergröße: 0,0 MB
Maximale Anzahl Threads, die Camera Raw verwendet: 2
Camera Raw SIMD-Optimierung: SSE2,AVX,AVX2
DPI-Einstellung des Systems: 144 DPI (High-DPI-Modus)
Desktop-Komposition aktiviert: Ja
Monitore/Anzeigegeräte: 1) 2560x1440
Eingabetypen: Multitouch: Ja, integrierte Toucheingabe: Ja, integrierter Stift: Nein, externe Toucheingabe: Nein, externer Stift: Nein, Tastatur: Nein
Informationen zum Grafikprozessor:
Intel(R) HD Graphics 5500
Check OpenGL support: Passed
Vendor: Intel
Version: 3.3.0 - Build 10.18.14.4029
Renderer: Intel(R) HD Graphics 5500
LanguageVersion: 3.30 - Build 10.18.14.4029
Anwendungsordner: C:\Program Files\Adobe\Adobe Lightroom
Bibliothekspfad: C:\Users\wmedetz\Lightroom\Lightroom Catalog.lrcat
Einstellungen-Ordner: C:\Users\wmedetz\AppData\Roaming\Adobe\Lightroom
Installierte Zusatzmodule:
1) Behance
2) Facebook
3) Flickr
Config.lua-Flags: None
Adapter Nr. 1: Anbieter : 8086
Gerät : 1616
Subsystem : 222717aa
Version : 9
Grafikspeicher : 0
Adapter Nr. 2: Anbieter : 1414
Gerät : 8c
Subsystem : 0
Version : 0
Grafikspeicher : 0
AudioDeviceIOBlockSize: 1024
AudioDeviceName: Lautsprecher/Kopfhörer (Realtek High Definition Audio)
AudioDeviceNumberOfChannels: 2
AudioDeviceSampleRate: 44100
Build: Uninitialized
Direct2DEnabled: false
GPUDevice: not available
OGLEnabled: true

I know that is the official line but copying speed is fine in Windows 8 under Parallels. I have the latest Windows 8 Broadcam driver installed for the network adapter in Boot Camp and everything else works fine.
I can download a file from the Internet 10x faster than I can from my Airport disk in the next room in Boot Camp!

Library Preview Rendering Slow

I'm sure I'm missing something here and am hoping someone can point me in the right direction. I just purchased lightroom 2.3 primarily as a workflow tool for the RAW photos I take at sports events. The first step in my process is to review all the photos and remove the ones with poor composition and ones that are out of focus so that I don't spend time cleaning them up before I do any cropping.
My problem is that the rendering of the preview thumbnails seems to take an inordinate amount of time before I can see the thumbnail in enough quality to make a decision on the focus quality. I opted to invest the time up front and generate 1:1 previews during the import process. I've got the thumbnails sized to display two thumbnails with the sidepanels hidden to use as much realestate as possible. However, when I move from thumbnail row to thumbnail row, at least one of the thumbnails is initially displayed in a blurry format and takes approximately 2 - 4 seconds to display in it's final state.
Considering I have 353 photos to review, I'm looking at sitting 17 minutes total just waiting on the final rendering of thumbnails to decide on whether they're in focus or not. This just doesn't seem right if I selected to pre-generate 1:1 previews. So I've got to have something set wrong somewhere. Any ideas or direction would be greatly appreciated!
Dale

Thanks all for your thoughts and ideas. It looks like I'll just have to live with the multiple pass slow rendering in Lightroom if I want to continue to use it. I ran a test with the same batch of photos in Capture One LE, the product I intended to replace with Lightroom. Once the folder and photos were imported into Capture One and thumbs rendered for the first time, moving from one large size representation of a photo to the next (there's no "library" module, it looks more like the LR Develop module and all work is done from there) took significantly less time than in Lightroom (less than 1 second).
Some other notes from the comments above:
- yes, I was using very large thumbnails to scan through the 300+ photos and filter out the bad ones and yes it requires me to do a lot more scrolling. Annoying, but necessary for me. One of the more difficult things for me to do is determine if a shot was in focus or not. This decision requires a large thumbnail for my old eyes ;-)
- I have 100Gb free on my catalog drive and 200Gb free on my data drive. I can't imagine Lightroom would require any more to render thumbnails and display photos in the develop module more quickly.
Thanks again everyone!

Preview builds Slow or Fast options available again

Just when I thought 9926 would be the last preview build until the RTM version is released, today, after installing update KB3035129, Slow or Fast options are available again.
I also understand that build 9931 and 9932 are offered to MSFT.
Does that mean we are going to get another preview build before the rtm is released ?

On Wed, 28 Jan 2015 04:14:45 +0000, david hk129 wrote:
Just when I thought 9926 would be the last preview build until the RTM version is released, today, after installing update KB3035129, Slow or Fast options are available again.
I also understand that build 9931 and 9932 are offered to MSFT.
Does that mean we are going to get another preview build before the rtm is released ?
More than one in fact. I can't find the link but someone from MSFT stated
that the only reason we had to wait so long between 9879 and 9926 was due
to the holiday break and that we'd be seeing more frequent releases moving
forward. Also, if you watched the live stream event you would have seen
that JoeB referred to/demonstrated loads of feature that aren't in 9926 and
that we could expect to seem them in future builds in the coming months.
Not sure where you'd get the impression that we weren't getting any more
builds before RTM.
Paul Adare - FIM CM MVP
He who joyfully marches to music in rank and file has already earned my
contempt. He has been given a large brain by mistake, since for him the
spinal cord would fully suffice. -- Einstein

Preview is slow

Similar Messages

Maybe you are looking for