Skip to content

Prefer SAM2 for point segmentation when both SAM add-ons are installed - #1972

Merged
BryonLewis merged 3 commits into
mainfrom
dev/prefer-sam2-segmenter
Sep 24, 2026
Merged

BryonLewis merged 3 commits into
mainfrom
dev/prefer-sam2-segmenter

Conversation

@mattdawkins

Copy link
Copy Markdown
Member
  • interactive_segmenter_default.conf is whichever SAM add-on was installed last, so installing SAM3 for text queries also switched point segmentation to SAM3
  • The desktop now starts the interactive service on interactive_segmenter_sam2.conf when it exists; the SAM3 text-query sibling config is still discovered alongside it

🤖 Generated with Claude Code

The default segmenter config is whichever add-on was installed last.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
@mattdawkins
mattdawkins force-pushed the dev/prefer-sam2-segmenter branch from d203066 to 4e21e36 Compare September 24, 2026 02:05
mattdawkins added a commit that referenced this pull request Sep 24, 2026
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

# Conflicts:
#	client/platform/desktop/backend/native/interactive.ts
A VIAME install rewrites interactive_segmenter_default.conf with the core
placeholder, so the choice cannot rest on the add-on's override of it.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
mattdawkins added a commit that referenced this pull request Sep 24, 2026
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

@BryonLewis BryonLewis left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get using SAM2 for the point segmentation instead of using SAM3.

@BryonLewis
BryonLewis merged commit 520df0d into main Sep 24, 2026
3 checks passed
@BryonLewis
BryonLewis deleted the dev/prefer-sam2-segmenter branch September 24, 2026 17:10
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.

2 participants