Linux workstation

Upstream software project

ladspa-tap-plugins

Tom's Audio Processing plugin

About ladspa-tap-plugins

Tom's Audio Processing plugin

This project links 2 native package records across 2 recorded operating-system releases. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

Fedora 43: 1 package records; Fedora 44: 1 package records. Catalog coverage diagram, not an application screenshot.ladspa-tap-plugins: recorded package coverageFedora 431 recordsFedora 441 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
ladspa-tap-plugins
Publisher
Not authoritatively mapped
Native package records
2
Operating systems
fedora-43, fedora-44
License expression
GPL-2.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Not reported

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

TAP-plugins is short for Tom's Audio Processing plugins. It is a bunch of LADSPA plugins for digital audio processing, intended for use in a professional DAW environment such as Ardour.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

Fedora 43

  1. ladspa-tap-plugins

    Fedora 43 / Unspecified / source ladspa-tap-plugins

    1.0.0-1.fc43

    Tom's Audio Processing plugin

    aarch64x86_6443

Fedora 44

  1. ladspa-tap-plugins

    Fedora 44 / Unspecified / source ladspa-tap-plugins

    1.0.0-1.fc44

    Tom's Audio Processing plugin

    aarch64x86_6444

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.