the mos3 yt tool works for you ?
Nope. 2 of 10 movies work.
My ISP is using a special youtube cache (
http://o-o---preferred---netia-waw1---v ... outube.com).
I'm not sure if this may cause the problem..
There are many files (containing text with long urls) created in /tmp/cached/
/tmp/cached # ls -l
-rw-r--r-- 1 root root 1294 Aug 31 15:41 stream.dat
---------x 1 root root 914 Aug 31 15:41 tmp.rss
---------- 1 root root 12 Aug 28 17:10 tmp.txt
-rw-r--r-- 1 root root 206 Aug 31 15:32 vm.43961604
-rw-r--r-- 1 root root 5290 Aug 31 15:41 yt.7NPdVpx5CgE
-rw-r--r-- 1 root root 6857 Aug 31 15:39 yt.Y_IszT7sSWw
/tmp/cached #
Can you please show your rssex2 settings?:
Here's mine:
- Code: Select all
BASEPATH=/usr/local/etc/translate
export AWKPATH=$BASEPATH/lib:.
RESOLVE_CACHE_ENABLED=no
WGET=/usr/bin/wget
CURL=/usr/local/etc/mos/bin/curl
XSLTPROC=$BASEPATH/bin/xsltproc
RTMPDUMP=/usr/local/etc/mos/bin/rtmpdump
JS=$BASEPATH/bin/js
STARTPOINT=$BASEPATH/etc/index.m3u
XSPFSCAN=$BASEPATH/etc/xspf.scan
MAINMENU=$BASEPATH/etc/menu/main.xspf
IPTVLIST=/usr/local/etc/playlist/iptv.m3u
CACHEPATH=/tmp/cached
YOUTUBE_HD=yes
VIMEO_HD=yes
IVI_HD=no
TVIGLE_HD=yes
NET_BANDWIDTH=
UDPXY_URL=http://127.0.0.1:8080/
TRANSLATE_CGI=http://127.0.0.1:88/cgi-bin/translate?
LOCALE=ru
Edit:
Using a url (in an url browser) from txt file, in my example:
- Code: Select all
http://o-o---preferred---netia-waw1---v18---lscache4.c.youtube.com/videoplayback?upn=JwnBoahM9UU&sparams=cp%2Cgcr%2Cid%2Cip%2Cipbits%2Citag%2Cratebypass%2Csource%2Cupn%2Cexpire&fexp=907725%2C922100%2C925107%2C922401%2C920704%2C912806%2C924412%2C913558%2C912706&key=yt1&itag=18&ipbits=8&signature=85F1ADD3B869B2E1E09C86EC1F4992917CD57576.A36F992EC5E9B4DDC9D32B22EF5F3156FAB182AA&mv=m&sver=3&mt=1346414771&ratebypass=yes&source=youtube&ms=au&gcr=pl&expire=1346438417&ip=91.236.137.34&cp=U0hTS1ROVl9GUUNOM19MSFpFOnpIdll0MlJtUkFC&id=ecd3dd569c790a01&quality=medium&fallback_host=tc.v18.cache4.c.youtube.com&type=video/mp4
video/mp4
returns Http 403 (Forbidden) status. Does it work for you? (a different link accordingly) or is it a cookie problem?