FFmpegSource2 !

[ToiletDuck]

For me FFVideoSource works fine for 2k, 4k, 8k content, like mentioned before, enabling hardware decoding might help.
LWlibavsource needs to create the index file, since it only creates the index file inside the RAM.
Hybrid does not support cache=false for LWlibavsource, since it will try to create the cache file next to the source.
iirc there was a tool named aui_indexer  which was able to create the lwi index files and one could load those files as source in LWlibavsource, but there were some issues with it and I haven't seen a .exe build of it for ages,...
(personally, I usually use DGDecNV for m2ts content,..)

so , do i read this ↑ right.. Only LWlibavsource creates index files, not ffmpegsource2 ?  I ask, because awhile ago you wrote that there alway's need to be index file created for filter preview.  So i thought, in any situation regardless of wich setting...

↑ that's one of the main reasons i like to use ts output, to automatically calculate overhead..

create a 2hr movie with low bit rate and look at the overhead,...
I doubt you can 'guess' the overhead correctly +/-  a few mb,...
Cu Selur
Ps.: Last version of aui_indexer seem to be from 2017: https://onedrive.live.com/?authkey=%21AN...75AC8933C6

i know, the difference in filesize between .mkv, mp4 etc and TS file is how you know too..  Again, depends how large the video & AUDIO track is aswell  !!

Like for an audio track of 7-8 GB, overhead is like 3 GB for crying out loud when you remux to a *.ts file..  
Overhead is much less when the audio track is like 3 - 4 GB naturaly... 

That's what i have found out..

so yes, once you know the filesize of the tracks (demuxed) you can pretty much guess the final filesize of an TS file ..  (give or take ... a few hundred MB's   )



cheers,
TD