-
Notifications
You must be signed in to change notification settings - Fork 374
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add another Flussonic link format #926
Comments
Locally tested, works fine |
You don’t say where your code should be added in the file. So it’s impossible to tell if the code is viable or not. My guy says it is not, as it will break things for other users. |
My fault - presumed, it was obvious from my message. |
I understand, that hard-coded link format is not flexible and that it's better to allow users to modify not only appendix, but the whole link using RegEx. To do so, we have to pass all the parts to UI.
|
Ok, I commented on the PR. This will require quite a bit of work to get merged if you want to do the work. |
Hi
I've got subscription for an IPTV with a bit different catchup link. Monitoring web-player, I've found out that its format is quite similar to Flussonic, but with a twist. Currently, there is no condition case for it, so I'm getting
Here are link formats - both work
http://server:port/ch1/**index**-1731156010-3600.m3u8?token=secret
or
http://server:port/ch1/**mono**-1731156010-3600.m3u8?token=secret
I propose to add this case for upstream.
src -> iptvsimple -> data -> Channel.cpp -> bool Channel::GenerateFlussonicCatchupSource(const std::string& url)
The text was updated successfully, but these errors were encountered: