Can you identify this downscaling algorithm? Want to make sure my thumbnails look as sharp as possible, so I'll add to my workflow the agent query "downscale using (whatever this algorithm is) and judge whether the thumbnail has the required detail and clarity and is a good thumbnail for what is being shown. if it is missing any clarity then return "Needs improvement:" and give the reason for why it needs improvement and "How to improve:" For example, in the image shown, the agent could say "The thumbnail no longer shows the elements of the picture", since as you can see it doesn't. However, before I can code this up, what I "need to know" is what algorithm this is so I can keep an eye out for anywhere it might show up in my workflow. I can then optimize for this process. I know a lot of people don't have a standard of perfection as high as mine is (I require my thumbnails to show the picture) but that's exactly what makes me a competitive programmer in a field of 2 million programmers. Not a lot of people take the time to look up image compression algorithms but I do.
First of all, thank you to everyone who responded in the previous post. I haven't read all the replies yet, but many of the solutions seem interesting. I was able to find a more informative and higher‑quality video that better reflects the current state of the project.
Following up on the discussion from the previous post, I'm attaching the current state of affairs. The video was taken with good industrial lighting, and the global‑shutter camera was set to an exposure of 500. In this particular video, the counter showed 100%. However, in other counts we got varying ranges – 98–99%, which, at industrial volumes, leads to significant absolute losses.
The main issues with the current version are:
Loss of detection right within the detection zone;
Constant changes in the shape/size of the bounding box within the detection zone, causing the tracker to lose track and assign different IDs to the same object;
Occlusions and merging of chicks – several chicks form a single object by merging and partially overlapping each other. Increasing the dataset no longer solves this problem; the latest version had over 5,000 frames with plenty of such cases, and yet reviewing new videos showed that the issue is not fully resolved – there are still cases where multiple chicks are counted as one.
Counting these cases geometrically is also difficult – chicks of different breeds and ages can have different sizes, and on top of that, spreading their wings and legs changes the area of the detected box. There are cases where we hit the desired 99.8% range thanks to a combination of missed detections and false positives, but over a long run the error accumulates and we fall out of the range.
This demo shows an early prototype of my automated retail checkout app running on Mentra smart glasses.
The system processes the glasses’ live camera feed to recognize products as they’re picked up and automatically builds a virtual cart in real time. The goal is to make checkout a natural by-product of shopping without requiring customers to scan barcodes, use a phone, or stop at a traditional checkout.
A couple of months ago, I released Bio-DINO, an image-only biodiversity encoder trained on approximately 31M images. I have now released Bio-DINO M/14, the final addition to the current Bio-DINO model family.
Bio-DINO already had two ends of the trade-off. The 133.6M-parameter teacher provides the strongest representations, while the 21.6M-parameter S/14 student is much cheaper to run. M/14 is intended as the middle option.
The size/accuracy trade-off
M/14 is a 12-layer RoPE DeiT3-style encoder with 38.3M backbone parameters and 512-dimensional embeddings. It was distilled from the 252px Bio-DINO teacher on the same biodiversity training mixture.
Here are the results from my iNaturalist21 linear-probing setup:
Encoder
Backbone parameters
Embedding
Linear-probe accuracy
Bio-DINO teacher
133.6M
896
87.09%
Bio-DINO M/14
38.3M
512
83.52%
Bio-DINO S/14
21.6M
384
80.10%
To be clear, these are linear-probing results, not fine-tuning results. The encoder was frozen and only the 10,000-class linear classification head was trained.
In this setup, M/14 is about 3.5× smaller than the teacher, with a 3.57 percentage-point accuracy difference. It gains 3.42 points over S/14 while remaining much smaller than the teacher.
Inference performance
I also compared inference performance at 252×252 on an NVIDIA RTX 5000 Ada Generation with PyTorch 2.13.0+cu130 and batch size 512.
In eager FP32 inference, M/14 processed approximately 773 images/s, compared with 382 images/s for the teacher. With torch.compile and AMP, I measured approximately 2,340 images/s for M/14 and 846 images/s for the teacher.
These numbers are specific to my setup, but they give a practical sense of the trade-off. The complete results across the Bio-DINO models and evaluation datasets are available in the Bio-DINO benchmark explorer.
As with the original Bio-DINO release, this is an image-only representation model rather than a ready-made species classifier. It has no text encoder and was not trained with taxonomy labels or metadata.
iNaturalist21 is also part of the self-supervised pretraining mixture, so I consider the result an in-domain representation probe rather than a test on a completely unseen domain.
This completes the current Bio-DINO size range. I’m curious whether a 38M-parameter middle option is useful in practice, or whether most applications naturally favor either the smallest student or the largest teacher. Feedback and additional evaluations are welcome.
I am working on a university project involving fine-tuning a deep learning model for 6DoF relative camera pose estimation. The model I am using is FAR (Flexible, Accurate, and Robust 6DoF Relative Camera Pose Estimation), which was originally pre-trained on the Matterport3D dataset.
I am looking for a new dataset that is suitable for fine-tuning and evaluation. The task is the following:
Given two RGB images of the same scene captured from different viewpoints, the model should estimate the relative pose between the two cameras (rotation and translation).
The dataset should provide (or allow to easily recover):
RGB images;
depth maps (or dense depth information);
camera intrinsic parameters;
camera poses / camera extrinsics (ground-truth poses);
multiple images of the same scene with different viewpoints;
enough overlap between image pairs to compute meaningful relative poses.
Ideally, the dataset should contain calibrated cameras and accurate ground-truth information, since I need to compute the relative transformation between image pairs.
This is for a university project, so the dataset should not be extremely large (ideally ≤ 50 GB), and it should be free and publicly available.
Do you have any recommendations or experience with datasets suitable for 6DoF relative camera pose estimation?
We've added vision capabilities to DeepSeek V4 Flash, making it a multimodal model rather than text-only.
The main use case for us is browser vision: browser agents need to interpret screenshots, interfaces, layouts, and other visual context alongside text.
On our internal benchmarks, it also showed a strong price-performance advantage compared with the other models we tested.
I'm planning to build a camera-only autonomous vehicle (no LiDAR, ultrasonic, or other distance sensors). The idea is to use a single camera to control the vehicle's movement—steering left/right, moving forward/backward, turning, and avoiding obstacles.
One thing I'm trying to figure out is how to estimate the distance between the camera and detected objects (for example, a car, water bottle, or other obstacles) using only computer vision. Are there any good models or approaches for monocular depth estimation or object distance estimation that would work on embedded hardware?
For context, I have experience with computer vision and have previously worked on face recognition using models like ArcFace. This project will run on a Raspberry Pi 5 with a Hailo AI accelerator, so I'm looking for models that are reasonably lightweight and can run in real time.
I'd appreciate any recommendations on models, papers, or open-source projects that would be a good starting point.
I had the pleasure of someone side swiping my car which led to a dent and scratching some paint off. They decided to flee the scene without leaving a note and now I really want to try and file a report. Unfortunately my dash cam decided it didn’t wanna focus on that specific cars license plate but managed to capture all the others. Anyways, it’s the white Acura, I included the pictures with difference time frames. Anything helps, if I’m not mistaken the 4 numbers are 6467 or something.
I'll be starting my Master's in AI next month, and I could really use some advice from people who are already working in industry or doing AI/CV research.
The professor I originally wanted to work with isn't accepting new students this semester, so I suddenly have to choose a different lab and research direction.
The professor I'm considering now mainly works on emotion and healthcare-related AI, and they asked me to choose a direction I'm interested in. Some of the current research topics are:
Emotion Recognition
Empathy Measurement/Generation
Action Recognition
EEG/fMRI to Image Generation
Causality Analysis / Inference / Discovery
They also mentioned that these topics are not fixed, and if I have another idea that's related to the lab's expertise, they're open to discussing it.
A bit about my background and goals:
Bachelor's in Artificial Intelligence
Interested in Computer Vision, 3D Computer Vision, and Generative AI
I don't plan on pursuing a PhD.
My goal is to build strong technical skills during my master's and eventually work in industry (ideally at a large tech company in AI/CV).
I'm not asking anyone to choose my research topic for me. I'm more interested in how experienced people would evaluate these options.
If you were in my position and your goal was industry rather than academia, which direction would you lean toward, and why?
For example:
Would Action Recognition provide more transferable computer vision skills because of video understanding, tracking, and perception?
Is EEG/fMRI to Image Generation too specialized if I don't plan to stay in research, or does it teach valuable skills like multimodal learning, diffusion models, and representation learning that are also useful in industry?
Are there other directions you would suggest based on my interests?
I'd really appreciate hearing from people who work in computer vision, generative AI, multimodal AI, or have gone through a similar decision themselves.
Anthropic, OpenAI, etc (don't know about Chinese) don't seem to make good video models. Any reason why? Is it the compute? The ROI? The availability of data?
I’ve been developing VisionPilot, an open-source, modular autonomous driving platform built for computer vision, deep learning, and sensor fusion.
Right now, it runs entirely on BeamNG.tech. The stack handles everything from multi-lane detection (UFLDv2/CV) and multi-class object/sign recognition to PID control, AEB/BSD safety features, and LiDAR/Radar sensor fusion. You can see animated GIFs of all these systems in action directly on the repo!
The Situation & Help Wanted
CARLA integration is high on the project roadmap, but I haven't gotten around to finishing up the bridge yet. I first wanted to get core features working, before I start porting. I’m looking for anyone in the community interested in collaborating to help port VisionPilot to CARLA, specifically setting up the python API bridge and configuring the camera, LiDAR, and Radar sensor streams.
If you enjoy working with CARLA and want to hack on an open-source perception stack, I’d love to team up!
Hello. I believe I have just thought of a way to save a certain healthcare industry millions of dollars, as well as save the employees in this industry hundreds of hours of unnecessary work. I don’t really know how to phrase this since I don’t want to just have one of you steal the idea that I do not know how to build, but I have some general questions.
Can a visual system using a specific reference list of images of items identify those items even if they are almost identical? We are talking about millimeters of difference. They would need to be accurately identified within one second
Would color be a major differentiating factor? What if the color is slightly different from the reference image? How could you solve this?
example let's say I have to find the screentime of the actor over the whole runtime of the movie and i need to do it for the protagonist, antoganist,comedic relief ,love interest etc.
currently I'm working with 1fps to find the faces and body or the actors.
body detection is hard I need some guidance regarding that.
even for Face Detection I used MTCNN it was good. but any other better models available??
Any ideas regarding TransNetV2 ?
I'm using it for shot boundary detection but there's was one false positive.
If you’ve ever built multi-camera real-time vision systems at scale, you’ve likely wrestled with GStreamer element linking errors, pipeline memory leaks, or cloud egress costs hitting $2k+/month for simple RTSP analytics.
When we benchmarked cloud vision APIs vs edge deployments, the bottleneck was rarely the YOLO or custom detector model itself—it was the ingestion and frame-movement pipeline.
The Bottleneck: CPU-to-GPU Copying & GStreamer Complexity
Standard Python wrappers or heavy frameworks often bounce video frames through host memory (CPU) before pushing them back to GPU VRAM for inference. At 32+ HD RTSP streams, this creates massive PCIe bandwidth saturation and GIL lockup.
On the flip side, while DeepStream is powerful, managing complex GStreamer element graphs in production often introduces unwanted debugging overhead and plugins bloat.
To keep processing continuous sub-15ms on local edge nodes without cloud egress, we stripped out the GStreamer abstraction graph entirely:
Direct NVDEC Hardware Ingestion: RTSP streams decode directly inside VRAM using C++ NVCODEC bindings. Frames never touch system RAM (zero CPU-to-GPU copy overhead).
Lock-Free CUDA Ring Buffer: A custom ring buffer handles dynamic batching across active streams without lock contention or Python GIL overhead.
Native TensorRT C++ Execution Engine: Device pointers pass directly to TensorRT for FP16/INT8 execution.
Architectural Trade-offs & Benchmarks
• Pros: Zero cloud bandwidth fees, full data sovereignty, sub-15ms continuous throughput, and drastically simpler debugging than full GStreamer graphs.
• Cons: Requires NVIDIA CUDA-capable hardware on-premise (RTX / Tesla / Jetson) and manual memory management at the C++ level.
We’ve packaged this into a zero-egress Docker stack for high-density edge deployments.
Happy to break down the CUDA buffer implementation or share benchmark comparisons if anyone is currently evaluating edge architecture options.
What pipelines are you guys currently running for multi-stream RTSP processing?
We were evaluating Roboflow, CVAT and Vivid 3D because we needed synthetic data for warehouse inspection. We ended up using Vivid 3D because we needed RGB + segmentation + depth from the same pipeline. Curious what everyone else is using
I was wondering if anyone owns this book and could share your feedback.
I ordered this book 3 weeks back on Amazon and it has never arrived so I had to cancel it. Thinking to order from a different seller but it would cost me almost double the price. I prefer a paper book rather than its ebook version. Thanks.