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

Logfile as option like --logfile #380

Open
alphavto opened this issue Sep 14, 2022 · 4 comments
Open

Logfile as option like --logfile #380

alphavto opened this issue Sep 14, 2022 · 4 comments

Comments

@alphavto
Copy link

I would like an option like --logfile to put an sidecarfile with input like "Reversability was checked, no issue detected."
Same what --framemd5 make to create a framemd5-file.
Actually is only possible to make it manually set the logfile output with >/Volume/Path/example.log after the rawcooked string.

For example, my string is now:
Rawcooked -framerate 18 -c:a copy -slices 24 -slicecrc 1 -g 1 -coder 1 -context 1 --framemd5-an --check

And i would like this:
Rawcooked -framerate 18 -c:a copy -slices 24 -slicecrc 1 -g 1 -coder 1 -context 1 --framemd5-an --check --logfile

In the logfile is a good result like "Reversability was checked, no issue detected." or a "Warning text".

@JeromeMartinez
Copy link
Member

In the logfile is a good result like "Reversability was checked, no issue detected." or a "Warning text".

We have similar option in other tools e.g. MediaInfo, but it just puts the console output in a text file, without need of pipe (useful for some workflow IIUC), so with all the output, is it fine for you?

Note: be careful about text, it may change in the future, use the command exit code when possible (0 = success, else error).

@alphavto
Copy link
Author

command exit code? which option is that in rawcooked?

@JeromeMartinez
Copy link
Member

command exit code? which option is that in rawcooked?

It is not specific to RAWcooked. It is a standard for all commands ;-).
See e.g. Bash command line exit codes demystified.

RAWcooked currently use 0 for success (including with warnings) and 1 for errors, 1 may change in the future (to other non-0 code for more detailed info).

@dericed
Copy link

dericed commented Nov 17, 2022

Recommendation from @BleakleyMcD is to add the timing data to this log, when each step starts and the duration of the process.

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

No branches or pull requests

3 participants