One final update for the time being. It appears that the situation improves when I roll back to Action! 3.7.1. Version 3.7.2 exhibits the same behavior, so it seems that that's where the issue was introduced.
I don't export my files from Action!, as I don't want H.264 or H.265 files. I edit with DaVinci Resolve and the Mirillis FICV codec is not supported in that, so I use Adobe Media Encoder to transcode the clips to DNxHR. I record at 1440p60 most of the time, sometimes dropping to 1080p60 if the scene I'm recording is too much for my PC to stay above 60 FPS. I've noticed that in recent versions of Action!, when recording at 60 FPS, Action! reports the framerate as 62 FPS, fluctuating a lot more than it used to. Again, this started around version 3.7.1-3.7.2 and has carried over into 3.8.0. Thoughts?
I'm recording to an SSD, a Samsung 850 Evo, so that should not be in the issue.
Dude I'm having the same exact issue, I'm also recording on a Evo 850 SSD at 1440p60, with your same exact Action! settings, and my videos is having crazy jumps/stutters all over the place. I refuse to record in mp4 since the bitrate is way too low. PLEAE HALP!not_leffen wrote: ↑Fri Dec 28, 2018 1:42 amHi,
Since updating to version 3.8.0, my recordings have been stuttering here and there. I've tried changing all sorts of things in my video recording and editing process and have narrowed it down to the recordings themselves having the stutters. To verify the issue, I reverted to the previous version, re-recorded the same video and the stutters were gone. Exporting the 3.8.0 recording using either version revealed stutters. Exporting the recording that came from the older version (again, exporting it using either version) revealed no stutters. If you need Action! settings, then here they are down below. Specifically, I'm recording Assetto Corsa at 1440p60 and am recording to a 500 GB Samsung 850 Evo:
File Format: AVI
Video Size: Original
Video Framerate: 60 FPS
Video Quality: Ultra
Use Multicore Rendering: Yes
Am I the only one experiencing this? Is this a known issue and a fix is on the way?
Users browsing this forum: Google [Bot] and 9 guests