People often ask me how the writing’s going. I interpret the question pretty broadly. As in, how’s the new writing going? Fairly well, thanks.
And: how’s my first novel doing?
There’s no short answer to that question. At least, no
short accurate answer.
A Time and a Place has been available just over two years now. I usually tell people that I’m not quite in Stephen King territory yet but it’s going reasonably well, and that my excellent publisher tells me that the book has paid for itself, which I hope leaves the impression that it’s achieved some measure of success.
Whether the book truly can be considered successful depends on who you’re asking, I think. I suspect that any big-time publisher might condemn the book as a complete and utter failure. Dan Brown’s The Da Vinci Code sold eighty million copies. Compared to that, A Time and a Place has not exactly taken the world by storm.
The aforementioned big-time publisher might—I say might—concede that the critical reception for A Time and a Place (professional and otherwise) has been reasonably favourable, but they would probably also feel compelled to point out the rather small sample size.
Some novelists, I suspect, might suggest that merely completing and publishing a novel constitutes success because doing so is goddamned hard. While I accept that, most novelists would also admit that that’s not enough. Almost all of us (if we’re being honest with ourselves) would admit that we define real success as massive book sales and wide critical acclaim. On those scores, A Time and a Place can not exactly be considered an unmitigated success.
Still, to be fair (especially to those who helped me with the book), it’s probably performing perfectly fine considering it’s a first novel by an unknown author published by an independent press. I assume all responsibility for any lack of greater success. And I am well aware that the freakish success of an author like Dan Brown is pretty much a complete fluke.
But I’ll let you be the judge. Here are the facts. Let’s start with sales.
of my most recent Royalty statement, for the first quarter of this year, covering
up to March 31st 2019, A Time and a Place has sold a total of 454
those, my publisher sold 333 print editions, 98 e-books, 1 e-library edition,
and 22 audio books.
Of the 333 physical copies my publisher sold, I sold 134
of those myself after purchasing them from my publisher (at a discount). I gave
away 13 books as gifts, another 2 were kinda gifts (I thought the people would
pay but they never did), and 1 copy was stolen after a reading at a library (she
picked it up off the table when I was across the room. I didn’t confront her. I
dunno, maybe she thought it was free). I
have another 18 copies sitting in my basement to have available for readings
and book fairs and so on.
I earn 50% of net on any e-books sold, 10% on print (possibly more if I sell them myself, depending how much I charge), 50% on e-library copies, and 50% on audio books. A Time and a Place has earned me a total of $5989.68 since July 2017 when it first came out. Factor in the cost of purchasing books at a discount from the publisher to resell, all the marketing and promotion I do to supplement what my publisher does, along with treating myself to attending one writer’s convention per year, and I’m not exactly getting rich. Actually, technically I’m in the red, if I’m honest about how much I’ve spent on writing related activities since I began all this.
So yeah, I don’t think I could call A Time and a Place a huge success financially so far.
It’s fared better on the critical front. Reviews have been mostly positive.
On Goodreads, it has been rated 42 times, accompanied by 23 reviews. It currently averages 4.35 out of 5, consisting of twenty-four 5 star reviews, thirteen 4 star reviews, four 3 star reviews, one 2 star review and one 1 star review. It’s been added to 100 bookshelves, including 45 To-Read shelves.
23 of those 45 ratings have been accompanied by reviews. The reviews range from positive: “Mahoney writes with a practised wit,” “I loved this mesmerising audiobook with its non stop action and adventure,” and “A brilliant, often hilarious, thoughtful and amazing read,” to not so positive: “The second half of the book got a bit muddled for me.” “I think that the author was a bit too ambitious,” and “…one of the least likeable protagonists I’ve read in some time.”
On Amazon.ca it has been reviewed four times. All of those have been 5 star reviews.
On Amazon.com it has been reviewed twelve times (one 3 star review, two 4 star reviews, and nine 5 star reviews).
On Amazon.co.uk, it has been reviewed two times (both 5 star reviews)
On Library Thing it has garnered six reviews (two 5 star, two 4 star, one 3 star and one 2 star, averaging 3.57 stars).
There are a few other reviews out there as well, mostly positive, a couple less so, on blogs and Audible. Some are replicated on Goodreads.
Out of the approximately eighty people who have rated the
book, I personally know, am related to, or have met (at least once) around
twenty. The rest are complete strangers to me. Personally knowing or having met
those who have rated the book has been no guarantee of a positive review; three
acquaintances have given A Time and a Place three star reviews.
A Time and a Place has also been reviewed professionally by Publishers Weekly, who gave it a largely positive review when it first came out employing such words as “skillfully,” “entertaining,” and “great” to describe the writing, but the reviewer also discouraged me from getting too fat a head by suggesting that “occasional segments… distract or feel a little overdone.”
The book is currently being carried in seventeen libraries around the world according to WorldCat, in libraries ranging from Austin, Texas to Madison, Wisconsin to Rangiora, New Zealand, and at least three Canadian libraries that I know of, possibly more (despite having only sold one e-library edition; most libraries appear to have purchased print editions).
Does any of this matter? Of course! Otherwise I wouldn’t have written about it. 🙂 Also, I just thought some folks, especially fellow writers just starting out, might find it interesting.
Does it REALLY matter?
Of course not.
But it sure is a great way to procrastinate.
One final thought. Here’s a great Ted Talk from Albert-László Barabási on how to increase your chances of success in any field, writing included.
The Splintered Universe is science fiction, published by Iambik Audio, and consists of three separate audiobooks.
In the third book of the Splintered Universe series, entitled Metaverse, Rhea Hawke travels back to Earth, hoping to convince an eccentric mystic to help her defend humanity from an impending Vos attack – only to find herself trapped in a deception that promises to change her and her two worlds forever.
Here’s an audio excerpt from Metaverse:
And just for fun, here’s a selection of proverbs that Rhea Hawke, the main character in the series, is known for using when confronting a challenging adversary or situation. Proverbs that we all can learn from:
“There are many paths to the top of the mountain, but the view is always the same.” Chinese proverb
“Knowledge is learning something every day. Wisdom is letting go of something every day.” Zen proverb
“The acts of this life are the destiny of the next.” Eastern proverb
“Never cut what can be untied.” Portugese proverb
“A little help is better than a lot of pity.” Celtic proverb
“What a fool does in the end, the wise man does in the beginning. “Italian proverb
“Be careful what you wish for; you’re apt to get it.” Chinese proverb
“She who has been bitten by a snake fears a piece of string.” Persian proverb
“He who wants a rose must respect the thorn.” Persian proverb
“A beautiful thing is never perfect.” Egyptian proverb
“Good soyka should be black like the devil, hot like hell, and sweet like a kiss.” Hungarian proverb
“The night hides a world, but reveals a universe.” Persian proverb
“The difficult is done at once, the impossible takes a little longer.” French proverb
“If you can’t dance, you’ll say the drumming is poor.” Jamaican proverb
“A cat pent up becomes a lion.” Italian proverb
“It’s not enough to know to ride; you must also know how to fall.” Mexican proverb
“Each of us must sometimes play the fool.” Yiddish proverb
“The only Zen you find at the top of the mountain is the Zen you bring with you.” Zen proverb
“Beauty without virtue is like a rose without scent.” Swedish proverb
“After the game, the king and the pawn go into the same box.” Italian proverb
“Call on God, but row away from the rocks.” Indian proverb
That’s the end of this special three part series on author Nina Munteanu and her series Splintered Universe. I trust by now you’ve purchased each book and devoured them all. If not, what are you waiting for? 🙂
I had submitted the files to my publisher, who had forwarded them to Audible (ACX), only to have them rejected because they were less than 192 kbps. This didn’t make any sense to me as I was sure that I’d exported them from Audacity properly. When I checked the files out, though, I discovered that I’d actually accidentally exported a couple of files at 32 bit sample rate. It’s weird this only happened to a couple of files; why would the settings change for just a couple of files?
Anyway, I figured this was the problem, so I corrected those files and resubmitted them.
Audible still rejected the files.
So I went back and had another look. I thought I had the settings in Audible correct, but my mistake (well, one of my mistakes) was that I hadn’t actually checked the files themselves. This was really sloppy on my part. The reason I hadn’t checked the files themselves was because, well, I had checked the files, but I’d done so on a Mac, which doesn’t tell you the bit rate. It tells you a lot of other stuff, but not the bit rate, unless you jump through a few hoops, which I hadn’t done. I’d simply assumed that Audacity was doing what it said it was doing:
It says it’s exporting 220-280 kbps. So isn’t it? Nope!
Turns out I should have selected “Constant” Bit Rate Mode, which would have resulted in a guaranteed Bit Rate of 192 kbps.
Live and learn.
Because of this mistake, I had to re-export all my files at the correct bit rate of 192 kbps.
This meant finding the original sessions of each chapter. Doing so, I discovered another bit of sloppiness on my part: poor file management. I’d carefully saved each session using a specific naming convention, but I hadn’t paid much attention to where I saved the files, other than ensuring they were saved on a hard drive somewhere in, say, my house.
Well, at least I knew all the sessions were saved on a hard drive attached to my MacBook Pro. Fortunately, my searches usually managed to locate the required sessions. Unfortunately, they didn’t always do so. I could not find the final sessions for about four chapters. The good news was that I was able to find and re-open at least the penultimate session for each chapter. This resulted in a bit more work than I would have liked. And I became paranoid that I wasn’t re-exporting the absolute final version of each chapter. Because of this paranoia, I decided I needed to re-listen to every second of every chapter to ensure that they were in fact the absolute final, pristine product.
This cut into the writing time of my second novel, which I usually worked on during my commute, and so was a bit of a drag, but it had to be done. Fortunately, I was able to download the files from Dropbox onto my Smartphone, which meant that I could listen just about anywhere I went. Unfortunately, this usually wound up being in rather noisy environments, which meant that I could confirm the proper pacing of the sound files, and that there were no missed edits, and what the chapters would sound like in the real world, but I couldn’t really tell if there were any little clicks or pops or mouth noise etc.
So I listened to all twenty-seven chapters this way, and during the course of this exercise discovered several chapters that weren’t quite up to snuff. In the case of some chapters, it was because I hadn’t been able to find and export the absolute final version, but in the case of other chapters it was because the absolute final versions themselves just weren’t quite up to snuff.
By “up to snuff” I mean mostly that the pacing was off. The way I had read and edited them had resulted in readings that were way too fast. My brain couldn’t keep up listening to them. They threatened to ruin the entire product. Even if listeners couldn’t tell exactly what was wrong, what was irritating about the product, I was pretty sure that it would still bother them. All of these chapters needed to be re-edited. There were a few other minor issues too that I took the opportunity to correct, mostly sloppy enunciation, and some minor issues with the levels.
If I hadn’t exported the files at the wrong bit rate to begin with, I probably wouldn’t have discovered these other issues until it was too late, so I was glad about that.
Looking back, the single biggest hurdles I encountered during the production of this audiobook was the fact that I performed it myself, and did the whole thing all alone. There was nobody to tell me I was reading too fast, and I was too close to the product to realize myself where I was going wrong. I didn’t actually even clue in that there was a problem until after I’d finished recording the entire novel and completed the initial edit of the first chapter. Listening back to that initial edit, I was horrified at the pace of my read. So I re-edited the entire chapter and it was STILL too fast. It wasn’t actually until a few weeks went by and I listened to the chapter again with completely fresh ears that I was able to tell what the proper pace should be. So I edited it AGAIN and finally got it in the ballpark (I hope!).
I made the same mistake with several other chapters, thinking as I was going along that I was getting the pacing right, but again I didn’t have sufficient distance to be able to tell for sure. It was several chapters before I acquired enough experience to know to insert far more space than I thought I needed. Doing so made it far easier on subsequent passes to edit the material correctly, tightening it up a bit.
Had I been a seasoned performer, I would have been able to get the pacing right in the performance, which would have resulted in one heck of a lot less editing.
At least one chapter (Chapter Four) was so bad that I was forced to re-record the entire chapter. But by then I had a much better idea what I was doing, resulting in a performance that was much closer to the mark, and that required only a light edit.
Bottom line: it’s mostly about the performance. If you get the performance right, post-production becomes infinitely easier.
I’m not saying that writers shouldn’t read and record their own novels. But I am saying that if you do, have a second set of ears present—preferably, somebody who knows what they’re doing—so that they can set you straight during the recording, which will result in a whole lot less post-production time.
If you can’t have someone else present, maybe just do one section or chapter at a time. This should reduce the learning curve, and maybe by the end of the book your performance which be much closer to what it needs to be.
Still, despite having created a whole lot extra work for myself on this audiobook production, I’m fairly happy with the final product. I did not release it into the wild until I was satisfied with it. I’m also really happy to have this one under my belt. With what I know now, if I ever have to do this again, it should (theoretically!) go one heck of a lot faster.
This made a lot of sense. Audio books are a booming business these days, and it just makes sense to have your book available in as many formats as possible. Also, I’ve been an audio guy since the age of sixteen when I got my first job announce-operating at CJRW in Summerside, PEI, later making my living as an audio technician/recording engineer for CBC Radio for nineteen years.
Doing sound effects in Studio 212 back in my radio drama days at CBC Radio
For an entire ten of those nineteen years at CBC Radio I made radio plays and recorded and edited tons of short fiction re-purposed for the medium of radio. I remember recording a radio-friendly version of Brad Smith’s novel All Hat over the course of a week or two.
So you would think that I would know what is involved in such a recording. Unfortunately, all my experience did was give me a wildly over-inflated sense of my own abilities. Yes, I did (more or less) possess all the skills required to produce an audio book. But somehow I completely failed to appreciate just how much work was involved in doing it all myself, and how demanding some of that work was.
When Lorina suggested I do the audio book, I truly thought I would be able to knock it off in a couple of weeks. Because I could read, I could record, and I could edit. Thinking back, I was pretty sure we’d done All Hat in a week or two.
It’s laughable, really.
Because thinking back on it a little more carefully, I’m pretty sure that the version of All Hat we produced was an abridged version, and it took four of us to do it: a recording engineer, a producer, an actor, and somebody to adapt it. Five people, if you include the casting director. And all I did was record it (I may have edited it, but I don’t really remember). I certainly didn’t read it.
Anyway, turning my novel into an audio book was a great excuse to gear up, so I went out and bought a mic, a mixer, and some other peripherals. I had a week of vacation time coming up and figured I could squeeze all the recording in then, and edit at my leisure afterwards, on evenings and weekends.
After one week of recording though, I only managed to record ten chapters. My wife attributed this to my propensity to get up late, linger over breakfast reading the Toronto Star, casually walk the dog, and then get started recording around 11am. All of this was true. Add to that trains going by, planes flying overhead, neighbours noisily draining pools, and mysterious noises with no obvious provenance interfering with the recording when I finally did get around to it, and you can see why the process took a bit longer than expected. Worst of all, though, was my inability to read more than half a sentence without making a mistake.
Turning a novel into an audio book was a much bigger deal than I’d realized.
In fact, what I originally thought would take me two or three weeks to accomplish wound up taking over two hundred hours spread out over eleven months.
Here are a few thoughts on the process while it’s reasonably fresh in my mind, in case anybody else out there is thinking of doing the same thing.
To record my audio book, I settled on a Shure SM7B microphone. I chose this microphone because I had chosen it back in 2007 to be the main microphone for the radio show Q. I’d tested a lot of microphones and it had sounded the best with the host of that show, and it sounded pretty good on me (if I do say so myself). I would have preferred a Neumann U-87 but I couldn’t afford that (it’s about three grand). But the SM7B (at about $500 Canadian) is a fine microphone with an excellent pedigree. Michael Jackson famously used it to record his album Thriller. Its only limitation that I could see is that it’s a dynamic microphone and you need to give it a boost to get decent levels. But this is easily fixed by placing a Cloudlifter in the chain, providing an extra 25dB of gain.
My weapon of choice, the SM7B
An advantage of the SM7B is that it pretty much records what you point it at and rejects most everything else. This was really helpful recording in my basement. When I turned off the air conditioning, made sure no other appliances in the house were running, and closed the door to the basement, the noise floor was almost non-existent, but there could still be some extraneous noise, so it was helpful to have a very directional microphone.
You do have to work the SM7B pretty closely to get a nice, plummy sound. The host I used to work with on Q worked it so closely that I wound up sticking two pop filters between him and the mic to avoid popping. In my case, I used the A7WS windscreen that comes with the mic out of the box plus one pop filter. I still popped a bit, but I had ways of dealing with that, which I’ll come to later.
My fairly straight-forward home studio in my basement.
The rest of my setup was pretty simple. You can see it pictured here. Basically the SM7B plugged into the Cloudlifter, the Cloudlifter plugged into a Steinberg mixer, which in turn is connected to a MacBook Pro via USB. And a pair of decent Sennheiser headphones and a mic stand. I read the script (just a PDF version of the novel) right off the MacBook, flipping back and forth between Adobe Reader and my audio software as required.
I recorded almost everything in Cubase, which came with the Steinberg mixer, but I never really got to like it. I’ve used a lot of audio editing software in my time (D-Cart, Dalet, DaletPlus, Sonic Solutions, ProTools, Audacity) and Cubase just didn’t compare in terms of immediate usability. Probably if I’d taken the time I would have gotten used to it, but when it came time to editing the audio book, I switched to Audacity, which can be downloaded free and is much simpler.
Earlier I mentioned that I couldn’t seem to record half a sentence without making a mistake. This was true in the beginning, and it surprised me. One of the reasons that I thought recording an audio book wouldn’t take too long was because I figured I’d just sit down and read it and do some light editing and that would be it. I’ve had some experience acting and I’ve worked professionally as an announcer/operator at two radio stations (CJRW in Summerside and CFCY/Q-93 in Charlottetown). I thought I could read. Heck, I even thought I could perform. But I couldn’t. Not in the beginning.
The problem was I would read a little bit and then, convinced it sounded horrible, I’d stop and start again. I thought, well, not a big deal, I can edit it all later. But the more mistakes you make, the more editing is required, and eventually all that extra editing adds up to one big editing nightmare.
I got much better with practice and experience, but even at my best I couldn’t get through a chapter without a fair amount of mistakes.
Typically, I recorded each chapter twice. I would get to know the chapter on the first read, and read it better the second time around. If I made a mistake, I’d stop, go back, and correct it right away. This made the editing process much easier later (making up somewhat for the amount of mistakes).
Because I didn’t have a producer, someone standing over my shoulder correcting me, I needed to be careful. If I thought I made a mistake during a passage, I always stopped and re-did it (sometimes the first time was perfectly fine, but better safe than sorry, although it did make for more work). Whenever I hit a word I wasn’t entirely sure how to pronounce, I looked it up online. Most online dictionaries allow you to listen to the word you’re looking up. Interestingly, I included words in A Time and a Place that, although I know perfectly well what they mean, I either didn’t know how to pronounce, or have been pronouncing incorrectly. They are correct in the audio book version, though. I made sure of that.
Sometimes I mangled words or sentences but didn’t discover this until the editing process, which was a pain in the butt, but far from insurmountable. One of the advantages of recording an audio book yourself is that afterwards the actor’s still hanging around if you need him or her.
A typical waveform, this one from Chapter 22 of A Time and a Place.
One of the fun parts of recording this novel myself has been doing the voices. I didn’t have unique voices for all of the characters, but some characters cried out for special treatment. One of the characters, Gordon Rainer, is supposed to speak with a British accent. He was by far the most difficult to get right. I’d once done a play for which I’d been trained to speak with a British accent, but I have no illusions about how accurate I’m able to do it (my British brother-in-law is only too happy to provide reality checks on that point).
I’d always thought of another character, Doctor Humphrey, as having a gruff voice, so I played him that way. And so on. I tried not to overdo it, as it could easily get silly, but I enjoyed the performance aspect of it all.
Like just about every other part of this project, the editing took a lot longer than I expected.
I edited one chapter at a time. It took me on average three to four hours to edit the first pass of each chapter. My chapters average twenty pages. The shortest is seven pages, the longest thirty. Transformed into audio, my chapters run anywhere from eleven minutes to thirty minutes long, averaging about twenty minutes. (Unedited, the raw files for each chapter run anywhere between one hour to two hours long.)
As mentioned earlier, I did all my editing in the free version of Audacity, which worked just fine. It’s easy to learn and I found that I could edit quite quickly and effectively with it. It’s also got a nice little suite of tools for mastering, EQ and so on.
Before editing each chapter, I would do a little processing. A little noise reduction, a little limiting or amplification as required to ensure that I was peaking at -3dB with a maximum -60dB noise floor as required by Audible. I did this at the beginning because if doing any of that introduced any problems, I wanted to catch those problems as I was doing the edit. I didn’t want to complete an edit, then do processing, and have it accidentally introduce issues such as clicks or pops or digital distortion that I might have less chance of catching near the end of the process.
Every chapter required multiple passes to edit. The first edit was mainly to get all the right takes in the right order and clean it up as much as I could. To help speed things up, I created a special template in Audacity’s EQ plug-in to eliminate popped Ps as I encountered them (I found the default EQ template for this too aggressive in Audacity).
Sometimes I encountered mangled words or sentences for which no good takes existed, that I had not noticed during the recording process. These I re-recorded right on the spot. Sometimes it was a bit tricky getting these re-takes to match, but it got easier with practice. It was a matter of getting the inflection and level right. I would tweak the level in Audacity using the Amplify plug-in (always careful not to peak at higher than -3dB), and try to use as little of the re-take as necessary, often cutting halfway through a sentence, or a word, even.
After the initial edit, I would go through the chapter again to clean up weird, extraneous noises such as bits of mouth noise, the cat knocking into the mic stand, or other weird noises such as bumps occurring elsewhere in the house that I hadn’t noticed during recording.
I popped the odd P or two, so I created a specific EQ that I called Subtle Bass Cut to deal with that (and a few popped Bs too)
I took a lot of time to address issues with pacing. I tend to read fast. Left unedited, few would be able to keep up with my reading. I worked hard to address this in the edit. I know that some audio book listeners want their audio books read fast. In fact, they will listen to their audio books at enhanced speeds to get through them quicker. I tailored my pacing for people who listen at normal speeds. If I ever record another one, I’ll try to get it right during the recording. A lot easier than having to fix pacing in the editing process.
Once reasonably certain that I’d addressed all issues in the edit, I would play the entire chapter from beginning to end to make sure that I hadn’t missed any edits, and to ensure that there were no other problems. Only when I felt that the edit was perfect would I consider it done, and share it with my publisher via Drop Box (who will subsequently submit it to Audible). One of my mottos is “If it only exists once in the digital domain, it may as well not exist at all,” so I always sent a safety version to myself via Gmail.
I didn’t keep a really accurate record of how long this project took me, but I estimate each chapter took on average two hours to record, and six hours to edit, master, and double check. That’s 8 hours a chapter times 27 chapters, plus little bits like intros, acknowledgements, and so on. I figure the entire project took about 220 hours. That’s 27 eight hour days. The book itself is ten hours, sixteen minutes and fifty-five seconds long, all told. I took three entire weeks off work and devoted several evenings and weekends to this project. Probably much longer than it should have taken. I read in this quite informative blog post that “your narrator will put in six times more production hours than the final length of the book.” Yeah… took me a bit longer than that.