Too many MENCODER Crop Detect messages in DEBUG logfile

General Support / Questions
1

Request Type:
Feature

MCEBuddy Version and Type (32bit or 64bit):
2.4.8 64bit
Operating System and Type (32bit or 64bit):
Windows 10 64bit

Summary of the problem or suggestion:
When in Debug mode, 90% of my logfile is taken up by messages similar to the below. This also makes the size of the logfile unwieldy (130k/hour).

Can a lower debug setting for that particular part of the conversion be looked at? Or can it be an option to pipe that output into a separate file?

2018-02-14T11:11:08 MCEBuddy.AppWrapper.MencoderCropDetect --> Pos: 696.9s 20888f (19%) 494.61fps Trem: 2min 323223mb A-V:0.000 [745714:0]

Steps to replicate the bug:
Any conversion where CropDetect is needed while in Debug mode.

1 Like
2

:)) unfortunately no, that’s required because MCEBuddy is reading those outputs to take decisions on how to handle the cropping. Plus it helps with debugging then cropping doesn’t work as expected. If you don’t want cropping you can turn it off in the Conversion Task Expert Settings page and it won’t run this function then.

You can however reduce your log level to warning to drop debug messages.

Do note that log files are automatically deleted after 14 days by default unless otherwise configured in the System Settings page.