On Sun, Jun 28, 2015 at 06:55:45PM +0200, wm4 wrote:
[...]
> > Ludmila is working on new tests that involve seeking to more than one
> > place based on wm4's request - from what I understand (not doing any
> > seeking myself) is that ffmpeg.c only seeks once ever. As an API user
> > it's useful to
On Sun, Jun 28, 2015 at 01:50:25AM +0300, Ludmila Glinskih wrote:
> Location of api-h264-test changed to special directory for api tests.
> ---
> libavformat/Makefile| 1 -
> libavformat/api-h264-test.c | 183
>
> tests/api/Makefile
On Sun, 28 Jun 2015 17:46:48 +0100
Kieran Kunhya wrote:
> > So I have a more conceptual question, maybe Kieran can help answer this
> > also. Why are these tests called api-$codec tests? I don't see anything
> > flac/h264 specific in these tests so far, and they could basically be
> > reused for
> So I have a more conceptual question, maybe Kieran can help answer this
> also. Why are these tests called api-$codec tests? I don't see anything
> flac/h264 specific in these tests so far, and they could basically be
> reused for any video (h264) or audio (flac) test (for audio: as long as
> the
On Sat, Jun 27, 2015 at 6:50 PM, Ludmila Glinskih
wrote:
> Location of api-h264-test changed to special directory for api tests.
> ---
> libavformat/Makefile| 1 -
> libavformat/api-h264-test.c | 183
>
> tests/api/Makefile | 1 +
Location of api-h264-test changed to special directory for api tests.
---
libavformat/Makefile| 1 -
libavformat/api-h264-test.c | 183
tests/api/Makefile | 1 +
tests/api/api-h264-test.c | 183
