Podcastamatic 1.0

Podcastamatic 1.0, my podcast automation program, has been released. Get it here. This version is a lot easier to get started with and more customizable.

Changes for v1.0

  • Simplified configuration.
  • Improved customization options.
  • Added log file generation.
  • Cleaned up internal code.

7 thoughts on “Podcastamatic 1.0”

  1. Great job on the Podcastamatic tool. Thank you very much for making this available to the community for free. Without it, I probably wouldn’t have gotten into this fun hobby. I recommend your software to anyone else interested in podcasting.

  2. The license seems to be up in the air this point. you would assume copyright protection only since nothing else has been specified.

    How are people dealing with quotes and apostrophe in their comments? While they show up fine in the HTML, the RSS has problems: today’s becomes today^?s, “everyone becomes ^?everyone, etc. The feed will not validate because of this.

    I found one reference to a possible fix– http://sourceforge.net/mailarchive/forum.php?thread_id=7082948&forum_id=37467, but subbing in " did not change the rss.xml.

    Any solutions?

  3. License: I’ve decided to license Podcastamatic under GPL. I’ll formalize this in the next release.

    Quotes and other special characters: I’ll fix this in the next release.

    If anyone else has any bugs/feature requests/whatever, let me know and I’ll try to address it.

  4. Just what I was looking for! I hope more people find this tool as creating rss feeds by hand is such a bore! :)

    FEATURE REQUEST: You may want to include spaces in the “special characters” if you haven’t already.

  5. It looks like iTunes is more strict with the RSS feed then most other Podcast receivers. It rejects feeds with non-encoded special characters (quotes, ampersand, etc). I will fix Podcastamatic this weekend (by July 4, 2005). The “workaround” until I fix Podcastamatic is to manually edit the XML to encode the characters (as per the link suggested by Sam Snow)
    < should be &lt;
    > should be &gt;
    & should be &amp;
    ‘ should be &apos;
    ” should be &quot;

Leave a Reply

Your email address will not be published. Required fields are marked *