Podcast download truncation...

[wtanksleyjr]

This is somewhat similar to an old bug that appeared in 4.0, but I'm seeing this in 4.1.0.1683 (portable mode).

What happens is that certain podcasts, generally ones with large episode files located on static servers (you know, those commercial distributed servers? I'm looking at one named 'netsolhost.com' in my download list), cut off in the middle of a download, and MediaMonkey creates a Song and PodcastEpisode entry for the truncated file (it also adds an IDv3 header if so configured). I can tell which files are truncated because the "Downloads" list contains an entry for the file (plus, the file is implausibly short and with an implausibly short duration).

One other thing that's somewhat special to my situation, and might explain the problem, is that I do most of my downloading through a 3G wireless connection -- WiFi is a little hard to get in my current position. I'm speculating that this MM bug is triggered when the server improperly aborts the download due to connection going idle -- or something like that.

Anyhow, ideally MM would recognize the error (which it seems to know is an error, since otherwise it would surely remove the aborted entry from the download list) and resume the download; if the download can't be resumed, restart or just undo the download so that it can be podcached next time.

[Lowlander]

You should try with the latest release for MediaMonkey 4.1.

[wtanksleyjr]

You should try with the latest release for MediaMonkey 4.1.

Heh, good point. OK, I did; I had to download 5 files before I hit the problem. It may "help" to have 4 large files all running at the same time through restricted bandwidth.

Personally, if I had the code in front of me, I'd try to find where the SONG entry is made, and see what paths can reach there. Simply leaving a dummy download is a problem.

-Wm
EDIT: this was build 1690.

[Lowlander]

If you still see it, you should capture it in a debug log (step 4b) and send the log to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341

Related: http://www.ventismedia.com/mantis/view.php?id=10860

[wtanksleyjr]

If you still see it, you should capture it in a debug log (step 4b) and send the log to support: http://www.mediamonkey.com/forum/viewto ... ?f=6&t=341
Related: http://www.ventismedia.com/mantis/view.php?id=10860

Unable to reproduce in Debug. I'll carry on and perhaps later it'll show up.

-Wm