Keep the moment.
Keep its place in the journey.

Copying a video to your Mac can give the file a creation date that differs from filming. You can also rename the file.

My solution

Cut prioritizes the date stored inside the video. If it is unavailable, you can choose to use the file creation date. Cut displays “Using file creation date” while that date is in use. It does not infer capture time from the filename or modification date. Without this choice, or if the file creation date is unavailable, the recording time remains unknown.

Reason

Showing the date source lets you check it while matching videos without internal dates to GPX and Marks.

Conditions and limits

Copying or exporting may change the file creation date. Check that it represents the start of filming before using it. Use clock adjustment if the camera clock or chosen date is offset.

Read this problem in the full list (Japanese)

A correction measured in Vroma Studio can also be used in Cut and Edit, but another recording may have the same filename.

My solution

Studio saves the video’s name, byte size, uncorrected start date, duration and correction seconds in VromaMedia.json. Cut compares these with the current video and applies the correction only when one entry matches.

Reason

The correction needs to identify its original recording before another tool uses it to find the same moment.

Conditions and limits

Name and size must match exactly; start dates must differ by less than 1 ms and durations by at most 0.25 s. A rename prevents a match. Normal import adds no correction when unmatched; explicit import reports an error if no videos match.

Read this problem in the full list (Japanese)

A scene at a camera’s file boundary is harder to inspect when each file is treated as a separate recording.

My solution

Cut groups files in one folder whose names follow VID_date_time_number, have the same date/time part, consecutive numbers and the same correction and date source. For example, VID_20260911_080012_025.mp4 can be grouped with the file ending in 026.

Reason

Adding the files’ durations gives one recording position for selecting a scene across their boundary.

Conditions and limits

This is a filename rule, not automatic camera-model detection. It does not verify gap-free filming from the internal timestamps. Different naming schemes, including GoPro names, are not grouped by this rule.

Read this problem in the full list (Japanese)

A Vroma Mark gives a timestamp, while editing an INSV file in Insta360 Studio requires a position inside a particular file.

My solution

Cut’s reference window reads start dates and durations and lists the matching file and position from its beginning. For grouped files it also lists the position from the start of the whole recording.

Reason

A Mark 30 seconds into the second file can be located using either the file position or the combined recording position.

Conditions and limits

The INSV reference accepts names such as VID_date_time_00_number. It does not prove recording continuity, trim INSV files or convert 360° footage.

Read this problem in the full list (Japanese)

Two clips beginning in the same second can produce the same date-based name. Another operation may also create that name.

My solution

Cut finalizes the output without replacing an existing file. On a name collision it tries vroma_01_timestamp.mp4, then 02 and so on. It stops at the start if another Cut export holds the same destination.

Reason

Keeping a new scene should preserve previously saved videos.

Conditions and limits

Serials are limited to 99999. Other save errors stop the operation. Edit instead asks for a different name rather than generating serials.

Read this problem in the full list (Japanese)

Some compressed frames need earlier frames to play. Starting a separate file at one of those frames can make its beginning unplayable.

My solution

Cut checks for an IDR frame, a frame that can start playback independently. It extends the requested range to suitable boundaries that include the chosen scene.

Reason

The desired scene needs to remain inside a standalone, playable video.

Conditions and limits

A general keyframe flag alone is insufficient. Requested and actual saved ranges are kept separately when they differ.

Read this problem in the full list (Japanese)

A camera video can contain several audio tracks. Saving only the first would discard the others.

My solution

Cut copies every supported AAC audio track. At a chapter seam, it checks the interval between adjacent compressed audio units and adjusts the stored duration of the preceding unit to that interval. This adjustment does not change the audio data or start timestamps, and its count is recorded with the export.

Reason

The supported audio in the original should accompany the saved footage.

Conditions and limits

At a chapter seam, the interval must be positive and no more than twice the preceding audio unit’s duration; otherwise export stops. The full list explains the time units and treatment of the final audio unit.

Read this problem in the full list (Japanese)

A saved file does not establish that all selected compressed video and audio data were copied correctly.

My solution

Cut reopens the output and compares the copied data, timestamps and unit counts with the values recorded during export. It also checks that the first frame is independent and the output starts at time zero.

Reason

Writing the file should not silently change the selected data or its timing.

Conditions and limits

Normal verification compares compressed data and timing. Decoding every frame is a separate optional check.

Read this problem in the full list (Japanese)

Rebuilding an MP4 can lose camera-specific information that is outside its compressed video and audio.

My solution

Cut saves those original information regions separately under SourceMetadata, together with an identifier of the original’s full contents. For the video/audio data region, it saves only the region header.

Reason

Information not carried into the new MP4 can still be kept separately in its original form.

Conditions and limits

The archive excludes the actual compressed video and audio. It cannot by itself restore the original or guarantee reuse in the camera manufacturer’s software.

Read this problem in the full list (Japanese)

Another device may change the CSV while a comment is open on your Mac.

My solution

Current Cut attempts automatic saving two seconds after the last input, comparing the version first read, your edits and the current file. It preserves external edits to comments you did not change. If both sides change the same Mark to different text, it stops the save.

Reason

Conflicting changes need review instead of silently choosing one side.

Conditions and limits

Deletion or multiple rows with the same timestamp can also prevent a unique match and require resolution.

Read this problem in the full list (Japanese)

Footage from two cameras can show the same event from different viewpoints.

My solution

Cut converts the main recording’s corrected capture time into a position in the comparison recording. The comparison follows playback, pause and seeking and is labelled as excluded from export.

Reason

Inspecting another view should not change the source being saved.

Conditions and limits

Missing dates or footage prevent comparison. Comparison audio starts muted; playback is not guaranteed frame-accurate synchronization.

Read this problem in the full list (Japanese)

Saving a comment or an exported video does not also save every candidate range or Mark added during editing.

My solution

Current Cut holds those working candidates and added Marks in memory. Comment CSV saves, output videos and mapping files, and window-layout saves are separate operations.

Reason

The saved result needs to be distinguished from the current working state.

Conditions and limits

The current app has no project save/open interface. It does not offer restarting with the same adjusted candidates and locally added Marks.

Read this problem in the full list (Japanese)