justiceiro's Posts

VERY DISAPOINTED
General Interest

" I own a business in two countries and no matter what, if something goes wrong. to my clients, it is my fault."

If this is the case, then either a) it is your fualt, or b) the client has unreasonable expectations.  I’m guessing it is B.  It’s important in business to make clear to your clients what your capabilities are, and that their responsibility to plan is as great as yours is.  

If a client rolls in and says "I need a photo book designed, printed, and bound in three days" then they are asking for somethign unreasonable.  If you are telling your clients that you have the capability to do that, then you are overpromising.

 

 

Posted by
justiceiro
Nov 16, 2007 9:03am PDT
Permalink
justiceiro
 
Turning off "autosave"
BookSmart

I don ‘t think the machine setup is the issue.  I’m running it in a Mac wit 2 gigs of SDRAM that run at 2.16 GHz  (the intel core 2 duo setup).  I think the issue is that the program imbeds (I am guessing here) the photos rather than indexing them, and it simpy can’t handle the the load.  I am running an average of 3 photos per page, all from an 8MP camera, converted from RAW, so by the time I reach page 120 that’s a lot of data.  And when I want to delete an earlier page, (say page 3), the the program has to try to re-arrange 200+ images.  It can’t do it.

Blaming this on the machine is ridicuous.  The Mac is specifically designed to efficiently run graphics intensive software, much more efficiently than a PC.  If a 6 month old iMac can’t do it, I fail to see how a PC can.  Nevertheless, I’ll run it on my PC and see what happens.  I imagine it will be EXACTLY like what happened the last time the system got hung (with version 1.8) when it crashed the same way it does now on both computers.

 Don’t the blurb programmers stress test this stuff?  Why are they releasing half-baked material?

Posted by
justiceiro
Oct 20, 2007 6:00am PDT
Permalink
justiceiro
 
Turning off "autosave"
BookSmart

Autosave sounds like a great feature.  And it would be, were the bookmaker software capable of running smoothly.

 

Unfortunately, it appears that booksmart is not capable of handling books above 120 or so pages.  Even after getting the new 1.9 version (on the previous version my book just kept crashing when I attempted to view past the 100th page) I still am getting the same crash issues.

 I would like to go back and trim the fat, but the book "autosaved" my 120+ pages, and now I can’t even delete earlier pages in order to make the book a size that the program can handle.  The Autosave clearly strains the capabilities of booksmart,  and that it allows the program to get into deep water from which it cannot return. 

 

I think blurb needs, like mypublisher, to admit the limitations of its technology, and set limits of 100 pages for books.  If I had known that this limitation existed, I would have designed my book in a far different way, and be enjoying an actual bound copy of my book, instead of contemplating waiting another 6 months for another booksmart fix that will allow me to add 5 more pages, and then get into the same trouble.

 

Very dissapointing.   

Posted by
justiceiro
Oct 19, 2007 4:21pm PDT
Permalink
justiceiro