23.09.2024, 19:14
(23.09.2024, 05:16)Selur Wrote: Updated a deoldify test version, to a version without the checks.
Wouldn't it make sense to keep these checks in the GUI too, to avoid having someone enable some DeOldify setting without checking the preview and then crash using processing?
Released new RC15, in this release are applied the following changes:
1) the input errors now are reported as FATAL error, the process is stopped, but are not shown all the function calls as before, only the error message, this should be less confusing
2) now in "sync" mode the the progress of coloring is reported as: "Colored Frame: n/total_frames"
In vsPipe there is the following code:
static const char *messageTypeToString(int msgType) {
switch (msgType) {
case mtDebug: return "Debug";
case mtInformation: return "Information";
case mtWarning: return "Warning";
case mtCritical: return "Critical";
case mtFatal: return "Fatal";
default: return "";
}
}
In HybridDebugOutput the message regarding the progress is reported only if I use the message type FATAL, but since the process will be stopped, it cannot be used (I attached the file).
Dan