# Qualcomm IM SDK release 2.0 RC2
## Release information
Table : Supported platforms and reference kits
| SoC platforms | Reference kits |
| --- | --- |
| QCS6490 |
Qualcomm DragonwingTM RB3 Gen 2 Vision Development Kit
Qualcomm DragonwingTM RB3 Gen 2 Core Development Kit
Qualcomm DragonwingTM RB3 Gen 2 Industrial Kit
|
| QCS5430 | |
| Qualcomm Dragonwing^TM^ IQ-9075 | |
| Qualcomm Dragonwing^TM^ IQ-8275 | Qualcomm Dragonwing^TM^ IQ-8275 Beta Evaluation Kit (EVK) |
## Contents of the release
The contents of the Qualcomm IM SDK release include:
- Recipes for building the individual components:
- Qualcomm^®^ Intelligent Multimedia SDK (IM SDK)
- Lite Runtime (LiteRT)
- Qualcomm^®^ Neural Processing SDK
- Qualcomm^®^ AI Engine direct SDK
To get started with the Qualcomm IM SDK, see [Qualcomm Intelligent Multimedia (IM SDK) Quick Start Guide](https://docs.qualcomm.com/doc/80-80021-51).
## Limitations
The following are the known limitations in the Qualcomm IM SDK release:
- Parallel decode or encode sessions aren’t supported.
- In config1, LiteRT IM SDK frameworks don’t support the GPU delegate.
- Frame drops are observed in daisychain detection‑pose usecases when the pose detection load (people per frame × model inference time) exceeds the per‑frame time limit (33 ms for 30 fps).
- Reverse playback is limited to video streams with a GOP length that fits within the buffer limitations of the video driver (<= 26).
- For Dragonwing IQ-9075 and Dragonwing IQ-8275:
>
>
> - Random corruption is observed at the beginning of playback for low-resolution (480p) NV12 UBWC-compressed streams.
> - Stability issues are observed when running multibatch ML use cases.
- The `waylandsink` plugin doesn’t support displaying windows at custom screen coordinates.
- When using the `qtimlpostprocess` plugin for postprocessing, a display latency occurs after approximately 30 minutes of running ML use cases on a camera stream.
- Use cases with files having dynamic resolution change (DRC) may fail. This issue occurs because the video driver allocates buffers that are only partially accessible to the GPU driver.
- `qtiobjtracker` exhibits non‑linear execution‑time growth during extended runs, which can act as a performance bottleneck.
- Classification Daisychain pipeline use cases aren’t supported.
- The Qualcomm IM SDK in a docker container isn’t supported in this release.
- The audio record pipeline runs, but no audio is present in the captured file.
- Video encode doesn’t work for resolutions lower than 4K with the UBWC (NV12\_Q08C) format.
- Pipelines that use GPU-based plugins followed by the encoder freeze.
- The encoder supports only framerates from 10/1 to 120/1 in the order of 10/1. Odd framerates from containers, such as 30000/1001, aren’t supported.
- For some models, certain operations aren’t supported in the QNN HTP backend. When a CPU fallback is available, the model executes but with degraded performance. If no fallback exists, model execution fails.
- Smart encode with a camera source isn’t supported because, in camera multistream, at least one stream must be in NV12\_Q08C format, and there is a known issue with the encoder for this format.
- A known issue exists in `qtivcomposer` related to GAP buffer handling. This affects use cases where `qtivsplit` is used (for example, daisy-chain ML), as `qtivsplit` can generate GAP buffers.
- Across the SNPE, QNN, and LiteRT frameworks, Super Resolution models produce blurred output.
- Across the SNPE, QNN, and LiteRT frameworks, segmentation models don’t function correctly.
- In the LiteRT framework, multistream use cases aren’t supported.
- In the LiteRT framework, quantized models run at low FPS.
- In Config3 and Config4, the camera service fails to start after CAMX overlay installation. For more information about overlay configurations, see [Use overlay configurations to derive image recipes](https://docs.qualcomm.com/doc/80-80021-150/topic/overlay_configurations.html).
- The `gst-pipeline-app` utility isn’t available.
- In Config2, sHDRv2 and sHDRv3 camera streams aren’t supported.
- On Dragonwing IQ-615, the encoder plugin supports only resolutions that are multiples of 16.
Note
The following plugins are deprecated. Use the corresponding replacement plugins.
| Deprecated plugins | Replacement plugins |
| --- | --- |
| `qtioverlay` | `qtivoverlay` |
|
qtimlvdetection
qtimlvclassification
qtimlvsegmentation
qtimlpose
| `qtimlpostprocess` |
## Related documents
- [Qualcomm Intelligent Multimedia SDK (IM SDK) Reference](https://docs.qualcomm.com/doc/80-80021-50/topic/qimsdk_landing_page.html)
- [Qualcomm Intelligent Multimedia (IM SDK) Quick Start Guide](https://docs.qualcomm.com/doc/80-80021-51/topic/qmi-sdk-qsg-landing-page.html)
- [Qualcomm Dragonwing RB3 Gen 2 Development Kit Guide](https://docs.qualcomm.com/doc/80-80021-251/topic/landing-page.html)
- [Qualcomm Dragonwing IQ-9075 Evaluation Kit user guide – Linux](https://docs.qualcomm.com/doc/80-80021-261/topic/iq9-ug-landing-page.html)
- [Qualcomm Linux Build Guide](https://docs.qualcomm.com/doc/80-80021-254/topic/build_landing_page.html)
- [Qualcomm Linux Migration Guide](https://docs.qualcomm.com/doc/80-80021-150/topic/landing-page.html)
Last Published: Mar 25, 2026
[Next Topic
Qualcomm IM SDK release 2.0 RC1](https://docs.qualcomm.com/bundle/publicresource/80-80021-52/topics/qim-sdk-release-2-0.md)