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,..)
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
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,..)
Quote: ↑ 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