Skip to main content

Sends compatible Loudspeaker Processor Interchange Format (LPIF) file parameters to supported dbx DriveRack loudspeaker management systems

Project description

LPIF to dbx DriveRack converter/applicator

This command-based application takes a Loudspeaker Processor Interchange Format (LPIF) file, containing audio filters for bands of a loudspeaker system, and applies these to a networked dbx DriveRack® loudspeaker management device.

Presently, only the DriveRack PA2 model is supported.

Requirements

  • Python (>= 3.11)

  • A compatible DriveRack hardware unit:

    • DriveRack PA2 (firmware version 1.2.0.1)
  • Network connectivity between this client and the device.

  • A properly-formatted LPIF file with at least one labeled processing block and DriveRack-compatible filters.

Quick start

pip install lpif2dbxdriverack

lpif2dbxdriverack /path/to/file.lpif

DriveRack compatibility

While this software was designed for use with Smaart® Data Modeler, any LPIF file generated with correct parameters should be compatible. The guidelines given here however are based on experience with Smaart Data Modeler.

Compatible filters & parameters

When using Smaart Data Modeler, selecting the Generic filter reference mode will allow any type of filter to be used. Any processing block attributes other than those that follow will be ignored. Automatic converstion is done between Q and bandwidth units, so either can be used.

Block ("DSP channel") attributes
  • Polarity (applied in the DriveRack crossover section)
  • Level (applied in the DriveRack crossover section)
  • Delay
EQ filters
  • Up to 8 filters per DriveRack output band
  • Gain between -20 and 20 dB
  • Frequency between 20 Hz and 22 kHz
  • High & low shelf BW roughly up to 2.7 (or Q down to 0.5)
  • Parametric Q between 0.1 and 16 (or BW roughly between 12 and 0.1)
Crossover filters
  • One high-pass and one low-pass filter per DriveRack output band

    • Crossover filters are mandatory in the DriveRack so if none are specified, the DriveRack will be set to use a Butterworth 6dB/oct filter set at the maximum or minimum ("Out") frequency.
  • Linkwitz-Riley 12, 24, 36, and 48 dB/octave (even ordered 2-8) filters

  • Butterworth 6, 12, 18, 24, 30, 36, 42, and 48 dB/octave (order 1-8) filters

Command usage & behavior

Usage: lpif2dbxdriverack [OPTIONS] LPIF_FILE

Options

  • --model - The DriveRack model to connect to. Currently only pa2 is supported so this may be left out.
  • --connect-single - When using the discovery feature, and only one DriveRack is found, connect to it without prompting.
  • --address - The IP address or hostname of the DriveRack PA2 to connect to. If this is provided, the discovery feature is bypassed.
  • --scan-time - The number of seconds to wait for devices to respond after a discovery scan is initiated. The default is 5 seconds.
  • --muted/--no-muted - By default, temporarily mute the DriveRack outputs while applying the settings, then restore the previous mute states after, to potentially avoid unwanted noise during adjustment. Use --no-muted to disable this behavior.
  • -r, --reset-unmapped - Normally, any bands that are not mapped to a DriveRack output will be left alone. This option will reset any unmapped bands to have no processing.
  • --crossover/--no-crossover - By default, the DriveRack crossover section will be set to use the high-pass/low-pass filters plus any polarity and gains specified in the LPIF blocks. Use --no-crossover to skip applying these settings.
  • --peq/--no-peq - By default, the DriveRack parametric EQ sections will be set to use the parametric and shelving filters specified in the LPIF blocks. Use --no-peq to skip applying these settings.
  • --delay/--no-delay - By default, the DriveRack delay sections will be set to use the delays specified in the LPIF blocks. Use --no-delay to skip applying these settings.
  • --room-eq - When specified, apply a single LPIF block to the AutoEQ PEQ section of the DriveRack. No other processing will be applied. If only one DSP block is present in the LPIF file, it will be chosen automatically instead of prompting.
  • --map-high, --map-mid, --map-low - Normally, an interactive prompt will ask you to map each DriveRack output to an LPIF block. If you know in advance what the name of the LPIF block is, you can use these options to specify which DriveRack band should be mapped and bypass the prompt.
  • --map-room - When specified, the AutoEQ PEQ section will be mapped to the LPIF block name specified, bypassing the prompt. Only utilized when --room-eq is also specified.

Contributing

Any DriveRack PA2 users are encouraged to test this module and provide bug reports or code contributions. I am seeking anyone with other DriveRack models (such as the VENU360) to help develop support for this and other devices.

Acknowledgements

Loudspeaker Processor Interchange Format (LPIF) is a trademark of Eclipse Audio Pty Ltd.

Smaart® and Smaart® Data Modeler are trademarks of Rational Acoustics LLC.

dbx, DriveRack®, and other brand names are trademarks of Harman International Industries, Inc., a subsidiary of Samsung Electronics Co., Ltd.

This project is not affiliated with or endorsed by any of these companies, and the use of their trademarks is for identification purposes only.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

lpif2dbxdriverack-0.0.3.tar.gz (14.0 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

lpif2dbxdriverack-0.0.3-py3-none-any.whl (12.8 kB view details)

Uploaded Python 3

File details

Details for the file lpif2dbxdriverack-0.0.3.tar.gz.

File metadata

  • Download URL: lpif2dbxdriverack-0.0.3.tar.gz
  • Upload date:
  • Size: 14.0 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/5.1.1 CPython/3.13.0

File hashes

Hashes for lpif2dbxdriverack-0.0.3.tar.gz
Algorithm Hash digest
SHA256 776289028de923a6394e519e175127b9f6e95e70f80c0664de6f3f6420d1d1ff
MD5 8d2b9b3eebef1b00ad74e5cdb4f3a1be
BLAKE2b-256 eefc9469456f125104318651bcd2ed2b9a9aaf681c6f140ce4cc81b5e2988eed

See more details on using hashes here.

File details

Details for the file lpif2dbxdriverack-0.0.3-py3-none-any.whl.

File metadata

File hashes

Hashes for lpif2dbxdriverack-0.0.3-py3-none-any.whl
Algorithm Hash digest
SHA256 084a872a30b1bb8506258980d4ad37c7617a9bfed36197e7af979c2ebd09f274
MD5 28eec5cb05673a36dd00086c306a1fd4
BLAKE2b-256 9057e7224bd2607631dfddce5edad2d9eeeeda59dc2270568593726b1ccd2332

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page