avs4x265 0.5 released - x265 with avisynth as input

[Kurtnoise]

I will check, thanks.

[benwaggoner]

Originally Posted by conc@n8

FFmpeg has implemented a few new muxing options recently, and perhaps -movflags faststart applies to such situations: http://ffmpeg.org/ffmpeg-formats.htm...-mp4_002c-ismv

This stuff is specifically for writing fragmented MPEG-4 files ala DASH and Smooth Streaming. These aren't compatible with many older .mp4 file-based players.

Also, there is no requirement for mov/mp4 that the MOOV atom be at the front. It's good to have it at the front for progressive download from a server that doesn't support byte-range access; this is called a "fast start" file. But for local playback or from a server that allows random access, it doesn't really matter.

[hydra3333]

These aren't compatible with many older .mp4 file-based players.

Thanks.
Confirming I haven't had any issues with "-movflags faststart" using a chromecast-from-raspberry-pi-webserver or a WDTV-live media player.
It seemed like a good practice, so I put it in my encoding stream anyway.

Does "-movflags faststart" mean that LigH's concern is no longer an issue ?

[Floatingshed]

Is there a 64bit version of this?

[stax76]

Originally Posted by Floatingshed

Is there a 64bit version of this?

I think this method is not very popular. There are different tools used by GUIs and users. In staxrip that is ffmpeg, avs2pipemod and vspipe and they all work equally well.

If you are in the x265 dialog in staxrip there is a tab called Other where you can find an option called Piping Tool, in the same dialog at the bottom there is a dropdown that has a Show Command Line menu item, best open a source file before, that can show you example command lines on how to use this three piping tools.

Typically, piping is done by GUIs or scripts of power users because it's not completely simple, often the y4m format is used which has the limitation that it does not support the frame count which is needed for an encoder to show progress, a power user can write a script but for normal users it's too difficult.

This type of piping works only in cmd however, running cmd in powershell works like this:

cmd /s /c --% "regular command line without any escaping between this quotes"

It should also be noted that there are x265 builds that can open avs directly, maybe even vpy (vapoursynth), both frame servers are supported in ffmpeg (libavformat (lavf)) which these special x265 builds use.

[MeteorRain]

My x265 has a patch to support loading avs directly, just like in x264. avs4x265 was likely to be used with hacked high bit depth or to support running 32bit avs on 64bit x265.

[halls]

Originally Posted by MeteorRain

My x265 has a patch to support loading avs directly, just like in x264. 64bit x265.

Hi!


Can you write a short cmd syntax for that?

[stax76]

https://x265.readthedocs.io/en/lates...mdoption-input

[Patman]

Originally Posted by halls

Hi!

Can you write a short cmd syntax for that?

I think it is the same like x264.exe (only x265 Yuuki-Asuna by MeteorRain)

x265.exe --output NUL C:\input.avs

[halls]

Originally Posted by Patman

I think it is the same like x264.exe (only x265 Yuuki-Asuna by MeteorRain)

x265.exe --output NUL C:\input.avs

ok.


Latest realese
ffmpeg is worinkg fine.
Maybe i did something wrong.

[MeteorRain]

Please use the latest. Yuuki 3.3+3+29 or Asuna 3.2+7+29 added direct AVS input support.

Also it's not necessary to include input-res or frames because they are supplied by AVS script.

And you requested main10 profile but uses 8-bit binary. If you want 10-bit encoding you have to use a 10-bit or a multilib binary.

My multilib binaries defaults to 10-bit encoding. (So if you want 8-bit you have to specify -D 8 on multilib.)

[halls]

Originally Posted by MeteorRain

Please use the latest. Yuuki 3.3+3+29 or Asuna 3.2+7+29 added direct AVS input support.

Also it's not necessary to include input-res or frames because they are supplied by AVS script.

And you requested main10 profile but uses 8-bit binary. If you want 10-bit encoding you have to use a 10-bit or a multilib binary.

My multilib binaries defaults to 10-bit encoding. (So if you want 8-bit you have to specify -D 8 on multilib.)

Thx. Its working now