How to Set Up a MAC for Self-Publishing to Itunes

Adventures in Apple-land: Using a MAC as a Self-Publishing Platform

When we last left our hero, he had made the decision - and leapt into the mist.

I ordered a MAC mini (hold the fries) and it arrived two days later. I celebrated by cleaning my desk and removing all the old hardware, cables and everything dusty.

We'll do this in steps. First, the unboxing:

Nice box from Best Buy online. Gas Duster for reference.

And look at all the stuff inside...

All hooked up with leftover/spare everything.

Proof that the Internet works - from the people who made my MAC necessary.

My full set-up with the right two monitors going to my Linux box.

I connected it up to an existing monitor, plugged in an un-elegant leftover USB keyboard and mouse, and followed their instructions. It's been some years, but the clunky stuff we use in the non-Apple world looks shoddy compared to its elegant design. (Next quarter's royalty payments should give me a Bluetooth Apple keyboard, mouse, and maybe the extra RAM - this quarter's bought this MAC.)

I last used one of the old PowerMACs (15+ years ago) so the familiar startup sound took me back to younger days...

Back to business.

As I suspected, everything I've needed to publish on Windows or Linux are available for MAC. So far, anyway. I'm in the middle of downloading programs like LibreOffice, Firefox, Calibre, Sigil to see if this is all available. I've got nothing against Safari, it's just that I'm not used to it. But yes, MAC versions are available for all of these, and the Writer2Epub plug-in works as well.(See below for links and download sizes.)

The idea here is that a non-MAC user should be able to shift platforms (like how I ditched Windows for Linux.) I'd worked out a production flow which had creation in LibreOffice, and side-checking with Sigil, meta-data stored in Calibre. Firefox has always been my browser of choice (IE has always had security issues, and Chromium is fine, but not the same.)

So if a person has that production flow in Windows or Linux, they can do it on the MAC, too.

Next, in order to publish on iTunes, you have to have an Apple ID, which is fairly easy to set up, and then download iTunes Producer.

Since we are straining my "poor" overworked Internet provider, we'll let that run and get some sleep tonight.

- - - -

After coffee and breakfast: Well, the download didn't. Turns out Safari doesn't handle resuming downloads simply (takes a command line trick.) So I restarted that Firefox download and will install "downthemall" plug-in to make this happen. (With that download manager, you can restart paused/incomplete downloads.)

Again, just making it so I can use the tools I'm familiar with to get to work on this platform.

The blow-by-blow continues...

Since this is a 56mg download and my provider is currently penalizing me at their end of their month, I'm going out to do my chores now, and come back to finish this (hopefully.)

Update: The MAC has pre-configured SAMBA filesharing - nicer than out-of-the-box Linux, actually. OK. Funny enough, the common denominator is reverse-engineered Windows network sharing. Will need some more time on this to figure it out completely. Some work on this (while waiting for my downloads) showed that logging in as a remote user was easiest to get access - but is not work-safe for kids or "hacker wannabe's".

I've taken all my current files and sending them over via the network, so I can test the entire workflow. Calibre and GIMP need something to do.

(Oops - this download didn't go. Too much too fast for my poor Internet Provider, who says I've already downloaded too much, until next month's allotment, which starts in a few days.)

Meanwhile, I finally got the downloads down and, well - see below...

- - - -

What you'll need to simply get started creating your ebooks just like you did on Windows or Linux:

The iTunesProducer file is a 305mg download. Firefox is 59mg, Calibre is 84mg, Sigil 34mg, LibreOffice 190mg, and writer2epub is 1.4mg. So you may be at this awhile to get what you need. Oh - and don't forget GIMP (95mg) for doing your covers.

This means a person can easily shift to the MAC. What the MAC mini does is to make it relatively inexpensive. Anyone who has dealt with older machines usually has leftover mice and keyboards and monitors around. (USB and HDMI video - not the older plug-in versions - although I have a VGA adaptor coming...)

[Update: The Sigil initial download wasn't accepted by the MAC - until I Googled the phrase and found this solution. With that window open (security preferences) it will allow you to install the dmg package that just failed, one at a time. (No need to permanently set yourself wide open.)]

[Update 2: Hold down the control key when you click open, and you get the same "Are You Sure?" dialog.]

[Update 3: While this could be a separate post, all you really need to post your book to the MAC is to download and install their free iTunes Producer. You manage your books in iTunes Connect (http://itunesconnect.apple.com) via most any web browser. If you are already editing it on your Linux/Windows platform, you don't have to download a bunch of stuff to get going. I use Dropbox to sync my latest version to my MAC, and then simply upload those files in the next batch I have going. I then edit or improve the meta-data through my web browser. Again, the added value of a MAC is in the A/V you're now able to create for marketing your book.]


That means we have all the tools we need to create and edit.

However, until I solve file transfer, I will be using the workflow described below. By getting all the vital tools over to the MAC, it says that a first-time self-publisher could easily use a MAC to get their books up and going. And anyone dissatisfied with Windows could make the jump to a better platform. If you need elegance, that would be the only reason to move to a MAC from Linux, IMHO. But I'm a geek down deep and have always loved to get below the hood and tinker. My MAC mini will be a very capable back-up for my dual-monitor production machine.

As I said, when I solve the file transfer (SAMBA) scene, then this may change.

Whoring the MAC to get to iTunes.

The basic summary is that I'll be "whoring" this platform, using it mainly as a "go-to girl" for uploading to the various distributors - but chiefly, this MAC will be used for uploading to iTunes and handling audio recording. Reason being that file transfer is buggy at best - until that is solved, there is no real way to get files across except "sneaker-net" with flash-drives.

One additional feature is the native ability to simply create podcasts. Yes, you can do this with either Windows or Linux, but having a second machine should make this much easier - as I don't have to move/unplug the mic. Yes, I can get good old Audacity for MAC as well. Podcasts and videos are the necessary content production needed for marketing.

This MAC didn't come with any iMovie (it's a $15 app) so it also doesn't qualify (right out of the box, anyway) to handle making audio into video. My Linux version actually came with several of these programs - again, I have those 15 years which was more Linux than Windows during that time. So creating videos is still a learning scene.

[Update: I've found most of these Linux NLE's (movie editors) are also ported to MAC OSX, so that's an upcoming adventure.]

Plus, my Linux box has dual monitors, which is a simpler work flow.

I'll get there with the MAC, but essentially it's the learning curve which is throwing rain on this parade. (Coming up on Day 3 where I should have been editing and publishing.)

The bottom line is: Yes, you can do everything I do to self-publish a book on all the various distributors on a MAC. But just because you have to publish to one distributor, doesn't mean you're going to have to publish everything from there. It's possible, though.

All these downloads will make my learning curve on this platform simpler and shorter.

An alternative work-flow

Go the Leanpub route to build your book. This gives you a tested version at the end, which should pass muster. Means you

1. Get a MAC (mini) and set it up with all these programs.
2. Edit your book into shape with LibreOffice, but save it as an HTML file.
3. Next, you open that in Leanpub and tweak it online.
4. As part of that, create the cover in GIMP.
5. Then, when you are happy with it, publish, then download their generated epub, mobi, and PDF files.
6. Right after that, test it on Lulu to be sure (and to get your free ISBN.)
7. If no go, sneaker-net it over to another box to tweak it on Sigil until it passes (or fire up a virtual machine and do it there.)
8. Then upload to iTunes and everywhere else, saving your metadata to Calibre so it's a copy/paste production.

Now you can do it all on a MAC. See, that wasn't so hard, was it?

If I were just starting out, this is the route I'd take, since that single investment in a MAC mini would pay for itself in short order.

Additional marketing goodies

The MAC started out as a desktop publishing wonder, but then quickly got adopted by the A/V crowd and never looked back. As an addition to my other workflow, this new MAC will be able to do my podcasts and video production to be able to reach a wider audience with my book projects. With LibreOffice being able to export PDF's with embedded links (Leanpub's capability for your finished book) you then have all the major formats anyone could want to find about your book - and also, to create packages of goods anyone could want. (And also do something like Tim Ferris' bittorrent marketing)

For me, I'll have a standalone solution to audio and video in addition to my book publishing. So this investment - which pays for itself in the fees I don't have to pay to any aggregator to just reach iTunes - gives me auxiliary bonuses. Before this, the mic would have to be unplugged and moved away and back when I wanted to record, which left it less than useful - and less prone for me to actually do the recording. (Not to mention that the MAC mini has no machine noise, so if I ever build a sound booth, it will fit in perfectly.)

Not bad for a bunch of leftover peripherals and a $600 box.

Hardware wars - over?

I used to mess with building and re-building machines in the old days, accepting any amount of used equipment people would throw my way. What I found was that it was burning my time with little results. Re-cobbling parts together would as often as not result in no working machine, even when I put the original one back together "just like it was."

The real scene is that producers have moved to new formats of RAM and connectors which have made the other machines too expensive to upgrade. With few exceptions, such as installing the maximal RAM you can when you buy a machine - key on Linux (Windows often won't see or be able to use the extra) - there's little additional to do.

With the MAC mini, you can go to top of the line for about twice as much, which will give you 16gigs of RAM and a monster CPU - but the question for a struggling publisher is the cost benefit.

$600 is just above what I'd consider a decent price range for a new box. Sure, I can get a machine with the same specs as this MAC Mini from Overstock or similar for maybe $300, also with no monitor (but giving me yet another keyboard and mouse) - but it wouldn't get me into iTunes. Sure, I could spend the time getting torrents downloaded of a MAC disk image which would run on a virtual machine inside my Linux box - but that's for the uber-geek.

Time invested needs to leverage into income. For the average author, getting a MAC mini as a replacement computer is quite a leap, but can result in doing everything you need. The extra $200 also means a week or so that I don't have to spend getting a machine up and running on Linux - and just as stable.

Note: In my mind, there is no reason to use Windows, if you haven't guessed this by now. Part of the upgrade was giving away my last two Windows-only machines, which were on obsolete hardware. No way to go back. (I do have XP running on a virtual machine, for a minority few programs which were only ever released to Windows platform. It's still amazing that each Windows machine has to have it's own anti-virus and firewall program,when Linux and MAC natively don't.)

[Update: I was annoyed by the lack of keyboard shortcuts. So I got a bluetooth keyboard which 1) didn't have the same look and feel - it slowed me down with errors, and 2) quit working once the original batteries went on the blink. So I plugged back in my old USB keybord (with those satisfying pushing keys/clicks) and found I could remap the "alt" key to do the same as the "command" key in Windows. As there are very few shortcuts which actually use the alt key on a MAC, it really solves the problem. (Chief short-cut I use is alt-tab - from Windows days - to shift between applications.) Situation solved - other than it takes another USB outlet.]

[Update 2: I've found that a lot of hardware which would only work with Windows (not on my Linux box) has been ported to MAC, so drivers are available. One scanner I thought was only available on XP was able to get going under a MAC, courtesy of the companies updated drivers.]

Batch production 

My current plans are to do the development of batches of books, then copy sets of epubs with the final-final versions and their covers over to a jump-drive for transfer. This looks to be the simplest, most direct, and most efficient production line. This makes iTunes the last on the block, maybe excepting Leanpub. (Even Amazon and Smashwords accepts epubs, so this is again the lowest common denominator approach.)

Out of the dozens of books I've published to date (OK, it's over a dozen dozen at this point) the public domain and PLR books sell the best. So setting up batches of these (or saving up collections until I have a batch) is simpler than some indie author writing original fiction. For that person, the best approach is to fire them out when the editing and proofing is done - and then get busy writing the next one.

Writers get paid by selling books, not by worrying over whether they are selling. "Writing feeds the soul; Publishing feeds, clothes, and houses the body - plus pays for the occasional night out on the town." It's the backbench of books which proves that theory.

- - - -

While this last section really requires a new blog post, a short analysis today (while waiting for downloads, etc.) showed me that this is the core of my little one-man-band of a publishing company.  I have a few large batches worked up for the near future, and then I'll be ready to move over to a quasi-original derivative set of hand-illustrated classic stories.

Right now, I'm learning from classic copywriters. Once I'm content with a sufficiently deep back-bench, then I'll move over to marketing what I've been creating and meanwhile doing a segue over to these illustrated children's fables.

Lulu just compounded my work-flow by forcing me to get a MAC in order to do what used to be their job.

What this will eventually do is to improve my marketing backend, as I can do a lot more A/V work with this set-up.

Now you've had another glimpse into the world of an avid self-publisher.

Yes, there's a book in your future - part of which you're reading now. Someone has to tell the story of how anyone in the middle of nowhere can create a "publishing empire" from little more than consistent, focused production over a few years time.

Stay tuned...

Related articles

• Greenie 14.04.1 Is an OS for Users Who Edit eBooks and Documents
• LibreOffice: An Basic Office Suite, for Free
• Self-publishing to iTunes - Simple or Extreme?
• The only Constant is Change - ebook publishing continues to shift.
• Updates to Online Publishing - Easier Than You Think...
• Notes on Book Publishing

How to Publish an Ebook, Audiobook, Video Ecourse at the Same Time

(photocredit: andrewmalone)

You may feel like a one-man-band, but it's always better for an indie author to work smarter, not harder. (Pays better, too.)

In researching podcasting, I came across some resources you should know about. This gives a slightly different workflow, but will earn you more income over the long haul.

While you are writing  your book, you also record the audio book and create the video series for a later ecourse. (Applies more to non-fiction books.)

It goes somewhat like this:

1) You blog your book. Every chapter or sub-chapter starts out as a blog post. (When you start a new book, set out a new Blogger blog or equivalent.

2) Once you have it the way you like it, then use the age-old editing method of reading it out loud - fix anything that doesn't read easily, as it's not the way you'd speak it. And similarly, old advice says to write like you talk.

3) When it reads well, then post it live.

4) Now, as you've practiced this a few times by now, go ahead and record it. Fix it up with Audacity. Now - after taking advantage of Podiobook's Mentorship program - submit it there .

5)  Come back with the hosting link and then include it as an enclosure link on your blog post so people can pick it up from your blog's RSS feed.

6) You go to Lean Pub and give them the RSS link, so they will auto-create your ebook from that blog. (Yet another learning curve, but a nice one.) [Update: best method is to scrape the individual pages and assemble in LibreOffice. Import to Leanpub if you are writing an original (for PD or PLR you should export with Writer2Epub plugin and proof in Sigil.) Preview it and put it up for sale on Leanpub (see notes on Leanpub below).

7) Since you have the audio and text, go ahead and make a slideshow/powerpoint of your post. You can make a slidecast on Slideshare.net, or simply create images out of the slides and use Camtasia or other program to make a video from the slides and audio. Post that to YouTube or similar if you want, linking back to the blog and Leanpub.

Time for your next inspired post.

What have you accomplished with all this?

If you're doing long blog posts (like my unfortunate habit) you'll have a chapter of your book ready, plus the audio chapter, plus a video for an ecourse.

As you continue to build your book, you are creating quality content in multiple formats.

When your book is ready, you then have an ebook already created by Leanpub, a collection of audio ready for uploading to ACX for Audible, and a series of videos which you can offer on an exclusive subscription basis to your readers - meaning you just created three potential income streams from one set of work.

What this saves you is having to drop everything to record the audio, or pay someone to do it for you. Same for videos, which can get tedious - so neither gets done. Most authors just publish the ebook and skip the rest. But readers like different formats - and all those digital versions can cross-link with each other, making it possible for you to Search Engine Market your book easily.

Every review of the data will make the book tighter (creating an outline before you start, particularly if you make the outline into a powerpoint can speed your writing as well.)

The feedback from your Leanpub audience will also help you improve the book as you go.

This assembly-line scene helps you work much smarter, instead of going back to rehash the old stuff once more. Again, you wind up with products which can be utilized on multiple platforms, each bringing you a separate income stream.

- - - -

I'm actually planning to use this line to revise a book I published last year. I'm going to add some chapters to the start of it, and clean up the content right through.

So it will go:
a. Set up a new Blogger blog.
b. Post the existing content in the order it currently is in. You could work at setting arbitrary dates for it such that there are two or three days in between in case I want to add more material, but this is probably unnecessary. Go ahead an publish it via Leanpub, putting it up for sale.
c. Start writing the new beginning material and use the assembly-line approach above:

1. Outline
2. Text
3. Audio
4. Video

d. Once the new material is complete, then take up each earlier blog post/chapter and put it through 1-4 above, which will tighten the prose.
e. When the book is complete,  you get it re-imported into Leanpub and they'll create your epub and mobi files. With the epub file, you can then publish anywhere.

Of course, you could get a Markdown editor (until you know enough to use a straight text editor) and so you could publish to LeanPub as you go - but the RSS feed arrangement is probably the simplest.

This is all simple theory at this point, but come back in a couple of months and I'll have put it to the test (and updated this blog post.)

The scene I'm working on here is to add value and publish to multiple formats with the least possible number of steps.

Note: you can also scrape your Firefox-viewed blog-posts, then cut/paste into Libre/OpenOffice to export to PDF. But Leanpub say's you'll also have that PDF file. I like my PDFs in trade paperback size (6x9) as they are closer to what most ereaders see, and will display better. Meanwhile, that 6x9 format makes your book ready for hardcopy publishing via Lulu...

Work smarter, always. Multiple streams of income from one set of writing.

Sounds like it should work.

If you have other ideas, leave a comment.

[Update: Notes on LeanPub -

Overall, a very, very nice site which is maybe 4 years old (started sometime in 2010.) However, it uses Markdown, which is a simple markup language to learn. Different from having a full GUI in front of you like LibreOffice.

Right now, it's easier for me to scrape each page and paste into Libre Office than it is to import and tweak the result in LeanPub. Doesn't mean it will always be that way. I've got a Markdown editor now, and the wrapping has just come off, yet. (Still has that "new app smell.")

The reason I'm sticking with this is to be able to bundle my books. Probably sole and only reason. I know that as I keep at this, I'll work out a decent speed on re-publishing these books through this distributor. Still, this is far more straightforward than Smashwords and the arcane rejects which iTunes and B&N hand down.

My advice would be for someone to start here, particularly if they are using a text editor anyway. Markdown is simple to learn, and this gives you a very fast route to getting published. You wind up with a pdf, epub, and mobi file - all can be readily used with various distributors.

It's just another learning curve.

If the other distributors would enable bundling, this wouldn't be necessary. However, LeanPub is improving daily (shortly to have an affiliate function) so this is well worth the effort.

The other thing, like Wattpad, it's a way to write with reader input. So they have a say in what the book ends up like. That may really be the most invaluable part of this.]

[Update 2: Leanpub doesn't do public domain books. Gets you canned.]

Related articles

• You may have thought self-publishing ebooks was bad - try audiobooks...
• Collected How-To's on Writing and Publishing Your Ebooks
• How to Drive Yourself Sane - Checklist for Self-Publlshing
• Tips and Tricks for Indie Authors in Self-Publishing Land
• Go Thunk Yourself! Online Self Help Course - Introduction
• The Thrivelearning Institute eLibrary Catalog