is there a way to separate live streams from movie and series?

[aniel300]

is there a way to separate live streams from movie and series? it seems when using proxy: reverse all streams including vod get this url structure http://xxx/m3u-stream/xxx/xxx/xxx. is it possible to separated it by type, something like for example:

http://xxx/live/xxx/xxx/xxx
http://xxx/movie/xxx/xxx/xxx
http://xxx/series/xxx/xxx/xxx
or
http://xxx/m3u-stream/live/xxx/xxx/xxx
http://xxx/m3u-stream/movie/xxx/xxx/xxx
http://xxx/m3u-stream/series/xxx/xxx/xxx

[euzu]

@aniel300 this are different api's. The m3u api does not make distincition between the stream types. The xtream api does.

[aniel300]

can u implement this for the m3u api?

[euzu]

@aniel300 rhis is not posible due to missing type information. There are no vod or seriea for m3u playlists.

[aniel300]

if i download the m3u from my provider i believe they do separate it by /live/, /movie/ and /series/. u can't do anything with that?

[euzu]

@aniel300 yes for xtream sources, no for m3u playlists. Why do you need this?

[euzu]

yes because the m3u playlist does not support types. There is no player (as far as i know) which can handle types on m3u-playlists (because there is no type).

[euzu]

That is the reason why you get only live and vod when you import m3u as xtream codes. The vod typing is guessing based on file extension.

[aniel300]

am confused. base on my understanding when i download a m3u plus from my provider it does separate live, from movies and series as follow. .../user/pass/xxx, ..../movie/... and .../series/... so my question is is there a way to make ur proxy base on that logic to export it that way when using m3u export?

[euzu]

@Aniel i think you are confused between m3u playlist and xtream codes.

• m3u-playlist -> simple url which returns you a list of channels.
• xtream-codes -> is an api which returns you json files with the different content types. Each type has another api endpoint.

What you describe is only valid for xtream codes. Yes you are right when you access xtream codes api, the streams are seperated as you describe.

But m3u api delivers you only a plain - m3u file. This means you don't have types in it. Each entry is only a link/url (with some header lines before).

What could be the use case inside an m3u file to differentiate between stream types.

[aniel300]

when i download a m3u plus from my provider inside of it looks something like this

#EXTINF:0 CUID="xxx" tvg-name="xxx" tvg-logo="xxx" group-title="xxx",xxx
http://serverurl/user/pass/xxx

#EXTINF:0 CUID="xxx" tvg-name="xxx" group-title="xxx",xxx
http://serverurl/movie/user/pass/xxx

#EXTINF:0 CUID="xxx" tvg-name="xxx" group-title="xxx",xxx
http://serverurl/series/user/pass/xxx

i just want to make this clear. in addition, am using xc for import so this doesn't even matter. what am asking is that when i use proxy: reverse with m3u export that it separates live, from movies and tv shows as right now it doesn't and clients, etc. see movies and tv shows as live tv. ideally something like

http://.../live/...
http://.../movie/...
http://.../series/...
or
http://.../...
http://.../movie/...
http://.../series/...
or
http://xxx/m3u-stream/live/xxx/xxx/xxx
http://xxx/m3u-stream/movie/xxx/xxx/xxx
http://xxx/m3u-stream/series/xxx/xxx/xxx
or
http://xxx/m3u-stream/xxx/xxx/xxx
http://xxx/m3u-stream/movie/xxx/xxx/xxx
http://xxx/m3u-stream/series/xxx/xxx/xxx

[euzu]

@aniel300 what you describe is only specific for your provider. This is not defined by the m3u playlist format.

I think your provider has the information inside an database and creates links based on this information.

However i have created a beta image for you to test. You dont need to fetch the new playlist, just start the new beta image and fetch the playlist.

[aniel300]

if i disabled/ use proxy: redirect then things work as expected. am using multiple providers so is not just specific to one provider

[aniel300]

am sorry i didn't see u created a beta image

[euzu]

@aniel300 i dont understand, did you test the beta image?

[aniel300]

sorry i didn't see u created a beta image for me

[euzu]

yes please test it

[aniel300]

seems to be working. will test more in deep soon. thank u very much

[aniel300]

i was testing more and channels dont see to be playing

[euzu]

@aniel300 which channels? All or only some? Any log output?

[aniel300]

[2024-12-02T22:51:37Z DEBUG m3u_filter::api::xtream_api] Target has no xtream output internal

[euzu]

This error only occurs with xtream api, not with m3u api. Are you really usind the m3u api?

[aniel300]

this is how i have it on my end

  targets:
    - name: internal
      output:
        - type: m3u               
          #filename: iptv.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"
    - name: external
      output:
        - type: m3u
          #filename: playlist.m3u
      sort:
        groups:
          order: asc
        channels:
          - {field: name, group_pattern: '^TR.:\s?(.*)', order: asc}
      filter: "!ALL_CHAN!"

 user:
- target: internal
  credentials:
    - {username: internal, password: internal, proxy: reverse, server: default}
- target: external
  credentials:
    - {username: external, password: external, proxy: reverse, server: external}

[aniel300]

i notice u removed some code as per: 563c249

[euzu]

Your output only supports m3u api, but yrou try to access it with xtream api. This does not work. You need to use the m3u api.

[aniel300]

This error only occurs with xtream api, not with m3u api. Are you really usind the m3u api?

yes am getting the link directly from the m3u that i have open in the browser itself

[euzu]

Ok i found the problem, but i am not at my pc, i will create a new image tomorrow.

[aniel300]

ok i will wait until tomorrow. please do not forget and thank you very much.

[euzu]

i have pushed the beta image. To get what you want you need to set options on target.

options: {m3u_include_type_in_url: true, m3u_mask_redirect_url: true}

targets:
    - name: m3u
      publish: true
      filename:
      filter: "!MY_CHANNELS!"
      options: {ignore_logo: false, m3u_include_type_in_url: true, m3u_mask_redirect_url: true}
      output:
        - type: m3u

[aniel300]

u are on fire. what does this one does btw? publish: true and m3u_mask_redirect_url: true}?

[euzu]

You asked for masking on redirect

[aniel300]

nice. let me try it right now and report back

[euzu]

i think publish is obsolete.

[aniel300]

where can i find the beta docker image?

[euzu]

Here:

[aniel300]

it is not masking when using proxy: redirect 😭

[euzu]

did you set the option?

[aniel300]

ok now it worked

[aniel300]

it works but it still leaking the provider info

[aniel300]

however, i might make work this way. stand by

[euzu]

what do you mean ? give me an example of what and where it is leaked ?

[aniel300]

the way am testing right now if i give idm a link from the proxy and i start downloading when it does the resolution the proxy gives back the provider url with user and pass. is there a way to make it dont do that while using redirect?

[euzu]

This is what i tried to explain you. There is no other way with redirect. You can only hide in reverse mode.

[aniel300]

ok fair enough. this is enough for me and i think i can make it work with this. sorry for my ignorance and thank u for all the hard work

[aniel300]

closing