You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes OME log files can grow very large with multiple restarts. And depending on your stream parameters, a lot of FFmpeg info/warning logs can be generated. Here's a simple shell script to help you trim your OME log files before submission or analysis.
It takes an --input or -I argument for the path of your OME log file, and an optional --strip-ffmpeg or -s argument to strip out any FFmpeg-related lines.
The output is just the OME run from the last startup until the end of the log file.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Sometimes OME log files can grow very large with multiple restarts. And depending on your stream parameters, a lot of FFmpeg info/warning logs can be generated. Here's a simple shell script to help you trim your OME log files before submission or analysis.
ome_log_trim.sh
It takes an
--inputor-Iargument for the path of your OME log file, and an optional--strip-ffmpegor-sargument to strip out any FFmpeg-related lines.The output is just the OME run from the last startup until the end of the log file.
All reactions