*OIC*.
i agree that the user interface GUI of WMR is a little more complicated than it needs to be. My
last tough testing of difficult challenging WMA-stream url's wasnt too long ago, and, although *some* tools are able to download those "test url's"... the results with
WMR (and WMD) were not satisfactory. i'll give WMR another chance. same url, same test.
EDIT:
with WMR 14.8, i've just downloaded:
mms://stream.zune.net/a4241/e3/008/146/123/at/audio.wma
8,17 MB (8.577.053 Bytes), FCD03CD3
and then:
rtsp://stream.zune.net:554/a4241/e3/008/146/123/at/audio.wma
4,09 MB (4.298.237 Bytes), 94907BCC
the file on the zune server is the same (identical url, except for protocol change). but WMR downloads 2 different (sized) files. the "4MB"-sized file smells right, because the bitrate of the audio is 128kbps. first of all, WMR should be able to reproduce identically-sized files, or am i wrong with this question ask alex? (correct file size is: 4,10 MB (4.304.213 Bytes); please dont question how i know that
4.304.213 Bytes is the correct file size. the corresponding CRC32 is "
95851B39". please dont question either. i cant tell where i have these data
sorry); then it should be able to reproduce the 95851B39 code.
*IMHO* if a download tool saves/records/captures/downloads 2 different sized files for the same original server file, then the download tool needs a serious fix. just my 2 cents.