x264 vs x265??

[gonca]

Same result

[poisondeathray]

gonca, can you open "normal" video with avs script ? e.g. download something from youtube MP4 , try with ffms2 and l-smash

[Selur]

you did install Avisynth 2.6a and replace the avisynth.dll right?

[gonca]

you did install Avisynth 2.6a and replace the avisynth.dll right?

Yes, your avs preview works.
MPC-BE portable doesn't

[jagabo]

latest from qyot27: http://forum.doom9.org/showthread.php?p=1685186#post1685186 contains an updated libav and thus supports hevc

Thanks, Selur.

[vhelp]

for hevc videos, i've been using v2.19 though latest version is 2.20.0 and i also use the l-smash plugin on them.

download and install avisynth v2.58 or greater..
file: https://www.videohelp.com/download/Avisynth_258.exe

  ..and install.                               # i currently use v2.58 under xp home

install ffms2 into plugins folder
file: http://www.mediafire.com/?andkdxy05mrb8a0 -- # FFMS2 C-plugin r927+41, v2.20.0.0

 keep these files together in your plugins folder. mine is here c:\plugins
  ffms2.avsi
  ffms2.dll                                    # v2.19 and v2.20.0 loads hevc clips

write similar script (notepad) for loading a clip via avisynth script into virtualdub.
add other script functions, ivtc, color, etc., if necessary.

 
  v = "g:\video.1.sewing.mkv"                  # i dump a lot of clips, so v="" works best
# v = "g:\video.1.sewing.hm10"                 # 
  LoadCPlugin( "C:\PLUGINS\ffms2.dll" )        # i prefer loading explicitly
  FFVideoSource( v ,fpsnum=24000, fpsden=1001) # 23.976 film's speed
# FFVideoSource( v ,fpsnum=30000, fpsden=1001) # 29.970 video / telecine speed
  ScriptClip( """ subtitle("put info here "  + string(current_frame) + " - " + string(framecount),12,12)""")

review your video, ..once satisfied, you're finished!

[gonca]

I've tried AviSynth 2.58 and 2.6a. I have those files together in the plugin folder. The dll is 2.20.
I'll have to check later, computer is in use, but I think that if I use the AviSynth features of Hybrid it crashes during the encode

[vhelp]

i still can't believe you can't get ffms working. maybe it has to do with mpc-be. that has caused me problems many times. anyway. its more effective to open videos in virtualdub via avisynth scripts. maybe mpc-be is rejecting your script-fed videos for other reasons. after all, ffms2 is decoding the videos. like selur said, you have to wait until the ffms2 indexes and writes the file, i.e., "video.1.sewing.mkv.ffindex" and that can take some time, several minutes on some systems, like mine.

i looked at your computer specs, your os is win 7 64bit. maybe not a 64bit version. i don't know, i don't use that os with video.

anyway. there is also one more option to try, haali media splitter. if you have that somewhere on your system, then somewhere in the package is the avss.dll file, add that to your plugins folder, ie, LoadPlugin( "C:\PLUGINS\avss.dll") and load the videos through the command dss2(video, fps=23.976) inside virtualdub. i believe that dss2 uses whatever media/video library coders are already on your system or whatever haali uses, not sure exactly. the following opens an hevc encoded video muxed to an .mkv file inside virtualdub, and there is no waiting since it does not index like ffms2 does.

  v = "g:\video.sewing.mkv"              # x265 1.1.253 -> video.sewing.hm10 -> mux via mkvtoolnix v7.0.0[mkvmerge] -> video.sewing.mkv
  LoadPlugin( "C:\PLUGINS\avss.dll")     # 
  dss2(v, fps=23.976)                    # set the framerate

[jagabo]

Remember, 32 bit AviSynth scripts can only be opened with 32 bit players/editors. 64 bit AviSynth scripts can only be opened with 64 bit players/editors.

[Selur]

Try this:
a. deinstall all Avisynth installations (this way only tools which come with their own avisynth.dll can open avisynth scripts)
b. open file with Hybrid, open the "Avisynth preview" and see if that works

[LigH.de]

@ EH:

No, Y4M is not a compressed format, it is "raw with header", therefore it is such a huge download. To limit the download size, one would want to use lossless compression, instead, but which archive or video format is as compatible and platform-independent as uncompressed, raw formats? ... That was my thought. But well, with the distribution of libav libraries, the meaning of "compatibility" will widen. Personally I would take "lossless AVC in MP4" as a very compatible exchange format already. Even CRF6 by x264 may be acceptable as "insignificantly lossy" when used as common original among testers.
__

@ vhelp:

If it is inside an archive, one would first download the archive (takes space), then unpack (takes additional space, even if on another drive), and then delete the archive after unpacking. Except there were a tool which could "transparently" unpack an archive during the downloading. That may work with .[t][g|b]z files when supported by the downloader. I even saw web servers which are able to compress files transparently on request while sending them (just add the filename extension in the request). But compress (.z) and gzip are not the most efficient compressors, compared to e.g. RAR or 7zip.

[gonca]

Avisymth preview works fine.

I'm aware of 32 bit / 64 bit issues.

MPC-BE and HC varieties, (portable) hang on the script Version()

Encodes can be done on my system with avisynth, have done it with simple scripts in the past

Haali is installed on my system

[Selur]

If Hybrids Avisynth functionality works you could use avsViewer to preview your script.

[gonca]

avsViewer works but encoding with avisynth functions tends to make hybrid crash, I just found out.

I uninstalled avisynth 2.58 and installed 2.6a. The avisynth.dll was not present in the avisynth folder so I copied yours.
I also used 7zip to view the contents of the installer exe and avisynth.dll is in there

Selur - I just posted in the hybrid thread

[Selur]

The avisynth.dll was not present in the avisynth folder so I copied yours.

either:
a. deinstall Avisnth completely
or
b. install Avisynth 2.6a and replace the avisynth.dll with the one from Hybrid! Note: Avisynth does install it's avisynth.dll into the Windows/SysWOW64 folder on 64bit systems and into the System32 folder on 32bit systems.
-> copying the avisynth.dll from Hybrid into your avisynth folder doesn't help

[hello_hello]

I'm not sure if you've got ffms2 working yet (maybe I'm not following the thread properly) but if it helps at all, here's the version MeGUI is using. (2.20 apparently). I don't know anything about it aside from the fact I copied it from MeGUI's update folder.
I can open the "balanced.mkv" sample from an earlier post with MeGUI which is in turn using AviSynth+ Portable 2.6.0.5. I can open the script MeGUI creates using both MPC-HC and MPC-BE with the version of Avisynth I have installed, which is 2.6.04. It appears not to be a C plugin? I'm running XP. Here's the script MeGUI creates (it works without "threads=1").

Oddly enough the first time I tried to index "balanced.mkv" it resulted in an error which didn't mean anything to me, but I've re-indexed it several times since without a problem.

LoadPlugin("C:\Program Files\MeGUI\tools\ffms\ffms2.dll")
FFVideoSource("D:\balanced.mkv", threads=1)

[gonca]

Uninstalled avisynth completely, again. Installed avisynth 2.6a. Reinstalled hybrid. Copied avisynth.dll from hybrid folder to syswow64, deleting the one that was there already. No joy

[poisondeathray]

Wow... the avisynth gods are not smiling on you

The only other thing I can think of is some conflicting auto load plugin . Clear out all the plugins , .avsi's in the avisynth/plugins folder, except ffms2.dll and try again . Or even completely clear it out and manually load them in the script to be sure

[gonca]

Here is my plugin folder
Do any of these look problematic.
Question --- could BD_RB have anything to do with this since it seems to have some plugins in its folder.
This might get straightened out next time I re-install windows

[poisondeathray]

Put ffms2.dll in a subfolder, so it's not directly at the level of the plugins folders

Open ffms2.avsi, edit the path for LoadCPlugin (it should be the 3rd line), to where the new path of ffms2.dll is, save it

I don't know if this is the same thing, but something similar happened to me on one of my computers where only some programs crashed when initializing avisynth upon opening an .avs script. I traced it to certain versions of ffms2 plugins, and that workaround fixed it. I don't know why or what specific conditions caused it, I couldn't isolate why it only occurred on that computer only

[gonca]

Put ffms2.dll in a subfolder, so it's not directly at the level of the plugins folders

Open ffms2.avsi, edit the path for LoadCPlugin (it should be the 3rd line), to where the new path of ffms2.dll is, save it

I don't know if this is the same thing, but something similar happened to me on one of my computers where only some programs crashed when initializing avisynth upon opening an .avs script. I traced it to certain versions of ffms2 plugins, and that workaround fixed it. I don't know why or what specific conditions caused it, I couldn't isolate why it only occurred on that computer only

Yay!!! It worked
Thanks poisondeathray

I'll do the SSIM tests in a day.

[gonca]

This has been such a PITA to get working that I am running the SSIM test now before something else goes wrong.

[gonca]

SSIM precise results --- balanced fastest highest
Can be posted is spreadsheet is so desired
If any other tests are desired let me know before this whole thing falls apart again

[deadrats]

am i reading that right? fastest had the highest ssim? can you do some tests with x265 and x264?

[gonca]

yes, I double checked when I saw that too
Further tests, sure
I'll use the same source for now to keep things fair

[deadrats]

if you can do some other metrics as well, like PSNR, DSBSF (dark shakari bull sh*t factor), anything else you can think of.

[gonca]

All tests done with 1 pass ABR 4000 kbps
x264 --- ultrafast medium veryslow

[gonca]

x265 --- ultrafast medium veryslow

[gonca]

re other metrics
same sample or other sample resolution etc?

[poisondeathray]

--tune ssim if you 're measuring ssim , --tune psnr if you're measuring psnr

sure it will yield higher metrics, but usually worse subjective image quality