Expose selected decoder plugin and backend per decoded sample
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 38/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
调研方向
Start by reading the generic decoder API around nvimgcodecDecoderDecode, nvimgcodecFutureGetProcessingStatus, and nvimgcodecExecutionParams_t, then compare the Python get_decoder_ids() API and the cuCIM workaround described in the issue. Define how per-sample plugin and backend provenance, fallback information, and results after completion should fit the C and Python APIs. Done means callers can query those details for successful and failed samples while preserving generic per-sample dispatch.
由索引模型根据 Issue 内容生成。
描述
Request
Please expose the decoder plugin identifier and backend kind that actually handled each sample submitted through the generic decoder API.
Motivation
Applications that audit heterogeneous decode pipelines need to distinguish GPU-only, hybrid CPU/GPU, and CPU fallback execution without inferring it from the codec, output buffer, or installed extensions. The generic decoder can fall through registered implementations in priority order, and a batch can contain per-sample choices.
Current API boundary
With nvImageCodec 0.9, nvimgcodecDecoderDecode plus nvimgcodecFutureGetProcessingStatus reports only processing status. nvimgcodecExecutionParams_t::backends can constrain backend kinds, but the selected nvimgcodecDecoderDesc_t::id and backend_kind are not returned.
Current documentation also provides plugin enumeration/selection (get_decoder_ids() in Python and plugin selections/framework queries in the newer C API), which is useful for configuration but still does not identify the implementation selected after generic fallback.
Suggested shape
A future/result query returning, for each submitted sample:
- selected decoder plugin ID;
- selected backend kind;
- whether fallback occurred (and optionally rejected candidates/statuses).
The query should remain valid after the decode completes and should work for both success and failure. An equivalent Python result/property would be useful.
Workaround and limitation
cuCIM can create separate generic decoders restricted to one backend kind and probe/decode in an explicit order. That provides truthful backend provenance but changes selection to a caller policy, cannot identify the plugin within that backend, and cannot preserve arbitrary per-sample mixed-backend dispatch in a single batch.
- 主要语言
- Jupyter Notebook
- 星标
- 164
- 派生
- 26
- 平均合并
- 27 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
NVIDIA/nvImageCodec 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 79/100
NVIDIA/nvImageCodec#65 · 1 条评论 ·
-
难度 3/5 1-2 天 新手友好度 72/100
NVIDIA/nvImageCodec#66 · 1 条评论 ·
-
nvjpeg2k error 3 (Bad jpeg) on valid JPEG 2000 aerial photos that OpenJPEG and ffmpeg decode identically可能已有人在做 @mkepa-nv 于 5 天前认领。 未关闭bug
NVIDIA/nvImageCodec#63 · 2 条评论 · 已指派 1 人 ·
-
难度 5/5 一周以上 新手友好度 8/100
NVIDIA/nvImageCodec#60 ·
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
NVIDIA/nvImageCodec#59 ·
查看 NVIDIA/nvImageCodec 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 77/100
tauri-apps/plugins-workspace#3780 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
AAswordman/Operit#1490 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 80/100
open-telemetry/opentelemetry-zig#179 ·
维护者通常 1 天内回复
-
area:cards enhancement hand-tail ready-for-agent
难度 2/5 1-3 小时 新手友好度 70/100
fil-donadoni/tolaria#9275 ·
维护者通常 1 天内回复
-
area/build area/events area/storage area/storage/kafkasql area/storage/sql
难度 2/5 1-3 小时 新手友好度 78/100
Apicurio/apicurio-registry#11079 ·
维护者通常 1 天内回复