![]() |
#1 |
Member
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 18
Karma: 12494
Join Date: Apr 2013
Device: Nexus 7, Kindle
|
Read/Unread syncing issue
Okay, so this is probably a very specific problem which I'm just going to have to live with but I thought I'd ask about it here just to make sure I wan't overlooking something obvious.
I read alot of fanfiction on my tablet and because I don't have a wireless connection at work I use ffdl to download them to calibre and then sync them over using CC. When something downloads new chapters, ffdl marks it as Unread and then when I read them on my tablet I mark them as Read in CC. I thought perhaps that this might cause an issue if I downloaded new chapters before syncing CC to Calibre to capture the change in the Read status from the what I had read since the last sync. So I've been syncing my device then disconnecting before allowing ffdl to do its thing. However, I've noticed when I sync the epubs with new chapters over to my device the status changes to Read even though it was marked Unread before the sync. Shouldn't the timestamp on the metadata in Calibre be newer then it was in CC? Basically my thought is, if the Read/Unread status in Calibre is newer, why is CC overriding it with the info it has? I've got a work around so if this is just an issue I'm going to have to deal with I'm fine. I was just curious. |
![]() |
![]() |
![]() |
#2 | |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,416
Karma: 8012664
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
Quote:
The timestamp plays no role in syncing the read column. Instead, it uses these rules in the order listed.
Exactly what gets changed when during the sequence you describe isn't completely clear to me. My guess is that we are in the situation where you change Read on CC and FFDL changes Read in calibre between two connections. If so, then according to the rules CC wins. |
|
![]() |
![]() |
Advert | |
|
![]() |
#3 |
Grand Sorcerer
![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Posts: 12,416
Karma: 8012664
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
|
The behavior you are seeing might be caused by the bug described in this post. If FFDL causes metadata to be sent to the device a second time during a connect, the bug could cause the Read info to change back to what it was before the connect. I am not sure, but it sounds that that is what you are describing.
|
![]() |
![]() |
![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Plugin Request - A Way to Tell which Books Are Read vs Unread | Milece | Plugins | 2 | 09-11-2012 04:00 PM |
Issue with syncing to last pg read (Kindle) | Statch | Calibre | 31 | 07-24-2011 10:12 PM |
Unread vs. Read books | xplosivo | Library Management | 2 | 06-15-2011 11:34 AM |
Read/unread field or button | Larksong | Library Management | 4 | 05-20-2011 12:21 PM |
Syncing Kindle with a very large Instapaper unread queue | 3rdparty | Amazon Kindle | 3 | 01-14-2011 03:31 PM |