After upgrading to Bandicam 4.5.5.1632, the problem seemed to be fixed (Test 1 failed to reproduce) for Windows 10 (not fixed for Windows 7). Note: I also upgraded Nvidia Display Driver to 442.19, but I doubt it's related. (as the testing results with Bandicam 4.5.5.1632 on Windows 7 before/after th...

We will try to find a better solution in the future.

Properly tagging the recorded video should suffice. (colorspace, should work)

You may have to try a different video codec. Source ...recording 4K NVENC doesn't produce a CFR video. Note: NVENC * may not be able to handle encodings of 4K (3840x2160) @ 60 FPS, especially when the recording source is of high scene complexity, and/or the encoder is configured to operate in non- I...

1. More Audio Channels "Format settings" -> "Audio": "Save as original format". (only available when "Codec" is "PCM") 2. Ignore Overlays Nice to have... though likely useless to me. 3. Real CFR. Check this . ...recording 4K NVENC doesn't produce a ...

...why does Bandicam insist on VFR even when CFR is chosen? Why insist on CFR when the input is actually of VFR nature?.. Does wasting bit rate on unnecessary duplicate frames do you any good? ( unless ) Also note: Bandicam 4.4.3.1557, "Prefer CFR", crash and/or corrupt output , likely un...

The real problem about the app's cutting accuracy is the misuse of ffmpeg's `-t` parameter over `-to`, which to some extent rendered the app's cutting accuracy near the last frame sort of unpredictable.

Or it can be a FFmpeg issue if the app uses `concat` demuxer for the purpose...

We've confirmed the issue where some videos recorded with MagicYUV codec have lower frame rates than the original ones and forwarded it to our development team. According to Test 8 and Test 5,6 it doesn't look like a codec issue... Also, we've found that there is no problem with H.264(NVIDIA NVENC)...

What is the file size of the video? I don't remember. Expect file sizes over a few ten GB... Could you let us know the file information of the video file? I believe the original post already gives enough information. Do you have a problem when you cut the video through the "Encoding mode"...

At times values like 63.45 (raw PTS from the file) can be displayed as 00:01:03.44 or 00:01:03.46.

Check the algorithms responsible for the timestamp display generation. (maybe even the whole timestamp interpretation process...)

Yes im using Windows 10. I have enhanced capture method turned off because it was causing problems when recording second monitor. I also performed some testing on Windows 10, and found: If I disable "Use enhanced capture method" there'll be severe stuttering observable on the screen, thou...