[Bug]: Exporting not working

[ndizeyedavid]

Search existing issues

• I have searched the existing issues

Describe the bug

When i click on export and choose export details and choose legacy as my export mode, it loads and fails righth away saying "Failed to fetch"

Expected behavior

it was supposed to export the frames into a final video like it did before

To Reproduce

No response

Screenshots

OS

Windows

OS Version

Windows 11

Other OS

No response

Additional context

No response

[meiiie]

Quick triage question: does this still reproduce on current main or the latest build, and is it happening only in legacy export mode?

The other useful detail here is whether the project is exporting a freshly recorded clip or a local/imported video file. "Failed to fetch" has overlapped one loopback/local-media path before, so knowing that would help tell us whether this is the same family as the older export fetch bug or a different legacy-export regression.

[ndizeyedavid]

I am using the latest build 1.1.24.0. It is happening both on Legacy and Lightning export. Even the gif export actually.

Another thing i can add on is that yesterday it was working when it was a 2min screen recording where I did 2 of them and exported successfully.

Today I am exporting an 8min video and that's when this notif is coming up. It is a Freshly recorded Clip, i didnt import anything except for the background image only.

I hope this more info can help in identifying the issue🤗

[meiiie]

Thanks, that helps a lot. This no longer looks like the older loopback/local-video fetch path: it is happening on both Legacy and Lightning, and even on GIF export.

The next useful split looks like this: is the imported background image the trigger, or is it just the longer project length? If you can, could you try the same project once with the background image removed, and once with a longer fresh recording that has no imported assets at all? That should tell us pretty quickly whether this is a shared imported-asset fetch problem or a more general long-export failure.

[ndizeyedavid]

Hi again,

1. I am from trying to export by first removing the background and still the notif said "Failed to fetch".
2. I also tried trimming the clip on the timeline and manually removing all the automatic zooms that had been created and still it showed that error "Failed to fetch"

🤔actually i also noticed another issue / bug, despite triming the clip, it appears to be showing its content even though i have even deleted it.

!!! but still it's not working😭😭 and recording this video again will be such a headache fr😭😭

[meiiie]

Thanks, this is really useful. That rules out the imported-background path and also makes it less likely that the trim / auto-zoom edits are the main trigger.

At this point this looks more like a broader long-recording export failure than the older loopback/local-media fetch bug. The trim / deleted-content behavior in the screenshots also looks like a separate editor/timeline issue rather than the same export failure, so it would be better to track that separately if it keeps happening.

The last useful split here is: does the same ~8-minute recording fail before any timeline edits at all? If yes, this points much more strongly to a long-project export path than to an edit-specific regression.

[ndizeyedavid]

yes, the export fails before even any edit on the timeline.

I have tested it by deleting all zooms on the timeline and leaving the clip only. Then when i tried to export, it failed again. Same error message.

is this what you are trying to mean??☝️

[meiiie]

Yes, exactly -- thanks. If the same ~8-minute recording fails before any timeline edits, that points much more strongly to a broader long-recording export path than to an edit-specific regression.

The trim / deleted-content behavior still looks like a separate editor/timeline issue, so I would keep that as a separate track if it continues.

[ndizeyedavid]

okay, maybe should i can create a new issue point it out too(the timeline issue)??

And for this issue, let me try recording again in chunks and see if it works and exports for each individual take🤗. I will probably do like 2 takes

[meiiie]

Opened focused draft #329 for a narrow hypothesis fix: export now prefers the real local source path over the preview media URL when the editor already has it. That removes one renderer-side fetch() hop shared by both MP4 and GIF export, which matches the Failed to fetch symptom more closely than an edit-specific regression.

Keeping this as draft until there is runtime confirmation against the #328 repro.

[ndizeyedavid]

.....okayyy😅 i guess i will wait for a new release build, to update on my side.

But overall, thank you for your time🤗 And for real, this tool is amazing in all aspects!!!! I couldn't believe my eyes when i first recorded a sample and saw that the zooms where automatically created🤯. I dont care how long it takes to fix this bug, i will never let go of this tool fr🤗

[webadderall]

Seems to happen when playback speed is changed

[meiiie]

Thanks, that narrows the repro.

I will treat this as a speed-edit export case now, not just a generic long-recording export failure. Draft #329 still removes the preview-URL fetch hop shared by MP4 and GIF export, but it does not directly change speed-region rendering. Keeping it draft until the playback-speed repro is retested; if it still fails after that path change, the next target should be the speed-region export path itself.

[MetaAffinity]

I am facing the same issue. After watching a 20‑second video, I get the error message “failed to fetch” in both modes. Do you know when this bug will be resolved?

Thanks for this great app. I really enjoy using it!