Great software to use. One problem. It fails when exporting. The ending of the log says the following. If more details are needed, please let me know.
I was exporting the work in progress OK then I added a short video from youtube and this problem started to pop up. If the time shown when export fails is the time in the video, it does not fails where the video is but rather around where a jpg is found on an additional video track. Question: should there be only one video track or are all tracks merged when exporting ? - Thanks !
[mp4 @ 0x7fcb48200f00] Using AVStream.codec to pass codec parameters to muxers is deprecated, use AVStream.codecpar instead.
[swscaler @ 0x7fcb30661e00] Warning: data is not aligned! This can lead to a speed loss
You could have several tracks and it works properly for me, I created a project with 6 tracks 2 hours of length and ram usage of about 27 GBs’ and it still ran smoothly and export was normal, you are having the problem due to a unsupported old version or unstable version, or you are running out of ram.
When it fails, does it always fail at the same spot? Or does it fail at a random percent?
From your test results it is difficult to conclude if the transition is causing the failure or if the failure is just intermittent. You could also try removing the transition and creating a new one.
The exit code failures are infrequent, inconsistent, and do not happy to most people. We have been working to reduce them, but if a failure does not happen for a developer, then the developer can not fix it.
We have a collection of advice here which may be helpful:
I am a developer and I do not know what that is. The front end GUI is written using QT and the backend processing (that is used for export) is mostly written in C, but some filters do use the QT library.
No. There is an EDL export feature in the File menu, if that is useful for you.
Years ago when I invited the Trolltech guys at the company it was called Qt. Uppercase Q, lowercase t. And it featured a multitasking ‘library’ consisting of slots and signals if I’m not mistaken. What I meant is that, part of Qt there are multitasking capabilities offered to the developer. Like a sub-system.
Version is 21.06.29
It does not fail always at the same place, considering no modification to the video. The time shown when exporting and failing corresponds to the middle of jpg file.
You will find attached the logs.
I wonder if it could be an external software called for processing that might be provoking what looks like a segfault.
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.
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.
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 ?