• View
• Edit
• History
• Print

F4M

F4M proxy with support for HDS streams

To play HDS but also m3u/hls streams you can call the F4Mproxy via the f4mtester plugin as in following example. If your url requires headers to be sent use | (pipe) and URL-encode the url.

There are other optional parameters if you want to include using & , like name, and maxbitrate etc. Also, you can now pass two more params, one is proxy "iport" format for example 108.163.254.214:7808 and other is proxy_for_chunks which is True/False. Some server only check at the manifest level (.f4m link) to make sure they are from their region (in this example US) but when you pass that block using their region proxy, then rest is open, so pass the US proxy and set the proxy_for_chunks to false. This way, it will get the manifest via proxy but rest will be as fast as your network could stream.


LSPRO allows the use of $$TSDOWNLOADER$$ parameter in m3u url. If present, the .ts entries will be executed with f4mtester.



With LSPro version 2.6.7 and f4mproxy version 2.5.9, now we support $$HLSRETRY$$ (HLS retry) for streams which support hls (.m3u8) but disconnects users after sometime. This is same as $$TSDOWNLOADER$$ but works with .m3u8 files. You need to make sure that your urls should be .m3u8. $$HLSRETRY$$ is used when you want to load the m3u8 which contains other m3u8 and you want to list and play with f4m.

When using f4mtester plugin syntax then you simply usestreamtype=HLSRETRY (just like you call for HLS OR HDS it's a new type).

Example:

Courtesy of moshoodo123.

Version 2.6.1 of f4mproxy and tester now support callbackparam and callbackpath. Callbackparam is string that the callback function will recieve. Callbackpath is the full file path of the python file containing the callback function, i have made the callback function static, it should be defined as:

where:

• param is the callbackparam you will receive back.
• type is 1 for time being.
• error is the error object for m3u8 file (for example 403).
• CookieJar is the cookies
• url is the old url the player was playing and headers are the headers it was using.

For time being, the callback function will only be used in situation where server returns 403 (due to cookie expiry or Url expiry for example filmon hd urls which are valid for 45 seconds or little more). The return value of callback function should be new url and the cookies.

Here is an example of filmon high quality stream playing more than its allowed to.

here you can see f4mcallback function reusing the same function which created the url, however since film returns different server address which runs different stream numbers, i am reusing the old server name so that the video could be stitched without any hitch.