On 01.07.2024 20:05, Dennis Mungai wrote:
On Mon, 1 Jul 2024 at 21:01, Timo Rothenpieler
wrote:
On 01.07.2024 18:52, Josh Allmann wrote:
On Thu, 20 Jun 2024 at 17:39, Josh Allmann
wrote:
In intra-only mode, frameIntervalP is 0, which means the frame
data array is smaller than the number o
On Mon, 1 Jul 2024 at 21:01, Timo Rothenpieler
wrote:
> On 01.07.2024 18:52, Josh Allmann wrote:
> > On Thu, 20 Jun 2024 at 17:39, Josh Allmann
> wrote:
> >>
> >> In intra-only mode, frameIntervalP is 0, which means the frame
> >> data array is smaller than the number of surfaces. This causes a
On 01.07.2024 18:52, Josh Allmann wrote:
On Thu, 20 Jun 2024 at 17:39, Josh Allmann wrote:
In intra-only mode, frameIntervalP is 0, which means the frame
data array is smaller than the number of surfaces. This causes a
crash when closing the encoder.
Fix this by making sure the frame data arr
On Thu, 20 Jun 2024 at 17:39, Josh Allmann wrote:
>
> In intra-only mode, frameIntervalP is 0, which means the frame
> data array is smaller than the number of surfaces. This causes a
> crash when closing the encoder.
>
> Fix this by making sure the frame data array is at least as big as
> the num
In intra-only mode, frameIntervalP is 0, which means the frame
data array is smaller than the number of surfaces. This causes a
crash when closing the encoder.
Fix this by making sure the frame data array is at least as big as
the number of surfaces.
---
libavcodec/nvenc.c | 2 +-
1 file changed,
