 |
I am somewhat hesitant to close this, but I can not reproduce and GG says he has used F_kerndeint and it has always worked really well for him. It can be reopened if it reoccurs. |
|
|
Marking as Resolved and will close in a couple of days. Only time will tell if there is a different problem from what was fixed by disallowing F_interlace. |
|
|
As previously stated, it is believed from the messages shown, that F_interlace causes a lot of error messages. After GG looked at them, he found out that ffmpeg interlace and tinterlace use the same parameters but some that are legal for tinterlace are illegal for interlace. Since the tinterlace alternative exists, interlace has been removed from the legal plugin list for ffmpeg. This plugin may still show up in your Resources window until the plugins are reloaded, either automatically or manually. We found that when this plugin was added, the UNDO stack was totally bofus and this may have caused the crash. I will close this issue after the April builds are complete since then F_interlace plugin will be gone. |
|
|
The F_interlace plugin may be the real cause of the crash as I have been able to get a couple of different error messages from that AND most disturbing is that it causes the UNDO to be totally wrong / not working. I can not get F_kerndeint to create any problems even though I stressed it out with changing the threshold slider bar over and over and hit apply as quickly as possible. First I will show GG the errors messages but most likely he will remove F_interlace from the allowed ffmpeg plugins to avoid the possible cause of the issue. I do not know why anyone in this day and age would want to add interlace to video anyway. After that will close this, assuming F_interlace is the cause. |
|
|
I have not yet been able to duplicate this but I want to spend more time trying before giving up. |
- Anonymous
