How to Install and Uninstall lv2-devel Package on openSUSE Leap

Last updated: December 25,2024

1. Install "lv2-devel" package

Please follow the step by step instructions below to install lv2-devel on openSUSE Leap


    
        
            $
        

        
            
                sudo zypper refresh
            
                    
    
    Copied


    
        
            $
        

        
            
                sudo zypper install
            
                        
                lv2-devel
            
                    
    
    Copied

2. Uninstall "lv2-devel" package

In this section, we are going to explain the necessary steps to uninstall lv2-devel on openSUSE Leap:


    
        
            $
        

        
            
                sudo zypper remove
            
                        
                lv2-devel
            
                    
    
    Copied

3. Information about the lv2-devel package on openSUSE Leap

Information for package lv2-devel:
----------------------------------
Repository : Main Repository
Name : lv2-devel
Version : 1.18.2-1.9
Arch : x86_64
Vendor : SUSE LLC
Installed Size : 252.7 KiB
Installed : No
Status : not installed
Source package : lv2-1.18.2-1.9.src
Upstream URL : https://lv2plug.in/
Summary : Development files for LV2
Description :
LV2 is a plugin standard for audio systems, similar in scope to LADSPA,
VST, AU, and others. It defines a C API for code and a format for data files
which collectively describe a plugin. LV2 consists of a core (roughly
equivalent in power to LADSPA) which can be extended to support more
functionality. This allows the interface to be "grown" to accommodate the needs
of real software as they arise.
LV2 is both a stable interface and a forward-moving project: there is a stable
set of "official" extensions in use while new functionality is actively
developed. Most functionality required by modern plugins is available, including:
* Audio, control, "control voltage" (audio-rate control), and event
(e.g. MIDI) input and output
* Expressive open-ended port metadata, including:
- "Meaningful" controls (e.g. gain or envelope attack) allowing intelligent
host control or UI generation
- Control units (e.g. Hz, octaves, dB)
- Multi-channel port groups (e.g. stereo, 5.1 surround, ambisonics
* Embeddable GUIs in any toolkit, with support for a full plugin/UI split
(including network transparency in capable hosts)
* Ability to bundle any files (e.g. samples or impulses) with plugins
* Presets (bundled and/or user saved)
* Plugin state saving and restoring
* Host-managed logging
* Non-realtime plugin worker methods (simple and portable host-managed
threading)
* Message-based plugin communication, allowing plugins/UIs to have advanced
interfaces without host support or specifications getting in the way
* Transport awareness, both real time and tempo time (bars, beats, etc-.)