Sometimes it happens, that encoding a video stream containing raw frames in YUV420p format using reference xeveb_app application (xeve_internal) produces EVC stream that causes problems with decoding.
It seem that the problem occurs only for certain values of encoding parameters, namely for some specific values of bframes (maximum number of type B frames) as well as for keyint (frequency of type I frames).
In these cases playing EVC stream causes SEGMENTATION FAULT.
Please see below test results:
| bframe |
keyinyt |
RESULT |
| 0 |
240 |
SEGMENTATION FAULT while decoding |
| 15 |
240 |
SEGMENTATION FAULT while decoding |
| 15 |
0 |
OK |
| 0 |
0 |
SEGMENTATION FAULT while decoding |
| 1 |
0 |
[xeve_app.c:919] cannot put reconstructed image to list |
| 3 |
0 |
[xeve_app.c:919] cannot put reconstructed image to list |
| 7 |
0 |
[xeve_app.c:919] cannot put reconstructed image to list |
As it comes to bframes, it is pretty clear case situation since allowable values are: 1,3,7,15 but what about keyint. Must it be always 0?
Sometimes it happens, that encoding a video stream containing raw frames in YUV420p format using reference xeveb_app application (xeve_internal) produces EVC stream that causes problems with decoding.
It seem that the problem occurs only for certain values of encoding parameters, namely for some specific values of bframes (maximum number of type B frames) as well as for keyint (frequency of type I frames).
In these cases playing EVC stream causes SEGMENTATION FAULT.
Please see below test results:
As it comes to bframes, it is pretty clear case situation since allowable values are: 1,3,7,15 but what about keyint. Must it be always 0?