mvasilchuk / yasem

GNU General Public License v2.0
77 stars 52 forks source link

Porting to QT Webengine from scratch #44

Open damdinsharav opened 6 years ago

damdinsharav commented 6 years ago

I'm thinking of creating MAG emulator using QT Webengine as a side project.

If you happen to know how Stalker portal work with browser please guide me.

As far as I know it seems like I need to change "User agent".

What else needed, how to send MAC address information to Stalker from browser?

Does anyone want to collaborate on this project?

ghost commented 5 years ago

Check the wikis on the infomir site. Rest, you can contact me. I amt a coder but I we can work something out.

damdinsharav commented 5 years ago

@hapishyguy how may I contact you? e-mail at damdinsharav[at]gmail[dot]com

mberard commented 5 years ago

I'm in too! I have compiled the current code, almost work. I got authenticated, got the USB storage message but soon crash. I would like to participate in this project. I would like to implement a PVR backend to yasem such as tvheadend, next PVR, ...

damdinsharav commented 5 years ago

I still wants to start from scratch on this project with QT webengine but I don't know where to start. If I load just url of stalker, it says "Firmware of your STB is outdated.Please update it." I think I need to pass some data to the server. Does any have documentation for it?

ghost commented 5 years ago

According to me you are connected to the server and need a connection now, means subscription. This is what happens when we connect the box also so thats why I am figuring.

mberard commented 5 years ago

This is normal behaviour, same here, probably with a different provider. I got further with my compiled version of YASEM, but it is very unstable. I recompiler ffmpeg also, latest version to expose the new library to YASEM. I also had a look to pvr.stalker Kodi project. On this project, I get the EPG loading but unable to stream video.

damdinsharav commented 5 years ago

@hapishyguy when I browse url from any browser that message comes up. So I think MAG's webkit sends certain data to tell server that it is MAG device, not a regular browser.