Seems like the source of the current versions isn't public, so it would be Windows only atm.
(from the Test 7 file)
Does that mean one would have to check the json index file each time to be sure the content stayed cfr?
=> if there's a kind of stable release I will think about it, but atm. adding this to Hybrid seems like a bad idea.
Cu Selur
bs.VideoSource(string source, int track = -1, bint variableformat = False, int threads = 0, int seekpreroll = 20, bint exact = True, bint enable_drefs = False, bint use_absolute_path = False, string cachepath = \<user data dir\>)
*track*: Either a positive number starting from 0 specifying the absolute track number or a negative number to select the nth audio or video track. Throws an error on wrong type or no matching track.
*adjustdelay*: Adjust audio start time relative to track number. Pass -2 to disable and -1 to be relative to the first video track if one exists.
*variableformat*: Allow format changes in the output for video. Untested.
*threads*: Number of threads to use for decoding. Pass 0 to autodetect.
*seekpreroll*: Number of frames before the requested frame to cache when seeking.
*exact*: Decode the full track to get an exact frame/sample count. Will throw an error if set to false and the frame or sample count can't be guessed at all. If too many frames/samples is guessed the end is passed with the last available frame/silence to fill up the missing data.
*enable_drefs*: Option passed to the FFmpeg mov demuxer.
*use_absolute_path*: Option passed to the FFmpeg mov demuxer.
*drc_scale*: Apply dynamic range compression to ac3 audio. 0 = None and 1.0 = Normal.
*cachepath*: The full path to the cache file. Defaults to `%LOCALAPPDATA%\bsindex.json` or `~/bsindex.json` depending on the OS.
*hwdevice*: The interface to use for hardware decoding. Depends on OS and hardware. On windows `d3d11va` and `cuda` are probably the ones most likely to work.Quote:Indexing files to get exact sample and frame counts is enabled by default but can be turned off by settings exact=False to speed up file opening. All indexing information is also stored in a single json file to not gunk up your pristine filesystems.this also seems troubling, if you can't tell the decoder to decode to a specific frame rate and content that before was cfr might turn into vfr,...
Indexless mode generally seems to works fairly well for avi and mp4 files. Do however note that nvops are dropped so some avi files will turn into VFR.
Does that mean one would have to check the json index file each time to be sure the content stayed cfr?
=> if there's a kind of stable release I will think about it, but atm. adding this to Hybrid seems like a bad idea.
Cu Selur
----
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.
Dev versions are in the 'experimental'-folder of my GoogleDrive, which is linked on the download page.