Hi Craig,
Just to update you on some progress (today was the 1st day I had time to look at the camera).
I updated the firmware and got the gst_viewer code to run out of the box on an x86 machine with ubuntu 20.04. The loopback didn’t work (not sure why).
Next I ran on the gst_viewer sample code on the nitrogen6x board running ubuntu 18.04 and got no feed and the following error.
start, hit any key to stop
[INFO] bitstreamMode 1, chromaInterleave 0, mapType 0, tiled2LinearEnable 0
Error: Internal data stream error.
stop
XIO: fatal IO error 22 (Invalid argument) on X server “:0.0”
after 8 requests (8 known processed) with 0 events remaining.
Then I set the resolution in the source code to THETAUVC_MODE_FHD_2997 as you had suggested and I got a streamed feed. SUCCESS!!!..but the latency was about 2seconds. After 90seconds of feed the latency was up to 10seconds. Perhaps there is a some way in the code to fix this. A 2 second lag would likely not kill us in our application, but it would have to be fairly static.
The loopback did not work. "Could not open device /dev/video1 for reading and writing. I am unsure what’s going on here. The kernal module was loaded etc. I am uncertain how to be sure the correct /dev/videoX is being selected. Not sure how to proceed here or if its worth it.
I tried the libptp examples and was able to set state parameters on the camera, capture images and copy them off the camera. In some settings this might even work for us…I will have to do some more testing.
I could not try the streaming over wifi, because I could not load the rtsp plugin onto the theta V, that requires a windows or mac box and I don’t have one of those here ATM.
So some success. If there is a way to stabilize latency the in gst feed that would be great. If there was a way to speed up the still image capture / transfer that would be great too. If you have ideas about the loopback let me know.
Cheers,
Andrew