Dude, just shut up already you're just being a d1ck. You're just trolling
people (including me) and you're not providing anyone any helpful
information except posting the adobe LR4.1 link. Which I might add is in
the adobe site already.
You can post as much as you want from the other thread, but until a fix is
actually released, you're not doing any good here. You may be filling your
ego by talking down to everyone here, but seriously, other than that,
you're not doing nothing helpful. If you want to offer up your technical
expertise, please by all means go back to that other thread and help them
there.
You have brought no one in this forum, any closer than where we already
are. No 'new' information provided by you solves anything nor does it help
any of us with workarounds. Neither does you talking down to us or posting
info from the other thread.
There is a lot of frustration apparent and while it is understandable please make sure that we keep in mind the forum guidelines.
The Lightroom team are working hard on the issues that have arisen in Lr4 and do appreciate informative responses.
Geoff the kiwi wrote:
There is a lot of frustration apparent and while it is understandable please make sure that we keep in mind the forum guidelines.
Right. But at least with the great new forum interface it's not clear who is being insulted ![]()
Exactly!!acresofgreen wrote:
Geoff the kiwi wrote:
There is a lot of frustration apparent and while it is understandable please make sure that we keep in mind the forum guidelines.
Right. But at least with the great new forum interface it's not clear who is being insulted
Their working hard on it but they have our money don't they Geoff?
Maybe this is a little of guided but I didn't think it was a deposit for Lightroom that I paid for.. Adobe advertised a complete working product. I didn't recieve the product as promised.
No matter how you put it.. I am have less funds and still no product.
We can try and bang our heads togather and come up with a soloution but for crying out loud isn't that defiying the purpose of buying the program in the first place? needs
Adobes needs to man up and honour their wrnty they give when they sell their products.
DNJphoto wrote:
Their working hard on it but they have our money don't they Geoff?
Maybe this is a little of guided but I didn't think it was a deposit for Lightroom that I paid for.. Adobe advertised a complete working product. I didn't recieve the product as promised.
No matter how you put it.. I am have less funds and still no product.
We can try and bang our heads togather and come up with a soloution but for crying out loud isn't that defiying the purpose of buying the program in the first place? needs
Adobes needs to man up and honour their wrnty they give when they sell their products.
EXACTLY!
I agree, uphotography, and DNJ
Thanks for being the thought police Geoff reminding us all to mind our P's and Q's
Aside of rules, guidelines and the like, most posters have paid to upgrade to a piece of software that is not functioning properly, is buggy and is slow. "Adobe are working on things" so we are told by people in the know(?) - you, Lee Jay and a few others who've taken on the role of advising in the absence of feedback and communication from adobe.
This is a public forum, so peoples views, opinions and comments, groans and frustrations are expected and needed, valued maybe and even taken under consideration.
polite policing does not help, rather feedback and communication from Adobe in the form of what they are planning to do to help those who've invested in a product that should not have been released as a public beta let alone paid for.
Lee Jay...I haven't posted in a while but still listening to this stream and the adobe labs one... I stick by my earlier point about the fact that it is not helpful whatsoever any more for people to post their experiences and provide input because there is no standard input 'form' being requested by Adobe. How can you diagnose a problem and trouble shoot it when noone provides the SAME base information that Adobe needs... We all 'think' we are providing adobe the right information to diagnose but are we? What EXACTLY does Adobe want to know about our configs/operating environment to run diagnostics, root cause, etc... WHO THE HE** KNOW! CPU? OS? RAM? Cache location? All guesses...some great guesses mind you from from very smart users, but without GUIDANCE from Adobe we're fishing for paper clips in the ocean. Just my 2 cents....I'll remain on 3.6 until fixed... (and my 5D MII...my new $3800 5D MIII is collecting dust at the moment beacause I can't process my *&^%!@&! RAW files!!!!)
Or maybe they know exactly what is causing the problem. In software
development, sometimes the difficulty is not in finding what exactly is
triggering a problem, but how to solve it. in a case like that, additional
bug reports are unnecessary.
This is a private communication sent from my mobile device. If you are not
the intended recipient, please delete this message from both your email and
your memory banks.
Okay all "oneupping aside", I am back to my basic question. I'm a professional photographer, and nowhere near the tech level of most of the people I'm listening to on this forum. Here is what I'm hoping to get answers for:
I had to upgrade to LR4 because LR3 won't open the files shot with my new Nikon D4, which I had to purchase after all my equipment was stolen in December, so it made sense to get the newest and best camera I could afford. I have about 50,000 images in my catalog (I'm unclear on whether that matters or not in terms of speed). I've been using LR since version 1 and using LR4 with these new files (yes, RAW, of course RAW) is unbearably slow in every way. Waiting for each image to "focus" to edit takes way too long, as do the rest of the adjustments. I can't shoot tethered with this camera either. I found a workaround with a free download called Sofortbild, or something like that, for my D700, but alas it doesn't recognize the D4 either. So now I have this sweet camera and new LR software and I feel like I'm in the dark ages.
There has been a lot of discussion about cache size and location. I have no idea where mine is or how to find it.
Am I just screwed until adobe fixes the issues with LR 4 and the nikon D4 compatibility? Do I have to shoot with my lesser D700 till then?
Thanks.
Lynne
I would say yes, you are screwed until its fixed...unless you opt for Plan B which is to ingest in LR4, convert to DNG then edit in 3.6....which I simply won't do beause its a PITA! Also, if you haven't already, pls post your experience/complait in the form that Adobe watches and add you name to the list here: http://feedback.photoshop.com/photoshop_family/topics/lr4_0_reacts_ext remely_slow
This is not going to get us anywhere - but what has so far?
There are several IT gurus around here. Can one of you explain why Adbobe cannot 'borrow' one of the machines reporting no speed problems, borrow one with them, and work out where they differ? Damn it all. The USA is not that huge. Surely FedEx could get both to the same lab room within 24 hours.
It is years since I wrote crude progams in dBase 2 - but in those days we could put them into debugging mode and see where they were failing. I know that these days software is significantly more complicated but surely diagnostics must have moved on as well.
The Lightroom software team must have dozens of machines running LR. Surely not every single one of them is glitch free?
I have a cynical view that there is some beancounter at the top saying 'no more money on this - we must move on'. But that is a view of a cynic who used to be a beancounter myself before retiring.
IT man - tell me what you can't put a working and non working LR installation side by side and puzzle out why they perform differently, please?
Tony
Consider the hyena, it is a strange animal.
The evolutionary path the hyena has lead is slowly killing the breed. All too soon, they will be no more. They have barked up the wrong tree so to speak, evolved in a direction that imposes such stress on the beast, that it simply can't go on, they are evoling themselves to death.
The structure and shape of a Hyena has made the next generation harder to develop, harder to carry to term and very often the offspring causes so much damage to the mother, often killing them, no wonder they bark and howl like banishees.
Feel free to swap the word replace the word Hyena with...
Being a software engineer on numerous commercial projects I can tell you that it is not up to the IT guru. No more changes are allowed after the business has signed off on the product with exception of bug fixes. If you look at all of Adobe's change logs they only fix functionality related bugs. Performance is not considered functionality by Adobe and it is shown by their track record of each new bloated release (Photoshop, Acrobat, Lightroom). Not to mention optimisation requires more expertise and money than say, building the DVD burning module. Which one will the business choose?
When performance really becomes a problem, it is too late. The IT gurus will tell the business it wil cost millions to redesign, rewrite, retest the existing code, and the business will simply say "No, we wlll go with a temporary fix and push up the system requirements".
Mmm.. Juw177 how far are they going to push the System requirments up?
I'm currently on a $10k single PC setup and it is beyond frustrating when open 100 raw files quicker in Photoshop CS6 and review them as opposed to Lightroom 4, 4.1, 4.2 etc.
My current specs: I7 2600K @ 4.5Ghz, 32Gb 1866Mhz DDR3, GTX570 Graphics, 120GB SSD OS drive, Adaptec dual Raid setup (48 SAS) comprising of 500GB scratch/cache disk Raid 0 1400MB/s R/W and 16TB Raid 6 with hotspare 900MB/s R/W. Any other program thrown at just blitz along including CS6, Premerie and 3D CAD programs.
The only way Adobe will fix their product is with a class action for as far as I can see.
Another matter that "really" peeves me of is Adobe are still selling and recomending this product as if we are pronoucing a hoax.
Thats a scary but very real possibility sadly....so here's a question then...if you believe those that beta tested LR4, they claim that the performace issue was not present then..only in the final release... This just begs the question, WTF happened in between!? I did not beta test but was it really not a problem then?
A C G wrote:
....Can one of you explain why Adbobe cannot 'borrow' one of the machines reporting no speed problems, borrow one with them, and work out where they differ? Damn it all. The USA is not that huge. Surely FedEx could get both to the same lab room within 24 hours....
There is no reason why a development group facing a difficult-to-reproduce problem cannot fix it. This happens frequently in software development and testing. Common solutions are remote debugging, or putting "instrumented" code on the customer site having the problem. These methods almost always work. As a last resort the machine itself can be overnight shipped to the development group. That should rarely be necessary.
The most effective solution is having a concise, well-defined "replication scenario". Tech-savy customers can help a lot by providing this. Needed are the exact steps to reproduce the problem, including system details, system & application logs, etc. If problem is data-specific, the customer can provide that. It's up to the development group to state what they need. If the product has special "verbose" logging output, the development group should state how to enable that, capture it and send it back.
If there are special information capture utilities, the development or escalation support group should provide those.
It's sometimes a lot of work, but end users who narrow down the replication scenario to specific steps and data are a big help.
If this isn't possible there are remote debugging tools the development group can use to run your product remotely under a debugger and examine it. If that isn't possible they can build an instrumented version of the product with data-gathering code targeting the problem area.
There are also specialized debugging tools for memory and handle leaks. However if program only enters that state under specific conditions, a replication scenario is often still needed.
I cringe when people here try to give advice to the software engineers.
Bug reporting here is useless because software engineers most likely know exactly why the application is slow. They just can't do anything about it. They are not allowed to make high impact code changes after the product is released. They are also not allowed to gimp existing functionality. That's why all we get are some gimmicky workarounds.
It is up to management to decide how much resource they dedicate to improve their product. And given how badly designed the application is, they have a long way to go.
juw177 wrote:
Bug reporting here is useless because software engineers most likely know exactly why the application is slow. They just can't do anything about it. They are not allowed to make high impact code changes after the product is released. They are also not allowed to gimp existing functionality. That's why all we get are some gimmicky workarounds.
That's all baloney.
Why is that baloney? You have been an active poster here. How did the big LR3.3 performance feedback thread go?
I am giving my perspective as an experienced software engineer. They are never going to come out and say that LR is slow because it is built on top of crappy architecture that is expensive to rewrite. The conservative approach is to brush it aside and go back to adding new features and up the system requirements.
LynneHarty wrote:
Okay all "oneupping aside", I am back to my basic question. I'm a professional photographer, and nowhere near the tech level of most of the people I'm listening to on this forum. Here is what I'm hoping to get answers for:
I had to upgrade to LR4 because LR3 won't open the files shot with my new Nikon D4, which I had to purchase after all my equipment was stolen in December, so it made sense to get the newest and best camera I could afford. I have about 50,000 images in my catalog (I'm unclear on whether that matters or not in terms of speed). I've been using LR since version 1 and using LR4 with these new files (yes, RAW, of course RAW) is unbearably slow in every way. Waiting for each image to "focus" to edit takes way too long, as do the rest of the adjustments. I can't shoot tethered with this camera either. I found a workaround with a free download called Sofortbild, or something like that, for my D700, but alas it doesn't recognize the D4 either. So now I have this sweet camera and new LR software and I feel like I'm in the dark ages.
There has been a lot of discussion about cache size and location. I have no idea where mine is or how to find it.
Am I just screwed until adobe fixes the issues with LR 4 and the nikon D4 compatibility? Do I have to shoot with my lesser D700 till then?
Thanks.
Lynne
Basically yes, you are screwed. Unless you start considering any of the competitor's alternatives to LR.
There are a few that are highly praised by reviewers. Some are paid, some are open source.
I am getting familiar with Corel After Shot Pro. Nice interface, (maybe not as elegant as LR, but IT WORKS!).
It was suggested to shoot RAW and then convert to DNG and then use 3.6. I wouldn't do that. First, you are only getting more and more tied to Adobe (I stopped DNG conversion altogether since some of the alternatives do not work well or at all with DNGs). Besides that, the thought of using a DNG converter (free) or even using LR4 as a mere DNG converter, that is very sad.
In case you want a list (I posted one somewhere else but it got buried in the "only last 15 posts are shown)
- Corel Aftershoot Pro (Paid - Free Win/Mac/Linux) http://www.corel.com/corel/product/index.jsp?pid=prod4670071&cid=catal og20038&segid=6000006&storeKey=us&languageCode=en
- Darktable (Free -Mac/Linux) http://www.darktable.org/
- RawTherapee (Free Win/Mac/Linux) http://www.rawtherapee.com/
- Cyberlink Photo Director (Paid Win/Mac) http://www.cyberlink.com/products/photodirector/overview_en_US.html?&r =1
I have tried all the them except for Darktable (I run a Win gig) (either the full version or the trial version). I was pleasently impressed by Corel Aftershoot Pro and I find myself playing with it more and more. I really believe that Adobe decided to release an unbaked software because it has to be done before X (X being the release of Cyberlink Photo Director) As much as I like some of the features in LR4, well, it's like Adobe didn't actually implemented them since I cannot use it! I feel almost like having a long empty street and a Ferrari... but no gas (and no gas station anywhere to be seen).
Like it was mentioned before, it is a bit disturbing that Adobe employees only pop up here and there to "moderate" but never to inform. I don't want to get into a side-by-side comparisson BUT if the government of your country would be performing business the way Adobe is doing things now, I think there would have been riots on the streets a long time ago.
In any case, I am dissapointed on:
- How Adobe is handling this
- How Adobe released a product like this
- Adobe's support.
uphotography,
For me a useful post. It does seem that I am going to have to wait for LR5 (I started by saying 'we are' until I remembered all the folk around here who say they don't have a problem) for software that runs smoothly.
In the meantime do I jump ship and move to Corel Aftershoot Pro - or do I move back to the 2010 process alternative in LR4?
You say "As much as I like some of the features in LR4,". Would you like to list them? I'd never use LR to make a book, a web folder or a map. All I want it to do is to produce the best tiff or jpg from my RAW files. I like the new slider arrangement in LR4 - but are they actually extracting more from the RAWs than 3.6 did? If not then I'm stupid not to move back to the 2010 process.
I worked on some pretty tricky images yesterday, using 2012, and love the results. Does anyone think I would not have done so well in 3.6? I suppose I ought simply to try. In fact I will - but I'd love a second opinion.
Tony
Stick with LR 3.6 Tony, Corel Aftershoot Pro is not nearly as good as Lightroom and it doesn't support Dng, I tried it when I couldn't get LR4 to work properly, I also looked at Elements 10 but ACR has less controls than LR 3.6 ie:- no gradient tool and noise reduction lacks some of the control in LR 3.6.
Robbie.
I didn't know whether you were still lurking. I re-tried your idea of putting the RAWs, the cache and the catalogue on Drive J (C is my operating drive) and it ran with fewer crashes (is this a complement you rightly ask) than with everything on C.
I guess that the number of times the screen went totally white was reduced - so do I smell progress?
Would you say that 3.6 is still better than running LR4 in 2010 mode?
What I have learnt using LR4 that its often best to start with the highlight recovery and fill shadow sliders at the extremity and then to ease them back (maybe but not always) as the exposure settles to what I want. But then I could do this with 3.6 of course.
Tony
A C G wrote:
uphotography,
For me a useful post. It does seem that I am going to have to wait for LR5 (I started by saying 'we are' until I remembered all the folk around here who say they don't have a problem) for software that runs smoothly.
In the meantime do I jump ship and move to Corel Aftershoot Pro - or do I move back to the 2010 process alternative in LR4?
You say "As much as I like some of the features in LR4,". Would you like to list them? I'd never use LR to make a book, a web folder or a map. All I want it to do is to produce the best tiff or jpg from my RAW files. I like the new slider arrangement in LR4 - but are they actually extracting more from the RAWs than 3.6 did? If not then I'm stupid not to move back to the 2010 process.
I worked on some pretty tricky images yesterday, using 2012, and love the results. Does anyone think I would not have done so well in 3.6? I suppose I ought simply to try. In fact I will - but I'd love a second opinion.
Tony
No, I don't use book creation. That's one of the things that baffles me. There were several suggestions on how to improve LR (from 3 to 4) and instead of delivering a sturdy LR4 , Adobe gave us a tool full of things that are not that important (in my opinion). It looks to me that Adobe wants to play catcher, pitcher and bat at the same time.
To give just one of the examples of things I like from PV 2012 is the possibility of having a white balance brush. Noise reduction is also a tad better. In general I find that I'm getting closer to what I had in mind when I shot the photo than I managed before. But, I can only do it 1 or 2 photos at a time. Then it is so non-responsive that I need to close it and open it up again. I feel I could be faster in a darkroom than with LR. The other day it took me close to 4 hours to export around 400 photos.
I cannot wait 1 or 2 years for LR5 to see if they solved the problem. Maybe then they also added other "convenient" features like a studio management tab. Maybe then they will sell LR with its own Computer as a way to ensure it works.
Corel AS doesn't support DNG? ok, then I stop dng conversions. Corel doesn't have the features LR4 has? Well, what's the use of having them if you cannot use them? Like I said, with LR4 I feel like I have a Ferrari, the highway for myself and no gas in the tank. I have work now, I have work "yesterday" and I have a great tool that doesn't work, and a good tool that works. It would be easier to wait if we would know for how long, what's the process, the diagnosis, ANYTHING.
I have to go with what I have, and that is:
But that's it for me.
I am experiencing the same clunky and lethargic performance with LR4 as many others. Performance with LR3 was perfectly acceptable, I am going to stay with with LR because it so perfectly suits (or would suit) my needs. While it is not unusable, it is verging on it.
What was a program that was a pleasure to use has now become one that I dislike using with the censequent impact on my enjoyment of my work. What a shame!
Download LR4.1 RC2 (Release Candidate)
It should have drivers for the D4 and also improvements in some way of
speed.
One thing I did and read on this forum was to increase the raw cache to
10gb instead of 2 gb that came as standard...
That gave some improvements in terms of speed!
Marcelo Trad
>Lr4/Pv2012 rocks! - that's my opinion.
I would agree. The quality of raw conversion in LR4 is head and shoulders
above anything else I have seen and the built-in soft-proofing is genius.
Luckily I don't have any significant speed issues but I would definitely
say it's worth the wait (sorry for the pun). My experience with Adobe is
very different from the strange image being painted here of a
marketing-driven place. It is quite the opposite in my experience and I've
had really good interactions with the software engineers that resulted in
changes to the raw processing pipeline in betas and subsequent versions
based on issues I encountered. My guess is that the issues discussed here
are far more complex than people realize. Also, I remember very similar
discussions when LR 3 came out about glacial performance and locking up
issues. Somehow those issues disappeared.
hang in there people: it's always darkest before the dawn...
In my extensive experience of being up early to photograph sunrises I have
noticed that it is actually really bright out right before dawn. The
darkest time is closer to midnight (in the old meaning of midway between
sunset and sunrise) in general.
juw177 wrote:
Why is that baloney?
This is:
Bug reporting here is useless because software engineers most likely know exactly why the application is slow. They just can't do anything about it. They are not allowed to make high impact code changes after the product is released.
Saying that they won't fix a major bug or bugs that are making the application unusable for a portion of the user base because management wouldn't allow it is baloney.
North America
Europe, Middle East and Africa
Asia Pacific