2014-07-25, 18:52
(2014-07-25, 13:00)cruise Wrote: EDIT: Okay - new working version. Tricksy hobbits!
http://casual-tempest.net/files/YouTubePlayer.py
Nice job!
Any chance you can point out the changes you had to make, to fix it?
(2014-07-25, 13:00)cruise Wrote: EDIT: Okay - new working version. Tricksy hobbits!
http://casual-tempest.net/files/YouTubePlayer.py
(2014-07-25, 13:00)cruise Wrote: EDIT: Okay - new working version. Tricksy hobbits!
http://casual-tempest.net/files/YouTubePlayer.py
FYI, I am also trying to get what would be a permanent fix for these sort of issues done. Google has open-sourced their javascript engine, V8 - and it's possible to tie it into python. I have a proof of concept working locally which simply runs the signature decryption routines natively, using the same engine Chrome browser uses. Anything which doesn't work for us then wouldn't work for anyone in a browser too.
However, this requires integrating, at the least, Google's javascript engine into XBMC. I have started a thread here: http://forum.xbmc.org/showthread.php?tid=200309 for doing so, but I have no idea when/if that'll happen.
(2014-07-25, 18:52)spoyser Wrote:(2014-07-25, 13:00)cruise Wrote: EDIT: Okay - new working version. Tricksy hobbits!
http://casual-tempest.net/files/YouTubePlayer.py
Nice job!
Any chance you can point out the changes you had to make, to fix it?
(2014-07-25, 20:40)MediaPi Wrote: Also thanks for putting in the extra effort for a permanent fix. If you was succesful, does it mean that we can get 1080p? from the sounds of what you wrote we will have the same quality playback as a browser will....?
(2014-07-25, 22:07)privado Wrote: HI cruise, nice fix. Personally I dont bother with a youtube account to watch content but it seems statutory now, is there anyway to bypass this ?
(2014-07-25, 21:27)cruise Wrote:(2014-07-25, 18:52)spoyser Wrote:(2014-07-25, 13:00)cruise Wrote: EDIT: Okay - new working version. Tricksy hobbits!
http://casual-tempest.net/files/YouTubePlayer.py
Nice job!
Any chance you can point out the changes you had to make, to fix it?
A new array operation, "splice", that wasn't currently translated into it's python equivalent, and use of an existing function (reverse) in a situation where the existing translation didn't work. So a few new lines added to _jsToPy basically.