Skip to content
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

xeve_app returns 205 exit code on encoding successful #137

Closed
olokelo opened this issue Aug 6, 2024 · 1 comment · Fixed by #140
Closed

xeve_app returns 205 exit code on encoding successful #137

olokelo opened this issue Aug 6, 2024 · 1 comment · Fixed by #140

Comments

@olokelo
Copy link
Contributor

olokelo commented Aug 6, 2024

Hello,

When xeve_app finishes encoding it exits with status 205 which means XEVE_OK_NO_MORE_FRM. Is it expected behavior?
I know that encoding was OK but shouldn't the app exit with code 0 on success? That would conform with the Unix Standard.

$ xeve_app -i dnd.y4m -q 38 --keyint 128 --profile main --preset fast --threads 8 -o dnd.xeve-evc_main_fast_g128_q38.evc
XEVE: eXtra-fast Essential Video Encoder
=== Summary ====================================================================
Bitrate                           = 268.7698 kbps
Encoded frame count               = 276
Total encoding time               = 367019.000 msec, 367.019 sec
Average encoding time for a frame = 1329.779 msec
Average encoding speed            = 0.752 frames/sec
================================================================================
[oloke@pc tmp]$ echo $?
205
@dariusz-f dariusz-f linked a pull request Aug 12, 2024 that will close this issue
@kpchoi
Copy link
Collaborator

kpchoi commented Aug 15, 2024

@dariusz-f
I guess that xeve_app should not return xeve libraries' return value.
XEVE_OK_NO_MORE_FRM is libxeve return value and it means that encoding was ok.
in that case, xeve_app should return 0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants