Skip to content

Stream mapping enhanced#56

Draft
ein-shved wants to merge 4 commits intoYeautyYE:mainfrom
ein-shved:stream_mapping_pr
Draft

Stream mapping enhanced#56
ein-shved wants to merge 4 commits intoYeautyYE:mainfrom
ein-shved:stream_mapping_pr

Conversation

@ein-shved
Copy link
Contributor

Started to work on #53. After some work, found out that you made some changes on the Issue in different way. It have many conflicts with my work and actually does not implement the features I am need an have no enough knowledge about field you are working on. So I'will complete features I'am needed in fork and left the draft PR here - may be you will find something useful.

Now allow to specify per-stream output parameters via StreamMap
Now the linklable parser supports up to 3 components in view
`input_index:media_type:stream_index`. Each component is optional for
parser (but is not optional for context) and could follow in any order.
First number stands for input_index, second - for stream_index.
@ein-shved
Copy link
Contributor Author

ein-shved commented Dec 1, 2025

@YeautyYE sorry, but I am giving up on this =( I've spent a week of evenings to understand why pipelines stuck in dead lock. I've decided to switch to calling cli from my project's code.

Did not you think about some kind of major refactoring? To decrease size of unsafe code, decrease amount of same almost copy-pasted loop blocks, split functional and service code (e.g. separately implement the pipeline framework and implement the demuxer, decoder, muxer, etc as its Node traits)? And, of course documents the guts.

This project is very good, but it suffers from design issues and it is very hard to learn how it works.

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.

1 participant