Expose selected decoder plugin and backend per decoded sample

Aberta
  • Algo errado?
#64 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
38/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
cpp, python
Domínio
backend-api-design

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Jupyter Notebook
Estrelas
164
Forks
26
Merge médio
27min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de NVIDIA/nvImageCodec

Todas as issues de NVIDIA/nvImageCodec

Issues semelhantes

Mais issues de Backend & API Design

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.