L-SMASH Source

[jpsdr]

Ok, i've figure out the issue.
Like a lot of people, VS2015 doesn't like when things are too tight, it needs space, so writing this :

"Failed to find %s track %" PRIu32 ".\n"

instead of this :

"Failed to find %s track %"PRIu32".\n"

solves the issue.
Is there someone i can provide/send a diff patch by mail to put on the github ?
Or should i try to make a PR ?

[WorBry]

Originally Posted by qyot27

It's L-SMASH itself that would need to be built shared, not L-SMASH-Works. The problem is that L-SMASH only uses -fPIC when building as a shared library. You have basically two options here: rebuild it as shared like TheFluff suggested, or rebuild as static but force the use of -fPIC in the CFLAGS (by appending ./configure with --extra-cflags="-fPIC"). checkinstall should be smart enough to do the general update tango so that you don't have a spare liblsmash.a without -fPIC laying around, but if you'd rather uninstall first, the command would be sudo apt-get purge lsmash.

EDIT: Beat to it. Oh well.

EDIT 2: Also, if you rebuild L-SMASH as shared, the checkinstall command would need the --stripso=yes --addso=yes options added to it.

Thanks all,

And the good news is I'm now up and running, on Kubuntu 15.10 (AMD 64) at least.

No problem opening native HD AVC (mp4 and mov) clips from various camcorders/DLSR's. But I cannot open AVCHD.mts clips from Canon, Panasonic and Sony models at all. Which is a bit frustrating, as it was my main reason for wanting to try L-Smash.

Loading a basic VapourSynth script into VSEditor:

import vapoursynth as vs
core = vs.get_core()
clip = core.lsmas.LWLibavSource(source=r"Path..../TestHFG10.mts",fpsnum=30000,fpsden=1001)
clip.set_output()

Opening Preview, there is brief pause and then VSEditor crashes. An lwi index file is generated though.

Searching for answers I came across this case:

https://github.com/VFR-maniac/L-SMASH-Works/issues/42

Ironically, the downloaded "sample.m2ts" clip from that post opened just fine with LWLibavSource. Tried running a gdb test (as cited in that thread) with my own mts clips:

Example gdb vsedit:
(note, the script file was named LSmashSource.vpy, but it was using LWLibavSource as above)

~$ gdb --args vsedit /home/bryan/Documents/LSmashSource.vpy
GNU gdb (Ubuntu 7.10-1ubuntu2) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>                                                                                                                                                                                                  
This is free software: you are free to change and redistribute it.                                                                                                                                                                                                             
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"                                                                                                                                                                                                     
and "show warranty" for details.                                                                                                                                                                                                                                               
This GDB was configured as "x86_64-linux-gnu".                                                                                                                                                                                                                                 
Type "show configuration" for configuration details.                                                                                                                                                                                                                           
For bug reporting instructions, please see:                                                                                                                                                                                                                                    
<http://www.gnu.org/software/gdb/bugs/>.                                                                                                                                                                                                                                       
Find the GDB manual and other documentation resources online at:                                                                                                                                                                                                               
<http://www.gnu.org/software/gdb/documentation/>.                                                                                                                                                                                                                              
For help, type "help".                                                                                                                                                                                                                                                         
Type "apropos word" to search for commands related to "word"...                                                                                                                                                                                                                
Reading symbols from vsedit...(no debugging symbols found)...done.                                                                                                                                                                                                             
(gdb) run                                                                                                                                                                                                                                                                      
Starting program: /usr/bin/vsedit /home/bryan/Documents/LSmashSource.vpy                                                                                                                                                                                                       
[Thread debugging using libthread_db enabled]                                                                                                                                                                                                                                  
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".                                                                                                                                                                                                     
[New Thread 0x7fffeba4d700 (LWP 2099)]                                                                                                                                                                                                                                         
QWidget::insertAction: Attempt to insert null action                                                                                                                                                                                                                           
[New Thread 0x7fffda18d700 (LWP 2100)]                                                                                                                                                                                                                                         
[Thread 0x7fffeba4d700 (LWP 2099) exited]                                                                                                                                                                                                                                      
[Thread 0x7fffda18d700 (LWP 2100) exited]                                                                                                                                                                                                                                      
[Inferior 1 (process 2095) exited normally]                                                                                                                                                                                                                                    
(gdb) quit

VSEditor opened with "Failed to open the file........" error message.

Not sure where to go next with this. I can post a sample lwi index file if it would give any clues.

No problem opening these AVCHD mts files with LWLibavSource in AVISynth, by the way.

[qyot27]

gdb wouldn't be much use to you the way you've built the libs; it requires leaving all the debug symbols in the binaries (all of them, preferably; FFmpeg, L-SMASH, L-SMASH-Works, VapourSynth, and VSEditor).

If you have the hard drive space, I'd just run the *.mts files through mkvmerge first and only work with the Matroska copies.

[WorBry]

Originally Posted by qyot27

gdb wouldn't be much use to you the way you've built the libs; it requires leaving all the debug symbols in the binaries (all of them, preferably; FFmpeg, L-SMASH, L-SMASH-Works, VapourSynth, and VSEditor).

Ah, OK.

Originally Posted by qyot27

If you have the hard drive space, I'd just run the *.mts files through mkvmerge first and only work with the Matroska copies.

Already tried that. The remuxed mkv files behave the same way as the mts files.

[speedyrazor]

Originally Posted by speedyrazor

Hi, I have hit a problem opening a Quicktime Prores in Avisynth, which has 1 audio track with 10 channels of audio in it. It works with 1 track with 2 audio channels, but with this file that has 10 channels I am getting this error:

LSMASHAudioSource: failed to open resampler.
(C:\Users\me\Desktop\test.avs, line1)

Here is the avs script:

LSMASHAudioSource(source="10_ch_test.mov", track=2)

I am using 'LSMASHSource-AviSynth-plugin-r859-static-32bit'.
I will attached a small movie sample later. Is there anything i can do to get round this, is it a channel limitation?

Kind regards.

Attached is a small 1 frame sample, which shows the error.

[WorBry]

Interesting.

It's not as if I've burned my bridges with Windows and AVISynth though, and I have other reliable options there for AVCHD (DGDecIM) - so it's not such a big deal really.

I just find it a bit odd that the AVISynth version of L-Smash I have installed (r804 in MeGUI) has no problem opening these mts files. And also why this VapourSynth version should open Sony AVHD m2t clips without any issues. So whatever it is that causing this version to choke on (Canon and Panasonic) mts files specifically must surely be pretty minor? Like I said, an index file is generated.

[kuchikirukia]

http://s000.tinyupload.com/?file_id=...36885519263005

DGDecode (CPU=4, info=3) + QTGMC: Works well enough to srestore
LSMASH + QTCMC: Horribly broken
FFMS2 + QTGMC: Horribly broken

Why the vast difference?

[Sharc]

ffms2 (still) has issues with interlaced sources afaik.
Don't know about LSMASH though.

[LigH]

Too few details. Before I download it: What do you mean by "broken"? How does it look without QTGMC? Did you enforce the correct field order (not all source plugins tell them correctly in all cases)?

[kuchikirukia]

Originally Posted by LigH

Too few details. Before I download it: What do you mean by "broken"? How does it look without QTGMC? Did you enforce the correct field order (not all source plugins tell them correctly in all cases)?

It seems to switch to BFF. DGDecode handles this.

[WorBry]

Originally Posted by kuchikirukia

It seems to switch to BFF...

I've just run a few tests with a couple of 1080/50i and 1080/60i AVCHD.mts clips from a Panasonic DSLR and Canon camcorder. I cant test them in Vapoursynth with LWLibavSource because they won't load at all (as reported above). But testing with ffms2 in Vapoursynth the output was definitely BFF. That's on the evidence of the back and to movement of the fields with:

clip = core.std.SeparateFields(clip, tff=True)

...and likewise of the frames after:

clip = haf.QTGMC(clip, Preset='Medium', TFF=True)

Seen both on Preview in VSEditor and after encoding to UTVideo.

Tried adding:

clip = core.std.SetFrameProp(clip, prop="_FieldBased", intval=2)

after ffms2 and before QTGMC, but it made no difference.

Testing the same clips with ffms2 and LWLibavSource in AVISynth, the QTGMC 50/60p encodes (UTVideo YV12) looked OK. But when doing the time honoured field order test:

SeparateFields()
AssumeTFF()

and looking at the movement of the fields in VirtualDub. With ffms2, I noticed that upon seeking to any particular frame, the movement was at "first back and to", suggesting BFF, but then after advancing a number of frames (I didn't count) it reverted back to a TFF pattern. But if I just let the script run through from frame 0 to finish, it looked to be all TFF. Testing with LWLibavSource the field movement pattern was consistently TFF when seeking to any frame.

That's all I can say.

[Sharc]

I did few tests again with ffms2. Forget it as a source filter for interlaced material. It messes up with the field order.
LWLibavVideoSource seems to work. I prefer DG tools though (DGdecNV).

[WorBry]

Originally Posted by Sharc

LWLibavVideoSource seems to work

But not the Vapoursynth version with AVCHD.mts files:

Originally Posted by WorBry

..No problem opening native HD AVC (mp4 and mov) clips from various camcorders/DLSR's. But I cannot open AVCHD.mts clips from Canon, Panasonic and Sony models at all. Which is a bit frustrating, as it was my main reason for wanting to try L-Smash.

Loading a basic VapourSynth script into VSEditor:

import vapoursynth as vs
core = vs.get_core()
clip = core.lsmas.LWLibavSource(source=r"Path..../TestHFG10.mts",fpsnum=30000,fpsden=1001)
clip.set_output()

Opening Preview, there is brief pause and then VSEditor crashes. An lwi index file is generated though.

Searching for answers I came across this case:

https://github.com/VFR-maniac/L-SMASH-Works/issues/42

Ironically, the downloaded "sample.m2ts" clip from that post opened just fine with LWLibavSource......

......Not sure where to go next with this. I can post a sample lwi index file if it would give any clues.

No problem opening these AVCHD mts files with LWLibavSource in AVISynth, by the way.

Is there no interest in fixing this? Despite the DSLR video boom and increasing trend to native progressive HD-AVC, and now UHD-AVC, mov and mp4 formats, there are still a lot of people recording AVCHD.

[TheFluff]

you can't randomly swap ffmpeg dll's around, the abi changes all the damn time, of course it's not gonna work

just link it statically like everyone else; plugins depending on shared libraries is an awful idea

[lansing]

Hi, I wanted to save the cache index file outside the source file location so that I can directly read those huge blu-ray video without extracting to local. I am looking for something like saving them to the same directory as the script file instead.

I had read the document for the cache argument but I couldn't find an option to do it.

[Music Fan]

Originally Posted by lansing

Hi, I wanted to save the cache index file outside the source file location so that I can directly read those huge blu-ray video without extracting to local. I am looking for something like saving them to the same directory as the script file instead.

I had read the document for the cache argument but I couldn't find an option to do it.

You can try cache=false, if I understand well what you need (it creates index outside the RAM), but I believe you can't select directory to write this index.

[dipje]

For the record, I've stopped using FFMS2 (in Vapoursynth) because of issues with 10-bit ProRes and my Sony DSLR AVCHD files (1080p25 / 1080p50).

That's why I switched to l-smash. At the moment, that was the thing that's working.

And it's still working fine on r875 (x64 Vapoursynth that is). So not all AVCHD streams are crashing apparently, mine are still working fine.

[TalasNetrag]

When trying to open a H.264 10bit video, LWLibavVideoSource only return a greenish artefact picture.

[stax76]

It's over a year the author posted here: http://forum.doom9.org/search.php?searchid=7538802

He posted 5 days ago at the issue tracker: https://github.com/VFR-maniac/L-SMASH-Works/issues

For a bug report it's good to have some script, log file and a sample of course.

[sneaker_ger]

Originally Posted by TalasNetrag

When trying to open a H.264 10bit video, LWLibavVideoSource only return a greenish artefact picture.

That's normal. AviSynth only natively supports 8 bit so l-smash's 10/16 bit output looks psychedelic. The simplest way to handle the problem is to tell l-smash to dither down to 8 bit:
LWLibavVideoSource("source.mkv", format="YUV420P8")

http://forum.doom9.org/showthread.php?t=173088
http://avisynth.nl/index.php/High_bi..._with_Avisynth