57 replies to this topic

[foxbob]

I am build pli5 in my solo2.Web tv work,but recording not play-Problem with network.

[rocco99]

And is it right i can not use mutiple audio and teletext subs in Web TV?

[rocco99]

On Chrome get message: problem with network VXG

On Firefox message: there is a plugin required to watch this content. VLC

 

It is possible to add Realpayer and/or WMP a possible players?

Edited by rocco99, 21 November 2016 - 11:19.

[Heppieboeddah]

Well, 

 

Great update of Openwbif

 

On my Zgemma installed as well as the VXG plugin. Installed it on the pc as extension as too

 

Seems to connect great, but after a while a network error.

 

Must say that i changed the port in Openwebif to a not standard port! Might that be a problem? [xxxxx instead of the standar port 80]

 

Because there is no setup for the VXG plugin on the box i am not able to check/change it..

 

Openwebif 1.01 was working out of the box with no problem

Anyway to refert back to v 1.01? If so howto? And is it possible to block any update of Openwebif till this problem is solved

 

Sometimes 'if it aint broken, dont fix it' is the best there is...

Edited by Heppieboeddah, 21 November 2016 - 13:45.

[SpaceRat]

We are currently in the process of getting as much as possible to work and hide stuff that is not going to work at all.
Previous versions have shown options that simply can not work.

Here is what will and should work:
- Live TV and transcoded live TV work without auth for streaming on any image.
- Live TV and transcoded live TV will only work using http, not https. This restriction applies to all images.
- "Recordings" (Or rather: files) work with and without auth for streaming and using http or https, using VLC, VXG and - if the video format is supported¹ - HTML.
- Live TV works with and without auth for streaming on VTi, Black Hole, using VLC or VXG
- Live TV works with and without auth for streaming on oe-a images using streamproxy and using VLC or VXG
- Transcoded live TV works with and without auth for streaming on machines using a different port for transcoding using VLC but not VXG

Browser restrictions:
IE, Firefox and Safari only support VLC but not VXG
Chrome, Chromium and possible other Chromium-based browsers only support VXG but not VLC.
Opera has no official way to install either VXG or VLC, technically it should support VXG as it is Chromium based.

Mobile Chrome, Firefox and Safari can handle neither VXG nor VLC.

We are in the process of hiding all elements that are unusable but as you can see that's a complicated matrix.

¹HTML5 player only supports MP4, WebM, and Ogg for video by design, additional restrictions apply to IE and Safari (Only MP4 there).
HTML5 player only supports MP3, Wav and Ogg for audio by design, additional restrictions apply to IE (Only MP3) and Safari (Only MP3 and Wav).

Edited by SpaceRat, 21 November 2016 - 18:08.

[MastaG]

Is it me or is the VXG package not built anymore?

[foxbob]

It is me too.

[SpaceRat]

This pull request should fix it:

https://github.com/O...e-core/pull/143

[littlesat]

Merged... thanks!!!

 

Great face lifts in OWIF within the last weeks....!!!!

[MastaG]

Thank you SpaceRat

[SpaceRat]

No problem.

There might be one issue though:
opkg can not handle files changing the package proving them well.
Those that have not installed the -vxg package should have no problem at all.
But for those who have installed it, the files for vxg will move from owif to owif-vxg through the next update and the result is nearly unpredictable.
If owif gets updated first and then owif-vxg, everything should be fine.
The other order might result in the vxg files missing afterwards or the owif or owif-vxg updates to fail.

If that happens, uninstall both packages manually and re-install them afterwards.

Gesendet von meinem Siemens C25 mit Tapatalk

[WanWizard]

Give the vxg package a dependency to the owif package, and owif will always be installed first?

[rocco99]

We are currently in the process of getting as much as possible to work and hide stuff that is not going to work at all.
Previous versions have shown options that simply can not work.

Here is what will and should work:
- Live TV and transcoded live TV work without auth for streaming on any image.
- Live TV and transcoded live TV will only work using http, not https. This restriction applies to all images.
- "Recordings" (Or rather: files) work with and without auth for streaming and using http or https, using VLC, VXG and - if the video format is supported¹ - HTML.
- Live TV works with and without auth for streaming on VTi, Black Hole, using VLC or VXG
- Live TV works with and without auth for streaming on oe-a images using streamproxy and using VLC or VXG
- Transcoded live TV works with and without auth for streaming on machines using a different port for transcoding using VLC but not VXG

Browser restrictions:
IE, Firefox and Safari only support VLC but not VXG
Chrome, Chromium and possible other Chromium-based browsers only support VXG but not VLC.
Opera has no official way to install either VXG or VLC, technically it should support VXG as it is Chromium based.

Mobile Chrome, Firefox and Safari can handle neither VXG nor VLC.

We are in the process of hiding all elements that are unusable but as you can see that's a complicated matrix.

¹HTML5 player only supports MP4, WebM, and Ogg for video by design, additional restrictions apply to IE and Safari (Only MP4 there).
HTML5 player only supports MP3, Wav and Ogg for audio by design, additional restrictions apply to IE (Only MP3) and Safari (Only MP3 and Wav).

 

At me OpenPli, live channels in browser don't work at all.

[SpaceRat]

In OpenPLi you might have to disable auth for streaming to make WebTV work.

But note that everybody and his grandma can access your streams (and occupy tuners) then if you happen to have have a port-forwarding for streaming ports.

[SpaceRat]

Give the vxg package a dependency to the owif package, and owif will always be installed first?

It doesn't work that easily.
Once both packages have been installed before and both get updates, the order of updates is unreliable.

The process migrating from Samba 3.0.x to Samba 3.6.x in oe-a was long and sometimes painful, because files had to be moved across packages.
I ended up adding a temporary (self-destroying) SysVInit-script to the box for certain upgrades, so that this script could perform uninstall/reinstall actions in proper order.

opkg also does strange things on RREPLACE and RCONFLICTS. You would guess that a package that rconflicts and rreplaces an existing older package will lead to uninstall of the old package and installation of the new one ... forget it!

[rocco99]

In OpenPLi you might have to disable auth for streaming to make WebTV work.

But note that everybody and his grandma can access your streams (and occupy tuners) then if you happen to have have a port-forwarding for streaming ports.

 

Already been disabled.

[christophecvr]

 

Give the vxg package a dependency to the owif package, and owif will always be installed first?

It doesn't work that easily.
Once both packages have been installed before and both get updates, the order of updates is unreliable.

The process migrating from Samba 3.0.x to Samba 3.6.x in oe-a was long and sometimes painful, because files had to be moved across packages.
I ended up adding a temporary (self-destroying) SysVInit-script to the box for certain upgrades, so that this script could perform uninstall/reinstall actions in proper order.

opkg also does strange things on RREPLACE and RCONFLICTS. You would guess that a package that rconflicts and rreplaces an existing older package will lead to uninstall of the old package and installation of the new one ... forget it!

 

Yes the RRconflicts never went fine with opkg . But on such big changes it's best to reflash the box then problems are gone. Just like a major base core update whatever You do .... Whitout reflash in 80 % and even more case you run into troubles. If You flash the box .... mostly no troubles unless there is a bug in th new core

[littlesat]

But note that everybody and his grandma can access your streams (and occupy tuners) then if you happen to have have a port-forwarding for streaming ports. 

->

Therefore it is never smart forward those ports to your box.... open ssh and/or (open)VPN instead....

[SpaceRat]

Therefore it is never smart forward those ports to your box.... open ssh and/or (open)VPN instead....

They require port forwards too

But a different topic.

[littlesat]

They require port forwards too 

->

Some routers have (open)VPN functionality....