Skip to content

waze-on-cluster: a second copy for a side camera view (waze-on-cluster-side.service) - #223

Closed
TheoneLT83 wants to merge 1 commit into
robertnisipeanu:mainfrom
TheoneLT83:pr/side-camera-copy
Closed

TheoneLT83 wants to merge 1 commit into
robertnisipeanu:mainfrom
TheoneLT83:pr/side-camera-copy

Conversation

@TheoneLT83

Copy link
Copy Markdown

waze-on-cluster-side.service (+ .socket) runs the same program with waze-on-cluster-side.conf: the camera unit's stream (media_transport.avb_streaming.1, the one Drive Recorder and the parking cameras use) drawn in the map area below the cluster's badge (map_rect = 0,36,1088,408), its cluster off until an app turns it on through its own control socket (/dev/shm/waze-on-cluster-side/ctl.sock, {"cmd":"cluster","on":"1"}). Only keys that differ from the built-in defaults; no features file, no CarPlay.

What turns it on is up to an app: in TheoneLT83/Cluster-apps, Cluster functions turns it on while a turn signal shows one side, with the cluster map off meanwhile, after asking the camera unit (ICAM2Proxy) for view 3 (left) or 4 (right). That app part is not in this pull request.

component.json: the conf, the two units enabled, the service in recmgr and restart.

Screenshots: none: nothing of this repository's screens changes.

AI: Claude Code, Claude Opus 5.5 (ported from TheoneLT83/Cluster-apps, waze-on-cluster 0.10.15 there). Tested: waze-on-cluster make test-node passes on this branch with this repository's tags; every key of the new conf is one this version knows. Not tested on a car (in TheoneLT83's fork it is released, not yet confirmed on a car). Human review: TheoneLT83 asked for this pull request; the code was not reviewed line by line by a person.

🤖 Generated with Claude Code

Merge Idrive7 assistant versions

…r-side.service)

The same program on the camera unit's stream (media_transport.avb_streaming.1), drawn in the map area below the
cluster's badge, its cluster off until an app turns it on through its own control socket
(/dev/shm/waze-on-cluster-side/ctl.sock).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01RaQUWvi4djHaPEqip7eCr8
@robertnisipeanu

Copy link
Copy Markdown
Owner

Thanks for this. Closing it: a camera view should be its own app or tool drawing through cluster-render, like any other client, not a second copy of the map program pointed at the camera stream.

As a second Maps on cluster service, every install gets a process that joins and decodes the camera stream from boot, even while the view is off. The camera view is also tied to the map's settings and status, and can't be installed or used without it. cluster-render already takes video layers from any client and composes several videos (README "Layers"), so a separate camera client can do this on its own, without changes to the map.

@arieljrxd

Copy link
Copy Markdown
Contributor

I am glad somebody is working on this as well, @TheoneLT83 if you want to collab i'm down. I am actually almost done with this one as well, various days of testing and making sure it doesn't conflict with the safety crash feature that auto records the accident.

But then, I have 2 kids and a wife haha! I just don't really have much free time on some days to tinker around it. I am on my final phase of testing tho, and it will be its own separate app.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants