From: Alexander Asteroth <alexander.asteroth@h-brs.de>
To: help-guix@gnu.org
Subject: Re: ffmpeg possibly missing compile option?
Date: Sat, 11 Dec 2021 15:03:24 +0100 [thread overview]
Message-ID: <87czm3fd4d.fsf@h-brs.de> (raw)
In-Reply-To: <87wnkcedgb.fsf@h-brs.de>
[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]
I was on the wrong track. Even though the library is not found this is
not the cause of the error. If I start vlc in a smaller frame (screen is
4k), something like less than 3k width, it works. If I resize the frame
to more than 3/4 of the screen width, vlc just shows a black screen
while sound still works. Strange!
Cheers,
Alex
On Fri, Dec 10 2021, 15:24:58, Alexander Asteroth <alexander.asteroth@h-brs.de> wrote:
> Dear all,
>
> I'm trying to use vlc and ffmpeg on guix to cut mp4 files. When trying
> to play the mp4 files using vlc I encounter errors like:
>
>> Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>
> In [0] it is suggested that missing compile options are the reason for
> these kind of errors might be missing compile flags (--enable...) which
> are in fact not enabled in the package specification of ffmpeg.
>
> On te ofther hand I tried to install vdpauinfo and it returns:
>
>> $ vdpauinfo
>> display: :0 screen: 0
>> Failed to open VDPAU backend libvdpau_nvidia.so: cannot open shared object file: No such file or directory
>> Error creating VDPAU device: 1
>
> So it might be caused by missing libraries for my graphicscard.
>
> Any idea? Someone?
>
> Cheers,
>
> Alex
>
> ----
>
> [0] https://forum.videolan.org/viewtopic.php?p=517583
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 524 bytes --]
prev parent reply other threads:[~2021-12-11 14:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 14:24 ffmpeg possibly missing compile option? Alexander Asteroth
2021-12-11 14:03 ` Alexander Asteroth [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czm3fd4d.fsf@h-brs.de \
--to=alexander.asteroth@h-brs.de \
--cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).