Skip to main content

MAKE: Blog: Audible does Podcasts - the complete guide (and HOW TO)

Phillip goes through Audible's podcasting support in great detail noting a great many of the issues with it.

I think I may have the same problem with the formats, especially if iTunes does this as well. Right now, I'm preparing for a day visit to Montreal and am loading my Pocket PC with podcasts. If I had downloaded an ACC file, I would be out of luck.

Podcasts as a distribution method need to be free (unless they ARE DRM'd - not the other way around). All of the companies offering this need to figure that out a bit better, if Phillip's take is any indication.

MAKE: Blog: Audible does Podcasts - the complete guide (and HOW TO)

Comments

Ted Roche said…
"Podcasts as a distribution method need to be free (unless they ARE DRM'd - not the other way around)."

Free as in... ?

If you mean the audio codec needs to be free from patents and encumbrances, then you would need to use .OGG, since MP#s are a patented technology of Fraunhaufer that can only be used with a paid license (your media player vendor paid it). Or do you mean "free" as in "not AAC?" Isn't that why it's a PODcast?
Andrew MacNeill said…
"free" as a distribution method.

A "podcast" does not require an iPod despite the name.

The issue that I had was that if I download a podcast from Audible, it needs to be done so that I can easily move it to my device for listening.

If you read Phillip's guide, you'll see that because Audible DRMs them.
From the article:
"Now on to some bad news for folks like me. You can't convert the file you bought to MP3. Since I have a ton of devices that support MP3, but not AA, I'm out of luck. You can burn the file to a CD, but from what I've read, you can only do that once. I tend to think the type of customer who buy audio over the web is pretty good with computers and if they have many computers, MP3 playing phones, etc...

There are, or "were" programs to convert the AA format to MP3, but it seems like Audible went after them?"

He then went on to copy the file to his PC and try it from there, but once again it wouldn't work.

I think this is going to be the issue with getting the larger software to support podcasts properly and in some way you can understand it.

If they are going to make the changes in their infrastructure to support Podcasting, then they should have the "right"(?) to want it to run on their own system.

Audible's approach will likely work best for those authors who choose to do podcasts through their network to make $$.

On your other point, Ted, I didn't mean that the codec should be pree from patents - just the distribution method.

On that note, I heard..(oh I'll just post about it - excellent talk by Lawrence Lessig)
This blog is awesome! If you get a chance you may want to visit this calendar software site, it's pretty awesome too!

Popular posts from this blog

Well, that explains CodePlex...

In a move that will be sure to anger open source (or rather anti-paid software, anti-Microsoft open source)  zealots, Microsoft is planning to buy GitHub.

A year ago, I mused about why Microsoft would shut down CodePlex and how the world needs competing source code repositories to be strong. I'm not the only one per this Slashdot article :
"...people have warned about GitHub becoming as large as it did as problematic because it concentrates too much of the power to make or break the open source world in a single entity, moreso because there were valid questions about GitHubs financial viability...." - Jacques Mattheij

I will be interested in seeing this play out - whether developers jump ship or not. Have all the efforts Microsoft has made in pushing towards open source be seen as genuine or will all the zealots jump ship or maybe even attack?

Microsoft's comment about why they shut down CodePlex referred to how spammers were using CodePlex. Well, GitHub has its own …

FoxInCloud Stats

FoxInCloud sent this link a while back about their statistics regarding visits to their site:

http://foxincloud.com/blog/2017/12/27/VFP-community-lessons-from-foxincloud-site.html



What's interesting here is the breakdown of people. Yes, I think it's understandable that the Fox community is getting older.

Another factor is the growth of the mobile and web environments taking over development. These environments really do push people towards the newer non-SQL or free SQL/hosted environments but more towards hosted storage options like Amazon and Google. A tool like FoxInCloud that helps MOVE existing applications to the cloud inherently competes with those environments.

But FoxInCloud also allows developers to extend their application further by giving them a starting point using Javascript and the basic CSS (such as Bootstrap). If you're not rebuilding your application from scratch, it's certainly a great step forward.

The World of Updates Today

I just received an update for Office 365. It certainly includes some cool features - including starting in one environment and picking it up in another environment. In recent years, I've certainly enjoined the use of Continuity on a Mac and in fact, I feel spoiled being able to start a message in one environment (even Google) and then finish it off on another.  This has become some pervasive when we were reviewing our most recent backlog at a client site, a similar feature was added to the current workload.

But with web applications, the trend is to reduce the amount of software on a client machine. I used to have automatic backup for all of my machines (thanks Carbonite!) but these days, many of my machines don't need anything beyond the core OS and some basic applications. Certainly that's the feeling with Chromebooks and even the lightweight aspect of many iOS apps. The functionality is mostly in the cloud.

When you upgrade your system, you expect it to a big update. So…