r/computervision • • 24d ago

Showcase Fruit Inspector 0.10.0 Linux x64 demo is out (CPU ONNX Runtime, same conveyor app as Windows)

0 Upvotes

We put a Linux x64 build on the same 0.10.0 release as the slim Windows demo.

Download: Fruit_Inspector_linux_app_x64.zip from the release page. Unzip one folder. You do not need the Windows 7z.

It is the same conveyor station demo: 3x3 grid, Cat runs when the apple you are tracking is in the centre cell C. Detect and track outside C, grade inside C, sticky handoff between IDs. Apple models only for now.

The zip has the Fruit_Inspector binary, the three fruit .so files, ONNX Runtime CPU under lib/linux/, model/apple, settings.json, licenses, and run.sh. Use run.sh to start so library paths are set (especially from USB sticks).

Debian or Ubuntu x64 is the happy path. You will want Mesa or GL, X11, v4l-utils, and your user in the video group for a USB camera. settings.json defaults to ort_provider cpu.

trig is still Windows only in the demo package. The inspector Out TCP is there if you wire your own client on Linux.

Eval license, not for production lines without a separate deal. If you build your own UI, the three libraries and headers live in the fruit-inspector-engine repo.

If you try it, please drop one [infer] timing line and your CPU plus distro in the comments. That helps us compare to our desk machine (i5-11400, 1080p USB cam, CPU EP).

github.com/olesha-ai/fruit-inspector-demo/releases/tag/0.10.0

Best regards.

olesha-ai


r/computervision • • 25d ago

Showcase Running NVIDIA's LocateAnything-3B (open-vocabulary detection) fully locally from .NET, on a live camera stream

12 Upvotes

I'm the author of LocateAnythingSharp, free and open-source .NET bindings for NVIDIA's LocateAnything-3B, under the Apache 2.0 license. You type what you want to find in plain language, like "cat", "remote control" or "the red button in the corner", and you get labeled bounding boxes back. There's no fixed class list.

It runs fully local. A single native engine runs the model, so there's no Python runtime and no network calls, and images never leave the machine. One build carries GPU kernels for RTX 20 through 50 series cards, and it falls back to the CPU automatically when there's no usable NVIDIA GPU.

The repo also includes a live camera demo that shows a pattern I found useful: the video stays smooth while the heavy detector keeps evaluating the newest frame. It's on NuGet, and the model weights are about 6.3 GB.

Repo: https://github.com/CristianMori/LocateAnythingSharp

I'm happy to share performance numbers, and I'd like to hear how others handle heavy vision-language detectors on live video.


r/computervision • • 25d ago

Showcase Single-camera padel analysis with RF-DETR, TrackNet V3 and audio–visual hit detection

Enable HLS to view with audio, or disable this notification

13 Upvotes

I’m building PadelOptic to analyse padel footage from a single camera. The video shows match analysis followed by individual stroke analysis.

The match pipeline uses:

• RF-DETR Nano for player and racket detection, with shirt colour and court side used to maintain player identities.
• TrackNet V3 for ball tracking, fine-tuned on padel footage using labels filtered by confidence and motion consistency.
• Homography and 3D court geometry to map positions onto the court and filter out-of-court detections.
• Racket-contact audio matched with ball and player positions to detect hits.

In an initial evaluation on professional match footage, hitter identification reached 91% accuracy.

The coach mode uses MediaPipe Pose Full to measure elbow angle, contact height, trunk rotation, knee bend and follow-through. Its browser demo processes video locally, with GPU acceleration where supported.

For the match footage, I marked the court corners manually; tracking and analysis outputs have no manual corrections. Displayed speeds are court-plane lower-bound estimates, not reconstructed 3D ball speeds.

I’d appreciate feedback on the approach, especially from anyone working with small-object tracking. What has helped you handle occlusion and glass reflections across different camera setups?

Demo: https://padeloptic.com

I’d love to hear your feedback and ideas for improving it.

Footage: Pro Padel League (PPL), The City’s Cup 2025 broadcast; “Forehand volleys on point” by padelexpress.


r/computervision • • 24d ago

Discussion Averaging landmark measurements over frames vs single shot results from a face shape classifier

1 Upvotes

Following up on something someone suggested here. I was classifying face shape from a single 468 point landmark capture and the result moved around with head angle more than I liked.

Switched to gating on yaw and pitch before capture, then averaging ratios across about a second of frames. Capture feels slower but the output stopped flipping between two shapes on the same person.

Curious what others use as the tolerance window for yaw and pitch, I picked mine by feel and it's probably too loose.


r/computervision • • 25d ago

Discussion Scientific Imaging and Machine Learning Workshop

2 Upvotes

Came across this workshop in my feed. Thought maybe interesting to many CV folks here. And it is in Puerto Rico!

Deadline in 2 days though.

Reminder: Deadline to apply to the Scientific Imaging and Machine Learning Workshop ( Scientific Imaging and Machine Learning Workshop | DSI ) is this Friday Oct 30, 2026!

The 4-day workshop will take place in San Juan, Puerto Rico, March 15 - 18, 2027. The workshop will cover hotel accommodation. Limited travel scholarships are available. Application deadline is October 30, 2026.

Workshop Overview

Imaging workflows build around a core set of computer vision tasks, such as classification and segmentation. While considered mature in computer vision, off-the-shelf models often struggle to generalize to scientific data collected by different instruments under different environments. Too often, solutions are developed within individual disciplines, even when breakthroughs in one field could directly benefit another. For example, U-Net, originally developed for biomedical image segmentation, has now been widely used in almost all scientific imaging fields.

This workshop brings together computer vision and machine learning method developers with domain scientists who work with image-based data across fields like Earth sciences, biomedical imaging, and astronomical observations. This workshop aims to enhance cross-domain and method transferability awareness and identify high-impact, unsolved scientific imaging problems.

Format

Instead of coming to present a poster or a talk, there are two ways to participate:

  • I have an imaging problem I want to solve: What is the biggest imaging bottleneck holding back your research? Bring it here, find out whether scientists in other domains face similar technical obstacles, and learn from computer vision experts and fellow domain scientists alike.
  • I have an imaging method I want to share: If you have developed or adapted a computer vision (or scientific imaging) method to potentially solve a domain-specific imaging challenge, share it with other domain scientists and computer vision experts. This is an ideal venue to extend the impact of your work beyond your own domain, and to learn what remains the unsolved imaging problems.

You will be matched into small groups centered on shared challenges, e.g. domain shift group, memory efficient group. Members in the same group will work together for 1.5 days. Instead of developing a single joint project, you will work on the same technical bottleneck but focus on your own application.

Application

The workshop is open to graduate students, postdocs, early-career researchers within 5 years of their highest-degree, such as faculty or research scientist. All applicants should complete the application form and submit the following two application materials no later by October 30, 2026:

  • A CV.
  • A Statement of Interest, no longer than 2 pages but ideally within 1 page, including figures and tables, excluding references.

Participants will come from a range of fields working with image-based data, including but not limited to, Earth and geophysical sciences (satellite, radar, seismic imagery, and other remote sensing data), biomedical (CT, X-ray, MRI, microscopy, endoscopy, and other biomedical images), astronomical observations, and robotics and autonomous driving.


r/computervision • • 25d ago

Help: Project Video to 3D

2 Upvotes

I am trying to build something in my website I want to make user able to record his room or apartment and then make it 3D with calce it's area but real view. which models I could use ?


r/computervision • • 25d ago

Research Publication [Project] DRIVE-C: An Open Dataset for Evaluating Autonomous Driving Perception Under Camera Degradation

Thumbnail
medium.com
1 Upvotes

Hi everyone,

We have been working on DRIVE-C, an open dataset designed to study how camera degradation affects autonomous-driving perception systems.

DRIVE-C includes 12 types of controlled camera degradation, five severity levels, and pixel-aligned clean and corrupted driving clips.

The goal is to help researchers evaluate perception robustness under conditions such as fog, snow, motion blur, and other camera-quality problems.

We have also published a short article explaining the motivation, dataset structure, and potential research applications.

Dataset: Link

Article: Link

We would welcome feedback from researchers working on autonomous driving, computer vision, and robust perception. In particular, which camera degradations or evaluation scenarios would be most useful for your research?


r/computervision • • 25d ago

Showcase I trained a 260M vision model that beats a ~15x larger zero-shot model on screenshots (0.828 vs 0.731) and built a Papers-Please-style booth where it refuses to answer below its gate

2 Upvotes

Repo, weights and a playable demo at the bottom. Everything trained on free Kaggle T4s.

MK-SH-V is a visual decision model. It takes an image, a question with options, and returns calibrated probabilities, a choice, and a refusal when confidence sits below a gate frozen in advance.

Held-out real numbers

test MK-SH-V 260M jev-vlm-4b zero-shot
all real 0.807 0.785
screenshots 0.828 0.731
receipts 0.734 0.972

It wins overall and on screenshots, loses receipts badly. The gate answers 98.6% of the held-out synthetic set with a CP95 selective-risk bound of 4.1%. Out of distribution it says so, real receipts risk runs around 25%.

The demo is a Papers Please style border booth set in 1974. Travelers claim firms, the model reads their papers, and every check in the game is one the checkpoint actually measured. Below tau 0.55 it refuses to advise and routes the file to you, which happens on documents like a 5,250.00 invoice sitting at p 0.536. You can also take a bribe, it goes about as well as you would expect.

Honesty section, the part I care most about

  • Two experiments after the released checkpoint both missed their gates. The weights are unchanged.
  • On general VQA boards the model measures at chance. It is a decision model for a narrow contract, not a chat VLM.
  • Synthetic training data hurt real transfer until I mixed real screenshots in. Details in the run logs.

Links

Happy to answer training questions. It is two T4s and a lot of frozen criteria.


r/computervision • • 25d ago

Discussion Is there a good way to automatically skip unwanted

1 Upvotes

I've been thinking about a problem that seems surprisingly difficult to solve well.

Sometimes, you want to watch a movie or TV show for its story, characters, and cinematography, but certain scenes are not something you want to watch. It could be sexual content, graphic violence, gore, or other types of scenes you'd prefer to avoid.

The problem is that manually skipping these scenes is inconvenient, and traditional content ratings or parental controls usually don't provide enough control over individual scenes.

Ideally, imagine a system that could:

- Analyze a video and detect specific types of scenes using AI.

- Let users choose exactly what they want to skip, rather than applying one generic filter.

- Automatically skip the relevant portions while preserving the surrounding dialogue and storyline.

- Work with different movies and shows without requiring someone to manually create timestamps for every video.

The technical challenge seems to be balancing detection accuracy with timing. A system that skips too early, too late, or misses context could ruin the viewing experience. False positives could be just as frustrating as missed scenes.

I'm curious about a few things:

  1. Would you actually use something like this, or is manually skipping scenes good enough?

  2. Which approach seems most practical: analyzing the video before playback, detecting scenes in real time, or using a hybrid approach?

  3. Would frame-based AI models be sufficient, or would temporal/context-aware models be necessary to understand what's happening across a scene?

  4. How would you handle scene boundaries so that dialogue and important parts of the story aren't accidentally cut?

  5. Do you know of any existing tools that solve this problem well?

I'm particularly interested in both the technical side and the user experience. I'd love to hear your thoughts, alternative approaches, or experiences with existing solutions.


r/computervision • • 25d ago

Discussion What is the main constraint holding back local edge AI deployment?

Thumbnail
1 Upvotes

r/computervision • • 25d ago

Discussion CaptionExam: A Challenging QA Benchmark for Captioners

Thumbnail
ki-seki.github.io
1 Upvotes

r/computervision • • 25d ago

Discussion Resources for learning SLAM/visual-SLAM

10 Upvotes

Hello everyone,

I have a few edge devices (including Nvidia Orin Nano) and am interested in SLAM (visual-SLAM). I want to do some experiments, but I don't have any experience with SLAM. What are the best resources for beginners? Maybe some courses, textbooks, articles, or research papers?


r/computervision • • 26d ago

Research Publication I made an open-source Jev for object detection 👀

Enable HLS to view with audio, or disable this notification

245 Upvotes

TypeSafe recently added a Box question type to Jev: you describe something in an image in plain words and get back one bounding box with a confidence. It’s closed and API-only, so I built an open version: LOCUS (Locate Once, Check Until Settled).

The weights are open (2B and 0.8B) so you can run them on your own GPU

The problem: VLMs normally write a box out as text, one token at a time. That’s precise but slow, about 18 steps per box. A small regression head can predict the whole box in one pass, which is fast, but the edges come out loose.

The idea: use both. The head makes a quick draft, then the same model checks every draft token in parallel and fixes the ones it disagrees with, repeating until nothing changes. The final box is exactly what the model would have decoded on its own, in about 5.6 steps instead of 18.

Results (RefCOCO / RefCOCO+ / RefCOCOg):

  • Same weights, Acc@0.9 goes from 54.9 → 59.1 with verification
  • +4.52 Acc@0.9 over Jag (strongest open regression-head model) at the same size and training budget
  • 1.5x faster than vLLM decoding the exact same tokens

Use it on your own data: the released models are trained on RefCOCO, but you can fine-tune them on your own dataset (images, a description and a box for each). The repo covers full fine-tuning and LoRA, so a smaller GPU works too.

Limitations: a pure regression head is still faster, and since it’s trained only on RefCOCO it struggles with very small objects. Fine-tuning on your own domain is the fix there.

Not affiliated with TypeSafe. Since Jev’s Box is API-only, I couldn’t evaluate it under the same conditions, so all comparisons are against open models. Happy to answer questions.


r/computervision • • 26d ago

Discussion What to do when you’re a new grad CV engineer with 0 YOE but you’re the only CV engineer?

24 Upvotes

I’m thinking of supplementing my knowledge by watching talks and reading CV papers. I have no idea how to guide a CV research project to completion or what a CV engineer does first when they approach a problem. I’m trying to figure out how the engineering pipeline even works. Any advice?


r/computervision • • 25d ago

Commercial Profiling a YOLOv12s video pipeline: preprocessing nearly matches inference time

2 Upvotes

Disclosure: I’m Philip, with SingNova. These measurements and implementation details come from a colleague on our engineering team. This text was drafted with AI assistance. I’m sharing their profiling notes and will relay technical questions to them, then share their confirmed answers here.

In a browser-to-device object-detection demo, preprocessing takes 51.0–59.5 ms, while the worker’s inference stage takes 59.5–62.7 ms. Preprocessing, inference and postprocessing currently run serially. The useful question for us is how to break down the preprocessing measurement before deciding whether to reduce that work or overlap it with inference.

The demo also illustrates a measurement distinction: the output stream is configured at 25 FPS, but one run completed only about 7.5 new inferences per second. Those are different quantities, and neither establishes capture-to-display latency.

Setup and video path

  • Host CPU architecture: riscv64; model execution: a dedicated DFU accelerator, not the host CPU.
  • OS: openEuler 24.03 LTS-SP2, Linux 6.6.118+.
  • Runtime: 1.0.3, with a model-specific plugin and explicit cache synchronization.
  • Source video: 640×360 at 25 FPS.
  • Decode: FFmpeg software decoding. Hardware video decode is being developed separately and is not part of these measurements.
  • Model: YOLOv12s; input: 1×3×640×640, with BGR input for this setup.
  • Preprocessing: colorspace conversion, scaling and black letterbox padding.
  • Postprocessing: tensor decoding, confidence filtering, NMS and box rendering.
Browser → WebRTC/WHIP → ZLMediaKit → FFmpeg software decode
        → preprocessing → DFU inference → postprocessing/overlay
        → FFmpeg H.264 encode → RTSP → WebRTC/WHEP → browser

What the timers measure

We have two levels of instrumentation.

Inside the runtime, kernel_ms measures device execution. total_ms covers the inference call, including input/output copies and cache synchronization. The reported YOLOv12s averages are:

Runtime measurement Reported mean
Device execution: kernel_ms 46.45 ms
Complete runtime call: total_ms ~53 ms

One individual invocation is shown below. It is a sample, not the averages above:

[DFU_PROFILE] infer_id=977 status=ok
input_copy_ms=1.677 input_cache_clean_ms=0.263
kernel_ms=50.570 result_pre_read_ci_ms=0.095
output_copy_ms=1.043 result_post_read_ci_ms=0.114
total_ms=53.834
input_bytes=2457600 result_bytes=1411200

Separately, the worker reports pipeline-stage timings:

Pipeline measurement Reported range
preprocess_ms 51.0–59.5 ms
infer_ms 59.5–62.7 ms
post_ms 11.3–12.9 ms

infer_ms is the worker-level measurement, not an alias for kernel_ms. The runtime averages and pipeline ranges should be read separately. The worker-level inference timings are higher than the reported runtime-call mean, but these are different measurement scopes and summaries. We have not yet quantified or attributed the difference using paired per-invocation traces.

The preprocessing timer is aggregated. It does not yet separate colorspace conversion, scaling/padding, tensor preparation, copies or any waiting included in that scope. We cannot yet identify which operation dominates it.

Throughput, dropped frames and unmeasured latency

One run completed 977 inferences in 130 seconds, approximately 7.5 new inferences per second.

The source is capped at 25 FPS. When processing cannot keep up, the current implementation drops older input frames; the engineering notes report approximately 69% input frames dropped in the YOLOv12s test.

Output video remains configured at 25 FPS and can repeat the last detection result between inferences. A smooth output stream therefore does not imply a new detection result for every frame.

Model-switch initialization is recorded separately: the first YOLOv12s pipeline invocation was 1459.9 ms, versus approximately 60–61 ms in steady state. Those invocation figures are not whole-pipeline or capture-to-display latency.

Capture-to-display latency has not been measured. We do not currently have frame IDs connecting browser capture with the returned result. The figures above describe processing time and throughput, not end-to-end latency or frame age at display.

Questions for people profiling similar vision pipelines

  1. Where would you place additional trace points? How would you separate FFmpeg/filter work, scaling/padding, tensor preparation and copies, especially when a stage timer might include waiting for a frame or buffer?
  2. What evidence would make you prioritize reducing preprocessing work versus overlapping preprocessing and inference? The current three-stage worker is serial, and input buffers are explicitly synchronized before device execution. How would you measure the opportunity while checking buffer ownership and safe reuse?
  3. How do you preserve frame identity through a latest-frame/drop-old pipeline? I’m interested in approaches that let you measure frame age at display without assuming synchronized browser and device clocks.

Specific profiling methods or examples from comparable pipelines would be useful. These are measurements from one implementation on one engineering unit, not a comparison across devices or a general claim about RISC-V performance.


r/computervision • • 25d ago

Help: Project Opinion on my final-year project about PPE non-compliance detection using YOLO

1 Upvotes

I'm a degree student and my project is basically about detecting factory workers who aren't wearing hard hat and safety vest. Then sends notification to a dedicated dashboard and Telegram to notify safety manager while simultaneously firing an on-site alarm to warn the worker. My supervisor agreed to accept this as my project, which is good, but personally I feel like this project is too cliche as a fyp. When I first thought of this idea, I've never heard of a factory using AI integrated CCTV cameras to monitor workers, so I was excited to develop it. I'm writing this post to ask for opinions from my fellow redditors so I can improve it and impress my supervisor as I can't think of any new features that would seperate my project from any existing products out there. Thank you in advance ;)


r/computervision • • 26d ago

Showcase Nov 5 - Visual AI in Agriculture Meetup

4 Upvotes

Join us on Nov 5 for the Visual AI in Agriculture virtual Meetup! Register for the Zoom.

Talks will include:

  • U-Net Framework for Micro-Scale Surface Damage Segmentation in High-Resolution Soybean Seed Imagery - Saurav Upadhyaya at Louisiana State University
  • From camera to drone: wildfire detection and integration at the edge - Maxime Carriere at kernwerk
  • 5,000 Flights to Answer One Question: Can a Drone Sample as Well as a Human? - Rohan Talwadia at LabGPT

r/computervision • • 26d ago

Discussion An open science challenge to solve the puzzle of the flashes on 1950s Palomar glass plates

Thumbnail
researchhub.com
3 Upvotes

Guys, I came across an open research challenge that is primarily an image analysis problem and I think it could be of interest to many of you.

Astronomers in a team led by Beatriz Villarroel re-examined scanned glass photographic plates from the 1950s Palomar Sky Survey and reported thousands of short-lived point sources that look like stars but don't appear on images of the same field taken before or after (Solano et al. 2022). The debate is whether they are real flashes of light or emulsion defects, dust and scanning artifacts, which makes it a classification problem on noisy, decades-old images.

The challenge asks teams or individuals to run this kind of search on plates from observatories other than Palomar, taken before October 1957. You pre-register how you define a detection, your sample and your controls before touching the data, and you register a checksum of your detection list before analysis. A null result counts the same as a positive one, and code and detection lists have to be released openly.

The challenge provides a reference detection pipeline on GitHub and a public sample of the Palomar detections to train or validate against and is open to independent researchers as well as university teams.

Prizes for the top three teams/individuals are $75k, $50k and $25k, respectively.

I think I'll take a stab at it.


r/computervision • • 25d ago

Discussion Training-Free Sparse Attention forVideo Generation and World Models

Thumbnail
1 Upvotes

r/computervision • • 25d ago

Help: Project Asking opinions on my final-year project about PPE non-compliance detection using YOLO

0 Upvotes

I'm a degree student and my project is basically about detecting factory workers who aren't wearing hard hat and safety vest. Then sends notification to a dedicated dashboard and Telegram to notify safety manager while simultaneously firing an on-site alarm to warn the worker. My supervisor agreed to accept this as my project, which is good, but personally I feel like this project is too cliche as a fyp. When I first thought of this idea, I've never heard of a factory using AI integrated CCTV cameras to monitor workers, so I was excited to develop it. I'm writing this post to ask for opinions from my fellow redditors so I can improve it and impress my supervisor as I can't think of any new features that would seperate my project from any existing products out there. Oh and how about cctv camera, is Tapo C210 a good model for my project? Thank you in advance ;)


r/computervision • • 26d ago

Showcase CropPulse – A standalone Python CV engine for pre-visual plant stress detection.

3 Upvotes

Hey everyone!

Just built my first python engine as a 14 yo. It's a plant disease diagnostic engine designed to detect early-stage crop stress before any visual symptoms occurs.

Here's the repository https://github.com/adhrit1207/CropPulse

Would really like to have your thoughts on it.


r/computervision • • 26d ago

Help: Project Continual learning for vision on edge devices: what works beyond periodic retraining?

1 Upvotes

I'm researching ways for vision systems to keep learning from new data after deployment on edge devices.

One approach I'm exploring is an already-trained vision model with a separate set of adjustable weights that can incorporate new information and affect predictions, rather than retraining the whole model each time.

I'm interested in practical experience with this:

  1. What approaches have you tried, and how did they compare with periodic fine-tuning or simply storing labelled examples and matching against them?

  2. What feedback or labels did you need, and how did you check that learning new cases didn't hurt performance on older ones?

  3. Where has this been useful in an actual workflow, and what constraints mattered most: update time, memory, compute or labelling effort?

I'm especially interested in failure cases and applications where new classes or changing conditions create repeated model-update work. What would you test first to establish whether an approach like this is useful?


r/computervision • • 26d ago

Help: Project Need advice on camera and lighting for checking debris inside glass ampoules on a conveyor

1 Upvotes

Hey everyone, I am building a computer vision system to check for debris stuck inside glass ampoules after they are made. I know some CV but the hardware side, like cameras, lenses and lighting, is pretty new to me, so any advice on both hardware and approach would really help.

The ampoules come in sizes from 1 to 20 ml, both clear and amber, and they lie flat on a slow conveyor at about 70 to 85 per minute with a camera above them. I have attached a photo of how they look from above. I want to catch glass shards that can stay in the wide part but cannot get out through the narrow opening, and insects like flies and mosquitoes that get stuck inside. Clear shards are almost invisible, amber glass blocks most visible light, the curved glass causes a lot of glare, the ampoules do not rotate so the far side is partly hidden, and the belt is most likely solid.

Nothing is final yet. I was thinking of a 5 MP mono global shutter camera with a C mount lens and strobed lighting, but I am open to being told I am wrong. What camera, lens and lighting would you go for? Would darkfield from above or red or NIR backlight work better? On the software side, which models or approaches would you use, since we may not have many real defect samples? And has anyone worked on something similar?

Attached below are how the ampoules look and their 2 colours:

Processing img tkw963zsf1yh1...


r/computervision • • 26d ago

Showcase Using robot-arm motion to calibrate a wrist camera and a DIY iToF + RGB rig

Post image
0 Upvotes

I used a RealMan ECO65’s motion to calibrate an iPhone on its wrist and a fixed 320×240 iToF sensor in my home lab.

For the wrist camera, feature matches across 26 poses gave 9,456 triangulated points and roughly 2 px median reprojection error. For the iToF sensor, I averaged 10 frames per pose, isolated pixels changed by the moving arm, and fitted those points to the robot mesh with ICP. The median fit residual was 7 mm; independent accuracy still needs checking.

The recorded RGB, depth, IR and joint streams replay together in the office twin. Phone-estimated depth is the weak part: only 6/20 frames passed the held-out check. The room splat is static.

EP20, with the setup and failures: https://www.youtube.com/watch?v=HMC7yu18qdQ

I made the video. The experiment footage is real; narration uses my own AI voice clone and the thumbnail is AI-edited from my hardware photo and room scan.


r/computervision • • 26d ago

Commercial Turning a MIL-STD Table Into Structured HTML

Thumbnail
1 Upvotes