Page MenuHomeSolus

Shotcut stuck at "pending" when exporting to file
Closed, ResolvedPublic


When trying to export eve the simplest project Shotcut stuck at "pending" status and never starts encoding.
Probably, it is looking for nonexistent libraries.

Terminal output gives me:
[Debug ] <MeltJob::start> "/usr/bin/qmelt" ("-progress2", "-abort", "/tmp/shotcut-k12809.mlt")

No other errors.
MLT is installed.

Event Timeline

Dainis created this task.Mar 1 2017, 7:38 PM

First off, try installing these two packages one at a time and see if this resolves anything

  • frei0r
  • ladspa

If not, I've pushed an update to 17.02 so try that once it's synced

Dainis added a comment.Mar 2 2017, 6:58 PM

Thanks for the response, but unfortunately it didn't help.
frei0r was already in system and installing ladspa didn't help either.

I tried archive version 17.02.05 from Shotcut webpage, but the result is same - stuck at "pending". BTW, i have only melt in /usr/bin/, but not qmelt, that Shotcut tries to reach. Is that normal?

Dainis added a comment.Mar 7 2017, 6:59 PM

Tested again with Shotcut from the repository. Issue still remains.

Can you try this?
My reading suggests qmelt is to workaround an issue that only impacts mac, which would make it unnecessary to provide.

sudo ln -s /usr/bin/melt /usr/bin/qmelt

Yes, I tried. Unfortunately, still the same.
Maybe full console output can help.

I'm seeing a couple of things.

Is there an easy way for me to reproduce this? Not having much luck in doing so (or working out how to do anything with this).

There are no specific circumstances to reproduce. Just opening really simple project (.mlt) containing short video with in- and out- points set and rendering it with one of the presets.
I've just noticed that timeline is missing toolbar and it is impossible to add clips. So, it is messed up too.

P.S. I'm really starting to think that it is time to reinstall Solus. Since last November, when I installed it, Solus has been through a lot of changes. Maybe something just went wrong during updates...
P.P.S. I have other issues as well..

I've made a bunch of fixes to mlt and shotcut to rectify this. Please test when the new version is available (17.05) in a couple of days. Thanks

Dainis added a comment.May 7 2017, 4:48 PM

Unfortunately, export issue still remains.
At least, timeline works again.

Is the error message still the same?

I've landed an update to produce qmelt the old fashioned way and fully by the book. Give it a crack when you get the update to webvfx (release 2)

Since you made a symlink before, just double check the qmelt binary is installed properly if having troubles. Should look something like this

$ ls -al /usr/bin/qmelt
-rwxr-xr-x 1 root root 35008 May 11 10:00 /usr/bin/qmelt
Dainis added a comment.EditedMay 23 2017, 6:02 PM

Still no luck... :( Maybe I should ask on G+ if anyone else has the same issue?

$ ls -al /usr/bin/qmelt gives me output
-rwxr-xr-x 1 root root 35144 mai 11 14:15 /usr/bin/qmelt

I assume it is OK?

P.S. It is a fresh system now. I've reinstalled it week or two ago.

Attached Shotcut log file.

I have the same problem with this thing too .

Attached Shotcut log file

@maizuddin35 you aren't using the Solus version and running it as root...

Ideally I require an example I can reproduce locally to look at this futher

I'm runnig Solus version 3.26.1
I think I run the app in Sudo .
Is there a way for me to provide some more resources/reference?

noko62 added a subscriber: noko62.Dec 2 2017, 2:23 PM

I've got the same issue and encountered the following: when I start shotcut from the command line and add a job to the export window, the output in the command window is like this example: [Debug ] <MeltJob::start> "/home/noko/" ("-verbose", "-progress2", "-abort", "/tmp/shotcut-fF3019.mlt"). By copying this, opening a new terminal and paste it, I get a 'bash: syntax error at unexpected word `"-verbose", '. But when I delete the parenthesis prior to Enter, everything works fine (the job starts and completes after a while).
Remind that the opening parenthesis does not appear in the bash syntax error output, instead it's printed as " ` " (the grave accent). Maybe a regional settings problem??? (I'm using 'German' regional setting and keyboard).

Best regards, Norbert

Are you talking about incoming update from unstable repository? Because at the moment for me nothing is resolved. Still stuck at "pending" while exporting. Now Shotcut produces even more errors.
Output from console

@Dainis eveything is released on the unstable branch first. You have to wait for the next sync to get the updates

Ok, thanks. I was afraid I had missed something :)

Dainis added a comment.May 2 2018, 6:53 PM

Thanks, everything works fine now. Though for some reason it doesn't appear in Budgie taskbar.

The same issue still exist for shotcut via snapcraft and the Appimage files too!

Debug  ] <Mlt::Controller::setAudioChannels> 2 
[h264 @ 0x52d7a40] Reinit context to 1280x720, pix_fmt: yuv420p
[h264 @ 0x5358a00] Reinit context to 1280x720, pix_fmt: yuv420p
[h264 @ 0x5467840] Reinit context to 1280x720, pix_fmt: yuv420p
[Debug  ] <MLT> [producer avformat] audio: total_streams 1 max_stream 1 total_channels 2 max_channels 2
[AVIOContext @ 0x52dec40] Statistics: 1527183 bytes read, 2 seeks
[Debug  ] <MLT> [mlt_producer avformat-novalidate] "/home/sia/Music/2019-06-11 17-16-21.mp4" checking VFR: pkt.duration 3000
[h264 @ 0x5335c00] Reinit context to 1280x720, pix_fmt: yuv420p
[Debug  ] <TimelineDock::setSelection> Changing selection to ()  trackIndex -1 isMultitrack true 
[Info   ] <MainWindow::open> "/home/sia/Videos/Cnwedan_Esta/Cnwedan_Esta.mlt" 
[Info   ] <MLT> [filter swresample] 2(stereo) f32le 44100Hz -> 2(stereo) f32le 48000Hz
[h264 @ 0x5335c00] Reinit context to 1280x720, pix_fmt: yuv420p
[Info   ] <MLT> [consumer sdl2_audio] Audio Opened: driver=pulseaudio channels=2 frequency=48000
[Debug  ] <EncodeDock::on_encodeButton_clicked> 449641725952 bytes available on "/" 
[Debug  ] <MeltJob::start> "/snap/shotcut/45/" ("-verbose", "-progress2", "-abort", "/tmp/shotcut-kU5438.mlt")

We aren't responsible for the snaps or AppImages, and neither of those two use our system libs.

Hi again,
Because both are working on debian and fedora from same source, isn't that solus issue?
And snapd is pre-installed on solus as i know 👍