A recording workflow has several separate success conditions: the source is available, the recorder receives video, conversion finishes, and the final file plays correctly. Treating those as one green indicator makes failures harder to diagnose.
This checklist uses CaptureGem as the desktop example. Use it for streams you are authorized to record with the broadcaster's permission. Cam Recording Notes is a software guide blog, not the official CaptureGem blog.
1. Verify the source identifier
Before changing network settings, compare the saved identifier with the source. Many integrations take a username; others take a stream ID or a stable numeric profile ID. A display nickname is not necessarily interchangeable with any of them. The wrong identifier can look like an offline stream.
In CaptureGem, choose the correct entry under Select Website and enter its identifier in Enter URL or Username. Leave Monitor Only off when you want a saved file. A preview alone does not establish that recording is enabled.
This app screenshot shows an empty recording list and an example setup, not proof of a completed capture.
2. Separate availability from recording
Confirm Recording in the Status column. If an entry reports Errored, hover over it for the reason. Keep a note of the actual message and the time it appeared. A source going offline and a conversion failure require different follow-up work.
For browser-based integrations, keep the CaptureGem desktop window open. Do not assume the standalone recorder daemon includes the desktop browser integration.
3. Wait for the final output
Capture stopping is not the last stage. Let conversion finish, then open the result in Review or use Open Video Folder. MP4 is the default container. Check the actual output location rather than relying on an old file with a similar name.
Record the filename and capture time in your test notes. That small step prevents a previous successful recording from being mistaken for the current result.
4. Sample picture, sound, and timing
Play the beginning, middle, and end of the file. Check that movement continues, sound is present when expected, and the duration is plausible for the captured session. For an important recording, a full playback or a suitable media-validation tool provides stronger evidence than a thumbnail.
A VR file may contain two side-by-side views when opened in a normal player. Choose the appropriate VR format in a compatible player before diagnosing that expected layout as damage.
5. Scale up only after a short successful capture
The free CaptureGem version currently allows ten added models and up to five minutes per recording, which is enough for a short workflow check. Premium adds automatic recording and removes those limits. Before enabling Actions → Modify Auto Record → Record Always, review free disk space, the output location, file-length settings, and whether the app will remain running.
If the short capture fails, fix that specific stage first. If it succeeds, retain a small checklist of the identifier, start time, status, output path, and playback result. That gives you evidence to compare after an app update or a source-site change.
See CaptureGem's current documentation for product-specific controls and supported integrations.
Example recording activity
Illustrative UI demo with fictional usernames and statuses; not a live capture.
