Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Peter Ross via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Peter Ross <pross@xvid.org>
Subject: [FFmpeg-devel] Re: Can a GetByteContext have a "sub" context?
Date: Tue, 2 Sep 2025 17:57:36 +1000
Message-ID: <aLajcEn6fQQqAOL3@436df3412bf9621d289a69bf8f875853> (raw)
In-Reply-To: <CAOLZvyFFv65OkL5s2F=7bkUT7fZvijUJcZ3S=v_BNgqyK3PkbA@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 586 bytes --]

On Tue, Sep 02, 2025 at 08:03:14AM +0200, Manuel Lauss via ffmpeg-devel wrote:
> Hello,
> 
> Is it possible to have a "sub" context with a limited byte range for a
> super-context?
> i.e. I read 4 bytes from context c1, these are a length, c2 =
> GetByteContext_from(c1, len) ?  Or is "GetByteContext(&c2, c1.buffer,
> len);" enough?

second one is what I do:
    bytestream2_init(&c2, c1.buffer, len)

also need to check that that len does not exceed c1 bytes remaining. use bytestream2_get_bytes_left(c1).

-- Peter
(A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B)

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 163 bytes --]

_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-09-02  7:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-02  6:03 [FFmpeg-devel] " Manuel Lauss via ffmpeg-devel
2025-09-02  7:57 ` Peter Ross via ffmpeg-devel [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=aLajcEn6fQQqAOL3@436df3412bf9621d289a69bf8f875853 \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=pross@xvid.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