-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
implemented VideoSequenceParser inspired by SDK_Segment_Utils.VideoSequencerParser from original SDK #67
base: master
Are you sure you want to change the base?
Conversation
…allbacks chore: added Cargo.lock to .gitignore
…allbacks chore: added Cargo.lock to .gitignore
…s.h form original SDK
@@ -1,3 +1,4 @@ | |||
#![allow(clippy::all)] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What does this silence? Instead of this, can we fix the clippy lints, or at least silence only specific ones?
log::debug!( | ||
"Clip Operator: {:?} {:?} {:?}", | ||
operator_node_type, | ||
operator_node_hash, | ||
operator_node_flags | ||
); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of all these log::debug!
calls, I think the parse_clip_operators
should return a structute which has all these fields you print here, but the struct impls the Debug
trait,. The end-user should just dbg!(parse_clip_operators(...)
if they desire, or use the values in other way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or return a tuple of the current Ok
and namely struct
, i.e. Result<(ClipOperatorsMap, ParseClipOperatorStatus), Error>
To simplify the manipulation of VideoSegment in Premiere Pro. Adobe provide the util class, VideoSegmentParser.
This pull request is a WIP re-implementation of this utility in a more agnostic way to let the users freely do what they want with the parsed datas.