All exports completing, but show as failed

Bug
1

Since updating to 21.12.24 every export job goes to 100% and the exported file seems fine, but it shows as failed. It’s not really a big deal, but it has happened on every single export since upgrade.

What is your operating system?

Win 10 Pro

What is your Shotcut version (see Help > About Shotcut)? Is it 32-bit?

21.12.24

Can you repeat the problem? If so, what are the steps?
(Please be specific and use the names as seen in Shotcut, preferably English. Include a screenshot or screen recording if you can. Also, you can attach logs from either View > Application Log or right-click a job and choose View Log.)

[libx264 @ 0000025b46b74e80] using SAR=1/1
[libx264 @ 0000025b46b74e80] using cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
[libx264 @ 0000025b46b74e80] profile High, level 4.0, 4:2:0, 8-bit
[libx264 @ 0000025b46b74e80] 264 - core 161 r3039M 544c61f - H.264/MPEG-4 AVC codec - Copyleft 2003-2021 - http://www.videolan.org/x264.html - 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=24 lookahead_threads=4 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=125 keyint_min=12 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
[mp3 @ 0000025b4eb96480] Skipping 0 bytes of junk at 2127.
[mp3 @ 0000025b4eb96480] Estimating duration from bitrate, this may be inaccurate
[mp3 @ 0000025b4eb3c280] Skipping 0 bytes of junk at 2127.
[mp3 @ 0000025b4eb3c280] Estimating duration from bitrate, this may be inaccurate
[producer avformat] audio: total_streams 1 max_stream 0 total_channels 2 max_channels 2
[AVIOContext @ 0000025b4ea76980] Statistics: 32768 bytes read, 0 seeks
[filter swresample] 2(stereo) f32le 44100Hz → 2(stereo) f32le 48000Hz
[mp4 @ 0000025b470edb40] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
[mp4 @ 0000025b470edb40] Encoder did not produce proper pts, making some up.
[mp4 @ 0000025b470edb40] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 7940096 >= 7940096
[mp4 @ 0000025b470edb40] Starting second pass: moving the moov atom to the beginning of the file
[AVIOContext @ 0000025b16edec80] Statistics: 12749764 bytes read, 0 seeks
[libx264 @ 0000025b46b74e80] frame I:34 Avg QP:10.72 size:111715
[libx264 @ 0000025b46b74e80] frame P:1035 Avg QP:12.31 size: 904
[libx264 @ 0000025b46b74e80] frame B:3067 Avg QP:12.91 size: 99
[libx264 @ 0000025b46b74e80] consecutive B-frames: 1.0% 0.3% 0.4% 98.3%
[libx264 @ 0000025b46b74e80] mb I I16…4: 59.0% 23.2% 17.8%
[libx264 @ 0000025b46b74e80] mb P I16…4: 0.1% 0.1% 0.1% P16…4: 0.7% 0.1% 0.1% 0.0% 0.0% skip:98.8%
[libx264 @ 0000025b46b74e80] mb B I16…4: 0.0% 0.0% 0.0% B16…8: 0.0% 0.0% 0.0% direct: 0.1% skip:99.8% L0:46.2% L1:45.5% BI: 8.2%
[libx264 @ 0000025b46b74e80] 8x8 transform intra:24.5% inter:75.2%
[libx264 @ 0000025b46b74e80] coded y,uvDC,uvAC intra: 34.8% 21.1% 11.2% inter: 0.1% 0.1% 0.0%
[libx264 @ 0000025b46b74e80] i16 v,h,dc,p: 93% 4% 2% 0%
[libx264 @ 0000025b46b74e80] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 17% 27% 39% 2% 2% 2% 4% 2% 5%
[libx264 @ 0000025b46b74e80] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 10% 63% 5% 2% 3% 2% 4% 2% 6%
[libx264 @ 0000025b46b74e80] i8c dc,h,v,p: 86% 8% 6% 0%
[libx264 @ 0000025b46b74e80] Weighted P-Frames: Y:2.2% UV:0.7%
[libx264 @ 0000025b46b74e80] ref P L0: 61.9% 38.1%
[libx264 @ 0000025b46b74e80] ref B L0: 88.7% 11.3%
[libx264 @ 0000025b46b74e80] ref B L1: 93.8% 6.2%
[libx264 @ 0000025b46b74e80] kb/s:243.58
[aac @ 0000025b46bbae40] Qavg: 3216.970
[AVIOContext @ 0000025b4eae4680] Statistics: 4 seeks, 101 writeouts

Failed with exit code -1073741819
Failed with exit code -1073741819

2

I do not know how to reproduce. I believe it is a problem specific to this project and not “all.” Sometimes Export or closing a project fails when releasing and closing resources.

3

The infamous “Failed with exit code -1073741819” message. If you search this forum for “1073741819” you will find many topics about this.

This is the most similar one:

Generally, this error is caused by something specific in the project that can often be removed to make the failure stop. I hope we figure out the root of this failure someday.

4

Maybe? I will say I’ve probably done 25 exports of small projects since upgrading and every single one of them has shown as failed while still exporting a complete and usable file.

5

Please try to help by finding what works for you and then what, when added, makes it fail like this? Thanks

6

It hasn’t shown an export as complete one time since I upgraded. It gets to 99%, pauses a moment then shows failed. 100% of the time since upgrade.

7

Hello all.
I’ve made a big project with SC latest version last year and also had exporting failures around 17% and I really went sweating and swaring.
The % indicated a problem in the time line so I tweaked my clips and their filters and it worked!

Now I’m back on SC to make another video and I’m now really worried of its completition due to forum issues on exporting.

So after a Sunday afternoon of preparing and gathering the clips I began putting them in SC: import photos and videos, cut clips, slow down clips, put FLAC audio track and add RICH TEXT to a photo clip.

At the end of the day, I wanted to try EXPORT and it failed!

So I rethinked to all those comment around exporting issues and I’m gonna be very careful now with filters trying not to go messing them (I use mouse a lot moving windows filters) but if I cannot export just a starting project I will be truly sad to stop working with SC, alas

8

The above post seems to be different than the issue I’m having. My files exports are completing and leaving me with complete and useable files. The issue is that it shows as failed in the Jobs window. Not a true problem, just annoying to have that red X on every job I export.

That said, another SC issue I have been having (more of an operational issue) has caused me to revert to an older version (picked one at random and landed on 20.10.31). That ‘fixed’ my operational issue and as a side effect has also fixed the failed job issue as well. Seems to be some combo of the newest SC version(s) and my current computer. Probably no way to narrow it down…will try a future version of the program and see if the issues come back.

1 Like
9

I’ve been working on my project for a week (3 video with pictures tracks, 2 audio tracks, proxy ON) and exported the project at the end of each day.

As of Canoteen the exported files is fine but the completed export task bar shows a 100% but FAILED.

Anyway the project is exporting fine, it’s just a feeling of something not truly working that annoys the standard user I am.

10

^^

Right? When I open the program and see all those red X’s staring at me, I start to question my choices in life.

11

I have just upgraded to V22.01.30 and can confirm that all my projects which were working fine before now exhibit this behaviour. Any export job completes fine but is marked as failed in the job queue.

I have just rendered a short test. The project is one I use to bring consistent titles into other projects and is completely Shotcut generated - three Text Simple filters with fade in/outs. Again, it renders fine but marks itself as failed. This seems to be a new bug in the latest versions. Log file below.

mlt_repository_init: failed to dlopen C:\Program Files\Shotcut\lib\mlt/libmltgdk.dll

(“C:\Program Files\Shotcut\lib\mlt\libmltgdk.dll”: The specified procedure could not be found.)

mlt_repository_init: failed to dlopen C:\Program Files\Shotcut\lib\mlt/libmltwebvfx.dll

(“C:\Program Files\Shotcut\lib\mlt\libmltwebvfx.dll”: The specified procedure could not be found.)

[h264_qsv @ 0000016300293240] Encoder: input is system memory surface

[h264_qsv @ 0000016300293240] Initialized an internal MFX session using hardware accelerated implementation

[h264_qsv @ 0000016300293240] Using the constant quantization parameter (CQP) ratecontrol method

[h264_qsv @ 0000016300293240] profile: high; level: 40

[h264_qsv @ 0000016300293240] GopPicSize: 125; GopRefDist: 4; GopOptFlag: closed ; IdrInterval: 0

[h264_qsv @ 0000016300293240] TargetUsage: 5; RateControlMethod: CQP

[h264_qsv @ 0000016300293240] QPI: 18; QPP: 23; QPB: 30

[h264_qsv @ 0000016300293240] NumSlice: 1; NumRefFrame: 3

[h264_qsv @ 0000016300293240] RateDistortionOpt: OFF

[h264_qsv @ 0000016300293240] RecoveryPointSEI: OFF IntRefType: 0; IntRefCycleSize: 0; IntRefQPDelta: 0

[h264_qsv @ 0000016300293240] MaxFrameSize: 0; MaxSliceSize: 0;

[h264_qsv @ 0000016300293240] BitrateLimit: ON; MBBRC: OFF; ExtBRC: OFF

[h264_qsv @ 0000016300293240] Trellis: auto

[h264_qsv @ 0000016300293240] VDENC: OFF

[h264_qsv @ 0000016300293240] RepeatPPS: OFF; NumMbPerSlice: 0; LookAheadDS: 2x

[h264_qsv @ 0000016300293240] AdaptiveI: OFF; AdaptiveB: OFF; BRefType: pyramid

[h264_qsv @ 0000016300293240] MinQPI: 0; MaxQPI: 0; MinQPP: 0; MaxQPP: 0; MinQPB: 0; MaxQPB: 0

[h264_qsv @ 0000016300293240] Entropy coding: CABAC; MaxDecFrameBuffering: 3

[h264_qsv @ 0000016300293240] NalHrdConformance: OFF; SingleSeiNalUnit: ON; VuiVclHrdParameters: OFF VuiNalHrdParameters: OFF

[h264_qsv @ 0000016300293240] FrameRateExtD: 1; FrameRateExtN: 25

[mp4 @ 000001637ff8a080] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly

[mp4 @ 000001637ff8a080] Encoder did not produce proper pts, making some up.

[mp4 @ 000001637ff8a080] Application provided invalid, non monotonically increasing dts to muxer in stream 1: 1615872 >= 1615872

[mp4 @ 000001637ff8a080] Starting second pass: moving the moov atom to the beginning of the file

[AVIOContext @ 0000016300558b00] Statistics: 515314 bytes read, 0 seeks

[aac @ 000001630031f4c0] Qavg: 65536.000

[AVIOContext @ 0000016300416700] Statistics: 4 seeks, 7 writeouts

Failed with exit code -1073741819

Failed with exit code -1073741819

12

WebFX filters have been deprecated. The last version 20.09.13 that has WebFX filters can be downloaded to continue the use of these filters.

13

Thanks. That is indeed the case but is not what is causing this issue.
I’m not aware of using any webvfx filters in this project- as I said, Text: Simple and video/ audio fade in/ outs are all that was here so why Shotcut is trying to access filters which are not used any more I don’t know.
Have just opened Shotcut, opened a video clip (mp4) and test exported - no filters at all, brand new 22.02.30 project and Shotcut outputs the file correctly but again marks it as failed in the job queue.
As has been stated before, at the moment this is more an annoyance than anything but it wasn’t broken before and now it is.

14

This tells me that you are not doing a clean upgrade and have old components at the same location. Reinstall by first removing the old version.

That does not always matter. You are still doing something unsupportable.

15

OK - I consider myself chastised! :grinning:

Uninstalled 22.01.30 and reinstalled from scratch. Ticked box to erase registry entries.
Lost my Recent Projects list but confirm that the error has now vanished.
Thanks.
In fairness to me, when I open up Shotcut and it is smart enough to know that there is a newer version available and download and install it for me closing the instance I had open before reinstalling, I kind of assumed (I know…) that it would do all the right things. I wonder if the Registry Entries box is usually unticked when I did that. Will check next time.

16

The “Clear Registry Entries” option is just that - an option. By default it is not selected and in general this is what you want. However - sometimes a registry entry can get screwed up and causes problems. In cases such as this it is best to clear the registry entries for Shotcut and hopefully this will solve the problem.

So basically, you only clear the registry entries as a last resort, that way you get a totally clean new installation of Shotcut.

1 Like