microsoft / microsoft/Windows-classic-samples
Enable DX11VideoRenderer in topoedit
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 5.7k
- Forks
- 3.3k
- PR merge metrics
- No merged PRs in 30d
Description
In the DX11VideoRenderer sample, README.md, section Run the sample, states that the registration of DX11VideoRenderer.dll adds the Topology menu line "Add DX11 Video Renderer" of the topoedit application or enables this line to add the DX11VideoRenderer sink to the topology. First, the DX11 Video Renderer appears not as an individual menu line, but as an option in the Other transforms category of the Add transform dialog. But DX11VideoRenderer is not a transform, and the node cannot be added in this way. Even if it could be able to add, the topology would not resolve.
I added the necessary code to the topoedit to enable the promised functionality and published an updated topoedit to the https://github.com/vasilich-tregub/topoedit-with-DX11VideoRenderer repository.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the DX11VideoRenderer sample's README.md, especially the “Run the sample” section, and inspect how topoedit is expected to register the renderer. Compare the reported implementation in the linked topoedit-with-DX11VideoRenderer repository, then verify that the renderer has its own appropriate UI entry and that the resulting topology resolves successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100