From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: media-video/gpac and media-video/mplayer fails to build.
Date: Fri, 21 Feb 2025 14:54:54 -0000 (UTC) [thread overview]
Message-ID: <vpa43u$13oe$1@ciao.gmane.io> (raw)
In-Reply-To: a198b888-fb71-899a-f9a6-0148de605238@gmail.com
On 2025-02-21, Dale <rdalek1967@gmail.com> wrote:
> Frank Steinmetzger wrote:
>> Am Thu, Feb 20, 2025 at 11:36:47PM -0000 schrieb Grant Edwards:
>>> On 2025-02-20, Dale <rdalek1967@gmail.com> wrote:
>>>>> Use flags for ffmpeg would give us a better idea. But I would guess
>>>>> they're either AV1 or H.265 encoded.
>>>> I'm getting some help off list from another Michael. O_O He suggested
>>>> several USE flag changes. Some I never heard of.
>>>
>>> Ask ffmpeg what's in the file. Then you'll _know_ what encoder(s)
>>> were used and what USE flags you need.
>
>> The command to just get file information is ffprobe. Its output is
>> very dense. I recommend mediainfo for a more human-friendly
>> output. It also comes with an optional GUI.
>
> The other Michael asked for ffprobe info, off list.
He's right, that's what you need to do (or something equivalent) so
that you know what codec you're missing.
> I enabled some USE flags and tried to recompile with those. It
> failed on some, again. I'm giving it another go now.
So are you trying to figure out why you can't play those .mkv files,
or just trying to get mplayer to build? I'll once again point out
that mplayer seems to by dying (hasn't had a new version released in 3
years). Most users seem to have moved to mpv.
https://wiki.gentoo.org/wiki/MPlayer:
Note
MPlayer is not very actively maintained anymore, but still
alive. However, its fork MPV is active and it comes with some extra
features too.
--
Grant
next prev parent reply other threads:[~2025-02-21 14:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 18:00 [gentoo-user] media-video/gpac and media-video/mplayer fails to build Dale
2025-02-20 18:14 ` Mark Knecht
2025-02-20 18:23 ` Dale
2025-02-20 18:35 ` Mark Knecht
2025-02-20 18:38 ` Mark Knecht
2025-02-20 19:06 ` Dale
2025-02-20 21:35 ` [gentoo-user] " Grant Edwards
2025-02-20 18:59 ` Grant Edwards
2025-02-20 23:15 ` [gentoo-user] " Frank Steinmetzger
2025-02-20 21:42 ` Michael Cook
2025-02-20 22:03 ` Dale
2025-02-20 23:36 ` [gentoo-user] " Grant Edwards
2025-02-21 0:05 ` Frank Steinmetzger
2025-02-21 8:06 ` Dale
2025-02-21 14:54 ` Grant Edwards [this message]
2025-02-21 15:38 ` Dale
2025-02-21 23:59 ` Frank Steinmetzger
2025-02-22 13:35 ` Dale
2025-02-22 22:42 ` Dale
2025-02-23 1:34 ` David M. Fellows
2025-02-23 7:53 ` Dale
2025-02-23 8:23 ` Michael
2025-02-23 10:21 ` Dale
2025-02-23 12:54 ` Frank Steinmetzger
2025-02-23 18:46 ` Michael
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='vpa43u$13oe$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.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