Docs

Load recordings · Last updated 2026-11-09

Load a recording

Every analysis starts with a recording. Stingray reads the recording in the browser. The app decodes the file on your machine. Saving a cloud project uploads project data. It does not upload audio, pictures or the source folder. What you can load, and what you get from the recording, depends on which of the two kinds of recording you have.

1. Two kinds of recording

The difference between the two kinds applies to the whole app. Read these two definitions first.

  • AIS data gives the track of each vessel. Ships broadcast their positions and identities over AIS. A receiver, a logger, or an export from an authority captures these broadcasts. AIS data tells you where each vessel was and who each vessel was. It is the traffic picture.
  • VDR data is the output of a voyage data recorder. It carries the same AIS traffic plus the instrument stream of the recording ship. That stream is raw NMEA across the serial channels of the VDR: GPS, gyro, engine, rudder and alarms. Depending on the recorder and supplied files, it can also carry bridge audio and recorded screen captures. Each source shows part of the bridge record.

This extra own-ship stream is the reason that some features need VDR data. The decode rules and the installation profile both work on those instrument channels. A plain AIS recording does not have those channels. Tracks, playback, CPA, notes and exports work with either kind when the required data is present.

2. Open a file

Click Open file in the header. It accepts one or more recordings. Stingray finds the format itself, so you do not select a type. Stingray reads plain CSV and six NMEA packaging dialects (from bare AIVDM to the Wärtsilä VDR wrapper and the NMEA 4.10 tag blocks). The reference has the full list and shows the form of each dialect on disk.

The CSV importer accepts many different column names. It recognizes the usual spellings of the fields that it needs:

mmsilat / londate / timesog · cog · headingname · callsign · ship typedimensions (A/B/C/D)

Stingray can read its own decoded-data CSV, but this is not a lossless project round trip. Some source details and raw field boundaries do not survive. Save a project and keep the original evidence when you need to continue the analysis.

3. Load a whole VDR folder

A VDR dump is rarely one file. It is usually a folder of per-minute or per-hour logs, sometimes in ZIP archives, with configuration files and audio.

Click Open VDR folder to load the full folder. Stingray scans the folder and classifies each file. It calculates the candidate time spans from filenames, headers and supported recorder formats. Stingray then lets you select a time window before the load. Thus you can reduce a multi-day archive to the hour around an incident. Stingray can also read configuration, indexes and neighboring data to interpret that window. Unknown spans are not proof of missing data.

The dialog shows the serial-file count and any salvage warning. Expand Not imported to inspect excluded file categories. Expand Possible decoding instructionsto see all candidate document paths. The counts and help links stay visible when these sections are closed. You can operate the section buttons with the keyboard; expansion does not animate when your system requests reduced motion.

The time-window panel shows UTC start and end fields. If the selected files may require too much memory, a warning appears below those fields. Its suggested duration is approximate. Select the interval around your incident and reduce the window as needed; the dialog does not choose an interval for you. The footer shows the estimated file count and bytes that the import reads.

The time window limits the retained observations. Read the load report for the actual scope, excluded files and timing decisions; its source inventory can include files outside that window. It does not establish complete coverage of the archive. Stingray also flags the files that are probably configuration documents. It shows them for the installation profile and for the decode-rules draft, so that you know which files to supply.

If Known recorder detected appears, review its configuration, interpretation and media choices before importing. Supported profiles can supply channel names, vessel identity and decode rules automatically. Follow the recorder data and media guide to review these choices, replay audio and Screens, and keep the sources needed after reopening.

Files not imported

The VDR folder import loads supported serial recordings, places selected audio and indexes supported screen captures. The Not imported list accounts for the other files found during the scan. Stingray does not delete or change these files.

  • Radar/display frames and video. Supported recorder pictures appear in Screens. Other images and videos are not decoded by that profile. Pictures do not become vessel tracks or sensor readings.
  • Vendor software. Programs, libraries and related files belong to the vendor’s replay tools. Stingray does not run them.
  • Config. Settings and channel maps are not recorded sensor readings. The scanner also classifies small CSV files as configuration. Files flagged under Possible decoding instructions can help you review an installation profile or prepare a decode-rules draft. A matched recorder profile can apply its supported configuration automatically; other candidate documents need review.
  • Recorder self-test reports. Some recorders write a report for each input when they test themselves, often months before the incident. A report quotes real sentences from the day of the test, so reading it as serial data would place the ship wherever she was that day. Recognized reports are listed here and not read as a recording.
  • Documents. PDFs and Word files are supporting material. Supply relevant documents separately when you review channel assignments or draft decode rules.
  • Other. The scan could not identify these files as supported serial data or another listed file category. This does not establish that a file is empty or corrupt. Check the source files or the vendor’s export options if you expected data here.
  • Skipped · empty or hidden. Empty files and files with names that start with a dot are skipped during the folder scan.

These counts describe file categories, not the selected time window. Serial files outside that window are excluded by the time selection; they are not added to this list.

4. Salvage mode

Some VDRs write their NMEA inside a proprietary binary container for which Stingray has no adapter. For eligible unknown containers, salvage mode searches the bytes for NMEA sentences with valid checksums. This recovers only recognizable sentences. It does not decode the unknown container or recover all of its data. A checksum checks sentence integrity, not the truth of its contents. A damaged recognized recorder format can be withheld instead of passed to generic salvage.

Salvaged timing is coarse
A salvaged sentence has no timestamp of its own. Stingray clocks it from the nearest time sentence (ZDA or RMC) and marks it coarse. Stingray never applies spline smoothing to those positions. The load report states that a salvage occurred. Salvage is a recovery method of last resort, and Stingray always labels it as such.

5. The load report

Each load ends with a report of what Stingray found. The report shows the data that Stingray decoded and also the data that Stingray could not decode. It groups the sentence formatters by the level of interpretation:

  • AIS. These are the vessel-position messages and the static messages.
  • Decoded. These are own-ship sensor sentences with a published field layout. Stingray reads them into real values.
  • Code tables. Stingray recognizes these coded sentences. Their meaning needs your decode rules.
  • Not decoded. These are proprietary or non-standard sentences. Stingray counts them but does not interpret them.

The report also shows the caveats that are important for a forensic read. It shows a salvage notice. It gives a count of the long-range (type 27) reports that Stingray counted but did not plot. It shows the safety-related text messages (types 12 and 14) with their sender, their addressee and their time. Stingray shows the retained messages in the report and saves that report with its recording in the project. Older projects may have no saved report. The report also gives a count of the physically implausible positions that Stingray dropped.

In a project with multiple recordings, use the selector in the report header to choose a recording. The report describes that recording’s imported window. Worth a look groups distress transponders and safety text. What was adjusted lists processing caveats and source choices. An amber dot marks a caveat; a hollow gray dot marks neutral handling, such as keeping a shore station outside the vessel fleet. CSV imports show the applicable findings without NMEA sentence counts or confidence tiers.

When the recording has raw sentence groups or saved rules, use Open decode tables in the report to review that recording’s decoding. The same button appears below the own-ship source selector, including when you select AIS. Its summary counts sentence type/channel groups without rules across the whole recording. A rule does not guarantee that Stingray interprets every field.

Fresh imports with usable onboard position fixes start on VDR sensors. The source selector offers AIS, VDR sensors and Both; AIS messages can also come from the VDR folder. Reopening a project or replacing a recording keeps its saved source choice. Recordings without usable onboard positions start on AIS.

For a VDR, the report shows which own-ship MMSI the sensor track linked to. If more than one own-ship MMSI appeared, the report flags this. Review unsupported sentence types and rejected-fix counts. Recorder and capture audits also explain their source and media decisions. These reports describe what the import could inspect; they do not establish that every byte in the original archive was understood or retained.

Not every AIS transmitter is a ship. The report tells you how Stingray treated each kind. Stingray keeps shore base stations as fixed marks at their broadcast (type 4) position. It shows them as muted triangles with their own display toggle. It excludes them from the vessel fleet and from the counts of moving traffic.

Stingray keeps the AtoN navigation marks: the buoys and beacons, and also the virtual wreck marks. It keeps the name and the position that their type-21 reports broadcast. Those marks give the charted context against which you judge an incident.

Stingray keeps the distress transponders (SART, man-overboard and EPIRB). It flags them clearly and shows the time window in which the recording contains them. A true distress transponder in a recording is the incident.

Implausible fixes
Stingray drops a fix only if the jump from the last accepted fix breaks two limits. The jump must be faster than 100 knots and also longer than 2 nautical miles. Real feeds carry corrupted positions. If a fix loses a digit from its latitude or longitude, the vessel jumps hundreds of miles. It jumps for one or two reports, and then it comes back. The map then shows a spike. Receiver jitter does not break both limits, so Stingray keeps those fixes. If a vessel appears again far away after a coverage gap, Stingray keeps the new positions when the new location continues. The load report counts every dropped fix.