Skip to main content
Participant
April 2, 2012

P: Book Module – Unfinished book vanishes

  • April 2, 2012
  • 124 replies
  • 2513 views

I’m creating my first Blurb book inside of Lightroom 4. There are some 175 images in my collection/filmstrip. I was about 80% complete with the book, when I selected an image to go into the Development Module for adjustments. When done I returned to the Book Module. But the book was gone! The filmstrip at the bottom of the page is there indicating images are in the book, but the book itself is empty with only a cover and two blank pages. If I add an already “used” image, the filmstrip counter goes from 1 to 2.

Trying to fix this problem, I backed up and optimized my catalog. But upon restarting Lightroom no change... and no book!

Any suggestions as how to get my book back? Or do I have to start over!

This topic has been closed for replies.

124 replies

Inspiring
September 17, 2012
Hi again!

I got the bug in a Step By Step procedure video!.. Hope this help the adobe lr4 team to put an end to this..

uploading the video to youtube right now...
Inspiring
September 14, 2012
I am having the same problem that was described in the original post. I lost my book pasting in text for a page caption. In addition, the backed up catalog is EXTREMELY slow to load the imagaes (I would venture to guess this is a LR issue not a Computer issue since this only occurs when I'm in a backup catalog.)

Would love to find a fix for this. ASAP.

thanks!
john beardsworth
Community Expert
Community Expert
September 13, 2012
Look, we all want it resolved ASAP but it takes time if the bug only crops up infrequently and they can't replicate it. And they are taking it seriously - in fact there may be more than one bug with the same external symptoms, and one was apparently resolved in 4.1.
Inspiring
September 13, 2012
It is so hard to believe that Adobe (Lightroom) has ignored this BOOK module problem for 8 months. It doesn't take 8 months to fix a bug in software. Why are they not taking this seriously? Mark
john beardsworth
Community Expert
Community Expert
September 13, 2012
The thread is marked as "in progress"
dadodAuthor
Participant
September 13, 2012
FYI, through my Adobe back channel, I was able to get Marko’s youtube link to both the guy who runs the Lightroom team, as well as an engineer who is working on the issue. Hopefully they'll be able get this nasty bug resolved. I believe that any other observations from users that might help pinpoint when this bug occurs would be helpful.

If anyone from Adobe is monitoring his thread, it would be nice if you would acknowledge in this thread that Adobe is working on this problem. You have a group of users here that are interested in helping out to resolve this issue.
john beardsworth
Community Expert
Community Expert
September 13, 2012
Marko, could you answer my question? I watched your video and it looked to me like the problem happened at the moment when you quickly moved from Book to Develop and quickly back to Book.

It may be similar to what I think I've been doing when it's happened here - in my case switching to a different book while in Book. Following this theory, I usually change between books by going back to Library and I've not lost a book while using this (unacceptable) method.

So is it the quick module change that always causes the problem?
Inspiring
September 13, 2012
Another guess is that the bug its related to the TYPE options in LR4.1... if you see the video, its happend just after I type down some text in the book..

LR4 has some problems too, with the TYPE options, like there is no "Acentos" in spanish options, and some times the page or the photo captions are aviable and they dont show... and there is another that the text selected its only highlighted when you are in the type function...

ETC...
Inspiring
September 13, 2012
Yeah, a single catalog its to risky as you say.. but there is and option in LR4 catalog options to do backups every day, every 30 days, every time you close LR, and whatever...

Do backups often... that will save your butt.. xD
Inspiring
September 13, 2012
Im not an expert, dont know anything about codes and stuff, but if i got to guess, I think that the problem happends when lightroom buffer hits the top and the software loses his stability...

As I already say, Im not an expert... just guesing about it.

LR4 operates not over the original files (non-destructive file handeling), instead LR4 works over somes JPGs generated and save in the software cache.

Looks like the software its always applying all the exposure modifications, filters and whatever over the JPGS on the cache every time that the user seens this image in a period of time to create the preview of the final image...

Im guessing, but when we operate in book module, and im switching between image and image, spread and spreads,,, there is a point that the software buffer hits the top... and buuum,,,

Maybe this is also has to be with your own computer configuration... mine its not the fastest in the world.. and maybe ADOBE GUYS are trying to find this bug in a super computer that never overwhelmn the buffer...

maybe...

as i already say... just guessing