вт, 13 янв. 2026 г., 21:27 Phyllis Smith <phylsmith2017@gmail.com>:

Update:

Unfortunately testing the latest x264 library does not fix the problem of h264 loads/renders on Debian 9.1 i386 32-bit.

I have built CinGG-20251231-i386 and uploaded on the website with the GIT source on December 31 but with x264 version r3106.  I will make a note in the manual that anyone compiling will have to get the x264 library from:

commit 6eece58c73502e502760595155a27178d64a4feb
Date:   Sat Sep 7 11:47:46 2024 -0600

And that the x264 library since:

commit 2ce09466ce02b9180d6d7ba30af02e99fca0bdc5
... + update x264 from r3106 to r3191

is temporarily not usable for h264 files, but seems to work for at least a couple of other formats that I checked.

I am almost sure that we could make a patch to fix the problem if I was a lot smarter and put some effort into doing so.

Does x264 build from r3191 works standalone (it eats y4m files normally, I think) in same hw/sw environment?

You can put whole git x264 tree there and just perform git bisect?

One bad problem - segmentation fault when rendering on older debian i386 32-bit.  Was testing the new h264.mov render format when I got this error and it took a really long time to figure out when this happened.  Embarrassed to find out it seems to be due to X264 upgrade in Sept. 2024!

commit 2ce09466ce02b9180d6d7ba30af02e99fca0bdc5

    <snip, snip> transfers/primaries, + update x264 from r3106 to r3191

May be it makes sense to try newer x264?

Year happened, so may be this error was already corrected ?

May be older gcc/nasm miscompiled something? Because I can't see this one Slackware 15.0 i586 

I'll try to make Debian 9 i586 VM (installer probably need manual mirror choice ....) but not right now - I set new USB hdd to test, and will finish ... in around 1000 minutes ;)