Closed ablwr closed 9 years ago
I might want to re-tool these test files to add a little bit more diversity among software platforms (eg, they were all made with the same application)
On Tue, Feb 17, 2015 at 10:16 PM, Ashley notifications@github.com wrote:
Basic descriptions: 3c893f9 https://github.com/MediaArea/PreFormaMediaInfo/commit/3c893f99827864b3ac84148666721ea5e3adeeee and d8909c9 https://github.com/MediaArea/PreFormaMediaInfo/commit/d8909c9a2475a148dfa15e904b7dbc45a4acfe9f
— Reply to this email directly or view it on GitHub https://github.com/MediaArea/PreFormaMediaInfo/issues/45#issuecomment-74804220 .
I think there may have been a desire to collect files "from the community" too.
How do we want to collect files and attribute them in the repo? Is this something that's low priority prior to wrapping out this phase?
On Tue, Feb 17, 2015 at 10:22 PM, Ashley notifications@github.com wrote:
I think there may have been a desire to collect files "from the community" too.
— Reply to this email directly or view it on GitHub https://github.com/MediaArea/PreFormaMediaInfo/issues/45#issuecomment-74804816 .
Yeah I think it's low priority.
"No MKV files yet"
Isn't e.g. ffmpeg -f lavfi -i testsrc -t 1 -c:v ffv1 -level 1 -t 1 ffv1_1.mkv enough?
Maybe... But I feel like these files are testing the ffv1-ness and potential conformance fails there, and test mkv files will test potential expected problems specific to Matroska.
Sent from my iPhone
On Feb 18, 2015, at 2:31 AM, Jérôme Martinez notifications@github.com wrote:
"No MKV files yet"
Isn't e.g. ffmpeg -f lavfi -i testsrc -t 1 -c:v ffv1 -level 1 -t 1 ffv1_1.mkv enough?
— Reply to this email directly or view it on GitHub.
Development of test files and documentation are ongoing so I will close these as "issues."
Should we add documentation on what the anticipated output for each of the test files are?
Related: No MKV test files yet!