From: Takashi Yano <takashi.yano@nifty.ne.jp>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] ffmpeg (5.1.2)
Date: Sun, 22 Jan 2023 21:20:47 +0900 [thread overview]
Message-ID: <20230122212047.f35ba52aaa87e7941b235e67@nifty.ne.jp> (raw)
In-Reply-To: <790f3692-3ab3-9b4a-ee6b-6fc379a02975@towo.net>
On Fri, 20 Jan 2023 21:05:51 +0100
Thomas Wolff wrote:
> Am 20.01.2023 um 16:58 schrieb Takashi Yano via Cygwin-apps:
> > On Fri, 20 Jan 2023 16:47:01 +0100
> > Thomas Wolff wrote:
> >> Am 20.01.2023 um 16:28 schrieb Takashi Yano via Cygwin-apps:
> >>> On Fri, 20 Jan 2023 16:04:46 +0100
> >>> Thomas Wolff wrote:
> >>>> Am 20.01.2023 um 11:35 schrieb Takashi Yano via Cygwin-apps:
> >>>>> I would like to propose new package ffmpeg which is
> >>>>> well known audio/video tool. ffmpeg is ported to
> >>>>> many linux distributions and other unix like systems
> >>>>> as well as widows. Since there is windows build,
> >>>>> the demand of cygwin port might be relatively small,
> >>>>> however its libraries are usefull for other softwares.
> >>>>>
> >>>>> I have posted another ITP for MOC (Music On Console)
> >>>>> which is a ncurses based music player, whose plugin
> >>>>> uses ffmpeg libraries.
> >>>>>
> >>>>> I have already prepared the ffmpeg package as follows.
> >>>>>
> >>>>> https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg/
> >>>>>
> >>>>> To build ffmpeg, other new packages i.e., x264, x265 and
> >>>>> xvidcore are required, I have proposed ITP at the same
> >>>>> time.
> >>>>>
> >>>> It's also missing cygswscale-6.dll which I don't find anywhere.
> >>> It should be in:
> >>>
> >>> https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg/libffmpeg/libffmpeg-5.1.2-1.tar.xz
> >>>
> >>> which is reuqired by ffmpeg-5.1.2-1.tar.xz.
> >> OK, I had overlooked that in the ffmpeg folder.
> >> Now I get:
> >>
> >> C:/cygwin64/bin/ffmpeg.exe: error while loading shared libraries: ?:
> >> cannot open shared object file: No such file or directory
> > Thanks for testing.
> >
> > You need libSDL2_2.0_0 package installed as described in
> > https://tyan0.yr32.net/cygwin/x86_64/release/ffmpeg/ffmpeg-5.1.2-1.hint
> A first test suggests that this build may be significantly (~70%) slower
> than the native Windows build of ffmpeg, unfortunately. Do you see a
> possible reason for that and a chance to compensate?
I tested the encoding speed of ffmpeg and the cygwin build indeed
slower than windows build. In my test, the speed is almos half.
However, I noticed that if "-threads 64" option is added, it gets
faster. Even with this option, cygwin build is 15% slower.
I am not sure why...
--
Takashi Yano <takashi.yano@nifty.ne.jp>
next prev parent reply other threads:[~2023-01-22 12:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 10:35 Takashi Yano
2023-01-20 15:04 ` Thomas Wolff
2023-01-20 15:28 ` Takashi Yano
2023-01-20 15:47 ` Thomas Wolff
2023-01-20 15:58 ` Takashi Yano
2023-01-20 20:05 ` Thomas Wolff
2023-01-22 12:20 ` Takashi Yano [this message]
2023-01-20 18:40 ` Jon Turney
2023-01-20 21:04 ` Brian Inglis
2023-01-22 12:25 ` Takashi Yano
2023-01-24 3:28 ` Takashi Yano
2023-02-04 16:45 ` Jon Turney
2023-02-05 8:40 ` Takashi Yano
2023-02-06 13:53 ` Takashi Yano
2023-02-13 18:28 ` Jon Turney
2023-02-14 9:11 ` Takashi Yano
2023-02-16 18:48 ` Jon Turney
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=20230122212047.f35ba52aaa87e7941b235e67@nifty.ne.jp \
--to=takashi.yano@nifty.ne.jp \
--cc=cygwin-apps@cygwin.com \
/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).