Recorder data & media · Last updated 2026-11-10
Review the recorder, then replay its media
A supported VDR folder can supply serial data, channel names, vessel identity, decode rules, bridge audio and recorded screen captures. What is available depends on the recorder, its configuration and the files supplied. Keep the original folder: a saved project does not contain a complete copy of that evidence.
1. Review the detected recorder
Choose Open VDR folder. The scan can recognize SAM/Wärtsilä VDR4370, JRC JCY-1900, JRC JCY-1800, Kelvin Hughes VDR and Rutter VDR-100 G3 layouts. Support applies to the documented layouts and variants. The model name alone does not establish that Stingray can read every file.
When Known recorder detected appears, check the recorder, configuration file, vessel identity and firmware shown. Expand What matched to inspect the detection checks. The card states which signals, channel names and identity fields the profile supplies. Some profiles supply names without decoding every signal.
Review the opt-out before importing. Without recorder decoding, standard decoding continues. Recorder audio and screen captures are not placed. Stingray can withhold recognized recorder media with an audit entry instead of importing it as generic audio. A near match also explains which condition prevented the profile from applying.
2. Select the sources and window
Set the UTC time window around the incident. Filename and header times help the scan select candidates; they do not prove continuous coverage. Import can also read configuration, indexes or neighboring records needed to interpret the selected data. Files with unknown or contradictory times can be withheld with an explanation.
Rutter folders can show Recorded representations, with separate choices for Serial data, Audio and Screens. Archive is the default when present. This preference does not prove that Archive and Export contain the same channels, times or content. Each choice imports only that representation. Stingray does not blend it with an unselected one or use the other as a fallback.
Under Audio on the timeline, select the channels to place. The card gives an approximate size and states that Stingray reads the audio from the folder on this computer. Under Screen captures, review the candidate displays and files. Stingray checks the pictures after import. Candidate counts are not counts of verified pictures.
Replay directly from a recorder folder needs Chrome or Edge with folder access. Other browsers can import supported serial data, but cannot keep this folder access for recorder media. Extract an archive to a folder if you need persistent access to its media.
3. Inspect the interpretation and audit
Open the recording's load report. Recorder audit explains the source files, read scope, hashes, clock decisions and supported media derivations available for that import. Use Download audit (JSON) to keep the audit. Screen indexing has its own status and Download capture audit (JSON). A pending or incomplete index is not evidence that the folder contained no pictures.
Read the reasons for unsupported, malformed, conflicting or withheld data. Stingray does not always read each candidate file in full. A partial read does not establish complete content identity. The interface can show only a bounded set of issue examples. Review the counts and downloaded audit as well as the examples.
In Decode tables, use the More menu to open Installation details…. There, From the recorder groups the read-only rules generated from the configuration and names their profile version. Your editable rules remain separate. Turn off recorder decoding removes the generated rules and their derived rows and alarms; restoring them requires re-import. See Decode rules and Installation profile for the editing and identity checks.
A panel report or event is an observation at its stated time. Silence after it does not establish Normal, a physical stop or an all-clear. The recorder audit keeps event-source details where the profile supports them; native event times remain distinct from the case's aligned timeline.
4. Replay audio and recorded screens
Imported audio appears on Own-ship rows, separated by channel. Use the timeline's mute and solo controls to choose what you hear. Audio plays at 0.5× to 2×; outside that range it is silent. At audible speeds, the playhead waits while audio indexing or preparation finishes. Indexing audio… and Buffering audio… explain that wait. Playback resumes when the required audio is ready; press Pause to cancel that automatic resumption.
The light strip on the timeline shows buffered audio across the audible channels. It describes playback readiness, not complete evidence coverage. After indexing finishes, muted channels do not block playback and actual gaps advance. A gap or withheld clip does not prove that the bridge was silent. Audio unavailable or Audio needs a click to start holds playback. Resolve any folder-access problem, then choose Retry audio. You can deliberately mute an unavailable row to continue without it. Hiding the tab suspends audio and the playhead; returning does not add the time spent hidden.
Open Screens in the timeline and select a display. It shows a ready capture at or before the playhead. At high speed, the picture can lag while another loads. The displayed time and source details describe the picture actually shown. Use the previous and next capture controls to examine individual pictures.
Inspect the profile's timestamp label and explanation. Hover over or focus the warning icon, Screen capture warnings, for stale-picture notices and metadata caveats. Open Source for the folder and file; expand Verification details for fingerprints and reference versions. A recorder stamp is not necessarily the instant the display acquired the picture. Display attributes report what the source says; they do not independently prove what the pixels show. A notice that no later picture is in the index does not prove that the recorder captured no later picture.
Imported media follows its recording's Clock offset. Native stamps remain available; On timelineshows a screen capture's time with a nonzero offset applied. Align on a justified shared event and record the reason. Retiming does not establish an absolute acquisition time. Manually attached audio has its own timeline placement; see Synced audio.
5. Save, reopen and keep the evidence
Save the project to keep decoded recording data, settings and available audits. Audio that reads from a recorder folder keeps that dependency in a local .stingray project and in a cloud project: Stingray does not upload the audio. On another computer or browser, reconnect the original folder before relying on playback.
Screen captures save an index and source references, not the picture files, in both local and cloud projects. After reopening, use Allow access or Locate folder… when prompted. Relinking checks the expected folder entries; playback also checks source content identity. Missing, changed, unverifiable or unsupported files can remain unavailable.
If a saved project says its interpretation or media references are from an unsupported earlier version, re-import the original folder. Opening or resaving it does not recreate missing source identity or upgrade those interpretations. Keep the originals, configuration and audit alongside the project.