autodidact Posted yesterday at 08:02 AM Posted yesterday at 08:02 AM On 7/9/2026 at 6:09 PM, VistaLover said: Hopefully you'll be able to get to the bottom of this, as I do use FFplay.exe myself under Vista SP2 (32-bit) ; thanks for all your hard efforts already! There are new Vista builds linked in the previous post. If you can let me know if ffplay is working for you. 2
VistaLover Posted 16 hours ago Posted 16 hours ago 8 hours ago, autodidact said: There are new Vista builds linked in the previous post. If you can let me know if ffplay is working for you. On 7/9/2026 at 6:55 AM, autodidact said: FFmpeg update. (...) VISTAx86: static shared libfdk-aac Thanks a lot for recompiling ; I've downloaded and tested the new n8.2-dev-2273 VISTA binaries and can confirm the new FFplay.exe files work as expected : If it's not too much to ask , can you share what the issue was with the previous FFplay offering? 1
VistaLover Posted 15 hours ago Posted 15 hours ago 13 minutes ago, VistaLover said: I've downloaded and tested the new n8.2-dev-2273 VISTA binaries and can confirm the new FFplay.exe files work as expected : ... Well, I think I spoke too soon ; while, indeed, MP4 media files with h264+aac now don't cause an FFplay crash, a tagged (metadata+cover) MP4 file with audio-only (HE-AACv1) still leads to a crash: The same tagged audio file plays fine with previous FFplay n8.2-dev-1568 (from early June): That file was downloaded from BBC Sounds with yt-dlp (it has now expired); if it's any help, below its MediaInfo log: Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/mp41) File size : 39.6 MiB Duration : 57 min 0 s Overall bit rate mode : Constant Overall bit rate : 97.1 kb/s Title : Dance Sounds of the 90s with Vernon Kay, Party Classics With Ultra Naté In The Mix Description : Ultra Naté makes a mix for Vernon's Classic 90s Party. Writing application : Lavf62.6.100 Cover : Yes Cover type : Cover Comment : https://www.bbc.co.uk/programmes/m001yrds LongDescription : Ultra Naté makes a mix for Vernon's Classic 90s Party. Audio ID : 1 Format : AAC LC SBR Format/Info : Advanced Audio Codec Low Complexity with Spectral Band Replication Commercial name : HE-AAC Format settings : Implicit Codec ID : mp4a-40-2 Duration : 57 min 0 s Bit rate mode : Constant Bit rate : 96.0 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 23.438 FPS (2048 SPF) Compression mode : Lossy Stream size : 39.1 MiB (99%) Language : English Default : Yes Alternate group : 1 Image Type : Cover Format : JPEG Muxing mode : moov-meta-covr Width : 1 200 pixels Height : 675 pixels Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Compression mode : Lossy Stream size : 104 KiB (0%) This is turning into a nightmare ; thanks in advance for any insight...
VistaLover Posted 15 hours ago Posted 15 hours ago (edited) The crash on the audio file isn't to do with it being tagged, because the crash is still invoked even without a tag (text metadata+cover): Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/mp41) File size : 39.6 MiB Duration : 57 min 0 s Overall bit rate mode : Constant Overall bit rate : 97.1 kb/s ContentType : Movie Writing application : Lavf62.6.100 rati : (Binary) Audio ID : 1 Format : AAC LC SBR Format/Info : Advanced Audio Codec Low Complexity with Spectral Band Replication Commercial name : HE-AAC Format settings : Implicit Codec ID : mp4a-40-2 Duration : 57 min 0 s Bit rate mode : Constant Bit rate : 96.0 kb/s Channel(s) : 2 channels Channel layout : L R Sampling rate : 48.0 kHz Frame rate : 23.438 FPS (2048 SPF) Compression mode : Lossy Stream size : 39.1 MiB (99%) Language : English Default : Yes Alternate group : 1 PS: The same untagged audio file plays OK with the latest n8.2-dev-2237 SHARED FFplay binary for XP: Edited 14 hours ago by VistaLover Added image for XP ffplay
autodidact Posted 12 hours ago Posted 12 hours ago @VistaLover I reversed this commit which got partial functionality but GCC 16 is still problematic for 32-bit builds. Here is a smaller build using GCC 15 for you to try. https://files.videohelp.com/u/69760/ffmpeg-8.2-2278-a09be9b91e-static-VISTAx86.7z 2
VistaLover Posted 10 hours ago Posted 10 hours ago 1 hour ago, autodidact said: I reversed this commit which got partial functionality but GCC 16 is still problematic for 32-bit builds. ... I'm trying somehow to understand, but, as a non-coder, I fail to do so ... Your previous working, FULL, FFplay.exe (32-bit) binary from early June, ffplay version N-124841-gb355200263-WINVISTA Copyright (c) 2003-2026 the FFmpeg developers built with gcc 16.1.0 (Rev5, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libdav1d --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug --enable-librubberband --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 60. 32.100 / 60. 32.100 libavcodec 62. 36.101 / 62. 36.101 libavformat 62. 19.101 / 62. 19.101 libavdevice 62. 4.100 / 62. 4.100 libavfilter 11. 17.100 / 11. 17.100 libswscale 9. 8.100 / 9. 8.100 libswresample 6. 4.100 / 6. 4.100 was compiled with GCC16, was it not ? However, more recent FFplay (32-bit) builds, when again compiled with GCC16, end up exhibiting the crash-y behaviour I have reported so far; have you changed in some aspect the compiler itself (GCC16) since the start of June or are the recent crashes the result of upstream (FFmpeg) new code, that makes the final binary incompatible with NT 6.0 x86? 2 hours ago, autodidact said: Here is a smaller build using GCC 15 for you to try. The GCC15.2 compile launches OK here, ffplay version N-125551-ga09be9b91e Copyright (c) 2003-2026 the FFmpeg developers built with gcc 15.2.0 (Rev14, Built by MSYS2 project) configuration: --prefix=/local32 --bindir=/local32/bin-video --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-zlib --enable-sdl2 --enable-gpl --enable-libmp3lame --disable-debug --enable-libfdk-aac --enable-libass --enable-libxml2 --enable-libshine --enable-gnutls --enable-libx264 --enable-libx265 --extra-cflags=-DLIBXML_STATIC libavutil 61. 4.100 / 61. 4.100 libavcodec 63. 6.100 / 63. 6.100 libavformat 63. 4.100 / 63. 4.100 libavdevice 63. 2.100 / 63. 2.100 libavfilter 12. 2.100 / 12. 2.100 libswscale 10. 2.100 / 10. 2.100 libswresample 7. 2.100 / 7. 2.100 Simple media player usage: ffplay [options] input_file ... and I couldn't help noticing lots of "first-to-be-seen" configure flags : --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion As for my audio-only MP4 file, it plays there with NO crashes : So, does this mean it's goodbye GCC16.1 and welcome GCC15.2 ? (OT: the appalling forum's code viewer did push my patience to its limits, while trying to send this comment ; will it ever get fixed?) 1
autodidact Posted 2 hours ago Posted 2 hours ago 7 hours ago, VistaLover said: ... I'm trying somehow to understand, but, as a non-coder, I fail to do so ... Your previous working, FULL, FFplay.exe (32-bit) binary from early June, ffplay version N-124841-gb355200263-WINVISTA Copyright (c) 2003-2026 the FFmpeg developers built with gcc 16.1.0 (Rev5, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libdav1d --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug --enable-librubberband --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 60. 32.100 / 60. 32.100 libavcodec 62. 36.101 / 62. 36.101 libavformat 62. 19.101 / 62. 19.101 libavdevice 62. 4.100 / 62. 4.100 libavfilter 11. 17.100 / 11. 17.100 libswscale 9. 8.100 / 9. 8.100 libswresample 6. 4.100 / 6. 4.100 was compiled with GCC16, was it not ? However, more recent FFplay (32-bit) builds, when again compiled with GCC16, end up exhibiting the crash-y behaviour I have reported so far; have you changed in some aspect the compiler itself (GCC16) since the start of June or are the recent crashes the result of upstream (FFmpeg) new code, that makes the final binary incompatible with NT 6.0 x86? The GCC15.2 compile launches OK here, ffplay version N-125551-ga09be9b91e Copyright (c) 2003-2026 the FFmpeg developers built with gcc 15.2.0 (Rev14, Built by MSYS2 project) configuration: --prefix=/local32 --bindir=/local32/bin-video --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-zlib --enable-sdl2 --enable-gpl --enable-libmp3lame --disable-debug --enable-libfdk-aac --enable-libass --enable-libxml2 --enable-libshine --enable-gnutls --enable-libx264 --enable-libx265 --extra-cflags=-DLIBXML_STATIC libavutil 61. 4.100 / 61. 4.100 libavcodec 63. 6.100 / 63. 6.100 libavformat 63. 4.100 / 63. 4.100 libavdevice 63. 2.100 / 63. 2.100 libavfilter 12. 2.100 / 12. 2.100 libswscale 10. 2.100 / 10. 2.100 libswresample 7. 2.100 / 7. 2.100 Simple media player usage: ffplay [options] input_file ... and I couldn't help noticing lots of "first-to-be-seen" configure flags : --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion As for my audio-only MP4 file, it plays there with NO crashes : So, does this mean it's goodbye GCC16.1 and welcome GCC15.2 ? (OT: the appalling forum's code viewer did push my patience to its limits, while trying to send this comment ; will it ever get fixed?) It is not NT 6.0 incompatible code as otherwise it wouldn't work no matter which compiler was used. This is likely a compiler issue so for now GCC 15 will be more reliable. The GCC 16 compiler hasn't been changed since the previous working build so I haven't been able to isolate the root cause yet. I will continue looking into it.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now