From: Marth64 <marth64@proxyid.net> To: ffmpeg-devel@ffmpeg.org Cc: Marth64 <marth64@proxyid.net> Subject: [FFmpeg-devel] [PATCH v2] web/index: fix invalid line breaks (BR) Date: Wed, 10 Jan 2024 11:29:21 -0600 Message-ID: <20240110172920.1894399-1-marth64@proxyid.net> (raw) In-Reply-To: <ZZ3XLSVIjo9Pcl9b@mariano> Uses preferred convention for ffmpeg Signed-off-by: Marth64 <marth64@proxyid.net> --- src/index | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/index b/src/index index 98cc516..edf8100 100644 --- a/src/index +++ b/src/index @@ -113,11 +113,11 @@ </p> <p> Internally, we have had a number of changes too. The FFT, MDCT, DCT and DST implementation used for codecs - and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).</br> - This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.</br> + and filters has been fully replaced with the faster libavutil/tx (full article about it coming soon).<br> + This also led to a reduction in the the size of the compiled binary, which can be noticeable in small builds.<br> There was a very large reduction in the total amount of allocations being done on each frame throughout video decoders, - reducing overhead.</br> - RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.</br> + reducing overhead.<br> + RISC-V optimizations for many parts of our DSP code have been merged, with mainly the large decoders being left.<br> There was an effort to improve the correctness of timestamps and frame durations of each packet, increasing the accurracy of variable frame rate video. </p> -- 2.34.1 _______________________________________________ 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".
prev parent reply other threads:[~2024-01-10 17:29 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-08 21:13 [FFmpeg-devel] [PATCH] web/index: fix invalid line-break (BR) tags Marth64 2024-01-09 23:30 ` Stefano Sabatini 2024-01-09 23:37 ` Marth64 2024-01-10 17:29 ` Marth64 [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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240110172920.1894399-1-marth64@proxyid.net \ --to=marth64@proxyid.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