FFmpegSource - Page 147

rgr · 10th April 2024, 22:51

Quote:

Originally Posted by Myrsloik

Eactly what did you open that took 30 minutes? And what did you read it from? I'm curious now

Video from HDMI recorder -- 22GB, 4h long, H265.

Opened from .avs file via BSSource. Creating the cache file took so long.

LigH · 11th April 2024, 08:53

Well, there are file formats which are hard to parse, because it requires sequential reading across the whole file, due to the lack of a header which contains a lot of useful information (like a list of GOP start positions) right in the beginning. TransportStreams, as used in Digital Broadcast, are such a case. Raw H.264/H.265 video streams too, they would strictly even require parsing bit by bit, fortunately most are conveniently aligned at least at byte boundaries.

rgr · 11th April 2024, 11:03

Yes, but ffms2 or Libav do it much faster, so there is room for improvement.

LigH · 11th April 2024, 13:42

Ah, okay; I guess BestSource needs its own thread then, I did not notice you mean "BS in contrast to FFMS2 and LSW".

rgr · 11th April 2024, 15:30

So to be in line with the topic, I will write that ffms2 does not want to support long paths -- with 219 characters (including national ones) I get:

Code:

[in#0 @ 000002752ddb7a00] Error opening input: Unknown error occurred
Error opening input file testXXX.avs.
Error opening input files: Unknown error occurred

11th April 2024, 08:53	#2922 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 6,782	Well, there are file formats which are hard to parse, because it requires sequential reading across the whole file, due to the lack of a header which contains a lot of useful information (like a list of GOP start positions) right in the beginning. TransportStreams, as used in Digital Broadcast, are such a case. Raw H.264/H.265 video streams too, they would strictly even require parsing bit by bit, fortunately most are conveniently aligned at least at byte boundaries. __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

11th April 2024, 13:42	#2924 \| Link
LigH German doom9/Gleitz SuMo Join Date: Oct 2001 Location: Germany, rural Altmark Posts: 6,782	Ah, okay; I guess BestSource needs its own thread then, I did not notice you mean "BS in contrast to FFMS2 and LSW". __________________ New German Gleitz board MediaFire: x264 \| x265 \| VPx \| AOM \| Xvid

11th April 2024, 15:30	#2925 \| Link
rgr Registered User Join Date: Jun 2022 Posts: 53	So to be in line with the topic, I will write that ffms2 does not want to support long paths -- with 219 characters (including national ones) I get: Code: [in#0 @ 000002752ddb7a00] Error opening input: Unknown error occurred Error opening input file testXXX.avs. Error opening input files: Unknown error occurred

11th April 2024, 11:03	#2923 \| Link
rgr Registered User Join Date: Jun 2022 Posts: 53	Yes, but ffms2 or Libav do it much faster, so there is room for improvement.