
jwArtWorks
Participant
jwArtWorks
Participant
Activity
‎May 04, 2021
01:01 PM
You could try using a Loupedeck controller. It allows full customization and lots of programming capabilities!
... View more
‎Feb 12, 2020
07:25 AM
Lightroom allows control of the Windows Menu bar by Shift+F or clicking on the 1 on the left of the filmstrip bar.
... View more
‎Feb 12, 2020
03:09 AM
Not having the problem with Windows!
... View more
‎Dec 03, 2017
09:20 AM
Try rebuilding previews as the library mode displays embedded previews unless standard previews are available. In Library mode, go to Library > Previews > Build Standard Size Previews and see if this changes anything.
... View more
‎Nov 03, 2017
11:31 AM
Why am I unable to run the 1709 update. It tells me it is not applicable to my computer. I am currently running 1703 and want to use the surface dial. It works in Windows but not in Photoshop!
... View more
‎Oct 02, 2017
11:40 AM
The DNG Converter currently showing in the link is version 9.1.2. Will it work on Canon 80D files? Second, I updated Photoshop CC and when I look at the Camera Raw (as described above) it still says 9.1.2. When I go to Adobe CC, it says Camera RAW is up to date. Why is this so confusing?
... View more
‎Jun 08, 2017
10:30 AM
Thanks. I'll post it there.
... View more
‎Jun 08, 2017
09:06 AM
I have been a Lightroom user since version 1. I have come to love Lightroom and use it daily. I manage multiple catalogs, some small and some large. From version 1 through version 5.7, I simply loved the software. I was using an HP workstation with 2.1 Ghz Quad-Core processor, 32Gig of 1600 speed RAM, 5400 RPM Hard Drives for my catalog, USB3 Drobos for my photo storage, and an Nvidia video card from 2003 that supported my two monitors (27" LG Monitors - neither is 4k or 5k)). Most of my images are Nikon RAW format from cameras with 12 or 16 megapixel FX sensors (D3, D5, D750, D500). When Adobe announced the Creative Cloud, I was hesitant but in an effort to remain current, I dove in and began using all Cloud applications (Lightroom was not yet a cloud product). Soon after, Lightroom became a part of the cloud but still a stand alone piece for the most part. With the advent of Lightroom CC, especially when the new GPU processing was introduced, I felt it was time to upgrade my PC. So, I custom configured a new workstation with 3.3 Ghz 12 Core processor, 64 Gig of 2400 speed RAM, 1 terabyte SSD internal PCI accelerated storage for my catalogs and software, the same USB3 Drobo units for my photos, an NVidia GEForce GTX Titan X Graphics card with 12 Gigi dedicated Video RAM, and the same two monitors. Every piece of software I use is lightning fast! My computer boots completely from a restart in less than 90 seconds. Only Photoshop and Lightroom perform pitifully. I have spent countless hours working with support people from Adobe, managers from Adobe, and some of their lead engineers (so I'm told) and I have made no progress. After tweaking some settings in one of the last updates with an engineer from Adobe, it looked like it might be a little better. That was an illusion! It is not better and gets miraculously worse with every update. I even asked if I should change graphics cards and the engineer told me my card was fine and I will be okay for the near future with Lightroom. Obviously, this is not the case. In an effort (as per their suggestions) to speed things up, I have deleted all my smart collections and built and tested using brand new catalogs with a few hundred images - nothing seems to help! After an hour of editing, everything slows down so much that I need to exit Lightroom completely and then restart Lightroom - this does give a small measure of relief for a short time!!! I am even editing Smart Previews as they suggested recently and it is still too slow to use! One thing that helps a little is to disable the GPU altogether in both Lightroom and Photoshop. This is far better for overall performance and gives me more time before I need to exit and restart Lightroom. Why should I need to do this? If the GPU implementation is designed to improve performance, how do I make that happen? I designed and bought this computer with the biggest (RAM) and fastest Graphics board made by NVidia at the time. How do I get the "better performance" promised from the GPU implementation? Adobe can't help or won't help or doesn't know - not sure which! Along with many loyal Lightroom users, I have been playing with ON1 RAW and just installed the latest RAW update. Had a few issues when I first started to use it so I emailed tech support. A few hours later, I received an email with instructions to update to the latest Graphics driver and try again. They even suggested some settings to change in the graphics driver implementation to improve performance and it works! It simply works. It is not slow by any means and makes Lightroom look positively dead slow. Even Photoshop tools have become slower and are annoying to use now - not so in ON1 RAW. There are still things missing in ON1 RAW holding me back from cancelling my Adobe cloud subscription and making me stay and SUFFER with Lightroom and Photoshop performance because I love some of the features in Lightroom that are not yet implemented in ON1 RAW. I suspect this issue will be resolved eventually and unless we get some relief from Adobe soon, I suspect many of us will be forced to abandon Lightroom and Photoshop in favor of ON1 RAW. As always, Adobe is scarily quiet on this issue which has plagued Lightroom for the last few years. Is it that Adobe does not care? Does Lightroom perform speedily on Windows computers at Adobe? Have they tried the graphics card I am using to see if Lightroom is compatible? Will they even respond?
... View more
‎May 24, 2017
09:42 AM
Okay, so I am confused as well. I have used the scroll wheel to adjust the size of tools for years and now it no longer works. It does work in Lightroom, but not Photoshop. I have tried dozens of combinations of checkboxes in the Prefe>Tools panel all to no avail. I am running CC 2017, up to date with the latest release. Someone at Adobe should tell us if this is design, bug, or what and what we can do as this is a huge impediment to speedy editing.
... View more
‎Nov 24, 2016
03:59 AM
Thanks, I posted the suggestion there!!!!!
... View more
‎Nov 23, 2016
05:04 PM
This feature is great because it saves lots of time when importing photos from my camera or memory cards. Since the settings for Import are "sticky", once this is set up, you can simply forget it and Lightroom does the job every time. Kudos for making this a great feature. There is one issue that I hope the design team will consider resolving... My workflow includes downloading every photo shoot into a new sub-folder (using the sub folder checkbox in the Destination Panel"). The naming convention I use is "YYYYMMDD - Description" as in "20161122 - Jameson Wedding". If it is customer work, these sub-folders are created inside my "Customers" folder. If this is personal, I create these sub-folders inside my "Photo Storage" folder. So, I have hundreds of sub-folders on my storage system and on a separate storage system I have hundreds of folders inside a "Photos Backup" folder. Here is the problem. Recently, one of my students using a similar system with a laptop and 2 external hard drives had a total drive failure on the drive with the "YYYYMMDD-Description" folders. She had followed my training to make backups of all photos using the LR "Make a Second Copy To" method described above. When she obtained a new external drive, she came to me to help restore her original setup so LR would see the photos. Unfortunately, she does several downloads on many days and had none of the original folder names in the backups. The photos from any photo shoots where she did more than one on the day are all mixed up! With hundreds of folders, she needed to spend days trying to divide photos for different photo shoots in a day and then copy photos, create, and and rename the new folders so LR would see the original image files. FINALLY, here is my suggestion: When someone marks the sub-folder checkbox in the destination dialog, the "Make a Second Copy to" logic should create the same sub-folder name inside the backup folder. So, instead of creating: F:\Photo Backups\Imported on Wednesday, November 23, 2016 the modified system would create: F:\Photo Backups\Imported on Wednesday, November 23, 2016\20161123 - Jameson Wedding F:\Photo Backups\Imported on Wednesday, November 23, 2016\20161123 - Jonas Ranch F:\Photo Backups\Imported on Wednesday, November 23, 2016\20161123 - Donkeys at Miller Ridge Farm and so on with the copies of the image files in each... So, even when someone downloads several different events in one day using different sub-folders, the "Make a Second Copy to" system would maintain the folder structure making the recovery process simple and easy. All someone would need to do is grab the folder (e.g. 20161123 - Jameson Wedding) and copy it to the new replacement hard drive. There even could be an additional checkbox in the "Make a Second Copy to" area so anyone that likes the current methodology would not have to follow this path.
... View more
‎Jun 23, 2016
05:41 AM
One has to wonder if Adobe actually looks at these posts and if they do, do they care? I am amazed at the number of bugs/issues/problems with the latest updates, especially the latest memory leak. When the updates came once every 18 months or so, they had time for some extensive testing followed by some beta testing, and all before the general release. Now, the update schedule has become so much more often that perhaps there is not enough testing or beta testing. I spent 30 years in the custom software development business and this level of issues would have surely chased away many of my customers. Adobe has taken a leap with CC by changing the software constantly. Perhaps someone up at Adobe HQ needs to take a deep breath and slow down. Personally, I would rather have fewer new features that actually work correctly spread out over a longer time period than the rapid deployment of poorly tested updates we are getting today.
... View more
‎Jun 22, 2016
10:56 AM
I use Photoshop CC and Lightroom CC on my computer and Photoshop is quite a bit faster in overall performance. In my PS config, my scratch drives are both SSD drives which I am guessing optimizes the PS performance. I have been wondering for a long time why LR does not use scratch drives. I know it uses proxies instead of original images but it seems to me that even with proxies, they could use scratch drives to read ahead and enhance the cache abilities. I optimize my catalogs every time I use them as the box is checked and I backup after every editing session. Recently, I had to create a new catalog and import form a previous catalog to fix a huge speed issue. This worked and made me wonder what is the purpose of optimizing? Why doesn't the program actually do a serious integrity test and repair as well to avoid these issues? Now, there is this memory leak that really slows down the longer you are using Lightroom. I know I can roll back to the prior version but I really do not have time to keep playing around with the software - I just need to do my work. Yesterday (or the day before) I received an email from Adobe telling me there are all these new additions to the Creative Cloud. I am sure all of us would rather they focus on fixing all the issues that exist in the current products before working on adding new products. How can I spend time exploring the new offerings when I am constantly delayed by the software I am currently using. As to Victor's comment about graphics cards, "With GPUs having 4 to 8 GB or RAM today, they should work with the real files." , my card has 12Gb of RAM and the speed with and without the GPU is about the same. Slightly faster with GPU but many things are slower making the overall effect negligible. In conclusion, I love Lightroom and I love Photoshop and many other Adobe products and services. I just wish they would take the comments from long-time users (I started with Version 1 beta) seriously and blame us a little less.
... View more
‎Jun 21, 2016
02:11 PM
I am betting you thought you were done listening to my complaining but unfortunately for you and me, I am back again. As per all the suggestions, I created a new catalog, deleted my preferences and the startup preferences (just in case) and both of these did speed up operations when I first tested them. Now, I have discovered another issue. If I open Lightroom and edit 1-30 images and then exit Lightroom the speed is not too bad. In fact, it is fine! However, when I spend a few hours editing images from a big photo shoot, the speed slowly deteriorates until Lightroom becomes so slow that I would be better off in Photoshop or sending film to the lab. I am going to upload two videos to show the difference. This video is after working for 30+ minutes editing photos: The second video shows the speed after exiting Lightroom, making a backup (with both checkboxes checked), and restarting Lightroom:
... View more
‎Jun 07, 2016
06:00 AM
Yes, I have dozens of smart collections arranged in a few sets. My workflow has me creating a simple smart collection (folder name, 3+ stars, and flagged) for every job I do. The numbers in these collections doesn't ever change after the job processing is done but I keep the collections. I'll play around with this to see if it changes the load speed of some other catalogs. Thanks!!!
... View more
‎Jun 07, 2016
05:20 AM
Yes, all of them as I am using LR since LR 1 beta
... View more
‎Jun 06, 2016
11:54 AM
Okay, it seems that the catalog is the culprit. Preferences made no difference so I put the old ones back... Purging the cache made no difference either... A New catalog with just a few images was okay - performance as you (tshaner) indicated for your computer. In fact, since I use several different catalogs, I have a few with this problem. So, the catalog with the biggest problem (Customers-1) has 53,465 photos. I backup every single time I make any changes to even 1 photo and I always have the optimize catalog and test catalog integrity checkboxes marked - every time! So, I will export my recent work as a new catalog and that should solve this issue. I am not sure why this catalog is so slow but something is wrong. I know 53,000 plus photos is a lot but most of what I have read seems to indicate that LR is okay until somewhere above 75,000 - I guess not! Finally, thanks for all your help and suggestions. Now you know I wasn't just whining about speed which is why I sent the videos.
... View more
‎Jun 06, 2016
11:00 AM
No. It is this slow – period! I am going to try tshaner's suggestions and I'll post something back...
... View more
‎Jun 06, 2016
08:05 AM
Here is another sample. As in the f irst, all images have 1:1 previews
... View more
‎Jun 06, 2016
06:17 AM
Okay, check out this video of my current job editing session.' ' All of the images in the filmstrip have a 1:1 preview created. The original file is on a Drobo connected via USB 3.0 and the catalog and cache are located on SSD. The catalog is on the NVMe super speed drive and the cache is on a standard SSD.
... View more
‎Jun 05, 2016
06:54 AM
You wrote: As I mentioned previously what is your definition of "noticeable delay" in specific numbers (i.e. seconds)? ~1-5 seconds zooming and ~1-3 seconds when going through the filmstrip image by image. Not any faster or slower than in my original Z210 workstation with considerably fewer resources. An interesting phenomenon is that as I scroll through the filmstrip, I select an image, move to the next image and wait for it to clear. If I then return to the previous image, it is already clear. If, however, I select an image and wait for clear, move to the next image and wait for clear, then move to a third image and wait for clear, and finally move back two images to the first one I selected, I again need to wait for it to clear. My cache is 20Gb and it is located on a 1Tb SSD drive. Also what specific camera file(s) are you using? On my modest i7-860 system with a single 2560x1440 display using Canon 5D MKII CR2 21Mp raw files Zoom from Fit to 1:1 view takes ~1.0 sec. to a fully sharp image. I don't consider that slow or unacceptable. I am using 42Mb NEF RAW from a Nikon D5. As for what is acceptable, my entire issue is that I went from an 11 year old computer which by today's standards had a slow CPU(3.1), slow RAM (1300), and 2Gb slow video card on a PCIe Version 2 motherboard to a new unit with a super clocked CPU(3.8-4.0), super fast RAM (2400), the fastest GeForce Graphics card available with 12Mb RAM, on a PCIe Version 3 motherboard and the Lightroom performance is really about the same. Every other application I use including Photoshop CC is dramatically faster in every way but not Lightroom. Do not confuse my criticism with dislike for either Lightroom or Adobe because I am a big fan but something is terribly wrong in the Lightroom software. I us ACDSee and ACDSee PRO & Ultimate occasionally (I teach classes in Photoshop, Lightroom, and ACDSee) and it has benefited dramatically from my new computer where Lightroom has not. What is the difference in Zoom time to fully sharp with 'Use Graphics Processor' checked and unchecked? Are you using LR with dual displays (i.e. Second Window open on 2nd display)? If so is zooming faster with the Second Window closed (i.e. single display)? No significant difference in time with or without the GPU. The only difference when using the 2nd display for window 2 is if I zoom in either one and wait for it to clear, there is no delay when I zoom on the other display. If I close window 2 completely, there is no change in speed. In conclusion, I am as big a fan as you are and only want Lightroom to succeed and grow. I am voicing what I feel are legitimate issues that get no comments, help, solutions, or admissions from Adobe. I am using Photoshop for many years (version 3) and Lightroom since the beta for version 1. Through my classes, I am responsible for hundreds of Lightroom and Lightroom CC users over the last 4-5 years and will continue to support the software as long as it continues to meet the needs of serious photographers. All I want is for it to work properly and with no discernible speed change from my prior computer to this one (other than those mentioned in the prior email that result from faster SSD storage) it seems like something is wrong somewhere. I am sure you noticed the hundreds of comments on speed from other users. It is somewhat unlikely that we are all wrong. As I said before, I await the next version of Lightroom hoping they will continue to improve the code for the GPU enhancement, the overall speed, and especially speed for the rest of the editing tools.
... View more
‎Jun 04, 2016
05:38 AM
Hi, Sorry it has been 4 weeks since I responded but I had a considerable amount of trouble with the HP Z640 forcing me to finally return it and get something different. The detailed specs of my new unit (shown from Lightroom) are below but basically this is the sort version of the specs. Core i7 6-Core 3.3Ghz Overclocked to 3.88Ghz - Supercooled, 64Gb 2400msec Ram, 1.2Tb Intel NvMe Super Speed PCIe SSD Main Drive (software and catalogs here), 1Tb Second Internal Drive (Photoshop Scratch here), GeForce GTX TITAN X/PCIe/SSE2 with 12Mb Onboard Graphics Memory. Using the speed tests available at http://cpu.userbenchmark.com/ , my pc shows up as a nuclear submarine in their speed vernacular with these details: UserBenchmarks: Desk 110%, Game 112%, Work 97% CPU: Intel Core i7-5820K - 94% GPU: Nvidia GTX Titan X - 119.4% SSD: Intel 750 Series NVMe PCIe 1.2TB - 186.8% SSD: Intel SSDSC2KW010X6 1TB - 97.5% USB: Drobo 5D 17.5TB - 77.2% USB: USB 3.0 Drobo S - Gen 2 9TB - 47.9% RAM: Unknown 8x8GB - 114% MBD: Asus X99-A/USB 3.1 It may be interesting to note that everything I do is extremely fast including Lightroom but Lightroom is not noticeably faster in Develop mode than before. These improvements are obviously related to the faster speed of the computer and have nothing to do with the GPU. The entire reason for getting the new computer was to take advantage of the new GPU enhancements in Develop mode since my old Z210 workstation was limited as it only had PCIe V2 and all the new and more powerful Graphics cards are V3. The reason I switched this newest workstation from the M4000 to the GEforce Titan is some research showing that this card was indeed faster in almost every test and since I was trying to maximize speed I switched Graphics cards. For monitors, I have an LG 27EA63 IPS LED display and an LG 27M67HQ IPS LED display - both connected via HDMI and Yes, both monitors are calibrated using Spyder 5 Elite. Yes, of course I am aware that GPU is only enabled in Develop and only for certain functions and they seem to work okay except for zooming which I would think should be instant but there is a noticeable delay after zooming until the display clears with full resolution. If I was using 4k displays, I am guessing this would be much worse.. Anyway, I await the next version of Lightroom hoping they will continue to improve the code for the GPU enhancement especially for the rest of the editing tools. Specs shown from Lightroom: Lightroom version: CC 2015.5.1 [ 1073342 ] License: Creative Cloud Operating system: Windows 10 Version: 10.0 Application architecture: x64 System architecture: x64 Logical processor count: 12 Processor speed: 3.3 GHz Built-in memory: 65447.0 MB Real memory available to Lightroom: 65447.0 MB Real memory used by Lightroom: 535.1 MB (0.8%) Virtual memory used by Lightroom: 477.2 MB Memory cache size: 239.8 MB Maximum thread count used by Camera Raw: 12 Camera Raw SIMD optimization: SSE2,AVX,AVX2 System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1920x1080, 2) 1920x1080 Input types: Multitouch: No, Integrated touch: No, Integrated pen: Yes, External touch: No, External pen: Yes, Keyboard: No Graphics Processor Info: GeForce GTX TITAN X/PCIe/SSE2 Check OpenGL support: Passed Vendor: NVIDIA Corporation Version: 3.3.0 NVIDIA 368.22 Renderer: GeForce GTX TITAN X/PCIe/SSE2 LanguageVersion: 3.30 NVIDIA via Cg compiler Application folder: C:\Program Files\Adobe\Adobe Lightroom Library Path: P:\Lightroom\Drive G - Assorted\Drive G - Assorted-2-2-2.lrcat Settings Folder: C:\Users\joelw\AppData\Roaming\Adobe\Lightroom Installed Plugins: 1) Canon Tether Plugin 2) ColorChecker Passport 3) Facebook 4) Flickr 5) Leica Tether Plugin 6) Nikon Tether Plugin 7) ON1 Effects 10 8) ON1 Enhance 10 9) ON1 Photo 10 10) ON1 Portrait 10 11) ON1 Resize 10 Config.lua flags: None Adapter #1: Vendor : 10de Device : 17c2 Subsystem : 29903842 Revision : a1 Video Memory : 12175 Adapter #2: Vendor : 1414 Device : 8c Subsystem : 0 Revision : 0 Video Memory : 0 AudioDeviceIOBlockSize: 1024 AudioDeviceName: Speakers (2- Realtek High Definition Audio) AudioDeviceNumberOfChannels: 2 AudioDeviceSampleRate: 44100 Build: LR5x102 Direct2DEnabled: false GPUDevice: not available OGLEnabled: true
... View more
‎May 09, 2016
09:59 AM
I have had the GPU turned off on My HP Z210 Workstation with the Graphics shown below. I decided to upgrade to take advantage of the GPU for Lightroom CC and Photoshop CC so I bought a new HP Workstation with details shown below as well. After testing, I see no improvement in Lightroom CC and Photoshop CC is worse with it on than off. Considering the unit I purchased, I expected blazing speed (which I see in all other applications) and it simply is not happening. Everything else I do is super fast and considerably faster than my old workstation. It may be important to note that both LR and PS load much, much faster on the new unit. Now what??? OLD: HP Z210 Workstation - Win 10 64 bit - 16gb Ram, 3.4Ghz Core i7 Processor (4 core), 500Gb HD 7200RPM System Drive, Separate 1Tb 7200RPM scratch drive for PS, USB 3.0 Drobo for Photos. Graphics Processor Info: Check OpenGL support: Failed Vendor: ATI Technologies Inc. Version: 3.3.12002 Core Profile Context 9.12.0.0 Renderer: AMD Radeon HD 5500 Series LanguageVersion: 4.20 GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS (actual = 32, minimum = 48) NEW: HP Z640 Workstation - Win 10 Pro 64 bit, 64gb Ram, 3.7Ghz Xeon V3 Processor (8 core), 1Tb Turbo SSD System Drive, Separate 1Tb 7200RPM scratch drive for PS, USB 3.0 Drobo for Photos. Graphics Processor Info: Quadro M4000/PCIe/SSE2 Check OpenGL support: Passed Vendor: NVIDIA Corporation Version: 3.3.0 NVIDIA 358.87 Renderer: Quadro M4000/PCIe/SSE2 LanguageVersion: 3.30 NVIDIA via Cg compiler
... View more
‎Mar 21, 2016
04:56 AM
It seems counter-intuitive to have DeHaze in Effects. Effects are things one might apply to create a "special effect" on an image that has already been tweaked to perfection. DeHaze is a mainstream correction that might need to be applied as one of the first adjustments in the tweaking process. Having the DeHaze Slider in the "Presence" section seems like the perfect place as if Clarity is part of "Presence", then certainly DeHaze belongs there as well. As Lars has indicated, in local adjustments it is already next to Clarity so it is time to move it in the main edit panels as well.
... View more
‎May 19, 2015
11:44 AM
Okay, here is some other information that might be helpful. I have an AMD Radeon 5500 Graphics Card (1 Gig) on an HP workstation with a 3.2Ghz Processor and 16Gig RAM. I have been getting "Graphics Processor disabled due to errors" and the develop module performance was slightly slower than LR 5.7 I came across this link https://helpx.adobe.com/lightroom/kb/lightroom-amd-graphics-cards.html After reading this page, I uninstalled the new drivers and reinstalled the prior 14.4 video driver from AMD. I restarted LR CC and no more Graphics Card errors. I tried a few things in the develop module and they really are quite a bit faster but not everything. The brush rendering is fast, the crop tool is slower. Image to image movement in the filmstrip is slower. Changes made in the Basic Panel and the Details Panel are fast. Overall, I think most things are a little slower than LR 5.7 except for those things I mentioned above. Another curious thing is why Adobe removed the ability to apply develop presets when you select a group of images and then right-click and choose "Develop Settings" can paste from previous but now I can no longer apply one of my user created presets this way. Why remove this?
... View more
‎May 14, 2015
09:43 AM
I originally installed CC on my HP Laptop while on a trip shooting many photos (Catalog for trip has 8500 RAW images). I needed to turn off the Graphics Processor Option or the develop performance was too slow to use. Switching from image to image took 5 times as long as w/o GCPU, Using the crop tool took 4 times as long as w/o GCPU just to show the bounding grid, etc. I decided to turn off GCPU so it would work faster and it did in fact work better. The other develop tools (brush, spot correction, etc.) seem to be about the same speed as LR5.7. When I returned home, I installed LR CC on my HP Workstation. I copied the RAW photos to my DROBO (USB 3) and the Catalog to a second DROBO (USB 3). I had no BSOD's or other crashes but it seems like LR CC does not like my video board. The preferences tab tells me there is an error. This is strange because I also am running Photoshop CC and it seems to be okay with my graphics option. Before buying my Laptop, I checked the Adobe website and selected a compatible video at extra cost to make sure I would be okay. When I upgraded to Photoshop CS6 (before I joined the cloud) I upgraded my video card in my HP Workstation so it would be okay with the improved graphics. Now, I am not sure what to do as there has been no response at all from Adobe. I currently teach classes in both Photoshop and Lightroom software and I have advised everyone on my student mailing list (over 300 students) to stay with LR 5.7 and not upgrade for fear of them having issues after they upgrade. Where do we go from here? I am a big fan of Adobe (Using Photoshop since version 3 - not CS3 just plain 3 & Lightroom since version 1) and I am okay if this is a bug, I am okay if this is something else, I am just NOT OKAY wondering what is going on and what is being done to help all of us loyal Adobe customers. All of us (or most of us) are willing to accept a problem if it exists and wait for the solution but it is extremely difficult to sit here wondering what is wrong and what to do. If we all need to go out and buy new video cards, that is not a great thing but then you should have told us this before we upgraded. Adobe, please communicate with us so we can remain your loyal supporters! //----------- Laptop Specs --------------------------- • Windows 8.1 64 • 4th generation Intel(R) Core(TM) i7-4510U Dual Core Processor + 4GB NVIDIA GeForce GTX 850M Graphics • 17.3-inch diagonal Full HD WLED-backlit Display (1920x1080) Touchscreen • 16GB DDR3L System Memory (2 Dimm) • 1TB 5400 rpm Hybrid Hard Drive • No Additional Office Software • Security Software Trial • 4-cell 48WHr Lithium-ion Battery • Blu-ray writer and SuperMulti DVD burner • Backlit Keyboard with Fingerprint Reader • HP TrueVision HD Webcam with Dual Digital Microphone • Intel 802.11ac WLAN and Bluetooth(R) [1x1] // ------------- Desktop Specs from LR CC ------------------------ Lightroom version: CC 2015.0.1 [ 1018573 ] License: Creative Cloud Operating system: Windows 7 Home Premium Edition Version: 6.1 [7601] Application architecture: x64 System architecture: x64 Logical processor count: 4 Processor speed: 3.3 GHz Built-in memory: 16342.0 MB Real memory available to Lightroom: 16342.0 MB Real memory used by Lightroom: 1137.3 MB (6.9%) Virtual memory used by Lightroom: 1109.8 MB Memory cache size: 126.3 MB Maximum thread count used by Camera Raw: 4 Camera Raw SIMD optimization: SSE2,AVX System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1920x1080 Input types: Multitouch: No, Integrated touch: No, Integrated pen: No, External touch: No, External pen: No, Keyboard: No Graphics Processor Info: Check OpenGL support: Failed Vendor: ATI Technologies Inc. Version: 3.3.12002 Core Profile Context 9.12.0.0 Renderer: AMD Radeon HD 5500 Series LanguageVersion: 4.20 GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS (actual = 32, minimum = 48) Application folder: C:\Program Files\Adobe\Adobe Lightroom Library Path: P:\Lightroom\20150415 - Australia & South Pacific Cruise\20150415 - Australia & South Pacific Cruise-2.lrcat Settings Folder: C:\Users\Joel Weisbrod\AppData\Roaming\Adobe\Lightroom Installed Plugins: 1) Behance 2) Canon Tether Plugin 3) ColorChecker Passport 4) Facebook 5) Flickr 6) Leica Tether Plugin 7) Nikon Tether Plugin 8) Perfect B&&W 9 9) Perfect Effects 9 10) Perfect Enhance 9 11) Perfect Photo Suite 9 12) Perfect Portrait 9 13) Perfect Resize 9 Config.lua flags: None Updated Toolkit: Adobe Camera Raw 9.0 for Lightroom 6.0 (build 1014445) Updated Toolkit: Book Module 6.0 (build 1014445) Updated Toolkit: Develop Module 6.0 (build 1014445) Updated Toolkit: Import Module 6.0 (build 1014445) Updated Toolkit: Library Module 6.0 (build 1014445) Updated Toolkit: Map Module 6.0 (build 1014445) Updated Toolkit: Monitor Module 6.0 (build 1014445) Updated Toolkit: Print Module 6.0 (build 1014445) Updated Toolkit: Slideshow Module 6.0 (build 1014445) Updated Toolkit: Web Module 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.AgNetClient 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.AgWFBridge 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.Headlights 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.LibraryToolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.MultiMonitorToolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.archiving_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.bridgetalk 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.catalogconverters 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.cef_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.coretech_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.curculio 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.discburning 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.email 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.export 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.ftpclient 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.help 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.iac 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.imageanalysis 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.layout_module_shared 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.pdf_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.sdk 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.sec 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.socket 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.store_provider 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.substrate 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.ui 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.video_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.xml 6.0 (build 1014445) Updated Toolkit: com.adobe.wichitafoundation 6.0 (build 1014445) Adapter #1: Vendor : 1002 D
... View more
‎May 03, 2015
01:10 PM
Okay, I get it but I simply don't get it! I am using an HP Envy Laptop, less than one year old with the upgraded video board package (Intel HD 4400) With Graphics accelerator turned on, the performance makes the software almost unusable. If I click on the crop tool, the screen goes black and then a few seconds later the image comes up with the crop box. When I click the next photo arrow in the filmstrip bar it is really slow displaying the next photo. I am comparing these speeds to the performance of LR 5.7 on the same computer. My LR 5.7 has the graphics option turned ON. When I turned off the graphics accelerator option and restarted LR CC, the speed was back to normal. I guess I can use it with this setting off but wonder why the accelerator on a new computer makes the performance suffer. I read your comments but we should be able to do better!!! Here are the specs from my pc. Lightroom version: CC 2015.0.1 [ 1018573 ] License: Creative Cloud Operating system: Windows 8.1 Home Premium Edition Version: 6.3 [9600] Application architecture: x64 System architecture: x64 Logical processor count: 4 Processor speed: 2.5 GHz Built-in memory: 16314.1 MB Real memory available to Lightroom: 16314.1 MB Real memory used by Lightroom: 292.2 MB (1.7%) Virtual memory used by Lightroom: 241.1 MB Memory cache size: 0.0 MB Maximum thread count used by Camera Raw: 2 Camera Raw SIMD optimization: SSE2,AVX,AVX2 System DPI setting: 96 DPI Desktop composition enabled: Yes Displays: 1) 1920x1080 Input types: Multitouch: Yes, Integrated touch: Yes, Integrated pen: No, External touch: No, External pen: No, Keyboard: Yes Graphics Processor Info: Intel(R) HD Graphics 4400 Check OpenGL support: Passed Vendor: Intel Version: 3.3.0 - Build 10.18.10.3496 Renderer: Intel(R) HD Graphics 4400 LanguageVersion: 3.30 - Build 10.18.10.3496 Application folder: C:\Program Files\Adobe\Adobe Lightroom Library Path: C:\Users\Joel\Pictures\Lightroom Catalogs\Lightroom Default\Lightroom Default-2.lrcat Settings Folder: C:\Users\Joel\AppData\Roaming\Adobe\Lightroom Installed Plugins: 1) Behance 2) Canon Tether Plugin 3) Facebook 4) Flickr 5) Leica Tether Plugin 6) Nikon Tether Plugin 7) Perfect B&&W 9 8) Perfect Effects 9 9) Perfect Enhance 9 10) Perfect Photo Suite 9 11) Perfect Portrait 9 12) Perfect Resize 9 Config.lua flags: None Updated Toolkit: Adobe Camera Raw 9.0 for Lightroom 6.0 (build 1014445) Updated Toolkit: Book Module 6.0 (build 1014445) Updated Toolkit: Develop Module 6.0 (build 1014445) Updated Toolkit: Import Module 6.0 (build 1014445) Updated Toolkit: Library Module 6.0 (build 1014445) Updated Toolkit: Map Module 6.0 (build 1014445) Updated Toolkit: Monitor Module 6.0 (build 1014445) Updated Toolkit: Print Module 6.0 (build 1014445) Updated Toolkit: Slideshow Module 6.0 (build 1014445) Updated Toolkit: Web Module 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.AgNetClient 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.AgWFBridge 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.Headlights 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.LibraryToolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.MultiMonitorToolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.archiving_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.bridgetalk 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.catalogconverters 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.cef_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.coretech_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.curculio 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.discburning 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.email 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.export 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.ftpclient 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.help 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.iac 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.imageanalysis 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.layout_module_shared 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.pdf_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.sdk 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.sec 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.socket 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.store_provider 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.substrate 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.ui 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.video_toolkit 6.0 (build 1014445) Updated Toolkit: com.adobe.ag.xml 6.0 (build 1014445) Updated Toolkit: com.adobe.wichitafoundation 6.0 (build 1014445) Adapter #1: Vendor : 8086 Device : a16 Subsystem : 228e103c Revision : b Video Memory : 0 Adapter #2: Vendor : 10de Device : 1391 Subsystem : 228e103c Revision : a2 Video Memory : f92 Adapter #3: Vendor : 1414 Device : 8c Subsystem : 0 Revision : 0 Video Memory : 0 AudioDeviceIOBlockSize: 1024 AudioDeviceName: Speaker/HP (Realtek High Definition Audio) AudioDeviceNumberOfChannels: 2 AudioDeviceSampleRate: 44100 Build: Uninitialized Direct2DEnabled: false GPUDevice: not available OGLEnabled: true
... View more
‎Dec 10, 2013
06:57 PM
2 Upvotes
The link in your post errors as Not Found!
... View more
‎Dec 10, 2013
06:56 PM
15 Upvotes
I have an Education License for CC. I actually teach Adobe Photoshop and Adobe Lightroom. I find the need to be able to teach users of Elements as well and think Elements should be available to cloud members. If the separate install is an issue, create a special license code for cloud members so we can run the install and use Elements for as long as our cloud membership is valid.
... View more