Samsung Tizen Grabber and Choice of Communication Protocols

[lellotavernello]

The HyperTizen app installed on the Samsung TV (with Host PC IP 127.0.0.1 in Developer Mode (the only way to send the video signal captured by the TV, don't ask questions about this hahaha)) was configured directly on its user interface to connect to the IP of my PC (which temporarily acts as a host while waiting for the raspberry) on port 19445. Although the TV correctly sent the data to that port, it used the HTTP protocol instead of the required ProtoBuf over WebSocket. Consequently, HyperHDR on my PC was unable to interpret the data received, making the connection ineffective. Is it possible to set hyperHDR to directly read the data sent as is from the TV on port 19445 but with the HTTP protocol instead of ProtoBuf?

[steve41200]

Hi, I try the same thing of you. Hypertizen on the TV. HyperHDR on a Lxc in my homely, nothing seeing in capture live.
HyperTizen on SSP device show nothing.
I have try on a raspberry, plug in USB in the TV with hyperHDR on it.

Hypertizen on SSP device Show the hyperHDRPi, and HyperHDR on my homely (no USB connection between them, too far)
But nothing see in capture video...
Have you find a solution ?

[lellotavernello]

As I mentioned in my previous post, Hypertizen transmits via HTTP on port 19445 (Hypertizen is very secure since it runs on Tizen OS). I think the best strategy is to work on the HyperHDR server side. The only way is to see if you can translate from HTTP to ProtoBuf over WebSocket without any perceived latency, or have HyperHDR read the HTTP protocol directly. Unfortunately, I haven't been able to figure it out, especially since I've been working hard these past few days and have other things to do. I'll try again next week, although, as I mentioned, I don't know much about HyperHDR and was hoping someone with more knowledge could help me out.

[steve41200]

Yes I'm little disappointed too.
I have play with log in HyperHDR and it seems little better
He connect to the TV alone
but I have always
"[WEBSOCKET] Pong received, protocol violation!"
and no changing color led.

Before the connection was not good between tv and Hyperhdr and I has a msg error about libX11.
I have install sudo apt-get install libx11-6

[lellotavernello]

In theory, "[WEBSOCKET] Pong received, protocol violation!" means the protocol is incorrect, but the data is arriving in the right place, just like for me. I'm not sure what to do now, though...

[awawa-dev]

Hi
I think a better place would be the Samsung Tizen Grabber author's repository. If he didn't include flatbuffers/protobuffers in his application for some reason, then it's too bad, I won't chase him or make any changes myself, especially since they concern the websocket (which is crucial for HyperHDR) chosen for some unknown reason, and such a protobuf can be implemented very easily even without using the official Google libraries (there are lightweight alternatives, I also use them in HyperHDR).

[lellotavernello]

For anyone else who needs it, this is the link to the hypertizen dev github conversation: reisxd/HyperTizen#10

[awawa-dev]

Seems their is already a proper PR reisxd/HyperTizen#8 so I think this PR can be closed now.