Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Excessive Logging
07-07-2016, 07:12 PM (This post was last modified: 07-07-2016 07:23 PM by ohBru.)
Post: #1
Excessive Logging
openhome-player is very verbose. At least the most recent Pi version is, I haven’t tried others. Every second we get "Pipeline report property: TIME {secs=657; duration=679}” which drowns out any useful information in the logs when run as a daemon. Sure, I can add a filter to remove this but a configuration setting to turn down the verbosity of openhome-player would be better. Is there one?

BTW: What does "Pipeline report property: TIME {secs=657; duration=679}” mean? There is no indication if it is an error or simply an observation. I assume the latter as everything works.
Find all posts by this user
08-07-2016, 11:19 AM
Post: #2
RE: Excessive Logging
(07-07-2016 07:12 PM)ohBru Wrote:  openhome-player is very verbose. At least the most recent Pi version is, I haven’t tried others. Every second we get "Pipeline report property: TIME {secs=657; duration=679}”

This pipeline state logging is informational only.

Unfortunately it's build time configurable only.

I agree it's too verbose to be on for release builds. I'll update things so that it's
only on for debug builds.

To effect this change manually avoid instantiating an instance of
LoggingPipelineObserver and adding it as a pipeline observer in the ExampleMediaPlayer constructor.

Also avoid deleting in in the ExampleMediaPlayer destructor.
Find all posts by this user


Forum Jump: