Basic.AI

In an first-person (Ego) view, you can annotate an object in someone’s hand. Switch to a third-person (Exo) camera, and the same object shifts in position, scale, and appearance. It may be occluded by the hand, or confused with similar items nearby. Segmentation and correspondence quickly stop being reliable then.

This is the main challenge of cross-view . In real systems, it stalls critical workflows in multi-camera , video retrieval, and human-robot teaching. Even cannot handle this well. Its spatial prompting was never designed to transfer across views.

A recent Highlight paper, V²-SAM, caught our attention. It extends SAM2 to a unified cross-view object correspondence framework, without requiring camera poses, semantic labels, or explicit . The same object can be reliably re-identified and segmented across different viewpoints.

📄 Paper: https://arxiv.org/abs/2511.20886
🏠 Project: https://jianchengpan.space/projects/V2-SAM/

The method splits the problem into two parts: where the object is, and what it looks like. V²-Anchor uses geometry-aware features from for cross-view matching, enabling SAM2's point-prompt capability in cross-view settings for the first time. V²-Visual introduces a Visual Prompt Matcher that aligns object appearance representations across views at both feature and structural levels.

On the Ego-Exo4D benchmark, V²-SAM sets a new record at 48.0 overall IoU, surpassing the previous best by 4.6 points, while using only 15M trainable parameters, less than 1% of the strong baseline ObjectRelator. On DAVIS-2017 video and the HANDAL-X robotic cross-view transfer task, V²-SAM leads by a wide margin. Zero-shot transfer to HANDAL-X reaches 77.2 IoU, showing strong generalization.

This work provides a practical, engineering-grounded answer to cross-view perception. It has clear potential as a general-purpose backbone for multi-camera understanding, embodied demonstration learning, and human-to-robot view transfer.

A question from one of our data annotators:
can already read, edit, and generate images. Can it also take over fine-grained annotation tasks like ?

Let's reframe that. Does really understand what every region in an image represents?

A recent benchmark from NTU, called 𝐏𝐢𝐱𝐞𝐥𝐀𝐫𝐞𝐧𝐚, offers a useful way to think about that question.

Most image generation benchmarks rely on metrics like CLIP Score or FID. Those scores tell whether the output looks right overall, but say little about pixel-level understanding. PixelArena takes a more direct route. It asks models to generate masks, then evaluates them with metrics such as F1, mIoU, and Dice.

The researchers sampled 150 images each from CelebAMask-HQ and COCO. Models were given the original image, a color-coding scheme, and a palette, then asked to generate standard segmentation masks in a setting.
🏠 𝐏𝐫𝐨𝐣𝐞𝐜𝐭: https://pixelarena.reify.ing/project

The lineup included Pro Image, Gemini 2.5 Flash, 1, and Emu 3.5, with dedicated models like SegFace and OneFormer as baselines.

On face segmentation, Gemini 3 Pro Image was the only general-purpose model that showed clear task understanding and reached a best F1 score of 0.708.

But on the more complex COCO , the best F1 score dropped to just 0.269, with clear instability across outputs. That is still far from stable, general, and reliable performance.

The researchers also found that models sometimes appear to reflect without actually checking themselves. Even when a mask was clearly wrong, the chain-of-thought reasoning confidently declared the results accurate.

Meta's SAM family, of course, has already demonstrated strong zero-shot segmentation. PixelArena suggests that general models are starting to show real potential for fine-grained visual annotation, while also laying bare their instability, sharp performance drops in complex scenes, and unreliable self-checking.

Ultralytics released , first shown at YOLO Vision 2025 (YV25). It’s the most advanced so far, with a strong focus on deployment.

Many teams can train a detector to score well on COCO, then watch it slow down or become unstable on edge devices. NMS introduced unpredictable latency, making perfect real-time nearly impossible in dense scenes. For about a decade, every YOLO generation has lived with this trade-off.

YOLO26 pushes YOLO further toward a true end-to-end detector by removing NMS entirely. The goal is a single pass from image to final, non-overlapping boxes, with clear design choices that favor a shorter, cleaner deployment path.
🏠 𝐃𝐨𝐜: https://docs.ultralytics.com/models/yolo26/

Classic YOLO variants allow multiple predicted boxes to match the same object, then rely on NMS at inference to filter duplicates. YOLO26 changes the default to a one-to-one prediction head, training the model to produce exactly one final box per object.

It also removes DFL. To maintain accuracy, YOLO26 adds STAL and ProgLoss to strengthen small-object performance and improve training stability. It combines the Muon optimizer idea from training with SGD, creating MuSGD for faster, steadier convergence.

On COCO, YOLO26 reports the best accuracy at the same latency, and the best speed at the same accuracy. CPU inference can be up to 43% faster. End-to-end outputs make latency more predictable and shorten the deployment pipeline.

YOLO26 reinforces a simple point: in , subtraction can beat addition. A simpler path to the same or better results is often what needs.

If these gains carry into real products, YOLO26 could reduce the cost of edge rollouts and make stable real-time perception easier on CPU-only setups, Jetson, mobile, and industrial devices. For safety-critical work like and , predictable latency and robust real-time behavior matter.

📖 𝐄𝐝𝐠𝐞 𝐀𝐈 𝐚𝐧𝐧𝐨𝐭𝐚𝐭𝐢𝐨𝐧 𝐬𝐭𝐫𝐚𝐭𝐞𝐠𝐢𝐞𝐬: https://www.basic.ai/blog-post/edge-ai-lightweight-computer-vision-models-data-annotation-strategies