Содержание
- Lightroom error on preview cache or displays gray thumbnails
- Lightroom displays gray thumbnails or the error: «Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches.»
- An error occurred lightroom
- Errors using Publish Services
- Issue
- Solutions
- Solution 1: Unauthorize then reauthorize the Publish Service plug-in.
- Solution 2: Reset the cache in your browser, then reauthorize the Publish Service plug-in.
- Solution 3: Set a different browser as default, then reauthorize the Publish Service plug-in.
Lightroom error on preview cache or displays gray thumbnails
Lightroom displays gray thumbnails or the error: «Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches.»
If restarting Lightroom does not fix the issue, remove the preview folder (Windows) or preview file (Mac OS).
In Windows:
- Exit out of Lightroom.
- Navigate to the folder that contains your Lightroom catalog. The default location is in the My Pictures/Lightroom folder under your user folder.
- Locate and open the [Catalog-name] Previews.lrdata folder.
- Drag the previews.db and root-pixels.db files to the trash.
- Restart Lightroom. If you continue to have the same issue. return to the folder you opened in step 2.
- Drag the entire [Catalog-name] Previews.lrdata folder to the trash.
- Restart Lightroom.
Note: You do not need to delete the [Catalog-name] Smart Preview.lrdata folder, if one exists. This folder contains smart previews, which are different from previews.
In Mac OS:
- Quit out of Lightroom.
- Navigate to the folder that contains your Lightroom catalog. The default location is in the Pictures/Lightroom folder under your user folder.
- Locate and drag the [Catalog-name] Previews.lrdata file to the trash.
- Restart Lightroom.
Note:You do not need to delete the [Catalog-name] Smart Preview.lrdata folder, if one exists. This folder contains smart previews, which are different from previews.
Note: After you delete the previews, your folders might reopen more slowly while previews are being rebuilt.
Источник
An error occurred lightroom
Если у вас не работает один из способов авторизации, сконвертируйте свой аккаунт по ссылке
Авторизуясь в LiveJournal с помощью стороннего сервиса вы принимаете условия Пользовательского соглашения LiveJournal
Cообщество пользователей Lightroom | [entries|archive|friends|userinfo] |
[ | userinfo | | | livejournal userinfo | ] |
[ | archive | | | journal archive | ] |
an unknown error occurred | [Mar. 29th, 2011|07:17 pm]
Приветствую. Подскажите в чем проблема может быть и как решить можно ? У лайтрума, через некоторое время работы(порой довольно быстро) наступает ступор — при попытке увеличить фото до 100% начинаются серъезные тормоза и до реального отображения картинки проходить может 3-10 секунд, либо вообще так и не показав толком картинку. И это сигнал к тому, что на следующем снимке вообще лайтрум откажется работать сославшись на некую непонятную ошибку — «an unknown error occurred» В итоге — картинка не кропается, не поворачивается, никакие действия не происходят. Приходится перегружать лайтрум. Становится со временем, как мне кажется, все хуже и хуже — раньше наступает такой ступор. Буквально 6-10 снимков обработаю и все, перегружаться приходится Памяти 3 гига, проц атлон 4-х ядерный 2.8ГГц В диспетчере задач никто посторонний не ест ни память ни проц, у лайтрума потребление памяти в районе 1-1.3 гига, свободной памяти еще 700-1000 метров есть. На винтах места достаточно. Источник Errors using Publish ServicesIssueErrors occur when you use Publish Services in Lightroom Classic.
SolutionsIn the Library module, right-click the Publish Service plug-in. Choose Edit Settings. Click Remove Authorization. Click Authorize and follow the steps to connect the plug-in to your Publishing Services account. Try publishing your images using the plug-in again. Note: For some services it can take a minute to gather data such as image or album names. Solution 2: Reset the cache in your browser, then reauthorize the Publish Service plug-in.You can Google search or check your browser’s Help documentation for instructions on how to clear the cache and cookies for your browser. Most browsers have a clear browsing history option in the application menu or File menu. Otherwise, it’s typically found in the browser’s preferences. Solution 3: Set a different browser as default, then reauthorize the Publish Service plug-in.Several users have reported that this step worked for them. See your browser’s documentation on how to change the default browser. Most browsers have an option to check for default browser at startup in the preferences. Note: This step is necessary only during the plug-in authorization. Once the plug-in is authorized and functioning, you can revert to your preferred default browser. Источник Adblock |
Разговоры
Открываю Lightroom, при загрузке выскакивает сообщение «Ошибка при чтении превью. Работа с Lightroom будет остановллена». Программа закрывается. Кто нибудь сталкивался с подобным? Как решить эту проблему?
Lightroom 5.4
Комментарии
Проблемы просто преследуют тебя
Да:( никогда такого не было
Удалить папку внутри с кешем. Предварительно сделайте копию.
Сообщение удалено автором
Lightroom 5 Catalog Previews.lrdata ?
Да это похоже на папку по умолчания, если вы своей не создавали то валите Previews.lrdata
-
Welcome to the Lightroom Queen Forums! We’re a friendly bunch, so please feel free to register and join in the conversation. If you’re not familiar with forums, you’ll find step by step instructions on how to post your first thread under Help at the bottom of the page. You’re also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
-
Stop struggling with Lightroom! There’s no need to spend hours hunting for the answers to your Lightroom 6 questions. All the information you need is in Adobe Lightroom 6 — The Missing FAQ!
To help you get started, there’s a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. When you upgrade to subscription, there’s also a Lightroom Classic version available.
-
Thread starter
hereugo
-
Start date
Nov 27, 2015
- Status
- Not open for further replies.
-
#1
I have started to get this catalog reading error and I am unable to find a post or thread that discusses the solution. It is not from the cache preview (which I also get once in awhile). This is an error when reading the catalog file. Lightroom closes, and when I reopen all is fine for a while, but then I get this error again. Nothing seems to be corrupted, just very annoying and concerning that something is wrong with my catalog.
I am using an external drive for catalog file and move from PC to PC frequently. I backup every time I close Lightroom, and optimize and test integrity every time.
Any suggestions?
Related question on the error reading from preview cache which I have also started to get, which maybe related? Right now I store my previews on the SSD drive of my computer, not the external drive (USB connected). Should I also be saving the 1:1 previews on the external drive with the catalog so that they are always there when I move to a different PC?
-
#2
I’m a little bit confused by your setup. If I understand what you’re saying, you have the catalog stored on an external drive which you switch from PC to PC….but your previews are NOT stored on the external drive, but are instead stored «on the SSD drive of my computer». So does that mean that in fact there are TWO sets of previews, one on each computer, which you access via symbolic links?
-
#3
Unless you have set up a symbolic link to the previews feed to format the EHD, the LR Previews will always be created in the folder along side the catalog file. How did you create the Previews folder on the SSD? Your Lightroomforums profile does not list your OS. To provide a complete answer, this information is essential.
How is the EHD connected to the computer? You could have a bad USB cable (if that is how it is connected) and/or you could have a failing EHD. How do you back up the critical user data that is on the EHD?
«Error Reading» could also mean «Error Writing» Depending on the filesystem, you could also have a permissions problem with the disk. What filesystem did you use to format the EHD?
-
#4
OK, sorry, let me explain and provide some more infor.
I own 2 copies of LR perpetual 5.7, which I have installed on 4 PCs. 2 of which are running Win 7, 2 of which are running Win 8.1.
It looks like I do have multiple sets of preview cache, one each «C» drive on each computer. I guess I just used the default for each system that I installed LR on.
I have my catalog and all photos on an external USB drive (WD Passport NTFS), which I back up to my various PCs, but always use the one external drive as my ‘master’ Lightroom file. All presets are also on the ‘master’ external drive, so never a problem moving from computer to computer.
I have been using this set up for a couple of years and never had any problems, until recently. My workflow has never included creating 1:1 previews, I just let Lightroom create/reuse when needed as I was viewing/editting.
The «loading» is a little of problem, but never caused me to change my workflow.
My catalog has around 17,000 photos, catalog size is about 800mb.
The only change I have made recently is that I added a Wacom Cintiq and now I am using the adjustment brush much more frequently. No other system changes or updates.
-
#5
One more clarification, on my ignorance of how this works. I am talking the cameraraw cache is on the different PC, not the previews. There is a previews file on my external drive with my catalog.
-
#6
So, you have not created any symbolic links? When you open the LR catalog file. Is it on the EHD or are you opening a catalog file that is on the C: drive? LR will always create a Previews folder along side the catalog file or attempt to use one that already exists (if it follows the same name as the catalog) So, if you have a Previews folder that has the same name as the catalog file but not created BY the catalog file, you could get the «error reading preview cache error».
EHDs that are formatted NTFS are owned by one and only one computer at a time. Unless you assume ownership of the «foreign» NTFS EHD, UAC only gives the connected computer read permissions. Hence the«Error Reading» would also mean «Error Writing» since you do not have write permissions.
If the EHD is formatted using exFAT or FAT32 you do not get these security errors since exFAT is not managed by UAC.
-
#7
No symbolic links. Preview files are on the external drive with the catalog, sorry I was confused with cameraraw cache which is on each computer.
One error message I get once in a while is error reading from previews, the other message once in a while is error reading a catalog file. I have no idea what is triggering the messages, seem to be random.
-
#8
Thanks for the clarification, that certainly makes more sense regarding the previews.
As well as the possible issue that Cletus has highlighted regarding the external drive being NTFS-formatted, another thing to consider is that the drive itself might be starting to fail. I use several WD Passport drives myself, but only ever as backup drives….I really wouldn’t feel comfortable using one as the prime drive for my catalog and previews, especially if regularly switching between systems. Instead I’d be looking for a faster and more robust portable drive, such as maybe the Lacie Rugged Triple….spins at 7200rpm, so should be noticeably faster than the 5400rpm Passport models.
-
#9
I am also concerned that the drive is ready to have problems. I had one before go bad, luckily the last thing I did with it was back it up, so I lost nothing. I back up to another drive every 2-3 hours or when I am done for the day, so I am usually well backed up. Thanks for the thoughts on the other drive, I will look into it.
The problem I have now is just annoying, and unless someone can point me to similar problems/fixes, I am assuming it is a specific disk problem
Thanks
- Status
- Not open for further replies.
Поделиться
Lightroom — замечательная игрушка. В сети про него масса текстов есть, поэтому нахождение информации в конкретный момент совершенно не проблема. Проблемой является другое, иногда информация эта может прийтись совсем некстати. Например, рухнул у вас каталог с Лайтрумом, пойдете вы в сеть, а вам там дадут только один рецепт — восстановите из бэкапа. Совет правильный и умный, вот только подходит он не всегда.
Ну, представьте, ищете вы помощь именно по этому вопросу, потому что как раз бэкапа у вас нет, и вы сейчас рвете на себе волосы. Естественно, после таких случаев приходишь к необходимости бэкапа, но давайте попробуем пошаманить. У меня такое случилось сегодня утром, а последний бэкап был вчера вечером, так что слишком сильно я не напрягся… в итоге, так и поступлю.
Прежде всего, давайте попробуем покликать на другие клавиши. Из четырех указанных полезной кажется только первая, ведущая на Adobe TechNote. Она помогает мало, потому что отсутствует и выводит вас, в итоге, на страницу 404. Наверное, поиск даст нам другой шанс: ищем «cannot repair corrupt catalog» на сайте суппорта, на которые выходят три ссылки, никакого отношения к нашему вопросу не имеющие.
Идем в более умную контору, ищем там то же самое. В качестве вариантов решения предлагается следующее:
Сделайте новый каталог, импортируйте в него поврежденный. Естественно, используется опция File → Import from Catalog… Сначала программа создает временный каталог с файлами для импорта, потом предлагает вам их перетянуть с одной из опций.
Я решил, что исходники у меня отличные (к тому же, дубли еще дома и на бэкап-диске лежат), поэтому предпочел не копировать их, а только взять из каталога настройки. Дальше «он сказал поехали и махнул рукой»… нажимаем Import.
Результат появляется сразу же: сообщение «Lightroom encounteren an error when reading the catalog and it needs to quit»… печально. Ищем другие варианты.
Это может быть связано с недостаточным местом на диске. Идем на диск, проверяем: свободно 60 Гб из 320, чего должно быть достаточно на большинство случаев жизни.
Ищем проблему в настройках отдельных кадров. Можно нажать Uncheck all, потом выделить все и кликом в окно выделить все. В таком случае, Lightroom проверит все фотографии по одной при выделении, и вы сможете понять, где проблема, и просто не будете импортировать проблемную картинку. Это решение требует времени и нескольких попыток, потому что программа может в процессе зависать.
На проблемных изображениях будет значиться запись «Preview not available». Что с ними делать, уже ваше дело. Прежде всего, импортировать их не нужно. Затем их можно взять с диска, куда вы делали бэкап или с основного компьютера (у меня две копии, кроме рабочей) и обработать заново, если на них сошелся клином белый свет. Рецепт здесь простой — следующий раз при импорте не импортировать предположительные дубли. В моем случае так и было — вылетел десяток фотографий по непонятной причине. Выключив их при импорте, я успокоил программу. В итоге, получил абсолютно идентичный моему каталог. Правда, я все равно восстановил потом из вчерашнего бэкапа, а эти танцы с бубном исключительно ради статьи.
Несколько советов:
В сети есть советы не нажимать на кнопку Repair catalog (меню предшествовало тому, что вы видите наверху) сразу. Закройте окно, скопируйте файл каталога в другое место, потом чините. Дело в том, что если программа попытается восстановить его и обломается, потом уже будет поздно.
Всегда при выходе делайте бэкап вашего каталога на внешний диск или Dropbox — эта не самая муторная операция избавит от многих проблем в будущем.
Можно иметь несколько каталогов (как в моем случае, разбитых по проектам), тогда потеря одного отдельного будет не столь страшной. Большой каталог с 20 000 фоток потерять страшнее, чем с 2 000. Меньше настроек, меньше восстанавливать. Хотя, тут уже вопрос, ведь как правило работаешь ты только с частью картинок, и совершенно неважно, какой каталог умер, ведь пропала работа только определенного объема, потому что раньше вы наверняка за что-то отчитывались.
В качестве самого параноидального совета, можно автоматически записывать изменения в XMP — тогда при потере каталога настройки отдельных файлов останутся. Уйдут, естественно, только коллекции.
Lightroom error on preview cache or displays gray thumbnails
Lightroom displays gray thumbnails or the error: «Lightroom encountered an error when reading from its preview cache and needs to quit. Lightroom will attempt to fix this problem the next time it launches.»
If restarting Lightroom does not fix the issue, remove the preview folder (Windows) or preview file (Mac OS).
In Windows:
- Exit out of Lightroom.
- Navigate to the folder that contains your Lightroom catalog. The default location is in the My Pictures/Lightroom folder under your user folder.
- Locate and open the [Catalog-name] Previews.lrdata folder.
- Drag the previews.db and root-pixels.db files to the trash.
- Restart Lightroom. If you continue to have the same issue. return to the folder you opened in step 2.
- Drag the entire [Catalog-name] Previews.lrdata folder to the trash.
- Restart Lightroom.
Note: You do not need to delete the [Catalog-name] Smart Preview.lrdata folder, if one exists. This folder contains smart previews, which are different from previews.
In Mac OS:
- Quit out of Lightroom.
- Navigate to the folder that contains your Lightroom catalog. The default location is in the Pictures/Lightroom folder under your user folder.
- Locate and drag the [Catalog-name] Previews.lrdata file to the trash.
- Restart Lightroom.
Note:You do not need to delete the [Catalog-name] Smart Preview.lrdata folder, if one exists. This folder contains smart previews, which are different from previews.
Note: After you delete the previews, your folders might reopen more slowly while previews are being rebuilt.
Источник
Lightroom says my preview cache is corrupted—how do I fix it?
December 13, 2014 (Updated December 21, 2017 ) 24 Comments
There are a few clues that your preview cache may be corrupted. The most obvious is Lightroom showing an error message telling you that it’s corrupted (“Lightroom encountered an error when reading its preview cache and needs to quit.”), or that it tried to repair it unsuccessfully.
Alternatively you might find that Lightroom displays the wrong preview for some of your photos, some previews or thumbnails disappear when the photo is deselected, or the photo only shows in the Develop module.
In Lightroom CC/6, Lightroom tries to fix the preview cache automatically when it restarts. If this doesn’t work, or you’re using an earlier Lightroom version, you can fix it by manually rebuilding the preview cache:
- Find your catalog on the hard drive. If you can open Lightroom, go to Edit menu (Windows) / Lightroom menu (Mac) > Catalog Settings > General tab and press the Show button to open an Explorer (Windows) / Finder (Mac) window, then quit Lightroom. If you can’t open Lightroom, and you don’t know where to find your catalog, you’ll need to search for *.LRCAT les.
- Using Explorer (Windows) / Finder (Mac), move or rename the previews folder (*Previews.lrdata) and restart Lightroom.
- Lightroom can now rebuild the previews from the original files. Select all the photos and go to Library menu > Previews > Build Standard-Sized Previews and leave it to work, perhaps overnight as it takes a long time. If any of the photos are offline (e.g. stored on disconnected external hard drives), these previews will remain blank until you reconnect the drive.
- Once you’re happy they’ve all rebuilt, you can delete the previous previews folder (*Previews.lrdata) if you haven’t already done so. I don’t usually recommend deleting the old previews before building new ones, just in case there are any missing original files, and the previews are the only copy you have left. If you’re comfortable that you still have all of your original files available, then you can delete the old previews before building the new ones.
Comments
Dusty says
Followed the directions. It works. It takes 2/3 second to build each preview. I’m in for a long night.
If you’ve used Library menu > Previews > Render Standard-Sized Previews, you can leave it running and go to bed!
Thanks for posting this tip on the interwebby. . . I was just starting to go into panic mode 🙂
John Samuel says
If you are using a sync like Google Drive then just don’t. 🙂
Yes, I’ve heard of a few issues with syncing via Google Drive. Dropbox has been working pretty well for some years, if you’re looking for an alternative.
Thank you for helping
Atul Rastogi says
How to prevent this problem because it happens very frequently despite renaming the preview folder.
If it’s happening more than once in a blue moon, I’d be asking why. Either Lightroom’s not being shut down properly, or there’s a hardware problem. I’ve also heard of some issues when the catalog’s stored in certain cloud storage folders (e.g. Box.net, OneDrive)
I deleted Previews.lrdata but the error still comes up. I need to work!!
You definitely deleted the Previews.lrdata for your active catalog, and not another random catalog? If so, post it at http://www.lightroomforums.net and we’ll consider other possible troubleshooting. I’d maybe try moving the catalog onto another drive in case it’s being caused by a hard drive failure.
My LR catalog got hung up a couple of days ago and now the previews aren’t showing up, except the last three I’m working with. I am unable to delete or rename my previews folder. I get this error “The Finder can’t complete the operation because some data in “2016-LR-JUNE-FORWARD Previews.lrdata” can’t be read or written. (Error code -36).” Any suggestions?
Error code -36 sounds like an OS X error – likely a problem with your hard drive or disk permissions. Phoning Apple would be your quickest solution.
David Hoffman says
I followed the process exactly and its churning through my photos. But, library view, I can’t see any new previews appear. Can this be good? Initially, I did not get an error message from LR, just every photo grayed out except in develop . . . .
I would expect some to be turning up David, but it may be outside of your current view. Tried scrolling?
A question as I am about to perform this fix . My photo files used in Lightroom are located on three external hard drives which cannot all be connected at one time. Can the I build the previews multiple times to recover the files on each drive? Thanks
Yes, that’s fine Ralph.
Duane Moore says
I have a disk cataloger that is used for searching for all sorts of things. I found that it was including Previews.lrdat and disabled that folder from being scanned. No more problems.
That’s a good tip, thanks for sharing Duane.
BURKE WALKER says
I went to LR catalog and deleted the PREVIEWS file. But I am STILL getting the “ERROR” box message. Any further tips?
You’re getting the error immediately after deleting the previews? Or are a little time has passed?
There are two things that come to mind. Perhaps you deleted the wrong previews, or perhaps there’s a problem with the drive. Those are the most likely suspects, but if that’s not it, post on the forum (linked at the top of the page and we’ll help you troubleshoot further. (Two way conversation is easier on the forum interface.)
I had a problem like this now for almost a week, with LR Classic and tried deleting the preview file(mac) with no luck what eventually realised that when i updated LR the new catalog file must have been corrupted, so i went back to the old one before the update made a copy then imported it again, so LR could convert it to the new V10 catalog now everything is fine.
Sounds like the upgrade didn’t work properly for your catalog and previews. Glad re-running has sorted it!
Hi I got a new computer and then I opened my previous catalog and I only have gray squares. my original files are on many different hard drives. I just want my previews back so I can reference the many shoots I have occasionally. I dont want to rebuild previews. Why can’t it connect to my large orginal lrdata folder?
Did you copy your Previews to the new computer at the same time as the catalog?
Moving to a new computer usually means the drive names / letters have changed and the foles need relinking.
Leave a Reply Cancel reply
Send My Free eBooks!
There is no charge for this service. Your personal data will be processed in accordance with our privacy policy. You may unsubscribe at any time.
Everything You Need To Know!
Sign up for the Photography Plan
Categories
Interested in Lightroom?
Whether you’re just getting started with Lightroom, or you’ve been learning for a while, you’ll love these FREE Lightroom eBooks.
You’ll learn not only how to get started, but more importantly, how to avoid the most frequent problems. There are Quick Start eBooks for both the traditional desktop-based Lightroom Classic, and for the new Lightroom cloud ecosystem.
The eBooks are yours to download absolutely FREE, along with a number of other free member benefits, when you register for a free account. Don’t worry, we won’t share your email address with anyone else, and there’s no obligation to buy anything.
Already registered? Sign in to download your copy.
Источник
F.A.Q. Решение проблем c Lightroom и Adobe Camera Raw
На страницу Пред. 1 , 2 , 3 , 4 , 5 , 6 | Для печати |
Автор | Сообщение | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Doroga |
|
На чтение 7 мин. Просмотров 144 Опубликовано 15.12.2019
Пуск > Выполнить %appdata%AdobeCameraRaw
Ок.
Удаляете папку Cache.
Запускаете LR. Ждёте когда перестроится кэш фотографий (LR будет подтормаживать при просмотре библиотеки)
А, вообще, Вам бы надо сделать проверку диска (Мой компьютер > C: Свойства > Сервис > Проверка диска. Соглашаетесь на проверку после перезагрузки. Перезагружаетесь.) Не тревожите ПК с полчаса пока Windows проверит диск на ошибки.
Проблема решена! Подробности здесь .
Lightroom «забывает» про то, что сделал превью — стандартного размера и и полные. Каждый раз, как я его запускаю и открываю фотографию в Loupe, он начинает рендерить превью заново.
Не всегда, но очень часто. Как это замедляет работу, можно и не говорить.
Что я пытался сделать и что не сработало:
- Создал превью. Стандартные и полные.
- Преобразовывал фотки в DNG.
- Удалил папку «prevews.lrcat».
- Сделал «Discard 1:1 previews» и создал их заново.
- Изменил размер кэша ACR и переместил его в другое место.
- Переместил каталоги на другой диск и на другой контроллер.
- Создал каталог заново, с нуля.
- Оптимизировал диск, убедился, что на нём полтерабайта свободного места.
- Выполнил «Relaunch and Optimize Catalog».
- Изменил размер / очистил кэш превью / переместил его на другой диск.
- Оптимизировал базы этим способом.
- Переместил оригиналы на другой диск и другой контроллер.
- Изменил несколько раз размеры создаваемых превью.
- Включал/выключал «Write changes to XMP».
- Попробовал Lightroom версий 2.3 и 2.4, x32 и x64.
- Отключал антивирусы, и вообще,
- запустил машину в безопасном режиме, без посторонних программ.
- Проверил права доступа на папки каталога и оригиналов.
- Всё это — с разными каталогами.
- Всё это — на Windows XP x64 и свеженькой Windows Vista x64.
Вроде всё сделал? По колесу постучал, зеркало протёр. Знаю, многое из перечисленного непонятно как влияет на каталог, но я перепробовал всё, что имеет хоть какое-то отношение к превью.
Однако даже во время создания превью размер файла каталога не меняется вообще, не меняется и размер и содержимое папки каталога. Только в папке ACR cache добавляется новых файлов кэша. Учитывая размер файла каталога, превью там вполне могут быть. И Лайтрум может просто отказываться их распознавать, а во время генерации ничего не меняется, потому что превью и так есть в файле.
Впрочем, внутри таблиц БД я не вижу ничего, напоминающего превью. Библиотеки работы с SQLite в системе? Нет, сомнительно. Лайтрум всё своё таскает с собой, на то это и SQLite. К тому же я проверил симптом на других установках Лайтрума.
Интернет и форумы Адоби молчат, как пленные партизаны. Ни следа проблемы. Похоже в целом свете только я словил симптомы.
Это уже становится интересным. Как технически такое вообще возможно? Не вижу вариантов.
Как и любой другой программой, с Lightroom иногда случаются неприятности. Она может перестать запускаться, начнет жутко тормозить, выдавать какие то ошибки и загадочные сообщения.
Чтобы избежать проблем, во первых не надо делать типичных ошибок при работе с программой, о которых вы можете прочитать в статье «Пользовательские ошибки при работе с Lightroom«.
Как быть если Lightroom «сломался»? Главное — не паниковать.
Затем — всегда иметь резервную копию каталогов. Вы наверняка замечали, что Lightroom периодически просит сделать вас back up каталогов. Вы закрываете это окошко или делаете то что вам рекомендовано? Может пора таки обратить внимание на совет, пока не стало поздно?
В идеале, кроме бекапа каталогов, стоит делать резервную копию исходников, но при большом количестве снимков, это может стать проблематично.
Зато имея резервные копии каталогов и исходников, можете спать спокойно. Что бы не случилось, вы не потеряете свои снимки.
Теперь рассмотрим список наиболее типичных проблем, возникающих с Lightroom и что с этим делать.
Содержание
- Lightroom не открывается
- Lightroom тормозит
- Lightroom показывает ошибку при экспорте
- Lightroom не показывает превью или само фото
- Lightroom ведет себя странно
- Универсальный способ решения проблем
Lightroom не открывается
Варианты решения. Во первых, банальная перезагрузка компьютера. Может и смешно, но помогает.
Если не помогло, то в первую очередь удалите файл с расширением .lock, который блокирует каталог, пока вы с ним работаете.
В обычной ситуации, файл удаляется автоматически, после закрытия Lightroom. Но иногда, если работа была завершена некорректно, может остаться и мешать запуску.
Узнайте больше на Lightroom.ru
Данный файл находится там же, где и все файлы текущего каталога. По умолчанию это
- Windows: Users[имя пользователя]PicturesLightroom
- Mac OS: /Users/[имя пользователя]/Pictures/Lightroom
Если файла .lock не было или удаление не помогло, попробуйте удалить файл с настройками Lightroom
Искать его нужно здесь:
- В Mac OS X: /Library/Preferences
- В Windows: c:Users[имя пользователя]AppDataRoamingAdobeLightroomPreferences
В Windows это файлы с расширением .agprefs в Mac — .plist
Если каталог по прежнему не открывается и у вас есть резервная копия, попробуйте ее открыть вместо текущего каталога.
На худой конец, попробуйте полностью удалить Lightroom и установить заново. При это желательно установить самую последнюю версию.
Lightroom тормозит
Оптимизация работы лайтрум под максимальное быстродействие — это отдельная тема. Но основные советы следующие.
Узнайте больше на Lightroom.ru
Первым делом попробуйте оптимизировать каталог File -> Optimize Catalog.
Увеличьте размер кеша для Lightroom. Кроме того, будьте уверены, что на диске, где расположен файл кэша достатчно свободного места.
Узнать где расположен кэш и изменить его размер можно в меню Edit->Preferences (Lightroom->Preferences на Mac) на закладке File Handling
Лайтрум довольно требователен к ресурсам компьютера. Поэтому для быстродействия — закройте все ненужные программы, обновите лайтрум до последней версии, а так же будьте уверены что с оперативной памятью компьютера все в порядке.
Lightroom показывает ошибку при экспорте
Самое простое, для начала попробовать перезапустить Lightroom. Если вы используете какие либо плагины, которые были применены в процессе обработки, убедитесь в том, что плагины работают корректно.
Не используйте неофициальные русификаторы для лайтрум — кто их сделал и как, никому не известно. Удалите файл настроек, как было написано выше.
Узнайте больше на Lightroom.ru
Lightroom не показывает превью или само фото
Во первых попробуйте удалить папку с превью ваших снимков. Она находится там же где и все файлы каталога. В Windows — это папка с названием каталога и .lrdata на конце, в Mac — файл с таким же названием. Попробуйте обновить драйвер видеокарты и профиль монитора.
Изменение пути к оригиналу, одна из распространенных ошибок
Кроме того, частая причина заключается в том, что вы переместили файлы исходников на диске в другое место и лайтрум их «потерял».
Вы этом случае при попытке работы со снимком вы увидите сообщение вроде — «The file named mybestphoto.jpg is offline or missing»
Как с этим бороться, читайте в статье «Потерянные файлы и папки в Lightroom«.
Lightroom ведет себя странно
Тут может быть большое количество «странностей», но их лечение в основном происходит шаманскими методами. Проверьте наличие достаточного месте для кэша Лайтрума, обновите драйвера видеокарты и профиль монитора, будьте уверены что с жестким диском и оперативной памятью все в порядке.
Универсальный способ решения проблем
Не забывайте обновлять лайтрум. Как правило в обновления включены не только новые камеры, о чем пишется в официальных пресс релизах, но и множество найденных и исправленных ошибок в самой программе. Поэтому есть вероятность того, что в очередном обновлении ваша проблема будет уже решена.
fancy hydrant [deleted] says:
Have you tried clearing the preview cache?
ages ago
(permalink)
nutritious border [deleted] says:
Yeah, I suggest you backing up manually (copy the .lrcat file) and then cleaning preview cache (rename or delete .lrdata folderfile depending on your system).
It will force LR to rerender all of them while viewing which will slow down the program a bit but not after previews are ready again.
Just to clarify: the backup process only copies .lrcat file while «Optimize catalog» works with preview cache. So if you uncheck optimize during backup LR should work fine.
ages ago
(permalink)
Rich Baum says:
Wow guys, thanks for the tip but I think this is a little beyond my LR skills. You would think a working photographer would better understand the process.
Anyway, is there any more info you can give me or walk my through it step by step. I wish there was a Youtube video explaining this process.
ages ago
(permalink)
Godfrey DiGiorgi
says:
— In Lightroom, open Catalog Settings and click the General tab. First item is Location, click the Show button. That will run the Mac OS X Finder or Windows Explorer and select the catalog folder on disk.
— Click back in Lightroom and quit.
— Open the catalog folder and delete the file or folder that ends with «.LRDATA». Do Not Delete the file that ends with .LRCAT.
— Now run Lightroom again. It will open with no thumbnails in the view and recreate all the thumbnails and previews that you deleted. If you have a large catalog with lots of files in it, this can be an overnight process. Just leave it up and running and it will churn its way through them all.
Originally posted ages ago.
(permalink)
Godfrey DiGiorgi (a group admin) edited this topic ages ago.
Rich Baum says:
Thank you, I will try it tonight and let you know.
ages ago
(permalink)
Purple Umbrella Photos says:
GD said:
— Open the catalog folder and delete the file or folder that ends with «.LRDATA». Do Not Delete the file that ends with .LRCAT.
As an extra safety net, you can rename this folder/package, instead of deleting it. Something like xxxcatalog_Previews.LRDATA.OLD
ages ago
(permalink)
Godfrey DiGiorgi
says:
@ PUP ::
Why bother? It’s a waste of space. Backing it up provides no additional security. I don’t bother backing up the previews at all either.
The xxx_Previews.LRDATA folder/package is a dynamically created entity that Lightroom manages. The issue pointed to in this question is that the previews on Rich’s system has something corrupt in it, so it’s best to just delete it and force Lightroom to create a new previews hierarchy.
If Lightroom cannot recreate the previews correctly, something else more fundamentally wrong is going on … backing up the previews will not solve that.
Originally posted ages ago.
(permalink)
Godfrey DiGiorgi (a group admin) edited this topic ages ago.
Harry® says:
It’s a funny thing with me too Godfrey, I usually add some xxx’s after the suffix myself just in case I need the file again, then I can delete it completely when all goes to plan!
I’m assuming that Pup intends later deletion of the file too!
I suppose it’s irrational but I feel better doing it that way!
Originally posted ages ago.
(permalink)
Harry® edited this topic ages ago.
Rich Baum says:
Godfrey,
I have done as you suggested but before I delete anything I want to ask,
It shows 3 folders:
Catalog-2 previews.lrdata
Catalog-3 previews.lrdata
Catalog-previews.lrdata
I also see a bunch of files that look like this:
Temporary Import Data- (numbers 2 — 15)
Temporary Import Data-12.db-journal
And I have one Folder «Backups»
So before I delete anything I wanted to ask if I delete one or all of these files.
I also wanted to ask, what’s the worst that can happen by following your suggestions? It’s not that I don’t trust you but this is some important stuff.
One good thing is I am fully backed up 3x
Thank you again,
Rich
ages ago
(permalink)
Godfrey DiGiorgi
says:
No problem, Rich. It’s good to be cautious.
You say «it shows 3 folders». What shows three folders? I’ll presume you are looking at the contents of the catalog folder, the folder name being «Catalog».
I get the feeling you’re running on Windows, not Mac OS X, but with LR running, INSIDE the working catalog folder the files should look something like this:
and with LR not running it should look like this:
Note that the .LRCAT-JOURNAL and .LRCAT.LOCK files are temp files used while Lightroom is running and deleted after you quit it. If you have these hanging around after LR quits, delete them. Other things like «temporary import data» blah blah are also temp files that should be deleted.
The fact that you have three .LRDATA folders (packages on the Mac), if they are in the catalog directory, means that either something funky is going on or that Lightroom on Windows has to partition the previews folders once they get to a certain size.
The ONLY critically important file in that directory (unless you put the Lightroom presets in the same directory as the catalog) is the .LRCAT file. Everything else is created by LR dynamically.
If you want to be utterly safe, create a new folder elsewhere, copy the .LRCAT file into it, then drag and drop that copy onto the Lightroom application. You’ll see LR generate a whole new preview data directory structure once it opens up…
ages ago
(permalink)
nutritious border [deleted] says:
Godfrey, don`t be so hard on Win;) If OP has three folders that means he has 3 catalogs in this folder hence three .lrcat files.
Rich let me explain:
Backup folder holds catalog backups which were made by LR. If you look inside you will find folders by date and catalogs (.lrcat files) inside
Every .lrdata folder holds previews for corresponding catalog. It seems that you have 3 of them, probably two of them are old and aren`t used at all.
I`m not sure what «Temporary Import Data-» is. Are they folders or files? It can be a folder with all imported photos backed up or it can be some strange catalogs if they are files with .lrcat extension
ages ago
(permalink)
ambient troutmask says:
Temporary Import Data
This is how my main catalog looks
Note the little arrow on the preview folder shows that it actually located on a separate drive, using the technique described here
A copy of my preference folder is also kept in the catlog folder. It is not used by LR as it uses the preferences from user/username/appdata/adobe/lightroom. I just keep a copy there for convenience in case of hard drive failure on my OS drive and to make it quick to copy everything over to other machines when I need to.
Dependent on how your folder view is set up in explorer it should look like this. The dates are usful in they show the last time the files were updated, from this you can tell immediately which is your most recently used catalog if you have more than one catalog in the same location. However it is best if you are going to have more than one catalog to have them in separate locations to avoid confusion. I have two catalogs and my other one is located in a separate folder here
The back up folders really shouldn’t be in the same place as your original catalog. LR defaults to this. The backup catalogs are used by LR to rebuild a corrupt catalog in which case they can be located in the same location. However they can also be used to rebuild your entire catalog if the drive fails. Obviously they can’t do this if they are on the drive that files. So change your backup location to a separate drive.
The Catlog-2 is the catlog created by LR 2 and I assume upgraded to catlog 3. Once you are completely happy that everything is working in LR 3 you can delete this. Personally I don’t until LR 4 is released. I do delete the previews associated with the catalog. The same may apply to catalog (in that this may have been a LR 1 catalog) and even I would delete that. However if either are catalogs you have deliberate created then leave them alone. The way to tell if they are LR 3 catalogs is to open them. If they are earlier catalogs LR will ask if you want to upgrade them. Don’t , just close LR and then you can delete if you want.
Originally posted ages ago.
(permalink)
ambient troutmask (a group admin) edited this topic ages ago.
Godfrey DiGiorgi
says:
Being hard on Windows? Don’t know what you mean. It sounded like Rich was working on a Windows platform, that’s all. I expected that what he might see inside the catalog folder could differ a bit on that basis from what I see in a catalog folder on Mac OS X.
What I said is still correct. The ONLY significant file in the catalog folder is the .LRCAT file at the top level of the hierarchy. That’s the one that contains all the essential data. Do what I suggested:
— Copy the .LRCAT file to another folder
— Open it with Lightroom
You’ll see all the other things created automatically as they are things Lightroom uses in the management of the catalog and its operations, but there’s no reason on earth to archive or save them if you’re trying to fix a problem. Let LR create them new from the .LRCAT file.
ages ago
(permalink)
nutritious border [deleted] says:
Godfrey, sorry for my English, I`m sure I would explain myself better if it was my native language.
I was talking about this:
The fact that you have three .LRDATA folders (packages on the Mac), if they are in the catalog directory, means that either something funky is going on or that Lightroom on Windows has to partition the previews folders once they get to a certain size.
Why do you think Windows is so strange that it`ll have to split folders to fit additional files. I just kinda feel that I have to stand for Windows in this particular case;) Or at least explain what is really happening since I`m familiar with how LR stores files in Windows.
Besides those folders being separate catalogs previews you are absolutely right and I`ve never said anything against your suggestions!
And please don`t take me too serious!
ages ago
(permalink)
Godfrey DiGiorgi
says:
@ MishaMask:
If you have three .LRDATA files in one catalog folder you’ve either got something funky going on or there’s an OS level issue with the construction of the Lightroom previews. NO LR catalog folder hierarchy should have two .LRCAT files at the top level. EG, in this case, you cannot have a valid catalog folder with
Catalog.lrcat
Catalog-2.lrcat
Catalog-3.lrcat
and their matching previews.lrdata files all at the top level. I suspect this is an artifact of Rich’s LR problem.
My statement was not a slam on Windows … I really don’t care, but this scenario is inconsistent with Lightroom’s normal file organization, as AT showed with his screen shots.
Originally posted ages ago.
(permalink)
Godfrey DiGiorgi (a group admin) edited this topic ages ago.
nutritious border [deleted] says:
@Godfrey you are wrong here, you can have multiple catalogs in the same folder. And they will even share presets stored in this folder with «Store presets with catalog» setting enabled.
Here is the screenshot of my catalog folder:
btw it is exactly the same for Mac since I have a MacbookPro;)
ages ago
(permalink)
ambient troutmask says:
LR defaults to creating all catalogs in the same folder on upgrade unless you tell it to do otherwise, as I said in my previous post
However it is best if you are going to have more than one catalog to have them in separate locations to avoid confusion
Whilst I am sure you aren’t confused by having more than one catalog in the same location as much of this thread shows many are.
There is absolutely nothing unusual about the OP’s file and folder structure once again as I explained
The Catlog-2 is the catlog created by LR 2 and I assume upgraded to catlog 3. Once you are completely happy that everything is working in LR 3 you can delete this. Personally I don’t until LR 4 is released. I do delete the previews associated with the catalog. The same may apply to catalog (in that this may have been a LR 1 catalog)
, and it doesn’t matter if you are on Windows or OSX LR is exactly the same. I have no idea why people should think it works differently on the two different OS’s. LR is a database using cross platform tools. Its folder structure is identical on both systems, as indeed it has to be otherwise it really wouldn’t be cross platform would it?
You can use the same catalog, located in the same place on both a OSX and a Windows machine. If they had different file and folder structures I can’t see how this would be possible.
Originally posted ages ago.
(permalink)
ambient troutmask (a group admin) edited this topic ages ago.
Godfrey DiGiorgi
says:
While you CAN have catalogs (meaning .LRCAT files) in the same folder, it is NOT the default NOR is it the normal case. Lightroom does NOT «default» to creating all the catalogs (.LRCAT files) in the same folder. As a matter of fact, it wont at all: I have tried and tried to make Lightroom create two .LRCAT files in the same folder. It does not work, it ALWAYS creates a new catalog FOLDER in the folder location I choose.
If it does on Windows, this is behavior impossible to replicate on Mac OS X without going outside of Lightroom and manually moving the files around.
The only reason for the .LRCAT and .LRDATA -2 and -3 folder/files is as AT has suggested, artifacts of the LR 1 to LR2 to LR3 upgrade process. All those older -X preview files are a waste of space unless you’re going to use the older version of LR concurrent with the latest one that made the revision files.
But all of this debate is off the point for Rich’s question:
«Keep trying to back up catalog but with no luck. Seems like it gets stuck on one file.
I get the following warning: Lightroom encountered an error when reading from it’s preview cache and needs to quit.
Lightroom will attempt to fix this problem the next time it launches. «
Rich has a corruption in the Preview folder/package hierarchy. The way to solve this is to separate the preview folder from the .LRCAT file … either by deleting it or by copying the .LRCAT file into a different folder, and then letting Lightroom re-create the previews from scratch with it. That’s all that’s required.
ages ago
(permalink)
ChuDabi says:
Hi, just wanna say this thread just saved me. There was a power outage in my home while working on Lightroom and this came up. Deleted my previews folder and I was back in, just had to rerender everything
114 months ago
(permalink)
Would you like to comment?
Sign up for a free account, or sign in (if you’re already a member).