Wednesday, 2 March 2016

How to backup and synchronise your writing data safely

One of my recent challenges has been to design and test a free backup and synchronisation solution. The solution is part of my next book, “How to write a Kindle book for free”.

The design principle was that any changes made to your local writing folder or directory are automatically synchronised into the cloud. One additional caveat is that if a different change is made in the cloud and locally that no data is lost. The solution must also be cross-platform compatible, in other words it works on a Mac, Windows and Linux. Finally, the solution had to be as easy to implement as possible.

The cloud part of the solution was a very simple decision. My experience with Dropbox over the last few years has been painless and straightforward. Also Dropbox is compatible with many apps, so any data would be backed up using this solution too. You could use Box, iCloud, Cubbie, or any other cloud solution that provides a local folder or directory.

The design principle is to synchronise two local folders. However, one of the local folders is a cloud folder, in this case Dropbox. The local folder is where I save all of my writing data, backups, images, notes and so on. This solution could, of course, be used for any project, writing or otherwise.

I tested many free synchronisation applications, but struggled to meet all of the requirements. I suffered crashes, unresponsive software, even data loss on a couple of occasions. Luckily this was in a testing environment.

In the end I found just one application that has worked extremely well. FreeFileSync is available for Mac, Windows and Linux. The latest version I have been using is 7.9, and can be downloaded from http://www.freefilesync.org/download.php.

The installation of the software is straightforward on all of the platforms. There are two applications included with the download:
  • FreeFileSync
  • RealTimeSync
FreeFileSync is used to create the synchronisation files or folders and to setup the type of synchronisation required. There are four choices:
  • Two-way synchronisation
  • Mirror (1-way synchronisation)
  • Update (1-way copy)
  • Custom (ability to customise your own synchronisation rules).
Once a folder pair has been chosen and the synchronisation type confirmed, the job can be saved. In addition, there is an option to save a batch file (SyncSettings.ffs_batch).

The batch file can be imported into RealTimeSync providing all of the settings required. RealTimeSync monitors the source folder, in my case the local writing folder, and immediately synchronises any changes. RealTimeSync is setup to run when the computer starts up.

I didn’t want to have a realtime synchronisation option, but rather a user specified time increment. This meant using FreeFileSync with a scheduler. I decided on a 15 minute interval.

In the case of windows I simply created a task in the Windows Scheduler to run every 15 minutes.
  • Program: “C:\Program Files\FreeFileSync\FreeFileSync.exe
  • Optional Argument: “C:\Users\ValuedUser\Batch Files\SyncSettings.ffs_batch.


If using Linux, I would recommend using Cron or some other scheduler option. Unfortunately, I have not had time to test a Linux installation.


On the Mac I used a free scheduler application called Scheduler for Macintosh version 6. It is available from http://www.macscheduler.net/. It is possible to use Automator, or even cron, but I wanted to keep it simple and intuitive. Automator always leaves me a little confused and cron is command line. Mac Scheduler 6 is both easy to use and intuitive.

I placed the Scheduler.app into my user startup items so that it runs at computer boot.





The schedule is created using the Document option which allows the user to specify both the application to run and any arguments required. In this case the “SyncSettings.ffs_batch” file location is all that is needed. I also set the repeat interval to 15 minutes.

The final stage, after implementation, was testing. I modified the contents of the same file in Dropbox and on my local folder in slightly different ways. In some cases, with other applications I tested, this resulted in one of the files disappearing and hence data loss.






In the case of FreeFileSync you are protected. An informative pop-up occurs if there is any danger of data loss.

I have been running this backup and synchronisation solution for a couple of weeks now. File and folder changes are made daily. The system has worked flawlessly with the added bonus that my iPad and iPhone app data, the data that is saved to Dropbox in this case, is also being backed up to my local drive.


SM

Saturday, 27 February 2016

Can you Really Write a Kindle Book for Free?

A thought occurred to me recently. Is it possible to write a professional looking Kindle book for free?

Don’t misunderstand me, I love my current software tools. I use UlyssesIII, Scrivener, Scapple, Affinity Designer, Pixave, Vellum and many others. I purchased these applications over the last few years, my decisions based mostly on blog reviews. When I purchase a piece of software I want it to be intuitive, easy to use, and feature rich.

The thought turned into an idea. Could I write a book about it? I started my research a few days ago, and do you know what? I reckon you can!

The beauty of writing a book using free software is you have to get down and dirty sometimes, and that is when you learn more about the process you have taken for granted in the past.

I have found some terrific free software. Some of it is a little clunky and not terribly intuitive, but others are real gems.

Take the writing application, for example. I looked at so many, most were good but lacking certain features I had become accustomed to. Some were in beta, and even though free they might not remain so. In the end only one application met my requirements.. and then some! TextNut!

TextNut reminds me of Ulysses, it doesn’t have quite as many features, but it is a joy to use and even offers some functionality that Ulysses doesn’t have.

I wrote 3000 very enjoyable words in it yesterday with no problems at all. The beginnings of the book structure are there, and my screenshot testing went without a hitch.

It exports via HTML, RTFD, PDF and Markdown. It uses Markdown, but you can write in wysiwyg.

The developer offers an in-app purchase to allow unlimited libraries and external folders, but the 4 libraries and 2 folders are more than enough for one book. It supports themes, exports to Medium, Blogger and Wordpress, and also has a ‘Zen’ mode for distraction free writing.

I am really impressed, can you tell?

Oh, and one final unexpected surprise, there is an IOS version that will sync via Dropbox or iCloud. The IOS version is also free with the same limitations as the OSX version, but it means I can write on my iPad too!

The developer is approachable and kindly gave his consent for me to use screenshots of the app in the book. TextNut is available from both Apple app stores. Here is a link to the app website: http://www.textnutwriter.com/

Thanks to TextNut, my next few weeks won’t be all cussing and swearing as I struggle to use free software to write the book. Although formatting is something I look forward to with a quiet foreboding.

SM

Monday, 22 February 2016

Visual Mapping for Writers is Alive!!

I am pleased to announce the release of my new book Visual Mapping for Writers in Kindle format. It is available from here:

UK: http://tinyurl.com/hoy2ede (Preview: http://preview.tinyurl.com/hoy2ede)
US: http://tinyurl.com/j675o6z  (Preview: http://preview.tinyurl.com/j675o6z)


I am debating whether to produce a Createspace version. My reticence comes from the predicted retail price of the full colour edition. I am not certain I could sell sufficient paperback copies to cover the time it will take to format it. I have done the usual things, such as increasing the book dimensions, choosing an appropriate font size, reducing line spacing and reducing image sizes. All this in an effort to reduce the number of pages. Unfortunately, the book is still 120 pages and would carry a retail price of £15.99 or $19.99.

Friday, 19 February 2016

The Vagaries of Kindle Image Formatting.

I am frustrated and a little disappointed at the moment.

I have spent the last week trying everything I could to reduce the file size of my latest book. The book has over 100 images, all created with care at 300dpi. I used my Retina Macbook Pro to ensure the original files had the highest resolution (144dpi) in lossless PNG format.  The results were very encouraging in the beginning….

Amazon charge a delivery fee for every kindle book sold. The cost is based upon the file size of the mobi7 folder. The greatest contributor to the file size is the image folder. I uploaded a draft copy of the book to the KDP and the delivery fee was shocking!

I tried various image optimisers. I hoped they would help optimise the images to reduce the file size whilst retaining quality. These worked extremely well. I had great results with Tinypng and ImageOptim.

Vellum is my formatting application of choice. I enjoy the experience, the simple and intuitive interface, and the results are always great.

I created larger dimension images at 300dpi, but smaller in file size than Vellum generates. I unpacked the Vellum generated mobi file and replaced every image with my own JPG version. I then recompiled using the Kindle Previewer. The results, in local testing, were very promising. The total mobi file size was reduced by over 35%.

Finally, I uploaded the file to Amazon KDP and the delivery cost was greater!

I now understand what happens in the background and, I must say, I am disappointed. Despite my optimised image files being smaller in file size than the original Vellum images, the mobi7 images are simply a reduced quality jpg. I had assumed the mobi7 images would be reduced in dimension, not quality.

I had increased the image size to a width of 1500px for all of my images and optimising them meant they were a smaller file size than the Vellum images. The Amazon conversion process for the mobi7 images is to simply reduce the jpg quality (to 69%). Because the image dimensions were greater (Vellum uses a 97% quality 1280px wide file) the mobi7 images were also larger in file size.

I even tested replacing a jpg with a gif. Unfortunately, the gif was over 200kb and Kindle Previewer converted it to a jpeg resulting in the same mobi7 size.

The conclusion to this sorry tale, at least for the moment, is the only way to reduce your Kindle book file size is to either reduce the image dimensions or the number of images contained within the book. The other option, one I am reluctant to entertain, is to increase the price of the book. My original target price was $5.99 or £3.99. The Amazon download fee means the price of the book may have to rise to $6.99 or £4.99, something I really don’t want to do.

Visual Mapping for Writers.

The book is coming along nicely. I reckon 90% of the words are written. The image capture and collation are almost complete.

Visual Mapping for Writers: Non-Fiction uses a different approach. It introduces the reader to visual maps, but aligned with the book itself. The maps and processes featured were all used to create the book.

I have found that visual mapping can help writers improve content, complete the book faster and have some fun on the way!

If the book does well I am looking forward to writing the sequel, Visual Mapping for Writers: Fiction. It is already planned and ready to start.