Quote:
Originally Posted by NiLuJe
@BloodRagg: Which error(s), specifically?
By design, it should only inhibit *non-critical* errors  . (By non-critical I mean anything that doesn't lead to an early abort). |
command line syntax errors , I have a number of while/for loops running in a script, they call fbink a lot But now and then some fall out of favor depending on the input stream its parsing and then all hell breaks loose. (given that your wonderful tool comes with a shitload of switches
and accompanying texts).
My logfile of 100k became like 40mb, its annoying if it happens but nothing critical.
If you have a solution that would be great
