57 replies to this topic

[mosskit]

Yes the content of the m3u8 file for transcoding is correct and work

Hi I dont bother about the file name. I turned off the authentication by @anudanan suggestion, restarted streamproxy and..  it works now on tellymote and VU+ official app! So the problem is with http authentication being turned on whatever transcoding method I use (m3u8 file from OWIF - phone icon, or other iOS apps).

 

 
 

[WanWizard]

@anudanan,

 

Yes, that is the one I meant. Back home, I'll commit a fix and bump the commit hash for the rc build in a minute.

 

@mosskit,

 

Yes, we know the contents works. But that doesn't mean other issues shouldn't be fixed.

[anudanan]

@mosskit

 

For the authentication of streamproxy I have open a feature request here

 

https://github.com/e...mproxy/issues/6

[WanWizard]

Done.

[anudanan]

thx

[Erik Slagter]

 

- the options defined into the transcoding setup screen are simply ignored, so no options: bitrate= width= height= aspectratio= interlaced=

 

VU+ doesn't use  / support these URL parameters, it only supports transcoding op 8002, and uses the streamproxy config file to determine how. This was the issue I fixed.

I didn't check the filename. Also, that is cosmetic, a file named "m3u8" works fine too.

Completely untrue. Streamproxy supports parameters set using the plugin (as defaults) and config file and allows overriding them using url parameters and even cookies.

[Erik Slagter]

@mosskit

 

For the authentication of streamproxy I have open a feature request here

 

https://github.com/e...mproxy/issues/6

I explained there why it isn't that simple.

 

Either use authentication for OWIF as a whole and streaming or don't use authentication for both and then it will work.

[Pr2]

 

 

- the options defined into the transcoding setup screen are simply ignored, so no options: bitrate= width= height= aspectratio= interlaced=

 

VU+ doesn't use  / support these URL parameters, it only supports transcoding op 8002, and uses the streamproxy config file to determine how. This was the issue I fixed.

I didn't check the filename. Also, that is cosmetic, a file named "m3u8" works fine too.

Completely untrue. Streamproxy supports parameters set using the plugin (as defaults) and config file and allows overriding them using url parameters and even cookies.

 

 

I have created a ticket on OWIF:

 

https://github.com/E...ebif/issues/890

[mosskit]

- the options defined into the transcoding setup screen are simply ignored, so no options: bitrate= width= height= aspectratio= interlaced=

VU+ doesn't use / support these URL parameters, it only supports transcoding op 8002, and uses the streamproxy config file to determine how. This was the issue I fixed.
I didn't check the filename. Also, that is cosmetic, a file named "m3u8" works fine too.

Completely untrue. Streamproxy supports parameters set using the plugin (as defaults) and config file and allows overriding them using url parameters and even cookies.

Hi I agree on that. I ve checked my box and stramproxy config files is overwriten with those params whenever I change them and restart streamproxy, thus bitrate and resolution changes for transcoded channels.


Wysłane z iPad za pomocą Tapatalk

[WanWizard]

Completely untrue. Streamproxy supports parameters set using the plugin (as defaults) and config file and allows overriding them using url parameters and even cookies.

 

This was not about the streamproxy capabilities, but about how the webif generates stream URL's. For VU+, it generates URL's with port 8002 without parameters, for the "Xtrend" types it generates URL's with port 8001 and with parameters.

[anudanan]

I´ve tested the last changes in stream.py of openwebif of that issue

 

https://github.com/E...ebif/issues/890

 

now the url includes the parameter like

 

#EXTM3U 

#EXTVLCOPT--http-reconnect=true 

#EXTINF:-1,Das Erste HD

http://192.168.1.43:...:C00000:0:0:0:?bitrate=1000000?width=720?height=480?aspectratio=2?interlaced=0

 

it works also with tellymote on iphone which uses the safari browser for playing transcodes videos

Edited by anudanan, 1 January 2019 - 15:37.

[anudanan]

I´ve tested it now with movies on the HDD. In the ts.m3u8 there are no bitrate parameter etc includes.

 

#EXTM3U 
#EXTVLCOPT--http-reconnect=true 
#EXTINF:1852,Notting Hill
http://192.168.1.43:8013/file?file=/hdd/movie/20190101%201810%20-%20zdf_neo%20HD%20-%20Notting%20Hill.ts

 

But I think it works also with the parameter, I´ve tested it.

 

#EXTM3U 
#EXTVLCOPT--http-reconnect=true 
#EXTINF:1852,Notting Hill
http://192.168.1.43:8013/file?file=/hdd/movie/20190101%201810%20-%20zdf_neo%20HD%20-%20Notting%20Hill.ts?bitrate=1000000?width=720?height=480?aspectratio=2?interlaced=0

 

 

So I think there is an other issue in OWIF for stored movies or I´m wrong?

Edited by anudanan, 1 January 2019 - 18:55.

[Pr2]

I think so too.

 

It is perhaps better that you open up a new ticket on OWIF git since now it is for recorded movie and not a live stream.

[anudanan]

I´ve made on my box the same fixes (from getStream function) now in the getTs function and it works

 

Here is the new issue

 

https://github.com/E...ebif/issues/891

Edited by anudanan, 1 January 2019 - 19:19.

[Pr2]

Then report it to OWIF or create a Pull Request to propose your change.

[anudanan]

I added the interesting Code inside the issue. I´ve not done a pullrequest until know and not very familar who to do this

Edited by anudanan, 1 January 2019 - 19:55.

[Erik Slagter]

Completely untrue. Streamproxy supports parameters set using the plugin (as defaults) and config file and allows overriding them using url parameters and even cookies.

This was not about the streamproxy capabilities, but about how the webif generates stream URL's. For VU+, it generates URL's with port 8002 without parameters, for the "Xtrend" types it generates URL's with port 8001 and with parameters.

And that, Littlesat completely failed to mention. OWIF doesn't know about streamproxy, it assumes the VU+ transtreamproxy which doesn't support URL parameters and should be configured the "transcoding settings" plugin. So again something OWIF needs to fix.

Edited by Erik Slagter, 2 January 2019 - 10:07.

[anudanan]

A question about this Topic to Wanwizard

 

https://forums.openp...rt/#entry989457

 

Yesterday I´ve removed my older OWIF plugin and installed it new from your feed (the version ist now 1+git3234+8e73e37-r0.0))

but now die filenamegeneration for transcoded  files is wrong without the name of the channel

 

I thought the fix is inside the new pluginversion ? Isn´t it?

Edited by anudanan, 2 January 2019 - 11:30.

[WanWizard]

Thought so to, but appearently it didn't fix it. Looking at it now.

[WanWizard]

I probably have to bump the version of the js file, otherwise chances are the browser uses the cached version. Could you force a reload and see if that fixes it?

 

If I do that I get a filename in the response, and VLC opens directly without wanting to save the "m3u8" file:

Hypertext Transfer Protocol
    HTTP/1.1 200 OK\r\n
        [Expert Info (Chat/Sequence): HTTP/1.1 200 OK\r\n]
            [HTTP/1.1 200 OK\r\n]
            [Severity level: Chat]
            [Group: Sequence]
        Response Version: HTTP/1.1
        Status Code: 200
        [Status Code Description: OK]
        Response Phrase: OK
    Transfer-Encoding: chunked\r\n
    Date: Wed, 02 Jan 2019 11:10:46 GMT\r\n
    Content-Type: application/x-mpegurl\r\n
    Content-Disposition: inline; filename=NPO1 HD.m3u8;\r\n
    Server: TwistedWeb/17.9.0\r\n
    \r\n
    [HTTP response 4/5]
    [Time since request: 0.006985399 seconds]
    [Prev request in frame: 26749]
    [Prev response in frame: 26759]
    [Request in frame: 28126]
    [Next request in frame: 41969]
    [Next response in frame: 41974]
    HTTP chunked response
        Data chunk (182 octets)
            Chunk size: 182 octets
            Data (182 bytes)
                Data: 234558544d3355200a23455854564c434f50542d2d687474...
                [Length: 182]
            Chunk boundary: 0d0a
        End of chunked encoding
            Chunk size: 0 octets
        \r\n
    File Data: 182 bytes