Hi guys, so a big thanks to jej79bob who has shared with me a video that causes a "crash" in ai 2.2.0. Armed with the problematic video I was able to pinpoint exactly what the issue was.
Although I've wrapped all the thumbnailing code with exception handling, it was actually the fact that the exception was caught but returned a null result to the engine. This caused the engine to stick into an endless wait loop. So from a user perspective it looked like it crashed but actually was just waiting forever!
All sorted now, I've fixed it in two ways. Firstly if an error is found then the jobservice flags the job as failed and moves to the next. You'll see a red icon in the archive queue next to the failed job. However to make the app a little more flexible and reliable (for example the video I had only had one single frame that was an issue, the rest was fine), then I've added a new local setting you can try which will allow a percentage of frame errors before aborting. All of this is to get the ai app to be as robust as possible especially for unattended processing of jobs overnight etc.
I've also updated some libraries for extra measure and finally removed the prototype flag, so this is now an official ai release with both GPU and CPU support.
Next for AI will be to add photo processing alongside video processing!
Links to ai 2.2.1 can be found in the welcome notes as usual.
charlie Brown
2025-02-09 23:12:33 +0000 UTCFBennett
2025-02-09 17:49:46 +0000 UTCcharlie Brown
2025-02-08 04:05:34 +0000 UTC