@
amet
After another look this is what it look's like to me...
Xbmc subtitles uses file name from file path to save subtitles in "sub_stream" dir, but file path sent to xbmc by icefilms includes a loot of caracters used for autentification...
example:
Code:
http://rsxxxxxx.rapidshare.com/cgi-bin/rsapi.cgi?sub=download&fileid=XXXXXXXXX&filename=XXXXXXXXXX.S01E05.HDTV.XviD-LOL.avi&dlauth=F8EA0706D49DAE40E2D6D1290070DA5722EE7471AA2078D3AC8E63BDC4DBFB94D397694ACA310C112AEA332F7A7C16260C2FDA9DE5EFD9D8ABA9135C4503EA32E086C9C3F219F85CFAF8AAFB8518A82A5DE84C117025C0FE8EAF13D49EFB2380FE3697652FC70518FCADDADECA1AA1A0
Now if i force the file path to be "tmp" (or whatewer random leters and numbers) or clean the file path like in my first atempt, it gets the movie title from infolabels and all works as expected...
It look's to me that this is caused by filename having to much caracters or posibly a special caracter in filename.
Now my question is how to be sure and what would be the xbmc way of fixing this.
The posible fixes that would not be icefilms or rapidshare specific:
Using a temporary file name for subtitles for streaming videos, somting like "stream.tmp.srt", this makes sense to me, because subtitles for streaming videos are temporary and saved in temporary directory (sub_stream).
Maybe ewen bether fix would be to use title infolabel for subtitle filename if it exists, when we are geting subtitles for a video stream.
Sorry for my bad english...