Thread: [Conversion Output] KePub Output Plugin
View Single Post
Old 02-06-2022, 10:00 PM   #500
Gone
Out of order
Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.Gone ought to be getting tired of karma fortunes by now.
 
Posts: 601
Karma: 1652684
Join Date: Feb 2014
Device: Libra Colour
Quote:
Originally Posted by davidfor View Post
I can think of two reasons for this. And I think you might have both.

Firstly, calibre is doing a conversion to kepub, not using the KoboTouchExtended driver to send the book to the device. Either, the KoboTouchExtended driver has been uninstalled, or it has been disabled. In either case, the built-in KoboTouch driver is being used. You can check the state of the driver in the Plugins page of the preferences.

You might have changed the default send-to-device action to the "Send specific format" instead of "Send to main memory". You can change this by right-clicking (or the Mac equivalent) the "Send to device" button, clicking the "Set default send to device action" and choosing "Send to main memory".

KoboTouchExtended is activated. KoboTouch is deactivated.When I plug in my Kobo, in Calibre it says that KoboTouchExtended has been detected.

You were right about the "Send to main memory". That was the culprit for me. Now it works like before.

Many thanks! It has been bugging me for a while.
Gone is offline   Reply With Quote