Cascades Development

[thubalek]

Hello,

I'm working on media player and I found extremely difficult to debug is as NowPlayingConnection and MediaPlayer are flooding log with a lot of useless logs.

Does anybody come with some solution how to turn these messages off?

I'm using 

slog2info -w | grep -v '=>' | grep -v MmrContextNotifier | grep -v NowPlayingConnectionPrivate | grep -v MediaPlayerPrivate | grep -v 'NowPlayingConnection::setPosition' | grep -v 'MediaPlayer::position' | grep -v 'NowPlayingConnection' 

but it far from to be perfect.

I would love to see some properties like debugLevel added into NowPlayingConnection and MediaPlayer.

[peter9477]

I do something similar with a shell script I put in ~/bin/slog containing this, currently:

slog2info -w | sed -re '/default      0 |OrientationSupportPrivate|MediaPlayer|MmrContext|=> END/d;s/^.{7}(\S+) ([^.]+\.[^.]+\.[^.]+)\.\S+\s+(\S+)\s+(.*)/\1 \2 \3 \4/'

 (That's all one line, in case it gets wrapped, and certain spaces are critical so do a straight copy/paste if you use it.)

There may be ways to shut it off, but as I believe it's a moving target (what we see with the next version will likely be changed again) I'm not really spending any time thinking about it for now. Just update your filtering as you see fit and carry on... if you type that long command line every time, of course, then that would get annoying. So.. don't. ;-)

[HorizonXP]

I have the exact same issue with the Camera QML component. Bit annoying to have your log filled with useless debug messages.

[peter9477]

Might be worth noting that this log *can't* be "filled" (although I know that's not really what HorizonXP meant).

The slog2 output goes into circular buffers in a RAM drive, so it's not only light-weight (no constant rewriting of flash memory) but it doesn't even consume much memory to do it since old messages are just replaced with new ones as you go.

It's an inconvenience only (handled with the above filtering techniques), and probably a temporary one at that.

[borceg]

Device log view in Momentics IDE provides selection between various slog2 messages CRITICAL, ERROR, WARNING, DEBUG1, INFO etc (Severity, verbosity, and filtering) but it's not quite polished at this moment. Some changed need to be done in order to distinguish between system messages (in which we are not interested at all) during debug and messages relevant to our code execution.