You can see that the URL path is different even though the filename is the same.

The problem is that Madsonic wants to dump these files into the same podcast directory on the server, which results in a collision. Once the first episode is downloaded, the remaining episode downloads are aborted claiming the file has already been downloaded. However, in the podcast web interface in Madsonic (and in the database), it shows all queued episodes have been downloaded.

It would seem like in this situation, the podcast downloader could detect the filename collision, generate a new filename using some type of algorithm to save the file, and save that into the database.

For the filename algorithm, a possibility would be to concatenate the podcast date + server time (in case the dates are also the same) to the filename provided in the xml feed.

In this case, all the episodes are called "download.mp3", but the path is different for each one. It appears that whatever is downloading the episodes is appending an extra number to the episode filename, but not including it in the database.

I'm looking to see if there is another feed that doesn't include the duplicates, but I doubt there is.