bytedeco/javacv

The recorder should be designed with multiple ways to handle frames

Open

#2,241 opened on Jun 13, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)Java (1,583 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (6,985 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

hi,The javacv framework should be a kind of wrapper for OpenCV.And off-heap memory should be used to the maximum image But in the diagram above, in order to adapt to the outputstream. JVM memory is used, which can put pressure on the JVM if the data stream is large

Contributor guide

Research direction
Examine the current recorder implementation in javacv to understand how frames are converted to JVM memory. Investigate options for using off heap memory (e.g., DirectBuffer) to reduce pressure on the JVM heap. Consider designing multiple frame handling strategies that can be selected based on the output sink.
Tech stack
java
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Java
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40