Re: Coreaudio-api Digest, Vol 9, Issue 104
Re: Coreaudio-api Digest, Vol 9, Issue 104
- Subject: Re: Coreaudio-api Digest, Vol 9, Issue 104
- From: Alex Matheu <email@hidden>
- Date: Tue, 10 Apr 2012 15:12:31 -0400
I got my copy of the book, now to read it. Although it won't help me on my current app, submitting in the next few days, but definitely on the next one.
On Tue, Apr 10, 2012 at 3:00 PM,
<email@hidden> wrote:
Send Coreaudio-api mailing list submissions to
email@hidden
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.apple.com/mailman/listinfo/coreaudio-api
or, via email, send a message with subject or body 'help' to
email@hidden
You can reach the person managing the list at
email@hidden
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Coreaudio-api digest..."
Today's Topics:
1. Re: Avila/Adamson CoreAudio book (uɐıʇəqɐz pnoqɥɒɯ)
2. Re: Avila/Adamson CoreAudio book (tahome izwah)
3. Re: QT -208 error (tahome izwah)
4. Re: QT -208 error (Stephen Davis)
----------------------------------------------------------------------
Message: 1
Date: Tue, 10 Apr 2012 10:48:38 -0700
From: uɐıʇəqɐz pnoqɥɒɯ <email@hidden>
To: Chris Adamson <email@hidden>
Cc: coreaudio-api API <email@hidden>
Subject: Re: Avila/Adamson CoreAudio book
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset="windows-1252"
Thanks Chris. I appreciated the insight into the process. I didn't realize that the book is available from other channels.
As for making money off this book, I feel that I have to tell you that it is underpriced. Compare to:
[search Amazon for Image Processing or Computer Vision]
[search Amazon for Audio Processing]
[many books found will be over $60, and even over $100. I removed these links to prevent posting issues]
I would expect a price of $60+ for your book. But pricing is a whole can of worms - increase pricing and people will resort to piracy; reduce it and people don't think the book is a serious contender.
Congratulations on getting it out and I hope, at least, you get tons of positive vibes, feedback and karma for tackling such a complex topic.
-mahboud
On Apr 10, 2012, at 6:31 AM, Chris Adamson wrote:
> So, uh, yeah, this book has been a long time coming. But it really is done. Here's a picture of me last week reading one of the first copies off the press:
>
> http://img.ly/g8Rh
>
> I don't know what's up with Amazon's crazy talk of a 1-3 month shipping time. Pearson was set to deliver the books to Amazon this week (which is why the page changed from preorder to "add to cart"). One of the guys in my CocoaHeads got a notice yesterday that it would arrive by Wednesday, and then this morning saw it pushed back to May-June. Don't be surprised if that changes again in the next day or so, once Amazon gets their act together.
>
> [I'm omitting purchase URLs in the following list of formats/vendors because if I use more than one URL, the post will get held for approval by a list administrator who does not actually exist. Hit the publishing category on my blog for recent updates and my affiliate kickback links: http://www.subfurther.com/blog/category/publishing/ ]
>
> The Kindle edition is available for immediate download from amazon.com (but not the international stores: amazon.co.uk, amazon.co.jp, etc.)
>
> Learning Core Audio is also available from the publisher's site, which also offers a paper + eBook bundle (the eBook is watermarked ePub and PDF).
>
> And it's on the iBookstore, but only in the US and Canada. I'm told that Pearson is still working through the legal process with Apple Europe to get it up over there. And I got a tweet this morning reminding me that I need to check on availability in Australia.
>
> And the final version is available to subscribers on Safari Books Online, where we've hosted the Rough Cut for the last year or so. And clearly a lot of people have been reading it there, because I keep seeing readers in the Core Audio forum on devforums.apple.com using Kevin's CheckError() function to wrap all their Core Audio calls, like we do throughout the book.
>
> So, that's the short story: any current delays you're seeing are temporary and caused by either incorrect status for the print edition, or contract and legal issues holding up eBooks in various countries.
>
> The long story… why did this get pushed back so many times?
>
> Well, that's a lot of things. When I came on to the book in early 2010, replacing Mike Lee (who was massively overcommitted to various pursuits and had to let something go), the book was already listed with a release date, even though Pearson's production process takes 3-4 months after the final draft, and Mike and Kevin just had a collection of fragmentary chapters and a couple code examples (all of which were worked into chapters 1-3). So that first date was hopeless anyways: if we'd worked 40 hrs/wk on it from January through June, we might have gotten a final draft done in the second half of 2010, which would mean that the book would have shipped in early 2011.
>
> Obviously, that didn't happen. Two things: first, because of the difficulty of the material, Kevin and I decided to write all the chapters together, rather than working in parallel like most co-authored books do. That way, we wouldn't have radically diverging code styles, writing styles, etc., and would have all our eyes on the technical issues. The obvious downside of this approach is that you go half as fast.
>
> The other thing is that writing is how I fill gaps in my billable client time. The fact is, writing computer books is completely impractical as a means of making a livable income. If you're writing for a big publisher, the royalty is in the 10% range, and Kevin and I are splitting that. Multiply that times what a niche title like a Core Audio book can be expected to make, subtract sales lost to people torrenting PDFs, and it's unlikely we ever out-earn our advance (which is about what I can make in a week of consulting… and my rates are a lot lower than many top iOS developers). I haven't attempted to divide the hours spent on Learning Core Audio by the advance I got paid, but it's probably lower than minimum wage. So, when I've got paying work, it comes first, and writing fills the gaps between gigs. Sorry, but that's how it has to be if I want to pay the mortgage and the health insurance bills.
>
> So, as time was available between gigs, I pushed through the easier material in mid-to-late 2010, and then took a few weeks to really dig into Audio Units in early 2011. By this point, the Rough Cut was available on Safari Books Online, and we got good feedback from readers. I came into WWDC 2011 worried about languishing feedback and attention from Pearson, but they surprised me by putting the entirety of the first audio units chapter into a 900-page eBook sampler for WWDC attendees, and we resolved to finish over that (northern hemisphere) summer. I did the iOS chapter, then ended up doing more of MIDI than expected, and we were just about done in September. Then our editor surprised us by announcing that he was taking a job at Apple and leaving at the end of the year, so we crunched in November and December to incorporate all the feedback from tech reviewers and Safari, and get in a final chapter on Lion and (post-NDA) iOS 5, which mostly meant getting in AUSampler. Oh, and I was also crunched on a risk-tacular client project (parsing and highlighting PDFs on iOS) and the second edition of iOS SDK Development for the Prags at this time. So, if I was really pissy on Twitter in late 2011, now you know why.
>
> In January and early February 2012, we did two error-fixing cycles, first on the Word docs (yes, really, that's what they use) and then on PDFs of the galleys. After that, it's all Pearson and their production process.
>
> So, I'd rather it not have taken over two years to write -- most computer books that take that long get cancelled because their topics are no longer viable -- but it was a big project that was already going to take a lot of time, and time wasn't something I had a surplus of. But at least it's done now, and people who've read the Rough Cut or the eBook seem pretty happy with it. Hopefully as the shipping and legal issues get worked out, everyone who wants one will be able to get one in the next couple weeks.
>
> —Chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/coreaudio-api/attachments/20120410/8a60f441/attachment.html>
------------------------------
Message: 2
Date: Tue, 10 Apr 2012 19:49:37 +0200
From: tahome izwah <email@hidden>
To: coreaudio-api <email@hidden>
Subject: Re: Avila/Adamson CoreAudio book
Message-ID:
<CAPSrgnW7=N+gr5nSEGeo7PA9rLteho-4R0cDk=email@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Forget it, this will probably never become available. It's been 3+ years
now.
--th
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/coreaudio-api/attachments/20120410/f0ccc68f/attachment.html>
------------------------------
Message: 3
Date: Tue, 10 Apr 2012 19:51:31 +0200
From: tahome izwah <email@hidden>
To: coreaudio-api <email@hidden>
Subject: Re: QT -208 error
Message-ID:
<email@hidden">email@hidden>
Content-Type: text/plain; charset="iso-8859-1"
So why does it think it's supposed to be in AIFF format? Do these files
have an .aif suffix? If so they're expected to be in big endian format and
QT won't be able to read them...
--th
2012/4/10 Vassilis <email@hidden>
> Hello,
>
> I have been trying to open some wav files, mono, 24-bit little endian,
> with QT player
> 7.6.6 and I get a OSStatus error -208 " (was not type AIFF or was of bad
> format,corrupt)" .
> error. Those files open ok in QT X. OSX is 10.6.8. Any ideas why this
> happens and how to fix?
>
> Best,
> Vassilis
>
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Coreaudio-api mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
>
> This email sent to email@hidden
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/coreaudio-api/attachments/20120410/7b1db42f/attachment.html>
------------------------------
Message: 4
Date: Tue, 10 Apr 2012 11:36:09 -0700
From: Stephen Davis <email@hidden>
To: tahome izwah <email@hidden>
Cc: coreaudio-api <email@hidden>
Subject: Re: QT -208 error
Message-ID: <email@hidden">email@hidden>
Content-Type: text/plain; charset="iso-8859-1"
Don't be misled by the mention of AIFF. -208 means badFileFormat, i.e. something not understood by the system. It originally started out as "bad AIFF" but is more generic than that.
stephen
On Apr 10, 2012, at 10:51 AM, tahome izwah wrote:
> So why does it think it's supposed to be in AIFF format? Do these files have an .aif suffix? If so they're expected to be in big endian format and QT won't be able to read them...
>
> --th
>
> 2012/4/10 Vassilis <email@hidden>
> Hello,
>
> I have been trying to open some wav files, mono, 24-bit little endian, with QT player
> 7.6.6 and I get a OSStatus error -208 " (was not type AIFF or was of bad format,corrupt)" .
> error. Those files open ok in QT X. OSX is 10.6.8. Any ideas why this happens and how to fix?
>
> Best,
> Vassilis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.apple.com/mailman/private/coreaudio-api/attachments/20120410/8a18096d/attachment.html>
------------------------------
_______________________________________________
Coreaudio-api mailing list
email@hidden
https://lists.apple.com/mailman/listinfo/coreaudio-api
End of Coreaudio-api Digest, Vol 9, Issue 104
*********************************************
--
Alex Matheu
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden