Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Derek Buitenhuis
On 1/3/2017 9:57 PM, Ronald S. Bultje wrote: > Hm, right... OK, yeah, I understand the issue, but I somehow doubt there's > an easy way to resolve that that isn't disgustingly hacky on our side. If you're not very fond of happiness or joy, you could run a separate 64-bit process to decode and

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Ronald S. Bultje
Hi, On Tue, Jan 3, 2017 at 4:35 PM, Matthieu Beghin < matthieu.beg...@garagecube.com> wrote: > Hi, > > > On 03 Jan 2017, at 18:26, Ronald S. Bultje wrote: > > > > Hi, > > > > On Tue, Jan 3, 2017 at 12:16 PM, Matthieu Beghin < > > matthieu.beg...@garagecube.com> wrote: > > >

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Matthieu Beghin
Hi, > On 03 Jan 2017, at 18:26, Ronald S. Bultje wrote: > > Hi, > > On Tue, Jan 3, 2017 at 12:16 PM, Matthieu Beghin < > matthieu.beg...@garagecube.com> wrote: > >> >>> On 03 Jan 2017, at 17:55, Ronald S. Bultje wrote: >>> >>> Hi, >>> >>> On Tue,

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Michael Niedermayer
On Tue, Jan 03, 2017 at 12:26:59PM -0500, Ronald S. Bultje wrote: > Hi, > > On Tue, Jan 3, 2017 at 12:16 PM, Matthieu Beghin < > matthieu.beg...@garagecube.com> wrote: > > > > > > On 03 Jan 2017, at 17:55, Ronald S. Bultje wrote: > > > > > > Hi, > > > > > > On Tue, Jan 3,

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Ronald S. Bultje
Hi, On Tue, Jan 3, 2017 at 12:16 PM, Matthieu Beghin < matthieu.beg...@garagecube.com> wrote: > > > On 03 Jan 2017, at 17:55, Ronald S. Bultje wrote: > > > > Hi, > > > > On Tue, Jan 3, 2017 at 11:44 AM, Matthieu Beghin < > > matthieu.beg...@garagecube.com> wrote: > > > >>>

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Matthieu Beghin
> On 03 Jan 2017, at 17:55, Ronald S. Bultje wrote: > > Hi, > > On Tue, Jan 3, 2017 at 11:44 AM, Matthieu Beghin < > matthieu.beg...@garagecube.com> wrote: > >>> I'm assuming that you're talking about 8K H264 with pixfmt=yuv420p10? 8K >> yuv420p10 frames are 100MB >> >>

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Ronald S. Bultje
Hi, On Tue, Jan 3, 2017 at 11:44 AM, Matthieu Beghin < matthieu.beg...@garagecube.com> wrote: > > I'm assuming that you're talking about 8K H264 with pixfmt=yuv420p10? 8K > yuv420p10 frames are 100MB > > Correct > > > 32 plus delayed output and current_pic gives H264_MAX_PICTURE_COUNT = 36 >

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Matthieu Beghin
> I'm assuming that you're talking about 8K H264 with pixfmt=yuv420p10? 8K > yuv420p10 frames are 100MB Correct > 32 plus delayed output and current_pic gives H264_MAX_PICTURE_COUNT = 36 > without threading: 36*100=3.6GB. What do you mean by "delayed output” ? Can you link me to a document ?

Re: [FFmpeg-devel] libavcodec memory usage

2017-01-03 Thread Ronald S. Bultje
Hi, On Tue, Jan 3, 2017 at 10:58 AM, Matthieu Beghin < matthieu.beg...@garagecube.com> wrote: > Hi, > > My application is using libavcodec etc. to playback movies. Everything is > ok with our 64 bits app. But I have a 32 bits app and there when playing a > 8k we reach 3 GB memory usage, so when