I can often only process 1 file successfully each startup

[MatteCrystal]

This issue is kind of a jumbled mess ATM. I'm not sure how actionable what I've provided so far is, I'll tried to provide more/ better info as i use the app.

Each startup of the app I'm usually able to get 1 good run and then if I attempt a second i will get an error.

I've mostly been using CPU mode which seems to have the best quality to time ratio. So maybe this bug is specific to CPU mode. I'll do a few runs for each now and list my results here.

For all examples i choose the same 4 video clips and audio file.

TLDR:

I did the below test and of course non of them failed like they were for me before. Which leads me to believe possible one of the following. Although more testing is needed to know for sure.

1. The choice of clips or size/count of clips may have and effect
2. I noticed in app player like with NVIDIA NVENC HEVC (H.265) takes awhile to process. Clicking generate again while the in app video player is still processing seems to do nothing. This could be one scenario i related to why i was having trouble generating a second video. Maybe it was still processing and i didn't notice. But also maybe depending on input videos this process might become unexpectedly long or even fail? (needs more testing)
3. I could of sworn there was a way I got it to fail before that gave a error in terminal but I'm not getting that now. I'll update this post if i see it again.

NVIDIA NVENC H.264

I did 3 runs, back to back, without closing the app. All three were successful except the first run displayed this error after the video was made. Although the video seemed to of been generated correctly.

Exception in callback _ProactorBasePipeTransport._call_connection_lost()
handle: <Handle _ProactorBasePipeTransport._call_connection_lost()>
Traceback (most recent call last):
  File "asyncio\events.py", line 89, in _run
  File "asyncio\proactor_events.py", line 165, in _call_connection_lost
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

NVIDIA NVENC HEVC (H.265)

I did three runs got this error at the end of each. I noticed during these runs that the terminal says processing is done but the video in file explorer doesn't seem to be ready, nore does the video play in app. The moment the video player in app populates with a video is also the same time it populates in file explorer and when the below error occurs

Exception in callback _ProactorBasePipeTransport._call_connection_lost()
handle: <Handle _ProactorBasePipeTransport._call_connection_lost()>
Traceback (most recent call last):
  File "asyncio\events.py", line 89, in _run
  File "asyncio\proactor_events.py", line 165, in _call_connection_lost
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host

CPU (H.264)

All 3 also seemed to process. I noticed in app player like with NVIDIA NVENC HEVC (H.265) takes awhile to process. But i can actually view file right away in file explorer. I tested clicking generate again while the in app video player was still processing and it would not generate another video. I wonder if this is partly to blame, maybe it was processing in app player before and i didn't realize.

ProRes 422 Proxy (Precise Mode)

I didn't test since these tests are all unexpectedly passing now so i suspect I may have to update with more real world bugs i run into.

My specs

• windows 11
• 4090
• ryzen 7 7800x3D