I
Quote:
|
'm new to my Sony PRST1 and to Calibre. My problem is that Calibre operation has become wretchedly and intolerably slow. I have approx. 350 books on a 32GB SD card, but it takes forever (23 minutes so far, and counting) just to get a list of books on the device. Adding books takes over 4 hours.
|
I've been advised to start a new thread on the above. I've also been advised to post 'a copy of the log which can be found under the list of jobs.', but cannot for the life of me find any such log. A screenshot of the jobs list:
Job 1, "Get List of Books on Device", reached a progress level of 100% by 1 minute, and yet it continued to do
something for 31m 19s before it finished. (The "Show Job Details" button just gives me a pop-up that says "No details available".)
After that half-hour wait, Calibre automatically started another job, "Send Metadata to device". Again, no details are available, so there's no hint of what is actually going on or what might be causing problems, but whatever this is, it typically goes on for many minutes (20 as I write this) or hours.
I have tried resetting the reader (soft reset). I've reformatted the SD card.
I selected most of my ebooks, told Calibre to send them to the device, and went to bed. Next morning Calibre still hadn't finished.
I have tried another SD card, but this made no difference. Rebooting the computer, reinstalling Calibre, likewise. I looked over the database with a SQLLITE browser, saw no obvious problems, was able to open and view the tables. I have switched USB ports. I have switched USB cables.
This time I copied the ebooks to the device's SD card manually, deleted the existing .db files, then started Calibre. It's not looking good.
If Calibre takes anything like 30 minutes to several hours to perform basic tasks, then it's just useless to me.
Most frustrating is the lack of information. Is Calibre having I/O problems? Trouble writing to the database? Is the database corrupt? (Might well be. Calibre refuses to let me delete a job, even one it hasn't started on yet, and when I shut it down it warns me that this might corrupt the device. Geeze! You'd think a "stop now" function is really basic, and a prompt, orderly shutdown without eating itself even more so.)
But there must be something wrong here. People wouldn't say this was a good application if it did this all the time. Does anyone have any idea what might be going wrong or what might help?