Skip to content

Conversation

@PrathamTI
Copy link
Contributor

The flowchart in section 6.2.2 incorrectly showed a single tiovxmultiscaler in the GStreamer pipeline, which did not match the actual pipeline code.

Since tiovxmultiscaler cannot scale beyond 1/4 resolution, multiple multiscaler blocks are required in the pipeline. Updated the flowchart to indicate "tiovxmultiscaler x2" to accurately reflect that two MSC blocks are used in the implementation.

This fixes the discrepancy between the documentation flowchart and the actual code implementation.

Fix: SITSW-6487
Reference: https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/edgeai-docs/common/edgeai_dataflows.html#id2

Copy link
Member

@cshilwant cshilwant left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The CI is flagging the commit message format. Can you update it to match the project's commit convention?

It doesn't match regex: ^(build|chore|ci|docs|feat|fix|refactor|style){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)|(Merge).*|(fixup!.*)
The commit message should follow Conventional Commits. See https://www.conventionalcommits.org/
Suggest: Use <type>(<scope>): <description> with allowed types

https://github.com/TexasInstruments/processor-sdk-doc/actions/runs/20775866269/job/59661383464?pr=615

The flowchart in section 6.2.2 incorrectly showed a single tiovxmultiscaler
in the GStreamer pipeline, which did not match the actual pipeline code.

Since tiovxmultiscaler cannot scale beyond 1/4 resolution, multiple
multiscaler blocks are required in the pipeline. Updated the flowchart
to indicate "tiovxmultiscaler x2" to accurately reflect that two MSC
blocks are used in the implementation.

This fixes the discrepancy between the documentation flowchart and the
actual code implementation.

Fix: SITSW-6487
Reference: https://software-dl.ti.com/processor-sdk-linux/esd/AM62AX/10_01_00/exports/edgeai-docs/common/edgeai_dataflows.html#id2

Signed-off-by: Pratham Deshmukh <[email protected]>
@PrathamTI
Copy link
Contributor Author

The CI is flagging the commit message format. Can you update it to match the project's commit convention?

It doesn't match regex: ^(build|chore|ci|docs|feat|fix|refactor|style){1}(\([\w\-\.]+\))?(!)?: ([\w ])+([\s\S]*)|(Merge).*|(fixup!.*)
The commit message should follow Conventional Commits. See https://www.conventionalcommits.org/
Suggest: Use <type>(<scope>): <description> with allowed types

https://github.com/TexasInstruments/processor-sdk-doc/actions/runs/20775866269/job/59661383464?pr=615

Resolved.

@cshilwant cshilwant merged commit f6d7bbb into TexasInstruments:master Jan 8, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants