Expose selected decoder plugin and backend per decoded sample

Aperta
  • Qualcosa non va?
#64 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
38/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp, python
Ambito
backend-api-design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Jupyter Notebook
Stelle
164
Fork
26
Merge medio
27m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di NVIDIA/nvImageCodec

Tutte le issue di NVIDIA/nvImageCodec

Issue simili

Altre issue su Backend & API Design

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.