Skip to content

Project & Driver Files

KFilter6 uses two complementary file formats.

Project files: .kfp

New KFilter6 projects are written as versioned JSON.

Current format:

KFilter project format version 10

The project stores the relevant state for all driver slots, including:

  • driver and enclosure parameters
  • passive crossover values
  • curve/summary state
  • measurement correction and hide state
  • project-wide measurement merge state
  • active-filter chains
  • baffle/diffraction settings
  • floor-reflection settings

Calculated transfer-response arrays are not persisted. They are derived again from the stored parameters when the project is loaded.

Legacy projects

Legacy text-based .kfp files remain readable through a dedicated legacy loader. When such a project is later saved, KFilter6 writes the current JSON format.

Driver-slot files: .kfd

Current format:

KFilter driver-slot format version 2

A .kfd file represents a complete driver slot, not just a raw driver-parameter record.

It can contain:

  • driver and enclosure state
  • all 48 serialized passive-network values
  • measurement correction data and Hide state
  • Merge Measurements metadata
  • complete Active Filter state
  • complete Baffle / Diffraction state
  • complete Floor Reflection state
  • selected dialog metadata

This allows a configured driver to be transferred between projects while retaining the processing that belongs to that slot.

Safe loading and writing

Current project and driver loading performs validation before replacing the destination state. Driver-slot writing uses a safe-file commit mechanism so a failed save does not intentionally leave a partially replaced file.

Unknown future format versions are rejected rather than guessed.