L-SMASH Source

[LigH]

I remember that there was recently an update to at least ignore Atmos extensions gracefully ... but which software was it?

Ah: LAV Filters 0.63.0 can ignore it now; eac3to may still need an update.

So if LAV Filters can, I wondered if LwLibav could as well. But that might require to port the patch? In the meantime, DDS2Mod might work for AviSynth users.

[the_weirdo]

I've uploaded new builds that linked with Libav libs. Those builds seem to work with files that contain TrueHD+Atmos tracks (though they can't decode those TrueHD+Atmos tracks at all).

EDIT: My bad. Those new builds are broken so I have to pull them down and do more testings before uploading new builds.
EDIT2: As it turned out there's no problem with FFmpeg builds (compare to Libav builds), I won't update Libav builds anymore.

There are some misunderstandings caused by my poor English and bad testing method. So to make thing clearer, builds linked with FFmpeg should be able to decode TrueHD from TrueHD+Atmos tracks (they work with some samples I have) while builds linked with Libav can't decode TrueHD+Atmos tracks at all. As Libav builds now don't offer any advantage over FFmpeg builds, I won't update them anymore.

[LigH]

Ignoring Atmos extensions is fine. As far as I read, their "rendering" is speaker setup dependent... They just should not make demuxing and decoding TrueHD audio tracks fail.

[LigH]

OK, the ffmpeg based L-SMASH Source build r733 was able to load the sample I received; now I hope the other user can handle the whole audio.

[forclip]

LSMASHSource (tested with L-SMASH-Works-r775-20150108-32bit from here) have a memory leak: when indexing unsupported video files, it doesn't freed the memory of the process, and it seems like the whole file is readed into it.
For example

ffmpeg -i "input_file.avs" -vcodec rawvideo -pix_fmt bgra64le -an "output_file.avi"

where "input_file" is a simple AviSynth script:

ColorBars()
Trim(0, 1000)

then load resulting AVI file (2+Gb) into AviSynth

LWLibavVideoSource("D:\Temp\output_file.avi")

While indexing, the memory consumption of the process (AvsP, MPC-HC,..) has increased to the same 2+Gb, and after that

LWLibavVideoSource: failed to get the video track.

Unloading the script doesn't freed the memory.

[stax76]

@VFR maniac

I have a small request:

if this is possible from a avs filter, please write indexing progress to stdout.

[LigH]

May be complicated when it is not connected to any console. But possibly via a debug message API?

[stax76]

In StaxRip I run DGIndex exactly like I run almost all command line apps and it receives progress from DGIndex so it must be in the source code and neuron2 must know it.

[qyot27]

But you're still using a separate CLI program that outputs its progress to stdout to do the indexing; DGDecode.dll isn't what powers the indexing in DGIndex. You'd need to look at FFMS2 and how it interacts with ffmsindex to see how to implement this for LSMASHSource.dll, provided there's a similar reporting structure in place in the code. Or just take the suggestion from the corresponding Github issue and use aui_indexer to generate the indices for LSMASHSource's filters rather than the .dll itself. I don't know if aui_indexer prints its progress or not (and if you want to support XP and pre-SSE2 users, you'll need to recompile it from the provided source).

[Selur]

don't know if aui_indexer prints its progress or not

it doesn't, posted about this at the beginning of this thread which is when I created the issue

[VFR maniac]

Write like the plugin for AviUtl.
I rarely care about the plugin for AviSynth.
I'm busy and lazy.

Hints:
https://github.com/VFR-maniac/L-SMAS...progress_dlg.c
https://github.com/VFR-maniac/L-SMAS...v_input.c#L104
https://github.com/VFR-maniac/L-SMAS...v_source.h#L24
https://github.com/VFR-maniac/L-SMAS...source.cpp#L74

[speedyrazor]

Hi, I am opening very large HD Quicktime Prores files, about 120GB, with LSMASHVideoSource, as I don't want to wait 20 mins for an index.
I am finding using the below avisynth script that it is still taking about 1-2 mins to open my file.
My source quicktime contains 8 channels of audio, which I need to use.
My question is... Is there anything I can do to speed up the opening of my files?

v = LSMASHVideoSource(source="E:\Source22.mov", format="YUY2")
a1 = LSMASHAudioSource(source="E:\Source22.mov", track=2)
a2 = LSMASHAudioSource(source="E:\Source22.mov", track=3)
a3 = LSMASHAudioSource(source="E:\Source22.mov", track=4)
a4 = LSMASHAudioSource(source="E:\Source22.mov", track=5)
a5 = LSMASHAudioSource(source="E:\Source22.mov", track=6)
a6 = LSMASHAudioSource(source="E:\Source22.mov", track=7)
a7 = LSMASHAudioSource(source="E:\Source22.mov", track=8)
a = MergeChannels(a1,a2,a3,a4,a5,a6,a7)
AudioDub(a,v)
ColorMatrix(mode="Rec.709->Rec.601", clamp=0)
Spline64Resize(720, 576)
AssumeFPS(25, 1)

Kind regards.

[speedyrazor]

Hi, When using LSMASHAudioSource with 24 bit audio all I am getting is white noise. Is LSMASHAudioSource compatible with 24 bit audio?

Kind regards.

[Selur]

Not atm. (LWLibavAudioSource is, but that requires an index)

[VFR maniac]

Originally Posted by speedyrazor

Hi, When using LSMASHAudioSource with 24 bit audio all I am getting is white noise. Is LSMASHAudioSource compatible with 24 bit audio?

Kind regards.

Yes, if the CODEC and its configuration are correctly detected.
If not, send such sample please.

[VFR maniac]

Originally Posted by speedyrazor

Hi, I am opening very large HD Quicktime Prores files, about 120GB, with LSMASHVideoSource, as I don't want to wait 20 mins for an index.
I am finding using the below avisynth script that it is still taking about 1-2 mins to open my file.
My source quicktime contains 8 channels of audio, which I need to use.
My question is... Is there anything I can do to speed up the opening of my files?



Kind regards.

Because the internal indexing occurs per each clip (video and individual audio channels), I guess.
To solve this, we need an implementation like the following method.

clip = LSMASHSource(source="source.mov")
v = LSMASHGetTrack(clip, track=1)
a1 = LSMASHGetTrack(clip, track=2)
a2 = LSMASHGetTrack(clip, track=3)
a3 = LSMASHGetTrack(clip, track=4)
a4 = LSMASHGetTrack(clip, track=5)
a5 = LSMASHGetTrack(clip, track=6)
a6 = LSMASHGetTrack(clip, track=7)
a7 = LSMASHGetTrack(clip, track=8)
a = MergeChannels(a1,a2,a3,a4,a5,a6,a7)
AudioDub(a,v)

I don't know if it can be achieved within AviSynth API restrictions.

[Selur]

Is there anything I can do to speed up the opening of my files?

you could create the index before opening the file,...
Just out of curiosity how large is the index file?

[speedyrazor]

Originally Posted by VFR maniac

Yes, if the CODEC and its configuration are correctly detected.
If not, send such sample please.

Hi, thanks for you response. I have sent you a PM with a link to a small test file.
I have tried using various source videos, all prores, all with 24 bit audio, I have also tried various settings, but all come out with white noise (same files with 16 bit audio work fine).
The sample I sent you is a typical prores file with multichannel 24 bit audio.
Thanks for your help.

Kind regards.

[speedyrazor]

Originally Posted by Selur

you could create the index before opening the file,...
Just out of curiosity how large is the index file?

OK, so using only LWLibavVideoSource for a 90 min HD Prores at 113 GB, it took 12 mins to index and produced a 457 MB file.
This was using a 10 GB network with media which was on a network share.
Here is the AVS script I used.

LWLibavVideoSource(source="J:\Folder\test.mov", format="YUY2")

Kind regards.

[VFR maniac]

Originally Posted by speedyrazor

Hi, thanks for you response. I have sent you a PM with a link to a small test file.
I have tried using various source videos, all prores, all with 24 bit audio, I have also tried various settings, but all come out with white noise (same files with 16 bit audio work fine).
The sample I sent you is a typical prores file with multichannel 24 bit audio.
Thanks for your help.

Kind regards.

Should be fixed @ L-SMASH rev1339 + L-SMASH Works rev782
Thank you for sending a sample.