-
Notifications
You must be signed in to change notification settings - Fork 46
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frames dropped during long recordings #863
Comments
I think this may have been caused be a host of system preference and hardware issues on my end. I haven't properly turned off sleep and screensavers, which may have contributed to the issue. I also found that I had some faulty hardware and have switched over to another computer for testing purposes. I still noticed some frame dropouts sometimes, but it's less common. I'm hesitant to mark this resolved until all frame dropouts are completely resolved however. As far as the proper sleep settings, this is what I would recommend for macOS Sonoma: Lock Screen Settings:
These may not be the correct settings, but I'm getting better results not. |
Unfortunately I seem to have spoken too soon. The issues are continuing, it's just that sometimes vrecord / cowsay doesn't report them. The dropouts are consistently happening around 3 hours and 15 minutes or 3 hours and 30 minutes. |
I would to recreate some of these tests...how are you generating the MPEG-2 Encoder Breaker pattern, and does that include audio? |
Thanks @bturkus! Unfortunately the breaker patteris proprietary so I think it'd break a license agreement if I were to share it. That said, I had similar issues with other test patterns. I have been capturing audio. I will look to see if I can legally share the encoder breaker. Do you have access to an SDI TSG? |
I've been doing stress tests to see how much I can throw at vrecord before it drops frames. Before concurrent QCTools reports were working I was making files with the following concurrent deliverables. These would drop frames about 7.71 hours into recording
Now that concurrent QCTools reports are working, I made a file with the following concurrent deliverables that dropped frames about 3.5 hours into reccording
The test pattern being captured is an MPEG-2 Encoder Breaker pattern. That said, the issue seems to persist regardless of what files or formats are being captured, or what the input is. I can run more tests if that would be helpful. Also, all of these tests were run on a single M2 Mac mini. I have a few more setup now and will test those out shortly to rule out faulty hardware.
Here are the log files and capture options:
The frameMD5 files I used to determine where the frames dropped are too large to copy into this post, but I'm happy to share them. In both cases two bad frames were made, then a bunch of frames were dropped.
The following is the terminal output from vrecord during and after a 480 minute capture:
The text was updated successfully, but these errors were encountered: