Every adjustment lags, and even scrolling down my photos in the Library module is choppy. Adjust your camera until you are happy with your exposure and camera settings.My powerful workstation laptop (Lenovo Thinkpad W540) with an i7 processor and 32 gigs of RAM on W10 struggles HARD with my RAF files from my X-T2. Now that Lightroom mobile is here, the question becomes can I shoot tethered into Lightroom mobile and the answer is yes However, even though the answer is yes, it still involves your computer as there is still no way to connect your camera directly to your iPad via a USB cable and shoot tethered like you do with your computer.Step 1: Open Lightroom and Catalog Step 2: Tether your Camera & Computer.
Exposure X7 non-destructive RAW photo editor. My drive has 40% free space, I only have about 6000 photos in my catalog, and I back-up and Optimize regularly.Exposure provides distortion, vignette, and chromatic aberration correction for many camera lenses. I've got a 40GB cache, I've turned GPU processing on, and back off, to see if it makes a difference (it doesn't) and nothing I've done seems to make any difference.
Makes my Windows systems look like slugs (actually slower than slugs). That system with 1.6 GHz processor, 8 gig RAM, and 128 gig SSD drive simply flies. Even without Lightroom open I found my hard drive being used at 100% for 100% of the time.I changed to a Macbook Pro with an SSD drive and found Lightroom flies! Not because of the power of my system - I suspect a Win10 system with an SSD drive would fly as well.I use my 11" Macbook Air when I travel with an external SSD drive. Win10 defender and other system utilities in Win10 also write to the hard drive frequently. Lightroom does not put everything in memory and then write to the hard drive later like most software - it writes to the hard drive as you work and make changes causing each move to be dependent on the speed of the hard drive. At first I blamed Win10, but after investigation I found that only partially true.My problem was the hard drive.
You only need to use lots of RAM should a large amount of data need to be stored in memory at the same time for quick access. Import/Export is a processor intensive task, so the CPU should peek at 100% since the computer is putting all resources into that task. Like, uncomfortably hot, with the fans running at full blast.That's not backwards. That seems backwards to me.The laptop also gets REALLY hot. I found the difference is the SSD drive instead of HHD.I decided to open up and watch my Task Manager while working through an import and some processing, and interestingly, my CPU usage spikes to 100% the whole time I'm importing or working (Quad core i7), but only 6 to 8 GB of my 32 gigs of RAM get used at any point. Works incredibly fast, in fact I would say it keeps up with my more powerful Macbook Pro.
If the fans are running at full blast that's a good thing because they are doing what they are suppose to be doing.With a faster CPU and more RAM, it doesn't mean the computer will now process the images/video with less RAM or CPU usage. GPU (graphics card) will also do the same if it is pushed real hard, but that only happens (usually) with gaming. So not RAM intensive.With the CPU being used 100%, that will generate the most amount of heat, so your computer will get hotter (more noticed on laptops versus desktops).
And I suppose as I think about it from a different perspective, I WANT it to be using my whole processor so that it moves more quickly. It means it should process quicker.Well all of that makes good sense. Edited Apby Adam WoodhouseWith a faster CPU and more RAM, it doesn't mean the computer will now process the images/video with less RAM or CPU usage.
Which makes the decoding noticeably slower.Other RAW decoding tools that are coded specifically for Fuji RAF files are much quicker. So there is lots of extra, inefficient work done in the ACR (Adobe Camera Raw) software for Fuji files. Haha"We have all been asking that exact same question!I have followed discussions about this over the many months and it appears that Adobes default RAW decoding algorithms are customized for Bayer pattern sensors and not the X-trans sensor design of the Fuji system. Makes sense to me now." So I guess now I'm just upset that even though it's using my entire CPU for 2 hours at 150 degrees f, why does it still take so ridiculously long to process RAF files. HahaEither way, thanks for helping me understand.
My catalog as over 55,000 images in one, and over 40,000 in another so doubt if your 6000 are causing the issue.Importing about 1000 uncompressed raw photos and creating 1:1 previews for all of them takes about 3 hours with my CPU at 100% and the fan cranking at full speed, assuming I just set my computer down and don't try to do anything else while it's working.For comparison, I tried it with some Canon raw files and that process took about 15 minutes.I don't shoot compressed raw just because I have plenty of card space and lots of spare hard-drive space, and didn't see the benefit of shooting compressed, even though it's supposedly still full quality.I've spent about 3 hours with Adobe support controlling my system, changing settings, resetting permissions, uninstalling and re-installing things, doing research on my processor and graphics card, etc. I wonder if Adobe has to take time to de-compress the files to actually make the changes (?) I'm only asking here, as I am not an engineer.But I'd be very, very curious to determine what you consider a long time, or slowness. What do you consider "slow" or "long"? I really am curious here as I'd like to benchmark my LR and my X-T2 raws.2. We live with the slow performance when using our RAF files.1. If you do a Google search on the topic, you should find some informative websites that have done thorough testing/reviews.But for those of us that use LR. Which tool is not only faster but which decodes the RAF files the best.
(Neither thing made a difference).I am glad to hear you are able to get things working. Two days later, I got an email saying that I should disable GPU processing, and update Lightroom, and that was it. We finally ended the session with her saying she would continue to do research and get back to me later with a solution.
0 kommentar(er)
