Refactore media properties #127
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
November 12, 2014 14:10
* Remove:
* file mediaProperty (hpp/cpp)
* files <type>StreamProperties (hpp)
* Add:
* file <type>Properties (hpp/cpp)
* util (hpp/cpp)
* Rename:
* file printMediaProperty.hpp to print.hpp
* struct Properties to class FileProperties
d3a03c6 to
aa8de0e
Compare
|
Complex to review ... |
|
New PR #130 |
cchampet
pushed a commit
to cchampet/avTranscoder
that referenced
this pull request
Mar 17, 2015
Fix build compatibility with libav
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Instead of making copies of all data, converting them our types (char* to string, etc...) and making our transformations (the 'sampleFormatLongName' for example), here we store pointers to FFmpeg objects (AVCodecContext, AVFormatContext, etc...) and have getters around these objects, which access and transform the data the way we want.
Note: some data are not perfectly handled by the FFmpeg library. We fix it by creating copies for them in the corresponding class.
Next step: store metadata in a schema like EBU-Core which can contains technical and editorial metadatas.