Hi there,

I've been a happy Amarok user for several years now with absolutely no problems, but my recent MP3 player purchase found me stumbling upon two Amarok issues in quick succession.  Perhaps someone else has seen these issues?  I couldn't find anything online about them:

1. The "convert spaces" option for Media Devices causes file transfers to fail. 

I am using the transcode option with the transkode script to convert OGGs to MP3.  However, when I check "convert spaces", Amarok fails to create the destination directory for the files it will transfer. Then, when it actually tries to copy the files to the device, the destination directories don't exist so all the transfers fail.  I have eliminated script problems from this issue (I tried 3 different scripts and even spun my own), and I also re-built Amarok with debug enabled and can confirm that it never appears to enter the "checkAndBuildLocation" function of the Generic Media Device class.  If I disable the "convert spaces" option, everything is fine. (I wish I correlated that immediately instead of spending 4 hours on this.)  So, has anyone else seen this?  Should I create a bug report?

2. Some podcast streams cause Amarok to download JPEG files instead of MP3.

I've used the PodCast features before with good success, but when I add this stream:

http://feeds.treehugger.com/TreehuggerRadio

Instead of downloading the MP3 files, it downloads JPEG files and tells me it can't play those.  I'm assuming this is a problem with the stream parser, although I'm surprised at what would cause it to fail on this one and not so many others?  Perhaps JPEGs in podcast streams aren't very common?  Dunno. 

Anyway, any direction on what I should do next would be appreciated. And if I'm totally missing something, you could point that out too. 

Thanks

Looking at the source of that feed I noticed:



This may be the source of Amarok's confusion. 

Good catch on that.  I have sent a message to the site to see if they can fix it.  Still, the 'right' media stream is further along in the XML.  It seems a little sanity checking on Amarok's part wouldn't hurt.

As for the other problem .. a bug entry it is?