3.6+30-aMod

• Sync with 3.6 official release
• Update compilation scripts so all executables are multilib now

Upd: 10 and 12 bit single version binaries has been uploaded

3.5+131-aMod

Sync with latest available upstream, check their commits for more info.

Upd: -oldapi builds should be used with older (R54 and older) VS versions.

3.5+67-aMod

Just an upstream code sync, you probably satisfied enough with older version.
I made that release due to few people's request.

P.S.: use -oldapi build with Staxrip, apparently it still doesn't work with Vapoursynth APIv4.

3.5+20-aMod

Previous aMod works with fresh codebase.
Patches squashed, so we have a smaller tag difference.

3.4+70-aMod

Changes:

• CLI: add option --progress-readframes - print <coded frames>(<read frames>)/<all frames> in progress line
• Vapoursynth: disable script's reported SAR by default (can be enabled again with --reader-options use-script-sar=1)
• Add help for reader-specific options
• Fix limitReferences default value for Medium preset

3.4+65-aMod

Changes:

• Avisynth: make possible to provide custom Avisynth library with --reader-options library=Path\to\AviSynth.dll
• Vapoursynth: major overhaul in async frame requests logic. Test and report if it works fine or not

3.4+62-aMod

Changelog:

• Avisynth: fix seeking
• Input reader: add --reader-options. Allows to pass extra options to reader
• Vapoursynth: now you can supply few options via --reader-options parameter
  library: use user-defined vapoursynth (you should point full path to vsscript.dll)
  output: select different output node
  requests: override auto-detected parallel requests
  Format of Vapoursynth reader options is option=value;option2=value2 etc
• Cli: add manifest to binaries (should help with Avisynth and UTF-8 scripts/paths)

3.4+56-aMod

Changes from last release:

• Vapoursynth reader: fix possible heap corruption for vanilla VS. doodle1 branch was not affected at all.

x265-x64-v3.4+56-aMod-gcc10.2.1 is a multilib build while CPU-specific builds are 10 bits only.
Binaries stripped and UPX-packed, your antivirus might trigger a false alarm.

3.4+55-aMod

x64 build that uses gcc 10.2.1.
Different binaries contains compiler optimizations for certain CPUs. If you unsure, pick file without opt.
Files stripped and UPXed, so your antivirus might trigger a false alarm.