nu-b
Explorer
nu-b
Explorer
Activity
‎Jan 17, 2024
08:15 AM
1 Upvote
This actually works! After dragging the image window (grabbing the tab bar) to the second screen, I replaced step 3 above (maximize) with Window > Arrange > Tile and then zoom in. It preserves the status line and bottom scrool bar. Thank you.
... View more
‎Nov 25, 2022
02:57 PM
This has become a pretty standard sequence for me when doing certain types of PS operations. Open a non-raw image from Bridge into Photoshop on 1st (left) screen Grab the image window tab and drag it over to the 2nd (right) screen Maximize the window on the 2nd screen Perform a zoom operation (in or out, happens either way) The bottom scroll bar disappears. If the image is zoomed in sufficiently that it doesn't fit within the screen, you can't quite scroll to the bottom. This has happened to me with both matched 1200x1920 monitors, and matched 4K monitors. It's been going on for some months; I don't recall when it started. Configuration: Windows 10 Intel Core I9 9900K 32GB RAM NVIDIA GeForce RTX 2070 Super video card All files on an NVMe SSD
... View more
‎Dec 21, 2020
04:26 PM
System has teo NVMe drives. Catalog/images are on one; program and camera raw cache are on the other. I've been using this setup for nearly two years, and the problem occurs only with LR 10.1.
... View more
‎Dec 18, 2020
03:48 AM
I've noticed something similar on Windows, though it only freezes once, about 15-20 seconds after start-up. I went back to LRC 10.0 and it works fine. https://community.adobe.com/t5/lightroom-classic/lr-classic-10-1-freezes-after-startup-for-about-10-15-seconds/td-p/11687878?page=1
... View more
‎Dec 17, 2020
08:20 AM
This started happening with LR classic 10.1 on Windows. Does not happen with 10.0, so I've downgraded back to that version. LR (10.1) starts up normally and runs fine for about 15-20 seconds. Then it completely freezes for about 10-15 seconds. After that it's fine. During the freeze, CPU usage is way up, but it appears the GPU is not being used. This happens every time I start it in 10.1, single or dual monitors, GPU turned on or off. System: two 4K monitors, Intel i9 9900K, 32gb RAM, GeForce RTX 2070 super. Program, catalog, images and cache are all on NVMe drives.
... View more
‎Mar 12, 2019
08:47 AM
1 Upvote
I see Photoshop CC 20.0.4 was released yesterday. Unfortunately no update to LR or ACR.
... View more
‎Mar 04, 2019
08:04 AM
My understanding is that camera manufacturers make new raw file specs available before the camera release date. In the case of the EOS 5Ds, Adobe released Camera Raw 9.0 (with support for the 5Ds) in April 2015, while the camera wasn't available until June 2015. I got mine 5Ds on the release data and was able to immediately process photos in LR and Camera Raw. I wonder why this hasn't happened with the RP.
... View more
‎Feb 12, 2019
03:46 PM
Thank-you for the suggestion. It sounds like what I need to do. Unfortunately, I seem unable to post there. After clicking on Sign In to Post (I'm already logged in to my Adobe account in the browser) it gives a choice of a number of sign-in methods. I click on the first one (Photoshop Family) and a separate window pops up saying I have successfully signed in. But the small sign-up pop-up remains visible underneath and it never posts. I'll try to figure it out tomorrow when I have more time.
... View more
‎Feb 12, 2019
02:07 PM
FWIW I've started looking into this again. It seems worse in a two-monitor setup and doing a shift+click to select a range of photos. The chances if it selecting the correct range if you move the mouse immediately after the shift+click is pretty low. Turn off the 2nd monitor and the success rate is higher. This is UI 101 and I'm disappointed that Adobe isn't interested in fixing this blatant bug. Time to start investigating darktable to see if it's any better.
... View more
‎Nov 26, 2018
06:10 AM
bhousto90​: I think you're describing something different. What happens for me about 50% of the time is that I click (press and release) on an image and then immediately move the mouse. LR does not select the desired image, but instead selects the image wherever the mouse pointer happens to be ~1 second later. So, it's pretty random what actually gets selected. This cannot be construed as "as designed". It is incorrect UI implementation.
... View more
‎Nov 24, 2018
11:59 AM
I tried resetting preferences, as you suggested. Big mistake. Not only is the selection problem still there, but now I have to change everything to make LR usable again.
... View more
‎Nov 24, 2018
11:55 AM
I find it hard to believe that LR could somehow influence the OS or mouse driver in such a way that it wouldn't be LR's fault. Nonetheless, I tried a fresh battery in the wireless mouse and also tried a wired mouse. Neither made any difference. I also ran system monitor while doing selections and neither CPU nor memory use got above 20%. And other programs do not exhibit selection delays, even when LR is running. I've also run CPU-intensive multi-threaded programs on this computer mouse behaviour is not affected. Finally, I do experience the same behaviour on my laptop. So, I think this falls squarely in Adobe's lap.
... View more
‎Nov 24, 2018
07:55 AM
This appears to be a UI bug on Windows that is causing me enormous frustration and errors. In any app that allows mouse selection, it is common to mouse click and then move to a button, menu etc. Or, shift+click and then move to perform an action. Because of the poor performance of LR, it is quite common to move the mouse before LR gets around to processing the click. When you click the mouse button to select a image (or shift+click to mark the end of a range of selected images), there is sometimes a ~1 second lag before LR responds to the event. That in and of itself is not a bug. However when LR gets around to processing the click event, it appears to read the current mouse coordinates, rather than those packaged with the event. If you have moved the mouse after clicking, it will select the wrong image. This has caused me to incorrectly tag images, and sometimes inadvertently delete the wrong image. The machine is fairly high-end (Core-i7 with 8 physical cores; 32gb RAM; GeForce GTX 1060 video card with 6gb; system, catalog and cache all on SSDs). I have performed all the performance tricks suggested by Adobe. My catalogs typically have 5,000-10,000 images. I am seriously considering looking at alternatives because of the frustration caused by this bug. Are there any suggestions out there, or is there some way to get Adobe to fix this bug? Thanks
... View more
‎Jan 16, 2018
08:00 AM
Thank-you for your reply. It certainly makes perfect sense to operate on only the target photo if the selection is not visible. However, the situation here is somewhat different. If in (library) grid mode on the PRIMARY monitor, changes apply to all selected photos. If in (library) grid mode on the SECONDARY monitor, changes apply only to the "most selected" photo. In both cases the entire selection is visible (unless it scrolls off the screen). This may be as designed if you look at it this way: Because the LR two-screen implementation is a bit of a hack (i.e., not fully implemented), moving grid mode to the secondary screen does not move the controls (menus, panels) to that screen. It also puts the primary screen in (library) loupe mode. In loupe mode, changes apply only to the single target photo. In other words, what's visible on the secondary screen is immaterial to changes made on the primary one. I'm not going to pursue this further based on the above understanding. Nonetheless, I still find this behaviour extremely confusing.
... View more
‎Jan 15, 2018
04:32 PM
I have trouble believing that it was designed this way. With over 40 years in the IT industry, I've never seen a UI that allows multiple selection but operates on only the first item selected. The film strip in Bridge handles multiple selection properly.
... View more
‎Jan 15, 2018
12:17 PM
My apologies if this has been asked and answered already; I couldn't find anything. I saw a helpful Adobe video on using two monitors. If you hit Shift+G it opens library grid mode on the second monitor and the 1st monitor goes to loupe display. However, if you then select multiple photos in the grid and make a change (e.g., add keyword, delete photos) it applies only to the first one you selected. You have to make such changes one at a time, or move the grid display back to the primary monitor.
... View more
‎Apr 13, 2010
09:45 AM
Well, I'm feeling pretty stupid right about now. I inherited this code and perhaps haven't learned it as well yet as I should. It turns out that there was an old version of textLayout.swc in one project's lib folder. After removing that, it runs fine. Many thanks for your help Richard and Robin.
... View more
‎Apr 13, 2010
06:50 AM
Thanks for your quick reply Richard. Unfortunately though, the problem still happens even after removing the workspace .metadata directory and doing a full clean/rebuild. It happens both when launched from FB4 for debugging, and when opening a Web page with the SWF embedded, in the browser. The problem occurs very early in the launch process. It's not possible to debug beyond the error, but if simply opened in the browser, I can dismiss the error message and the app largely works. FYI, here is the stack dump: VerifyError: Error #1053: Illegal override of exportXMLAttributes in flashx.textLayout.conversion.FXGExporter. at flash.display::MovieClip/nextFrame() at mx.managers::SystemManager/deferredNextFrame() at mx.managers::SystemManager/preloader_preloaderDocFrameReadyHandler() at flash.events::EventDispatcher/dispatchEventFunction() at flash.events::EventDispatcher/dispatchEvent() at mx.preloaders::Preloader/timerHandler() at flash.utils::Timer/_timerDispatch() at flash.utils::Timer/tick() Thanks, Rich
... View more
‎Apr 12, 2010
08:17 AM
Well, I'm seeing this after moving from Beta 2 to released FB 4. I've grep'ed for both exportXMLAttributes and FXGExporter, and neither exist in our code. Happens on two different machines with FB4 installed. Flash player 10,0,45,2; Firefox 3.5.9, Windows 7 64-bit. Any suggestions anyone...? Thanks, Rich
... View more