FFmpegSource

[tuanden0]

ffms2-7c36121-win64 (https://drive.google.com/open?id=18W6Hg1xEf78FOvL5lFp_YFQAQ368K15W)

New build with libdav1d and also applied the modified patch.

Libraries:
FFmpeg 4.2-dev-93320-g5ab44ff20c
libdav1d 0.2.1-7f7b5586

I got error "There is no function named 'FFAudioSource'" when using it with AVS :confused:

[Groucho2004]

I got error "There is no function named 'FFAudioSource'" when using it with AVS :confused:
1. Post your script
2. Run Avisynth Info Tool from my signature

[Morku]

I got error "There is no function named 'FFAudioSource'" when using it with AVS :confused:

Same here with 'ffvideosource("MVI_0001.MOV")'
Build of HolyWu is fine.

[OS/Hardware info]
Operating system: Windows 10 (x64) (Build 17763)

CPU: Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz / Coffee Lake (Core i7)
MMX, SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, FMA3, AVX, AVX2
6 physical cores / 12 logical cores


[Avisynth info]
VersionString: AviSynth+ 0.1 (r2772, MT, x86_64)
VersionNumber: 2.60
File / Product version: 0.1.0.0 / 0.1.0.0
Interface Version: 5
Multi-threading support: Yes
Avisynth.dll location: C:\Windows\SYSTEM32\avisynth.dll
Avisynth.dll time stamp: 2018-12-20, 12:55:16 (UTC)
PluginDir2_5 (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64
PluginDir+ (HKLM, x64): C:\Program Files (x86)\AviSynth+\plugins64+


[CPP 2.5 Plugins (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64\avstp.dll [1.0.3.0]
C:\Program Files (x86)\AviSynth+\plugins64\colormatrix.dll [2.5.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\dfttest.dll [1.9.4.0]
C:\Program Files (x86)\AviSynth+\plugins64\dither.dll [2015-12-30]
C:\Program Files (x86)\AviSynth+\plugins64\EEDI2.dll [0.9.2.0]
C:\Program Files (x86)\AviSynth+\plugins64\LSMASHSource.dll [2018-05-30]
C:\Program Files (x86)\AviSynth+\plugins64\TDeinterlace.dll [1.1.0.0]

[CPP 2.6 Plugins (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64+\ConvertStacked.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\DirectShowSource.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\ImageSeq.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\Shibatch.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\TimeStretch.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64+\VDubFilter.dll [2018-12-20]
C:\Program Files (x86)\AviSynth+\plugins64\AutoAdjust.dll [2.6.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\Average.dll [0.94.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\aWarpsharpMT.dll [2.0.1.0]
C:\Program Files (x86)\AviSynth+\plugins64\DCTFilter_avx2.dll [0.5.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\Deblock.dll [2013-12-03]
C:\Program Files (x86)\AviSynth+\plugins64\DePan.dll [2.13.1.3]
C:\Program Files (x86)\AviSynth+\plugins64\DePanEstimate.dll [2.10.0.2]
C:\Program Files (x86)\AviSynth+\plugins64\eedi3.dll [0.9.2.3]
C:\Program Files (x86)\AviSynth+\plugins64\fft3dfilter.dll [2.6.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\FrameRateConverter-x64.dll [2017-09-02]
C:\Program Files (x86)\AviSynth+\plugins64\grunt-x64.dll [2016-05-17]
C:\Program Files (x86)\AviSynth+\plugins64\KNLMeansCL.dll [2018-01-29]
C:\Program Files (x86)\AviSynth+\plugins64\masktools2.dll [2.2.18.0]
C:\Program Files (x86)\AviSynth+\plugins64\mvtools2.dll [2.7.40.0]
C:\Program Files (x86)\AviSynth+\plugins64\nnedi3.dll [0.9.4.51]
C:\Program Files (x86)\AviSynth+\plugins64\RgTools.dll [0.97.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\SmoothAdjust.dll [3.2.0.0]
C:\Program Files (x86)\AviSynth+\plugins64\svpflow1.dll [4.2.0.133]
C:\Program Files (x86)\AviSynth+\plugins64\svpflow2.dll [4.2.0.145]
C:\Program Files (x86)\AviSynth+\plugins64\TIVTC.dll [1.0.11.0]
C:\Program Files (x86)\AviSynth+\plugins64\vinverse.dll [2013-11-30]
C:\Program Files (x86)\AviSynth+\plugins64\yadifmod2.dll [0.0.2.0]

[Scripts (AVSI)]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.avsi [2016-07-05]
C:\Program Files (x86)\AviSynth+\plugins64\AnimeIVTC.avsi [2018-04-17]
C:\Program Files (x86)\AviSynth+\plugins64\Deblock_QED.avsi [2017-05-05]
C:\Program Files (x86)\AviSynth+\plugins64\dither.avsi [2015-12-30]
C:\Program Files (x86)\AviSynth+\plugins64\FFMS2.avsi [2019-02-22]
C:\Program Files (x86)\AviSynth+\plugins64\FrameRateConverter.avsi [2017-09-03]
C:\Program Files (x86)\AviSynth+\plugins64\LSFmod.avsi [2018-07-13]
C:\Program Files (x86)\AviSynth+\plugins64\QTGMC.avsi [2019-02-21]
C:\Program Files (x86)\AviSynth+\plugins64\SMDegrain.avsi [2019-02-18]
C:\Program Files (x86)\AviSynth+\plugins64\Srestore.avsi [2019-02-21]

[Uncategorized DLLs (64 Bit)]
C:\Program Files (x86)\AviSynth+\plugins64\ffms2.dll [2019-03-11]

[Uncategorized files]
C:\Program Files (x86)\AviSynth+\plugins64+\colors_rgb.txt [2016-07-05]
C:\Program Files (x86)\AviSynth+\plugins64\ffmsindex.exe [2019-03-11]

[Groucho2004]

Same here with 'ffvideosource("MVI_0001.MOV")'I have no idea what to make of this ffms2.dll. PE Explorer seems to think it's corrupt. There are no exports whatsoever.

@Wolfberry
I presume you tested this build so it worked in your environment. Any idea why it does not work for others?

[ChaosKing]

Maybe it was compiled only with vapoursynth support? It only works in VS on my machine.

[ChaosKing]

I can't get it to work in avs or via avs.Loadplugin. How did you test it in VS?

I get some "FunctionExists not implemented" messages in VS with core.avs.LoadPlugin(r"D:\ffms2.dll"),
but clip = core.avs.FFVideoSource(r"D:\amy.mkv") or clip = core.avs.ffms2(r"D:\amy.mkv") doesn't work.

[tuanden0]

I am using the meson build system by HolyWu: https://github.com/FFMS/ffms2/pull/338

The src/avisynth source files are indeed missing.

I compiled a new build (https://drive.google.com/open?id=1U8uIYflE8sbEJkNyN90Yv3oZpJTgqu8H) with AVS+ headers

Tested by using core.avs.LoadPlugin and it loads.
Libraries are the same as the previous build.
I tried your new build but still missing FFAudio Source :confused:

Here's my script:
a=FFAudioSource("E:\Download\Source\Discovery\[JAV-11] Sora Aoi Collection.mkv")
a=AssumeFPS(a, 24000, 1001)
c=FFVideoSource("E:\Download\Source\Discovery\[JAV-11] Sora Aoi Collection.mkv",colorspace="YV12")
c=AssumeFPS(c, 24000, 1001)
AudioDub(c,a)

[filler56789]

I understand why there are no avisynth support in the autotools / meson build system.

Because gcc compiled plugins will not work in (msvc compiled) avisynth, so no avisynth support unless I can build it with msvc (so far it fails miserably)

Are you really sure of that? :confused:

When you say gcc, ¿don't you mean «a NON-MinGW-w64 toolchain»? :confused:

[Groucho2004]

Are you really sure of that? :confused:

When you say gcc, ¿don't you mean «a NON-MinGW-w64 toolchain»? :confused:
Avisynth C++ plugins must be built with MSVC or Intel C/C++ compiler (which uses MSVC libraries and linker).
Avisynth C-plugins however can be also be built with GCC.

[filler56789]

Avisynth C++ plugins must be built with MSVC or Intel C/C++ compiler (which uses MSVC libraries and linker).
Avisynth C-plugins however can be also be built with GCC.

Thanks for the clarification *THUMBS UP*

[VS_Fan]

Problem in AviSynth: Does this build support it?
Script error: ffindex does not have a named argument "uft8"

[VS_Fan]

It's working fine. I must have made some mistake. thanks again

[LigH]

I'm not sure which parameter would support a text codepage ... but if there is any at all: It's UTF, not UFT.

[Nico8583]

Hi :)
Could you tell me the difference between original releases, Wolfberry's releases and HolyWu's releases ?
I would like to use it with latest AviSynth+ MT in order to decode 1080p/4K video.
Thank you !

[Wolfberry]

My builds are for VapourSynth only.

HolyWu builds are AviSynth+ compatible and use newer libraries than the official one on GitHub, so you should use that.

[Nico8583]

Thank you ;)

[Nico8583]

I'm trying to open an AVS (.264 file extracted from a Blu ray with tsMuxeR) with FFmpegSource2 but it doesn't work.
I use "ffms2-r1273+4-win64-20190401" and "AviSynthPlus-MT-r2772".
The ffindex is created but if I try to encode with x264, it starts but nothing happen and if I try to open it with MPC-BE, it stays at "Opening'.
My AVS script is very simple :
LoadPlugin("ffms2.dll")
FFmpegSource2("D:\MyFile.264")
Could you help me ?
Thank you !

[sneaker_ger]

How long did you wait? FFmpegSource2 needs to index the file first. If the file is big and your HDD slow it can take minutes.

[Nico8583]

I tried 2 ways : let the AVS create the ffindex and create manually the ffindex then launch encoding/playing. Same result.

[sneaker_ger]

How long did you wait? How big is your file? How fast is your HDD (SSD?)?

[Nico8583]

I've deleted ffms2.dll and ffmsindex.exe from plugins64's AviSynth+ folder and copy it locally in the AVS folder and now it works.
Thank you for the help and sorry for inconvenience.

[LigH]

By the way, this is a raw video stream. FFVideoSource is sufficient here.

[dandyclubs]

megui 2908 x64
ffms2-r1273+4-win64-20190401
AviSynthPlus-MT-r2772

i replace ffms2.dll and ffmsindex.exe from ffms2-r1273+4-win64-20190401

bluray to mkv by megui hd streams extractor

make avs file by megui file indexer ffmsindex

but

megui hang when open avs script creator windows

error clould not read avs frame

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

[stax76]

Is there a recent build that is not using the C interface and supports both avs and vs. I cannot use the C interface in staxrip because it is leaking memory.

[StainlessS]

Is there a recent build that is not using the C interface and supports both avs and vs. I cannot use the C interface in staxrip because it is leaking memory.
HolyWu post #2465, ffms2-r1273+4-win64-20190401.7z :- https://forum.doom9.org/showthread.php?p=1870563#post1870563
Is CPP, NON XP, Avs+ 64 bit(no x86 dll), supporting 10Bit, Only tested with 1920x1080 YUV422P10. (VS not tested, but has a VapourSynthPluinInit according to DependencyWalker).
Missing doc:- https://github.com/FFMS/ffms2/blob/master/doc/ffms2-avisynth.md

Older HolyWu version that is same as above:- ffms2-20181016-f3c6b00-win64.7z
https://forum.doom9.org/showthread.php?p=1858199#post1858199

EDIT: There is yet another at post 2489, ffms2-20190214-7c36121-win64.7z, Untested.

[stax76]

@StainlessS

I tried 2019-04-01 and it appears to have a memory issue as well.

[StvG]

You can try this (http://www.mediafire.com/file/yhctxufbr4pztd4/ffms2.7z/file) version too.

[stax76]

Thanks, I get this error:

Indexing using ffmsindex failed with exit code: -1073741511 (0xC0000139)
The exit code might be a system error code: {Entry Point Not Found}
The procedure entry point hs could not be located in the dynamic link library hs.

[StvG]

Can you try indexing with ffms2 (ffvideosource() will index the file)?

[stax76]

For staxrip I would need ffmsindex.

[StvG]

I added ffmsindex (same download link).
Do you have installed Visual C++ Redistributable for Visual Studio 2015+ (https://support.microsoft.com/en-us/help/2977003/the-latest-supported-visual-c-downloads)?

[stax76]

ffmsindex and memory management is working now, thanks! :thanks:

[StainlessS]

STvG,
How did you modify the zip on MediaFire without editing your original post #2483 link ? (Is it a paid MediaFire account option).

Thanx in advance.

[StvG]

I used trial upload option (without creating account). A pop up window appeared with options skip/replace/keep both when I uploaded the updated ffms2.7z (same file name as the previous one). I replaced the old file with the new one and the shared link is kept.
Other cloud services have an additional option to keep both files with same file names but without renaming any of them - old one is hidden and there is option to see versions of the files. Maybe MediaFire has this option too but just it's not available without account.

[StainlessS]

Thanks StvG,
I've had a little look around but dont see anything obvious to replace file using same link (Free Account).
If anyone has located MediaFire method to replace file for same link (in free of paid acc), then please post a howto somwhere, cheers.

[ChaosKing]

@StainlessS Have you considered hosting your stuff on github?
If a "stable link" is important, maybe dropbox is also an option for you.

[StainlessS]

@StainlessS Have you considered hosting your stuff on github?


Yes thanks, I considered it last time you suggested it :)
still same response though, not lookin' forward to figuring out the GIT stuff, maybe one day.

[stax76]

:thanks:

[frank]

HolyWu's release of ffms2 has the seek issue at ts streams again but the version (2.31.00 ??) from StvG is ok and much smaller.

StvG, how did you compile it?

[StvG]

My build has reverted those commits (https://forum.doom9.org/showpost.php?p=1848947&postcount=97). I didn't include any additional libraries (only ffmpeg release/4.1) but I guess the big difference in sizes comes from different compilers (I used msvc).

Here (https://www.sendspace.com/file/dvfvki) can be downloaded a newer build. It has reverted this commit (https://github.com/FFMS/ffms2/commit/722a02d77685e94c7aa7f39b6b38666d544cacb7) which should fix that issue (https://github.com/FFMS/ffms2/issues/345). Also it has removed the same thing related to AVC (https://github.com/FFMS/ffms2/blob/master/src/core/videosource.cpp#L189) which should fix an issue with 1 frame off.

[Wolfberry]

I didn't include any additional libraries
Your FFmpeg build doesn't have zlib? That's an additional library outside of FFmpeg source code.
but I guess the big difference in sizes comes from different compilers (I used msvc).

I will guess the size difference is beacause the Holywu build has more additional libraries than your build (libaom, libopenjpeg...)

[StvG]

Your FFmpeg build doesn't have zlib? That's an additional library outside of FFmpeg source code...

It has zlib.

[ChaosKing]

I've made a seeking test with "StvG ffms2" and it performs the same as "ffms2_test8.dll" https://forum.doom9.org/showthread.php?t=176231

[StvG]

Can you show which samples are VP9.mkv and VC1.mpg in your test?
Thanks

[ChaosKing]

Can you show which samples are VP9.mkv and VC1.mpg in your test?
Thanks

https://www.dropbox.com/sh/bxwibb20m8rnnro/AABmPSXEWGgE7nBK-PvwyU6Aa?dl=0

I wished the newer ffmpeg (ffms2) versions would also be frame accurate for the h264 mp4 files...

[videoh]

DGDecNV works good for that use case. If you have an nVidia card I can give you a free license (also any other Doom9 developers or contributors, just shoot me a PM).

[FranceBB]

I'm trying to index a DCP sample which has been exported in XYZ 4:4:4 12bit, however FFVideoSource seems to internally convert it to YUV 4:4:4 12bit.
Now I'm wondering... is there a way to let FFVideoSource output XYZ rather than YUV if someone wants to?
I mean, don't get me wrong, the idea of having the conversion done automatically is fine, but what if someone wants to get the original XYZ color space?

Images of what I mean:
Indexing (YUV) (https://i.imgur.com/WB4raGy.jpg) - Source (XYZ) (https://i.imgur.com/4NXvKJa.png)

Thank you in advance,
Frank.

[LigH]

AviSynth source filters can only output color spaces supported by AviSynth. At least to an AviSynth clip variable, to give following video filters any sensible meaning.

Regarding a "conversion" between XYZ and YUV, it might even just directly translate unknown color space components without any matrix math.

To receive different formats explicitly, it would have to be able to write a separate output file...

Does this "XYZ" refer to the CIE XYZ 1931 color space?

[Myrsloik]

I'm trying to index a DCP sample which has been exported in XYZ 4:4:4 12bit, however FFVideoSource seems to internally convert it to YUV 4:4:4 12bit.
Now I'm wondering... is there a way to let FFVideoSource output XYZ rather than YUV if someone wants to?
I mean, don't get me wrong, the idea of having the conversion done automatically is fine, but what if someone wants to get the original XYZ color space?

Images of what I mean:
Indexing (YUV) (https://i.imgur.com/WB4raGy.jpg) - Source (XYZ) (https://i.imgur.com/4NXvKJa.png)

Thank you in advance,
Frank.

VapourSynth might pass it through and there's a slight chance it'd be somewhat correctly flagged as well. I have no idea what you'd do with it next though since there's not much that can correctly work with the format.

[FranceBB]

Does this "XYZ" refer to the CIE XYZ 1931 color space?

Yes, CIE XYZ 1931.

VapourSynth might pass it through and there's a slight chance it'd be somewhat correctly flagged as well. I have no idea what you'd do with it next though since there's not much that can correctly work with the format.

I see... Well, although it's represented correctly, the idea would be to convert XYZ 1931 with my LUT rather than relying on the indexer to do that, but that's just a guess. I believe that for the vast majority of people having it in YUV 4:4:4 12bit planar is absolutely fine.