Ricoh Theta S getLivePreview Javascript

[bleudreams]

Greetings Everyone,

I am currently building a mobile application that leverages A Ricoh Theta S camera for 360 images. Within the Ricoh Theta api exists a functionality called getLivePreview. This functionality is intended as sounds.

I am currently working within the javascript ecosystem and to this point have encountered significant issues in getting this functionality to work.

I can send the post request and see that a stream engages but I am unable to access the data of the stream. I can also interrupt the stream and grab the tail of it, which amounts to a jpeg image, which can be rendered.

Has anyone faced this issue? If so, what were your findings?

[tekcor]

Are you sure you are talking about vvvv? What do you want to know exactly?

[io]

I also thought you were creating a vvvv app, anyway @tekcor, he came here because of

Http multi part mjpeg stream

Hallo, I am using the API of the Theta S camera, it is based on json communication, more info here: https://developers.theta360.com/en/docs/v2.1/api_reference/ So far it is working as supposed but there I can t get the live preview as it is a multi part mjpeg stream. I am not sure whether it is even possible with the HTTP nodes or the https://vvvv.org/contribution/vobjects addon. https://developers.theta360.com/en/docs/v2.1/api_reference/commands/camera.get_live_preview.html tx Simone EDI…

that said should we be able to fix this in JS then it should be fairly easy to port it to vvvv, that project of mine went dead atm but I wouldn t mind to be able to get the preview.

S.

[bleudreams]

Continuing the discussion from Http multi part mjpeg stream:

@io

Unfortunately I don’ t think it is possible, or it is not trivial, as the camera creates its own access point so I am not really sure about how to do some NAT on my router to give it a public access (furthermore I am on a HDSPA connectio right now, but I ll have a look at it).
The “ritual” is as following:

• POST to IP/osc/commands/execute with payload
  {
  “name”: “camera.getLivePreview”,
  }

• the camera starts to stream (akwnoledged by monitoring the wifi use of bandwidth), nothing comes out of the http nodes

• if you stop the stream (must be done in the camera because if you do it with an http request, the latest response will erase the previous, or alternatively with a parallel request) the http node spits out the recorded frames with the folowing content type, they frame boundary is explicitly defined

multipart/x-mixed-replace;boundary=------live_preview--------

IO,

How did you figure out that “-----live_preview------” is the right boundary name?