Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [FFmpeg-cvslog] fftools/ffmpeg: convert to a threaded architecture
Date: Thu, 14 Dec 2023 12:26:20 +0100
Message-ID: <170255318065.1197.12080511072536048846@lain.khirnov.net> (raw)
In-Reply-To: <4e37c599-95f9-470f-899e-49a62298d4f9@gyani.pro>

Quoting Gyan Doshi (2023-12-14 12:22:51)
> 
> 
> On 2023-12-14 02:48 pm, Anton Khirnov wrote:
> >>> On Tue, Dec 12, 2023 at 07:41:18AM +0000, Anton Khirnov wrote:
> >>>> ffmpeg | branch: master | Anton Khirnov<anton@khirnov.net>  | Tue Jul 18 16:37:52 2023 +0200| [d119ae2fd82a494d9430ff4d4fc262961a68c598] | committer: Anton Khirnov
> >>>>
> >>>> fftools/ffmpeg: convert to a threaded architecture
> >>>>
> >>>> Change the main loop and every component (demuxers, decoders, filters,
> >>>> encoders, muxers) to use the previously added transcode scheduler. Every
> >>>> instance of every such component was already running in a separate
> >>>> thread, but now they can actually run in parallel.
> >>>>
> >>>> Changes the results of ffmpeg-fix_sub_duration_heartbeat - tested by
> >>>> JEEB to be more correct and deterministic.
> >>>>
> >>>>> http://git.videolan.org/gitweb.cgi/ffmpeg.git/?a=commit;h=d119ae2fd82a494d9430ff4d4fc262961a68c598
> >>>> ---
> > should be fixed by the patch I just sent
> >
> 
> I tested a single input --> output conversion to compare performance and 
> I noticed the final report now displays N/A for time, bitrate and speed i.e.
> 
> frame= 1500 fps=109 q=-1.0 Lsize=   17363kB time=N/A bitrate=N/A speed=N/A
> 
> whereas commit 1439784ff0 shows
> 
> frame= 1500 fps=108 q=-1.0 Lsize=   17363kB time=00:00:59.97 
> bitrate=2371.6kbits/s speed=4.34x
> 
> Is this expected?

No, but check whether
http://lists.ffmpeg.org/pipermail/ffmpeg-devel/2023-December/318326.html
(also depends on the previous patch) fixes it.

-- 
Anton Khirnov
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".

  reply	other threads:[~2023-12-14 11:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20231212074119.EC15B41151B@natalya.videolan.org>
2023-12-13 23:16 ` Michael Niedermayer
2023-12-13 23:42   ` Michael Niedermayer
2023-12-14  2:07   ` Michael Niedermayer
2023-12-14  3:44     ` Anton Khirnov
2023-12-14  3:25   ` Anton Khirnov
2023-12-14 18:23     ` Michael Niedermayer
2023-12-14  8:18   ` Thilo Borgmann via ffmpeg-devel
2023-12-14  9:18     ` Anton Khirnov
2023-12-14 11:22       ` Gyan Doshi
2023-12-14 11:26         ` Anton Khirnov [this message]
2023-12-14 11:36           ` Gyan Doshi
2024-03-27 14:35 ` Michael Niedermayer
2024-03-27 17:49 ` Michael Niedermayer

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=170255318065.1197.12080511072536048846@lain.khirnov.net \
    --to=anton@khirnov.net \
    --cc=ffmpeg-devel@ffmpeg.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

Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
		ffmpegdev@gitmailbox.com
	public-inbox-index ffmpegdev

Example config snippet for mirrors.


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git