From: oldlaptop <oldlaptop@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] shotcut should depend on ffmpeg
Date: Sun, 02 Apr 2023 17:45:19 +0200 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43214@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]
New issue by oldlaptop on void-packages repository
https://github.com/void-linux/void-packages/issues/43214
Description:
### Is this a new report?
Yes
### System Info
Void 6.1.21_1 x86_64-musl AuthenticAMD notuptodate rF
### Package(s) Affected
shotcut-22.01.30_1
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
Not applicable.
### Expected behaviour
When told to open a variable-frame-rate video file, shotcut offers to convert it to a more sensible format for editing purposes, and attempts to do this with ffmpeg (meaning the binary `/usr/bin/ffmpeg`).
### Actual behaviour
shotcut does not depend directly or indirectly on ffmpeg, meaning it's possible to have it installed without ffmpeg and have the conversion fail. (I've just had the dependencies actually shake out that way for me in a fresh installation.)
### Steps to reproduce
Install shotcut, do not install ffmpeg, attempt to open a variable-frame-rate video file in shotcut, and accept its offer to convert the file to a better format for editing.
next reply other threads:[~2023-04-02 15:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 15:45 oldlaptop [this message]
2023-04-02 23:43 ` mhmdanas
2023-04-03 2:57 ` oldlaptop
2023-04-03 8:09 ` [ISSUE] [CLOSED] " Johnnynator
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43214@inbox.vuxu.org \
--to=oldlaptop@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).