Linux: Cannot export

No, this is not the case at all. Every time data was written on the disk. Just tried to export again, see attached screenshot. The file created was FaceValue.mp4 :

-rw-rw-r-- 1 user user 58367244 Jul 19 21:26 FaceValue-backup.mp4
-rw-rw-r-- 1 user user 57490285 Jul 21 13:00 FaceValue-backup2.mp4
-rw-rw-r-- 1 user user 57677914 Jul 21 13:13 FaceValue-backup3.mp4
-rw-rw-r-- 1 user user 61866032 Jul 23 06:46 FaceValue.mp4

Aside from this I do not experience any disk related problems. I create music and use Bitwig and Harrison’s Mixbus32C. Never had any problem with that disk.

The disk space is:

/dev/sda6 289G 260G 15G 95% /VM

15G available, should be more than enough. Nevertheless Shotcut shows a warning at the beginning of the export. See second screenshot.

shotcutFailed2

And this is the other screen shot since new users can only put one at a time:

shotcutFailed

This is just a portion, can you put the screenshot of the whole shotcut window.

Darn. Without doing any modification to the project, just opening Shotcut and exporting, it succeeded. Let me do it once more. I’ll close Shotcut, restart it, then export again …

There it goes, it failed. And here’s the full screenshot.

There isn’t much to spot out, but have you tried to use hardware encoding? If you have tried it, try to configure what you will be using in it now.

Hardware Encoding

The benefit of hardware encoding is that it reduces the load on your CPU by using a purpose built piece of hardware on your Nvidia graphics card.

I hope it’s a useful piece.

Pure speculation here… Do all of your clips have the same exact frame rates (fps) as your video mode?

  • When it keeps stopping, as in your screenshot (3m : 27s: 10th frame) at that location does that file have the same exact FPS as your Video Mode?

    • To check your current video mode, click on “Output” in the timeline, then click on Properties. And to check on that clip, select it on the timeline, then Properties.

    • What what exactly is happening at that location? Transition I’m guessing. What filters and settings are being used at this location?

  • What distro of Linux are you using?

  • Did you get Shotcut from this website? Shotcut - Download

If you were to do a Save As (save it as a new file name), and delete those problem sections or delete filters/transitions at that location, will it export 100%?

1 Like

This is simply a warning and not blocking export. It cannot accurately predict how large the file will be. Read it; it is simply telling you getting low on disk space.

You see that time code next to “failed” in the job view? There is likely a problem around that point. But maybe also you are running out of memory.

I am not a developer of Shotcut (though I have done software development on other projects), so take this with a grain of salt - but in general, I would say that running any modern OS with your disk drive 95% full is likely to run into intermittent problems. The OS needs some room to swap things out, and even though the “swap file” may “only” be, say, 4Gb, the way that the system allocates temporary files can chew up a lot more space than that.

Keep in mind that video is VERY memory/disk intensive. If your RAM is not overly generous, on top of a 95% full disk, then I would say you need to address the memory and disk space issues before trying to pin down any particular cause for any software that may be crashing.

Hello. To everyone else: I haven’t had much time to pursue the problem these last few days. However there was one successful export of the current state of the project. I’ll be back to it in the coming days.

@awake : There are currently three disks. The disk here labeled /VM is not hosting the OS. And there’s no user partition on that one. However the main disk with the OS and the user partition is also on the low side. That might be a good point and I can do some cleanup on that one. I can rather easily clear up 16GB on the OS drive, which in turn would give more space for /tmp.

System memory is 16GB and the swap is on the /VM disk with the /VM disk having 14GB free. Which means that after cleanup the thing that will be different will be the /tmp directory having at least 16GB available (actually more). I can give this a try, no problem. In the next few days. Thanks.

1 Like

Hello. Sorry for the delay ! I have made some space. Now the main drive which hosts the OS and /tmp has 18GB free. I have tried an export of a very simple clip taken from youtube which I split in two parts and put the last part to the beginning.

It failed again. I rebooted and tried another export w/o changing anything and it worked.

Looking at the log it reported the following when it failed:

(cannot include the log text, see screenshot)

Looking at the log when it succeeded, it reported the following:

(cannot include the log text, see screenshot)

My question is: Is it possible to add a ‘verbose’ or ‘debug’ flag to melt-7 ?

Ans here’s the log text:

You need to look at the job log, not the application log. right-click the failed export job and view log.

Here’s attached the export job log that was shown just now. I had to export twice since the first export worked all right. Then I moved a clip a bit to ‘do something’ and tried to export again, and it failed.

exportLog2.txt (2.5 KB)

From the application point of view, melt-7 is called and apparently is failing. There’s a verbose switch passed on to melt-7 although it does not provide much feedback in that case. Is the export log the actual output from melt-7 ?

RAM is 16GB
OS is Xubuntu 18.04
/ has 18GB free space, which includes /tmp

The project is made of a single youtube clip which is then split in two halves. The 2nd half is put in front of the first and that’s it. Nothing else except just a little transition where the two clips are overlapping.

I tried again and it failed. Not at the same location. There are two clips but it does not failed always at the same place.

Thanks.

i use Linux exclusively. that said, most of my troubles came from export settings. some codecs are better than others and some quality settings, etc are better/worse as well. hardware acceleration or not, is also a factor (i actually get better results with software than hardware, at the cost of speed). one huge factor for me in the past was removing movflags=+faststart from the “other” tab in export. but i have not tried replacing such recently.
just some considerations to pursue. squashing to 1 track is not necessary.

From the log

Failed with exit code 11

Not enough information, and I am unable to reproduce your problem. Turn OFF Export > Advanced > Video > Parallel processing. See everything written above again plus FAQ

Export > Advanced > Video > Parallel processing is already disabled.

As for information that’s all the information shotcut is giving, I cannot squeeze more debug information out of it.

I am willing to do everything to provide more information but shotcut as it is now will only give what was shared here. Hence I was asking about additional debug flags for either shotcut and/or the mset-7 utility.

My domain of expertise are embedded Linux devices. I can debug things. Provided the software I use and write does have additional very verbose debug flags. Otherwise it is guessing and that takes time and is not efficient. 11 as a signal is a segfault.

So if shotcut supports more debug options, let me know I’ll be happy to try them.

I’ll browse the faq just in case.

Since it works one time and the other it doesn’t without any modifications, there’s obviously some instability. Is it hardware related or software related is the question.

Thanks. I did a couple of exports removing that parameter each time and it did not improve the state. I’m using the default settings for export. I do not know much about codecs so I’m not that much inclined in just ‘fooling around’ with parameters hoping to strike the right combination.

There’s clearly, from how I see it, some instability as it exports nicely once and w/o any modification to the projet will not the second time around. As far as I know the computer I built and use does not have any hardware support for videos. I’m using the ASUS mobo’s display output. It is an i5-3570 CPU @ 3.40GHz with 16 MB RAM. Not the latest around although I think it can handle this.

1 Like

There are also some ideas here:

Coincidentally, one of the solutions for exit code 11 was to delete a video track. But I suspect that having more than one video track is not the problem itself.

If an export fails inconsistently, and at a different time for each try, then we typically ends up being a resource problem (memory or disk). If an export fails consistently at the same spot, then there is usually a problem occurring with a specific filter or transition. In those cases, the user can delete the filter or transition that occurs around the time of the failure and then recreate it.

i am also facing same problem