[t0mm0]

so here is what i just did when taking a quick look at this site.....

Thanks getting back so quick.

The site is vidreel
http://vidreel.com/video/OTM3NDM0/ which redirects to http://vidreel.com/human/OTM3NDM0/ straight away. I know that I have to include

Code:

"name" : "watch" and "action" : "#"

but how do I know what else needs to be included eg cookies, Referer. Is it trial and error?

in a incognito window (so you don't get any old cookies) of chrome, open dev tools (ctrl+shit+i) then load the page. as you say it is diverted to the /human page. right click on the 'continue to video' button and choose 'inspect element' and you will be taken to the html code for the button. you'll see that it is in a html form, but that the button itself is just an <a> tag which just links back to the original page. weird. unless there is some fancy javascript going on the form isn't being submitted.

click on the button and look at the top entry ion the network tab of the dev tools. you'll see that sure enough, it is just a GET request. you'll notice that there are some cookies sent (you can ignore all the tracking ones - '__utma', '__utmb' etc. - you'll notice these appear on lots of pages) - 'videohuman' an sometimes 'video'. maybe these are all that is required?

so i test in python. in the 'lib' directory of script.module.t0mm0.common i type python to enter the interactive interpretor and use the Net class with the debug flag enabled to load the page (this is easier than straight urllib2 as it handles cookies etc. with hardly any code required). it gets diverted to the /human page but you can see the cookies being set. so i load the page again, this time it desn't get diverted! so all you have to do is load the url twice, the first time the cookies get set and the second time it loads the real page. you can see my python session here

stage one done!

Here is the code for the video.

Code:

<script type='text/javascript'>
var so = new SWFObject('../../9.swf','ply','600','340','9','#ffffff');
so.addParam('allowfullscreen','true');
so.addParam('allowscriptaccess','always');
so.addParam('wmode','transparent');
so.addVariable('file','08022eb20345a3d9fd77b34f087a97f8.mp4');
so.addVariable("skin", "../../dangdang.swf");
so.addVariable('bufferlength','5');
so.write('mediaspace');
</script>

Is the link?

Code:

http://vidreel.com/9.swf:08022eb20345a3d9fd77b34f087a97f8.mp4

Do I need to include the other parameters for the file to play?

getting close.

as you noticed the javascript you posted above shows the file name but not the server or protocol - this means it is probably embeded in the swf file so we need to do more work.

pressing the play button on the flash player gives no entries in the network tab of the chrome dev tools so it is probably not just downloading the video via http. that makes it a little tougher.

i decided to use rtmpsrv which comes with rtmpdump and lets you intercept calls to rtmp servers and gives you an rtmpdump command line to use.

(this is on linux, dunno about other os's) first off i run the iptables command that diverts traffic for port 1935 (the rtmp port) to localhost. then run rtmpsrv and press play on the flash player. now don't forget to remove the iptables rule (or prepare to get very confused later!). my terminal output from this process is here.

copy and paste the rtmpdump command line to test - it works!

this gives you all the needed information to play the link in xbmc. the rtmp command line translates to

Code:

rtmp://213.163.74.245/vod/mp4:08022eb20345a3d9fd77b34f087a97f8.mp4 swfUrl=http://vidreel.com/7.swf pageUrl=http://vidreel.com/video/OTM3NDM0/

in xbmc talk. bung that in a .strm file to test and.... yay! that works too

now all you need to do is try a bunch of different videos to see if they all use the same rtmp server, and if not work out how to tell the difference (hint: maybe the different numbered swf files refer to different servers? can you just pick one at random or do you need to use a specific server for a specific video? so many questions - this is where the fun of testing comes in )

hope that helps - shout if you don't follow any of that. obviously it isn't written as a nice tutorial but is literally just notes i took as i was looking at the site. maybe we can turn it into a proper tutorial as part of the docs for this module.....

t0mm0.