Convert a X265

[Zerou]

How to convert a MKV X265 file on a mp4 or AVI X264 file ?

[KarMa]

I think Handbrake can read x265 files now, and it can convert it to a x264 inside a MP4.

[LigH.de]

I guess every converter based on a current version of ffmpeg (e.g. Handbrake, Hybrid, TEncoder) or AviSynth (with L-SMASH Source or FFMS2, e.g. MeGUI or StaxRip) should be able to convert HEVC (the video format created by the x265 encoder) to AVC (the video format created by the x264 encoder).

Do not use AVC in AVI; the AVI container is obsolete and not recommendable to contain this video format. The MP4 container would be the native container for AVC video.

[Zerou]

So with the Hybrid 2015.12.23.1 there no possibilities to do the conversion from a MKV X265 to a MP4 X264 ?

[Baldrick]

Didn't LIgh.de just say that it will work with Hybrid? Have you tried it?

[LigH.de]

I did not promise. But Selur is usually very interested in keeping his tools up to date.

Just claimimg that it doesn't work is not enough. Proving the content of the source file with a MediaInfo analysis, and explaining the attempt step by step, is a minimum requirement. If there are any error messages, try your best to quote them letter by letter.

[AlanHK]

I think Handbrake can read x265 files now, and it can convert it to a x264 inside a MP4.

Are you sure? I tried to load an x265 file as source, but it can't recognise it.
Handbrake 0.9.9.5530

PS -- I see there is a 0.10.2 version out. I'll try that.
PPS 0.10.2 doesn't install on Win XP, so I can forget about Handbrake.

[KarMa]

May want to try getting the newest Handbrake 10.2

[AlanHK]

May want to try getting the newest Handbrake 10.2

Tried that, won't install on WinXP.
So far can't find any way to decode x265 on XP.

(If anyone want to lecture me about how obsolete/dangerous/uncool/stupid it is to be running XP, please assume I know that.)

[Selur]

Should work with Hybrid. (at least works here; mkv(x265) -> avi(x264))

[AlanHK]

Should work with Hybrid. (at least works here; mkv(x265) -> avi(x264))

Thanks, will give it a try.
I had passed it by since it's Qt based.
Is it Qt4 or 5?
Qt5 is very flaky on XP if it works at all.

[Selur]

Qt5 is very flaky on XP if it works at all.

if you say so

It's qt5 based nowadays and works fine here on XP,...

[Selur]

Qt5 is very flaky on XP if it works at all.

if you say so

It's qt5 based nowadays and works fine here on XP,...

[LigH.de]

If everything else fails, you may have to go down to manual labour (using the CLI tools like ffmpeg with detailed options, or writing an AviSynth script). Some 32 bit builds are still compiled with enabled XP compatibility, even though XP is already obsolete. As one example, Vista+ Windows offer a better multi-threading support, which e.g. x265 had to emulate to stay XP compatible.

[KarMa]

L-smash and ffmsindex seem to index and frameserve x265 fine, in megui

[AlanHK]

L-smash and ffmsindex seem to index and frameserve x265 fine, in megui

Tried them. Avisynth is my weapon of choice for the last 10 or 15 years.
But the x265-capable plugins all crap out in XP, at least so far.

[LigH.de]

x265-capable plugins

What's that? AviSynth plugins should not be aware of the encoder the script is provided to. If you mean those with high efficiency (fast enough not to delay the slow encoder much further): They may be more RAM demanding or require newer versions of MS VC++ runtimes which Microsoft may not support for XP anymore (which is obsolete according to their marketing schedule).

all crap out

The more exactly you can describe how they fail, the better one may try to solve the issue. But we don't have crystal balls.

Anyway, x265 on an almost only 32 bit OS like XP is a dead end; x265 itself is so complex, it may already fail for FullHD resolutions, being out of memory on a 32 bit OS. Not to mention the encoding speed, if your CPU is that old.

[AlanHK]

They may be more RAM demanding or require newer versions of MS VC++ runtimes which Microsoft may not support for XP anymore

I have 4GB RAM. Never come near to using it all.

I Googled the error messages and they all lead me to MS VC++, and a dead end.

all crap out

The more exactly you can describe how they fail, the better one may try to solve the issue. But we don't have crystal balls.

I wasn't asking for help on the plugins. I think it's impossible on XP.

Anyway, x265 on an almost only 32 bit OS like XP is a dead end; x265 itself is so complex, it may already fail for FullHD resolutions, being out of memory on a 32 bit OS. Not to mention the encoding speed, if your CPU is that old.

My PC is 2 years old and more than fast enough.

I don't want to encode x265, just some videos are only available in that and I need to convert them so my media player can play them.
And the media player isn't upgradeable, it's a bit older and handles xvid and x264 fine, but that's it.

[El Heggunte]

^ As a "last resort", you could try DSS2Mod() — which does not depend on Haali Media Splitter, and may use the LAV Filters

You can even use a faster 32-bit HEVC decoder (namely, the Lentoid Decoder) with DSS2Mod(),
as long as the source video does not contain unsupported features (10-bit compression, for example).

[LigH.de]

I have 4GB RAM. Never come near to using it all.

But 32-bit processes can only use 2 GB of it (maybe 3 with some tricks). And with enough threads and a large frame dimension, complex filters like QTGMC can easily fill it up, so AviSynth and the encoder together may get out of RAM. Well ... x264 is not so demanding, that should mostly work. And with a moderate thread count, most plugins or import functions can do well. But runtime libraries ... most developers see no reason in supporting XP still, while W7 is already becoming obsolete ("Mainstream support" already ended in January 2015 = one year ago; "Extended support" will end in 2020). Grab it while it's cheap. And go for 64 bit, don't miss the future already yesterday.

[AlanHK]

I have 4GB RAM. Never come near to using it all.

But 32-bit processes can only use 2 GB of it (maybe 3 with some tricks). And with enough threads and a large frame dimension, complex filters like QTGMC can easily fill it up,

I don't have any problems with RAM.
The problem is the software just aborts because of some function it wants that isn't in my system.

so AviSynth and the encoder together may get out of RAM. Well ... x264 is not so demanding, that should mostly work. And with a moderate thread count, most plugins or import functions can do well. But runtime libraries ... most developers see no reason in supporting XP still, while W7 is already becoming obsolete ("Mainstream support" already ended in January 2015 = one year ago; "Extended support" will end in 2020). Grab it while it's cheap. And go for 64 bit, don't miss the future already yesterday.

For me, video is just a hobby. For my work I need to use old software and that doesn't play nice with newer OS.
Won't run at all on a 64 bit system.

One day I'll have to upgrade and work out some emulation or other tricks for my old software, but not yet.

==========================

PS: found a simple, though inelegant way to do this.
VLC can play x265, even on XP. And VLC can convert any file it can play.
The options aren't as comprehensive, but it does the job.

I do want to be able to feed x265 into Avisynth though, so I'll keep trying options.