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
Currently, all of the output from ffmpeg and packager goes to the terminal. It would be nice if this output could be optionally ignored, logged (separately for each process), or shown. When the output of ffmpeg is not being shown, it would be nice to have some status from Shaka Streamer so that the user could see roughly what is happening, but in an easy-to-read format.
The text was updated successfully, but these errors were encountered:
Each node that creates a subprocess now has control over the output
handles and environment variables for the subprocess. This will
enable environment-based logging (as ffmpeg uses) or logging based on
a file handle.
This is a step toward logging support.
Issue #12
Change-Id: I717d411e4b708eeaf05af03e1a16602336c2d065
This is very primitive logging, with no control over output filenames,
paths, or log rotation. As such, it is only meant for debugging.
To enable, set debug_logs: true in the pipeline config.
Issue #12
Change-Id: I16696b5cea54579b921ff8186c944e8e5a5939fc
Currently, all of the output from ffmpeg and packager goes to the terminal. It would be nice if this output could be optionally ignored, logged (separately for each process), or shown. When the output of ffmpeg is not being shown, it would be nice to have some status from Shaka Streamer so that the user could see roughly what is happening, but in an easy-to-read format.
The text was updated successfully, but these errors were encountered: