Quote:
Originally Posted by spatlese
Any ideas what may be happening, or is this just an anomaly with the T1?
|
I wonder if you're running into the PRST1
PITA quirk I noted in this paragraph?
Quote:
|
[In case you're wondering why the PRST1 needs the 2nd plugboard (the epub one) -- it's because, for some unknown reason, sometimes after connecting it to Calibre, the T1 decides to update its book database by re-reading all the metadata inside each book. The 2nd plugboard makes an effort (for epubs at least) to make the data it re-reads the same as the data it just threw away. However, the epub plugboard is only used when you send the book to the PRST1, not every time you connect T1 to Calibre.]
|
You can test by doing the following...if your plugboard info 'disappears' from the T1 after a connection to calibre, connect it a second time, let calibre do its stuff, then disconnect again. Does the plugboard info come back?
If it does, it is indeed the PRST1 anomaly (which, BTW, doesn't occur on earlier Sony models).
Did you set up
both plugboards as per the detailed step-by-step, i.e. the one for 'device_db'
and the one for 'epub'? You can't stop the anomaly, but the 'epub' plugboard should protect your epubs from you noticing it when it does happen.
It is important to understand the difference between the 2 plugboards, so I'll attempt to explain.
- The 'device_db' one writes your plugboard info directly into the PRST1's book database and this is updated every single time you connect the T1 to calibre.
- The 'epub' one (which contains the same data) writes your plugboard info into each epub as you send-to-device or save-to-disk (or connect-to-folder???). So epubs which you have sent to the T1, since you put both plugboards in place, should be protected when the anomaly happens. The anomaly causes the T1 to re-extract all data from the epubs on the T1. Because the plugboard data in the epub is the same as that in the T1 book database you don't notice the anomaly has happened.
Next time you connect the T1 to calibre, calibre will send the 'device_db' plugboard info, once again, to the T1 book database... and on it goes until the next anomaly.
If you change metadata in the main calibre library (author, series, title) the 'device_db' plugboard will keep the T1 book database absolutely up-to-date next time you connect. However, the 'epub' plugboard info was only inserted into each epub at the time you copied it to the T1. So you can see how it is possible for T1 epub metadata to become out-of-synch with calibre metadata, over time, when the anomaly happens. However, if you go through the connect/disconnect routine a couple of times, eventually the device_db plugboard should 'win' and you're properly up-to-date again.
If you've followed me so far
, just to add a final bit of info. Unfortunately it doesn't appear to be possible to protect your PDFs from the anomaly, other than by trying another connect/disconnect cycle. However, TXT files are immune from the anomaly.
To get back to your original question...you should not need to reformat your T1 but resending all books, once only, after both plugboards were added was a good idea because now you should be protected when the anomaly happens.