FFMpegCore/FFMpegCore.Test
crypton 83c9478007 ffprobe duration parsing
- on large recordings (e.g. radio transmissions), ffprobe might return number of hours which is too large for TimeSpan.Parse (exception: The TimeSpan string '149:07:50.911750' could not be parsed because at least one of the numeric components is out of range or contains too many digits.)
- use regex groups to extract components (hours/minutes/seconds/millis) then parse/create new timespan from that
- NOTICE: this will discard microseconds provided by ffprobe, not sure if this is significant
- ffprobe has inconsitencies with how it represents millisecond component. Sometimes it may return just `82` for 820 milliseconds, so padding with 0s is required on the left. Likewise, sometimes it might return microseconds past milliseconds (first 3 significant figures); this is currently discarded
- Added InternalsVisibleTo to help with unit testing *just* the duration parsing function


Former-commit-id: 35ca34c0b0
2021-02-06 16:50:12 -08:00
..
Resources Reencode raw file 2020-12-07 17:41:31 +01:00
ArgumentBuilderTest.cs Dump 2020-12-07 00:47:47 +01:00
AudioTest.cs Convert to mp3 instead of opus 2020-12-07 17:52:47 +01:00
BitmapSources.cs Fixed color pallette (#58) 2020-05-12 18:26:52 +03:00
ffmpeg.config.json Major refactoring 2020-05-08 11:07:51 +02:00
FFMpegCore.Test.csproj Test with .NET 5.0 2020-12-07 18:07:23 +01:00
FFMpegOptionsTests.cs Minor cleanup 2020-05-12 22:47:57 +02:00
FFProbeTests.cs ffprobe duration parsing 2021-02-06 16:50:12 -08:00
PixelFormatTests.cs Clean unused using directives 2020-07-20 15:26:34 +02:00
TasksExtensions.cs Major refactoring 2020-05-08 11:07:51 +02:00
TemporaryFile.cs Dump 2020-12-07 00:47:47 +01:00
VideoTest.cs Add NotifyOnOutput 2020-12-18 00:40:09 +01:00