How about telling us what you have tried and what has happened when you did (like the EXACT error message).
So far all we know is that you're annoyed.
Unless you uninstalled LR 5 it is still on your system. LR 6 doesn't overwrite or remove LR 5.
So yes you can go back to it. It is in your Applications folder or in your start menu.
I can export DNGs just fine out of LR CC/6.0.1. I’m exporting to a subfolder of the master photo folder of raw files.
I cannot export a DNG file out of Lightroom!
Works fine on my WIn 8.1 box.
So yes - what happens when you try? And what's the camera?
Lets see a screen print of your Export dialogue settings.
Thanks guys for your responses. Apologies for the tone of my post.
I'm calmer now
I've re-installed 5.7 so I can't replicate or screen grab the error message. From memory it was a box with a list of all the images that could not be exported "Lightroom was unable to export these files"
I did loose all my edits from yesterday so will have to start again (but its a price I'm happy to pay to get the images out) DNG to JPEG etc.
I will say I also have access to a Windows 7 machine somewhere else using a Canon 7D camera and have the same issues (though nerver as bad as last nights 32 out of 44 files!)
Here at home / my business office I'm using two Canon 5D MkIII's as cameras.
I've been using LR since version 3 and processed 100,000's of images without this new issue (I'm very well versed with Lightroom and how it functions).
Would it be the presets I use on Import / export? This appears to be a ramdom that isn't affecting everyone?
Having said this I do also get screen display issues when comparing a file before & after develop module adjustments or scrolling though images. Its difficult to say but Lightroom just seems "buggy" and less consistant than it was with version 5.7
Try turning off the GPU acceleration and see if that doesn't clear some of the Glitchyness up.
As for your exporting problems I have never encounter any so I have no idea what to suggest. I take it you are using a Mac and most of the time failed exporting is cause by a permissions problem. OS X sometimes forgets who has and doesn't have permissions to write to certain folders. That is why there is a Fix/Reset Permissions section in Disk Utility's First Aid area.
I'll look into the GPU settings. As stated in the post I'm on Windows 8.1 and 7 machines (both with the same issue since V6 was installed)
Now back on 5.7 on the Windows 8.1 PC and all's perfect. I'll just stay with this until I see some reasonable looking updates from Adobe or someone else has a better idea. Cheers
I also have problem with skipped files during the export from raw to jpg ! on Windows 7. I DID disable the GPU acceleration to speed things up. Out of 75 files 12 were "rejected", then in the rerun, out of these 12, one was, which in the third run was ... kosher.
Yes, that's exactly the same problem I'm getting. Glad to see it's not just me. This has to be a bug. And for me critically serious to my workflow. Does anyone working for Adobe read these threads? Do they ever respond?
Wow! Export is fundamental to LR. Hard to believe that a bug like this can get through testing. This is the first time I have waited to upgrade LR as there was no beta - a right decision for once :-)
It's a bug. That's what bugs are. Bugs happen.
One workround seems to be to close Bridge before exporting! I'll give this a go on my windows 7 machine at work (I'm off this week so it will have to wait to after then). For now I'm sticking to 5.7 until this is fixed. Have fun beta testing V6 guys!! I find it intollerable that companies release bug ridden output and expect it to be acceptable (BIG dent in my Adobe confidence / reputation!)
Sure, especially when you don't do your basic testing. This bug is NOT something unusual. It happens predictably and consistently. General public should not be beta testing a program that has been released as a final product.
AGAIN... I DO NOT USE BRIDGE AT ALL! This has nothing to do with Bridge. It looks to me that there is a internal conflict in multitasking programming, where one thread is stepping over some other
Having Bridge open on the Export output folder will lead to File Cannot Be Opened errors; however, this is different than the random white exports when a graphic watermark is used.
To detect the white exports it does help to open Bridge on the Export folder after the Export is finished. This is because if you choose to have high-quality thumbnails rendered, Bridge will compute a thumbnail from the full-size image, rather than just using the embedded thumbnail-which isn't white when the fullsize image is.
It happens predictably and consistently.
It doesn't happen here.
General public should not be beta testing a program that has been released as a final product.
I know that this "we're paying to be beta testers" cliche is a popular (and oh-so-boringly predictable) internet meme, but if Adobe tested Lr to the extent that it could guarantee no bugs, Lr would cost more than most of us would be prepared - or even able - to pay.
Again. It's a bug, Bugs happen. They're always a huge deal to the people affected by them, and always - in their eyes - some sort of proof of Adobe's utter incompetence: but it's not it's just a bug, and it'll be fixed.
Sorry Keith but I can't agree.
I accept that all software may have some bugs but there are so many fundamental issues arising with LR6 that it has reached unacceptable levels. I think it's reasonable to expect the code to be tested on various GPU configurations before releasing onto the market; Adobe knows perfectly well that there are quite a few different GPU cards out there.
The number of issues arising in LR has increased with each version and many of them are fundamental, not small irritations. This is creating the impression that Adobe doesn't give a d**n about their customer base. The result of this is that folks will look elsewhere for their photo software.
Here in the UK I think that one could make a case for Adobe being in breach of the Sale of Goods Act as LR6 is not of saleable quality.