On 06/22/2013 05:18 PM, Justin Ruggles wrote:
> On 06/22/2013 10:57 AM, Luca Barbato wrote:
>> +#if HAVE_SYSLOG_H
>> +static void log_callback_syslog(void *ptr, int level, const char *fmt,
>> + va_list vl)
>> +{
>> + switch (level) {
>> + default:
>> + case AV_LOG_PANIC: level = LOG_ALERT; break;
>> + case AV_LOG_FATAL: level = LOG_CRIT; break;
>> + case AV_LOG_ERROR: level = LOG_ERR; break;
>> + case AV_LOG_WARNING: level = LOG_WARNING; break;
>> + case AV_LOG_INFO: level = LOG_NOTICE; break;
>> + case AV_LOG_VERBOSE: level = LOG_INFO; break;
>> + case AV_LOG_DEBUG: level = LOG_DEBUG; break;
>> + }
>> +
>> + vsyslog(level, fmt, vl);
>> +}
>> +#endif
>
> In theory, can't actual Libav log levels be in-between the pre-defined
> levels?
I should mask the first 3 bits before that probably. My 255 col support
tries to use them to add additional tints, currently its usage is
dubious at best.
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
