On 4/27/19, Clément Bœsch <u...@pkh.me> wrote: > On Sat, Apr 27, 2019 at 12:29:44PM +0200, Paul B Mahol wrote: >> On 4/27/19, Clément Bœsch <u...@pkh.me> wrote: >> > On Thu, Apr 25, 2019 at 04:47:00PM +0200, Paul B Mahol wrote: >> >> On 4/25/19, Reto Kromer <li...@reto.ch> wrote: >> >> > Paul B Mahol wrote: >> >> > >> >> >>Found 65x65x65 3D LUT in wild >> >> > >> >> > FYI: 128x128x128 3D LUTs do also exist in film production. >> >> > >> >> >> >> Thank you, changed locally. >> > >> > This means one single malloc of 24M unless I'm mistaken. Are we sure >> > that's what we want? >> >> So you want this to be dynamically allocated? How you want to access >> elements? > > It is actually already dynamically allocated (the private context is), but > I suppose you meant individual allocs for each dimension. It really is an > open question. Maybe it's not an issue, it's just that I would just think > twice before doing such change because I would assume it would impact > performance on low-end machines due to more sparse memory accesses. >
Considering that some filtergraphs needs 64GB of RAM I consider that non-issue. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
