VideoPad can't compress H265 (.mp4) in XP

HunterEdits

Just what it says on the tin.

Doing so produces the following error:

https://i.imgur.com/doumsWH.png

Searches suggest this means a version of ffmpeg that won't work in XP is being triggered. These searches say if the newest XP compatible version of ffmpeg is used that this can be avoided, but due to the way VideoPad integrates codecs, there's no obvious way to drop in an ffmpeg file. Seemingly VideoPad includes two different versions of ffmpeg already; this may be a red herring. All I can tell you is it doesn't work.

Reported though bug reports on 8.56

If you have any suggestions, please share them.

borate

Update to Windows 10. Of course, you knew that suggestion was coming... 🤨

HunterEdits

borate wrote:

Update to Windows 10. Of course, you knew that suggestion was coming... 🤨

I didn't expect it, no. Is XP not a supported OS for VideoPad?

borate

It's doubtful that XP - ancient as it is - is actively supported

Try an older version of VP, from back in the day. http://oldversiondownload.com/

HunterEdits

borate wrote:

It's doubtful that XP - ancient as it is - is actively supported

Try an older version of VP, from back in the day. http://oldversiondownload.com/

Older versions don't include H265. Anyway, according to the product page at

https://www.nchsoftware.com/videopad/index.html

XP should be included.

Thrawn wrote:

...they need to configure the cmake build toolchain for their built-in x265 encoder with the cmake option WINXP_SUPPORT set to ON to make it XP-compatible. The corresponding commandline parameter for cmake is -DWINXP_SUPPORT=ON.

If they were compiling with Microsoft VisualStudio, they’d also need to pick an appropriate platform toolset. E.g. for Visual Studio 2017, this cmake option needs to be added: -DCMAKE_VS_PLATFORM_TOOLSET=v141_xp (v141 would be the modern one, v141_xp the one targeting XP). However, a quick $ strings x265enc3.exe analysis on UNIX suggests that the x265 bundled with the newest VideoPad was compiled with mingw/GCC 4.9.0 or mingw/GCC 5.4.0, probably within a CygWin or MSYS2 system on Windows. If this is true, DCMAKE_VS_PLATFORM_TOOLSET must not be set, but WINXP_SUPPORT still needs to be enabled.

There is a negative side-effect though: XP/Vista-compatible x265 is slower by 20-30%. NCH software might want to create two separate builds, a regular, modern one, and a legacy XP/Vista one. In that way, users of modern platforms can pick the faster, modern build and wouldn’t be negatively impacted by VideoPad providing an XP/Vista-compatible x265 encoder as well.

...

Another side-effect of this solution would be the limited options VideoPad gives you for configuring x265. x265vfw would be better in this regard.

borate

You can always make your wishes known via the Send Suggestion link accessible via the chevron at the top-right of the VP window.

VP may run on XP, but that doesn't guarantee that all current features will be available.

Can't speak for the company, but it's a fair bet that NCH will put in about as much effort as does MS on that obsolete, no longer supported OS.