tv_box
June 21, 2023, 10:53am
1
Hello, when exporting a file more than 2 GB, it’s error on 98% progress
LOG:
[h264 @ 000002173abec480] Reinit context to 1280x720, pix_fmt: yuv420p
[h264 @ 000002173cf60440] Reinit context to 1280x720, pix_fmt: yuv420p
[h264 @ 000002173aabc7c0] Reinit context to 1280x720, pix_fmt: yuv420p
[producer avformat] audio: total_streams 1 max_stream 1 total_channels 2 max_channels 2
[AVIOContext @ 000002173abe3d00] Statistics: 6945170 bytes read, 2 seeks
[chain avformat-novalidate] E:/CashLab/Video/Целые стримы/PLO 60$ на PokerBros 13.06.mp4
checking VFR: pkt.duration 3000
[libx264 @ 000002173ae4dc40] using SAR=1/1
[h264 @ 000002173afceac0] Reinit context to 1280x720, pix_fmt: yuv420p
[libx264 @ 000002173ae4dc40] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 000002173ae4dc40] profile High, level 4.0, 4:2:0, 8-bit
[libx264 @ 000002173ae4dc40] 264 - core 164 r3094M bfc87b7 - H.264/MPEG-4 AVC codec - Copyleft 2003-2022 - x264, the best H.264/AVC encoder - VideoLAN - options: cabac=1 ref=2 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=6 psy=1 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 lookahead_threads=2 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=1 keyint=150 keyint_min=15 scenecut=40 intra_refresh=0 rc_lookahead=30 rc=crf mbtree=1 crf=23.0 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
[h264 @ 000002173adfe240] Reinit context to 1920x1088, pix_fmt: yuv420p
Failed with exit code -1073741819
Failed with exit code -1073741819
Windows 10 64x shotcut 23.06.14
Help me please to fix this problem.
https://forum.shotcut.org/search?q=1073741819
The two most common causes for this error are running out of memory or a corruption of some part of your project.
To check the memory, use the task manager to monitor memory usage during the export.
If your computer is not running out of memory, there may be something in your project causing the failure.
Consider these steps:
Observe the % complete of the export when the failure occurs.
Create a copy of your project using File->Save As and make a new name.
Open the new file and remove one …
Also read this:
Your export failed for one or more reasons. There is always a reason why it failed. Below are the posts by others describing their faults and solutions. This tutorial is not a definite tutorial as you may have a unique situation not described in here.
Time Code
After failure to export it may display a time code, make a note of the time displayed and look on your timeline to see what’s there that could be causing the problem. It could be a clip, audio or video file, transition.
[firefox_20…
You are probably going to have to manually try and identify what is causing the failure at 98%. Pay careful attention to the TIMECODE where your project failed and check your timeline around that area. You can use markers to help with the export process when testing if you want.
Markers are like time-based bookmarks for your project to help you remember and quickly go to sections.
Timeline Markers were added in version 21.10.31.
[Timeline Markers]
Press M or click toolbar button the first time to add a marker at the playhead (current position) with no dialog.
[image]
Markers appear in the time ruler/track/row at the top of the Timeline.
Drag a marker to move it.
There are several ways to seek to a marker: Click directly on a marker, press < or >, or click the see…
That should be enough to identify the offending item(s).
However, you only mentioned Windows 10 and nothing about your computer specs (how much RAM, for instance). But without knowing that and understanding your current situation, I would advise setting a larger than normal swap for this kind of thing, especially if you only have 8GB RAM. See this post for more info and instructions on changing virtual memory:
Weird. I guess Shotcut performs better on low level machines when running Linux. Case and point (and this has a LOT of keyframing):
[Mariahs 21st Birthday (Updated with New Intro)]
So I guess you will have to invest in more RAM if you want to avoid these problems, which isn’t very expensive these days and is probably easier than moving to a different OS.
Incidentally, how is your virtual memory configured?
On programs that can occasionally hog memory (like Photoshop) some users h…
Good luck!