I had Apollo crash twice on 3:2:2 using crop, stabilization and 50i Deinterlace DVx2 and Apollo 59.94fps all together. Will try same with 3:2:3. Using 2080Ti.
UPDATE: My 2080Ti fan seems to be blowing lots of hot air out, and presumably Apollo (as above job settings) is flying through the WHOLE job without crashing.
Will report later…
This issue goes way back to version 1. It’s been reported many times.
FWIW I started with Voyager sourced from PAL, but I was disappointed in the quality. Even though PAL has 625 lines of resolution, it was still converted from NTSC master with 576 lines of resolution. Even with the extra lines of resolution, you gain nothing in regards to output quality. The PAL colors are terrible. I purchased the NTSC set of DVD’s and got much better results, except for those bizarre moving blotches in the more dark areas.
I would like to mention that in the 3.2.3 version the preview is not following the processing properly and at some point it even might get stuck completely showing a static image for the rest of the processing.
On the other hand a whole movie 720 pixels wide and enlarged to full HD can now be processed in only five hours via Proteus V4 on my RTX 2070 Super.
Just updated to 3.2.3 on my M1 Mac mini and now the application simply will not open any video content to edit. Neither dragging and dropping, or opening by searching.
Do you make an upscalle of DS9? For my part, I do a deinterlacing via Handbrake without changing the resolution. Then I have 2 options:
Either I scale to 1280x1024 with Proteus relative to auto with some setting and then I finish by scaling to 1440x1152 on the 2nd pass.
Or I do directly in one pass with Proteus relative to auto with stronger settings than before. And I finish in Premiere pro with a light sharpening filter or the denoise filter from the Magic bullet suite from Red Giant (now called Maxon)
I get very good results in general as you can see on this picture.
This is an issue our team is aware of and will be patched soon. For now, a clean install of the 3.2.3 release (from the full .dmg installer) will correct the error.