Trent wrote:1) You'd be able to remove downloads that you know are never going to succeed (site's gone, file moved, etc).
Hmmm, I coulda sworn there was retry limit but it seems that there isn't
Although Awasu will stop trying after the item gets purged from the feed (for being too old).
2) You could remove downloads that you really don't need. For instance, I recently subscribed to a security feed and Awasu found 185 episodes of their podcast in the feed, at around 100MB per episode.
That's not good on metered net access.
Yah, I thought about all this kind of stuff when I first added support for enclosures but the problem is that once you start going there, you basically have to write a full-blown download manager. People will want to adjust the queue order, add and remove entries, tweak queued requests, etc. I don't know if it's still the case but FeedDemon used to ship with a download manager <i>as a separate application</i> just to manage downloading enclosures
I did look around for a third-party download manager that Awasu could integrate with but didn't find anything - let me know if you know of one.
In the case you described, I usually just delete the channel and re-subscribe with the <i>"download enclosures"</i> option turned off. As <i>kevotheclone</i> pointed out, you're probably best off setting this is as the default option for new channels (Channel page in the Program Options) and turning it on as required.
If you don't mind getting your hands dirty, you can also manipulate the queue directly - it's contained in the <tt>offline_content_download_queue</tt> table in the <tt>archive-offline.db</tt> file
(an SQLite database). Best results with Awasu not running, of course...