Exception caught: Object reference not set to an instance of an object #96

New Issue

melithine · 2025-12-14T02:45:23Z

melithine commented

2025-12-14 02:45:23 +00:00

We were hoping that #82 would have solved this issue, but a user in Discord reported that it still continues.

To be clear for anyone following this issue, the error generated is not the actual error, but is actually obscuring the real error that FFmpeg is generating, so we are unsure exactly what the issue is. We will first have to correct that and beef up the logging, and then we can look into the actual problem afterwards, once we have more information.

That all said, this usually seems to be some form of networking error, and if you're running into this often (which none of the dev team has encountered, but users definitely have), trying a VPN if you're not using one, or trying direct if you are, is our best recommendation at this time.

We were hoping that #82 would have solved this issue, but a user in Discord reported that it still continues. To be clear for anyone following this issue, the error generated is not the actual error, but is actually obscuring the real error that FFmpeg is generating, so we are unsure exactly what the issue is. We will first have to correct that and beef up the logging, and then we can look into the actual problem afterwards, once we have more information. That all said, this usually seems to be some form of networking error, and if you're running into this often (which none of the dev team has encountered, but users definitely have), trying a VPN if you're not using one, or trying direct if you are, is our best recommendation at this time.

image.png

248 KiB

melithine added the

bug

label 2025-12-14 02:45:23 +00:00

melithine commented

2025-12-14 03:57:24 +00:00

My bad, this is still being tracked on #78, so this is a dupe.

melithine closed this issue

2025-12-14 03:57:25 +00:00

melithine added

duplicate