One reason may be that raw H.264 video may lack some important attributes you can usually only keep in a surrounding container format (e.g. And there are hardly any source filters which can read it in raw format. It won't use LSMASHVideoSource, because M2TS is not a derivative of ISO Base Media containers and LSMASHVideoSource would not write an index file either, even if the container would be supported, instead it would rely on a keyframe index chunk in the container.īut a raw H.264 video file has no container. Indeed, the File Indexer can use L-SMASH Works to use LwLibavVideoSource for indexing an MPEG-2 TransportStream container (M2TS). Just to play naive: Does your abbreviated "with L-SMASH" mean exactly "with LSMASHVideoSource" (this source filter) or "with L-SMASH Works" (this AviSynth plugin = LSMASHSource.dll)? You can either use the script as the source video for MeGUI's script creator, or you can use the *.lwi index file as the source.įor what sort of file type? It probably will be if the m2ts/ts file contains mpeg2 video, although I don't work with m2ts files much, so I can't remember for certain. If you have Avisynth installed you could open it with any program capable of opening scripts. The first time you open the script, L-Smash should create an index file. LoadPlugin("C:\Program Files\MeGUI\tools\lsmash\LSMASHSource.dll") You can work around it by creating a script to open a h264 file yourself. I guess that functionality was never added. MeGUI's file indexer (MeGUI 2672) will definitely index m2ts files with L-Smash for me.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |