L-SMASH Source

[qyot27]

Originally Posted by Sparktank

I don't know, I'm no programmer, but a public repository might help a lot of experienced users.

There always was?
https://github.com/VFR-maniac/L-SMASH-Works

And there was some recent activity in one of the forks:
https://github.com/hydra3333/L-SMASH-Works

Of course, that does require building L-SMASH itself and [FFmpeg or Libav] first, and then the LSMASHSource AviSynth plugin. For the VapourSynth plugin, all of that can be done in GCC, for the AviSynth plugin, you have to use MSVC and manually copy things like AviSynth's headers/lib around first.

[Sparktank]

Thanks for those!

Especially for the hydra3333 fork.

I never really thought to search for it on github in case someone created a fork.

It'll be nice to check on the commits.

[LigH]

As I did not install any MSVC, I'll have to wait for a new binary AviSynth compatible release by anyone else then...

[LigH]

But there is noone else?

[DJATOM]

x64 version (AvisynthPluginInit3) with ffmpeg libs built near 1 month ago: https://mega.nz/#!GTxkmbJD!FgOYX1dJV...Em5BmZ2nwM4xiw
x86 will require building 32 bit libs for linking, I'm too lazy for this.

[MysteryX]

Originally Posted by MysteryX

There's a nasty bug in LWLibavVideoSource causing misplaced frames under certain circumstances
https://forum.doom9.org/showthread.p...89#post1814489

This bug still hasn't been resolved, so I'll post it again.

[MysteryX]

I was reading this about FFSM2. Does the same issue apply to L-SMASH Source when not using cache file?

FFAudioSource will have to remake any index implicitly created by FFVideoSource and therefore code like
AudioDub( FFVideoSource(X), FFAudioSource(X) )
will require two indexing passes. Apart from the time consumed this is harmless. To work around it open the audio first.

[LigH]

IIRC, only one of them required this quirk, so if it was FFMS2, it's not LSW. But it doesn't hurt to write scripts in this order (if you need audio at all, use it first) in any case.

[masterkivat]

Originally Posted by DJATOM

x64 version (AvisynthPluginInit3) with ffmpeg libs built near 1 month ago: https://mega.nz/#!GTxkmbJD!FgOYX1dJV...Em5BmZ2nwM4xiw
x86 will require building 32 bit libs for linking, I'm too lazy for this.

I hope someone can provide a 32-bit build anytime soon

[l33tmeatwad]

So this was kind of a pain to figure out so I decided I would post some build notes to help anyone else out trying to compile their own. The static libs build is a single DLL file and the shared libs contains the libav DLLs.

LSMASHSource r941 (hydra3333 Mod)
Static Libs Build (x86 & x64) | Shared Libs Build (x86 & x64) | Sources
Bonus: FFMS2 with Shared Libs

Build Notes:
Compiled with Microsoft Visual Studio 2015
Shared Libs & Include Files were copied to the Visual Studio Directories in: C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC
Patch included with previous releases was applied to FFmpeg before compiling.

Static FFmpeg compiled with:

./configure --toolchain=msvc --enable-gpl --enable-version3 --disable-encoders --disable-programs --disable-filters \
 --disable-network --disable-doc --disable-avdevice --disable-swresample --disable-postproc --disable-avfilter --enable-avresample
make install

Shared Libs FFmpeg compiled with:

./configure --toolchain=msvc --enable-gpl --enable-version3 --enable-shared --disable-encoders --disable-programs --disable-filters \
--disable-network --disable-doc --disable-avdevice --disable-swresample --disable-postproc --disable-avfilter --enable-avresample
make install

Visual Studio Project Modifications (x86 Static Build)
Project Properties > Configuration Properties > VC++ Directories
- Include Directories: C:\msys32\usr\local\include
- Library Directories: C:\msys32\usr\local\lib
Project Properties > Configuration Properties > Linker > General
- Additional Library Directories: C:\msys32\usr\local\lib
Project Properties > Configuration Properties > Linker > Input
- Additional Dependencies: libavutil.a;libavcodec.a;libavformat.a;libswscale.a;libavresample.a;

Visual Studio Project Modifications (x64 Static Build)
Project Properties > Configuration Properties > VC++ Directories
- Include Directories: C:\msys64\usr\local\include
- Library Directories: C:\msys64\usr\local\lib
Project Properties > Configuration Properties > Linker > General
- Additional Library Directories: C:\msys64\usr\local\lib
Project Properties > Configuration Properties > Linker > Input
- Additional Dependencies: libavutil.a;libavcodec.a;libavformat.a;libswscale.a;libavresample.a;

Changes to exlibs.cpp (both Static Builds)

//#pragma comment( lib, "libmingwex.a" )
//#pragma comment( lib, "libgcc.a" )
#pragma comment( lib, "lsmash.lib" )
#pragma comment( lib, "bcrypt.lib" )
//#pragma comment( lib, "avutil.lib" )
//#pragma comment( lib, "avcodec.lib" )
//#pragma comment( lib, "avformat.lib" )
//#pragma comment( lib, "swscale.lib" )
//#pragma comment( lib, "avresample.lib" )

Changes to exlibs.cpp (both Builds w/ Shared Libs)

//#pragma comment( lib, "libmingwex.a" )
//#pragma comment( lib, "libgcc.a" )
#pragma comment( lib, "lsmash.lib" )
#pragma comment( lib, "avutil.lib" )
#pragma comment( lib, "avcodec.lib" )
#pragma comment( lib, "avformat.lib" )
#pragma comment( lib, "swscale.lib" )
#pragma comment( lib, "avresample.lib" )

Included Libs:
LibAV (from FFmpeg 4.0)
L-Smash 2.14.5

Other Software:
MSYS2 (i686 & x86_64)
Yasm 1.3.0 (General Use Executables)

[poisondeathray]

Thanks for the updated build

[LigH]

[poisondeathray]

Would it be possible to build an updated vapoursynth vslsmashsource.dll companion please ?

[l33tmeatwad]

Added a copy of FFMS2 that works with the same shared libs in case that's useful for someone, to like safe space and stuff maybe?

[LigH]

That's an interesting bonus. Let's hope they work well.

[l33tmeatwad]

Originally Posted by poisondeathray

Would it be possible to build an updated vapoursynth vslsmashsource.dll companion please ?

That's low on my priority list, but I'll see what I can do.

When decoding 10-bit YUV 4:2:0, is there a need/way to specify whether the source is Rec.709 or Rec.2020? My source is Rec.709.
I'm using this bit of code from the wiki:

## Decoding 10bit, YUV 4:2:0 source
LSMASHVideoSource(<path>, stacked=true, format="YUV420P10")
ConvertFromStacked(bits=10)

It works. I'm just wondering if there's anything else that I need to add.

[sneaker_ger]

Not in that simple script because you are not doing any "real" color conversions (like YUV to RGB or vice versa), only changing the storage format. (But you should set the correct flags in the encoder like x265/x264 you feed the script to.)

[Yanak]

Hello and thank you for the update of L-SMASH,

Previously i was using the FFMS2 shipped with Staxrip ( version 2.23.1 too apparently ), to give it a try I replaced it by the one released with libs and tried to open a .GIF file as input/source and it does not like this :

Indexing using ffmsindex failed with exit code: -1073741701 (0xC000007B)

Tried some other files and getting the same kind of error messages with some MKV's or MP4's containers having some x264 streams inside.

Then tried to replace the ffmsindex.exe provided in the zip file by the one shipped in Staxrip (while keeping all other dll's you provided) and it seems to work like this, not sure what is going on.

Noticed that here https://github.com/FFMS/ffms2/releases there is a different ffmsindex.exe for both x86 and x64 ( hash is different ), while on your release a single one is provided for both, not sure if normal or not.

Using win7 x64 and all the workflow in Staxrip is x64 if this helps.

Thanks a lot

Edit : command used triggering the problem when i use your release:

LoadPlugin("H:\StaxRip-x64-1.7.0.6-test\Apps\Plugins\both\ffms2\ffms2.dll")
FFVideoSource("H:\test.mkv", colorspace = "YUV420P8", \
              cachefile = "H:\TEMP\test_temp\test.ffindex")

Originally Posted by sneaker_ger

Not in that simple script because you are not doing any "real" color conversions (like YUV to RGB or vice versa), only changing the storage format.

Thanks! I should have thought of that. May I ask how I convert the video to 10-bit RGB? (The source is progressive, and I'm using Avisynth+.)

Sorry for this! I've looked at the Wiki but can't work it out. I've never worked with a 10-bit source before...