This commit is contained in:
legop3
2026-07-10 00:57:10 -04:00
parent 6a31d8bc35
commit c406ace339
+8 -2
View File
@@ -11,7 +11,10 @@
- if you are a spectator, you can see the snapshots for it - if you are a spectator, you can see the snapshots for it
- local spectators should get full video like they already do now though - local spectators should get full video like they already do now though
- the camera needs to be a replay source - the camera needs to be a replay source
- camera video needs to go through the same pipeline as rover video does and get to the client over webRTC
## camera learnings
- scan for all onvif features that the camera has
## UI flow: ## UI flow:
- whole UI should be very technical and utilitarian - whole UI should be very technical and utilitarian
@@ -24,8 +27,9 @@
- a big button to open the camera controller - a big button to open the camera controller
- the fullscreen camera interface - the fullscreen camera interface
- the rest of the site needs to go away when this is open - the rest of the site needs to go away when this is open
- when its open, it takes over your rover controls. whatever they are
- easy route for this could be to intercept it right before the control goes to the server, so any control gets converted to a ptz control
- desktop - desktop
- takes over rover controls
- movement controls pan and tilt - movement controls pan and tilt
- camera up / down controls zoom - camera up / down controls zoom
- headlight and laser buttons hopefully control spotlight and IR light or something - headlight and laser buttons hopefully control spotlight and IR light or something
@@ -33,4 +37,6 @@
- right sidebar with info and controls info - right sidebar with info and controls info
- mobile - mobile
- uhhh idk - uhhh idk
- - obviously, camera on the screen
- probably add a variant of the mobile controls just to retitle the things from the rover controls to the camera controls
- and just use the same control columns