Reducing logging

[mvallevand]

Sub is there any why to reduce the rather extreme volume of logging done during rendering by way of the client. ML3 does one second updates of the playing location and the render hash output for the screen updates is filling up 1.5 Mb of logs very quickly. An example is in pz1's post here
http://forums.gbpvr.com/showpost.php?p=3...tcount=102

Martin

[sub]

Ok, I'll reduce these specific messages. I'ev been meaning to do this.

[mvallevand]

Thanks. This info. still is helpful in coding incremental updates so if it could stay as in new log level, it doesn't need to be a config option, that would be great.

Marin

[whurlston]

Another I'd like to add along these lines is the check signal status during recording. The check comes in handy for QAM in case the tuner did not get initiated/tuned properly (rare these days but it still happens every now and then). I'd just like it to continue the checks but have the option to not log them repeatedly if there is a locked signal.

[sub]

ok.