Output formats and NLE integration

HandySaw DS provides flexible export options for your video workflow. You can generate project files that link directly to your source media. The built-in engine also allows splitting source clips into separate physical files.

Strategy 1: NLE project file recommended

The software generates an edit list pointing your NLE to the original video files. This method provides instant export times and guarantees frame-accurate scene boundaries. We strongly recommend this workflow for compatible editing systems.

Final Cut XML (Sequence)

Generates a complete timeline sequence with every scene pre-cut. The file includes your custom scene names and timeline markers. It opens natively in Adobe Premiere Pro and DaVinci Resolve alongside Final Cut.

Final Cut XML (Bin)

Creates a structured media bin containing all recognized clips. This option suits editors who prefer arranging scenes on the timeline manually.

Adobe Premiere PSQ 6

Produces a native Premiere sequence containing your user comments. Importable into Adobe Premiere Pro.

Adobe Premiere PSQ 5 / PLB

Supports legacy Premiere 5 environments. The PLB option creates a project library where each scene acts as an independent clip with an optional marker track.

Sony Vegas EDL

Generates a specifically formatted text EDL for direct import into Sony Vegas.

CMX3600 EDL

Provides the industry-standard edit decision list. This highly compatible file works with Adobe Premiere Pro and most enterprise editing environments.

EDIUS EDL

Creates a dedicated edit list optimized for Canopus EDIUS systems.

HTML scene list

Compiles a human-readable log of your processed media. You can use this document for client reviews or print it directly via the Clip Sheet feature.

Strategy 2: Separate media files

Certain workflows require actual physical media files for each scene. HandySaw DS utilizes FFmpeg to perform this separation for archiving or delivery. You can select your preferred encoding preset in the application preferences.

MP4 High Quality recommended

The engine processes each scene using the H.264 codec. This setting delivers frame-accurate boundaries and maintains excellent visual quality. File sizes remain highly manageable for everyday workflow.

MP4

Applies aggressive H.264 compression to your media. The resulting files take up significantly less space at the cost of slightly reduced image fidelity.

HuffYUV AVI

The software utilizes lossless compression for AVI output. You get massive files with mathematically identical visual fidelity. This preset works perfectly for demanding downstream post-production tasks.

MPEG-2

Transcodes your video into the MPEG-2 format. We included this option specifically for legacy DVD authoring workflows.

Xvid AVI

Encodes the separated scenes using the Xvid algorithm inside an AVI container. Your system must have the appropriate codec installed locally.

Direct stream copy use with caution

The engine duplicates the original media stream directly. Visual quality remains absolutely untouched during this process. Please note that inter-frame codecs enforce cutting at keyframe boundaries. The software snaps output files to these intervals automatically. We recommend this setting exclusively for intra-frame source material like DV or specific ProRes profiles.

Direct stream copy from keyframe use with caution

This variation operates similarly to the standard stream copy mode. It explicitly forces every boundary to align with the nearest available keyframe. The same format limitations apply regarding intra-frame footage.

Configure the core splitting engine via Preferences. Windows Media Format provides native parsing for WMV sources. You can also engage the DirectShow AVI engine for specific legacy formats.

Custom output plugins

HandySaw DS includes a flexible scripting engine for custom export requirements. Developers can write JavaScript or VBScript plugins to format the scene list data. These scripts process the timeline parameters and generate any required text-based format. You will find complete API documentation inside the application help file.