Linux-audio-announce

linux-audio-announce@lists.linuxaudio.org

3198 discussions

by Sven Jaehnichen

Hi, I pushed a new release of the LV2 audio chopper plugin B.Choppr (successor of B.Slizr). Now you can link different instances of the plugin via shared data, too. Github: https://github.com/sjaehn/BChoppr Demo/Tutorial: https://youtu.be/PuzoxiAs-h8 Have fun Sven

4 years, 8 months

Drumstick MIDI Monitor 1.0 and Metronome 1.2 Released

by Pedro Lopez-Cabanillas

Drumstick MIDI Monitor for Linux using ALSA sequencer and Qt5 user interface. This program was previously known as "kmidimon". More info: https://kmidimon.sourceforge.io Sources and AppImage: https://sourceforge.net/projects/kmidimon/files/1.0.0/ Drumstick Metronome is a MIDI metronome with Qt5 user interface, based on the ALSA sequencer. It was previously known as "kmetronome". More info https://kmetronome.sourceforge.io/kmetronome.shtml Downloads https://sourceforge.net/projects/kmetronome/files/kmetronome/1.2.0/ Minimum dependencies for both programs: * Qt 5 * Drumstick 2.0 * ALSA * CMake 3.9 * C++11 compatible compiler Copyright (C) 2005-2021, Pedro Lopez-Cabanillas Licenses: GPL v2 or later

4 years, 8 months

[LAD] [LAU] Mamba - Virtual Midi keyboard for Jack Audio Connection Kit release 2.1

by Hermann Meyer

Hi Mamba release v2.1 is out Mamba is a Virtual MIDI keyboard with some extended, unique features. Key features: Supports jack-interconnect-ALSA MIDI I/O. 16 Channel Live MIDI Looper Every channel use it's own Color to display the played Notes per channel. MIDI File player/recorder Integrated Fluidsynth support. NSM support. Release v2.1: Add option to allow 2 keys per note in the Custom Key-map Editor, thus allow setup key bindings for chromatic button accordion. Add option to use right mouse button for permanent note on event. (Press again for note off) Add 'XDG Places' to file selector Fix some minor bugs and hopefully don't introduce to much new ones. Mamba is released under the BSD Zero Clause License license The GUI is build on libxputty - A damn tiny abstraction Layer to create X11 window/widgets with cairo surfaces https://github.com/brummer10/libxputty To build Mamba from source, the following dependencies must be meat. * libfluidsynth-dev * libc6-dev * libsmf-dev * libcairo2-dev * libx11-dev * liblo-dev * libsigc++-2.0-dev * libjack-(jackd2)-dev * libasound2-dev So, here is the project page: https://github.com/brummer10/Mamba and here you'll find the last release: https://github.com/brummer10/Mamba/releases/tag/v2.1 regards hermann

4 years, 8 months

liquidsfz-0.2.2

by Stefan Westerfeld

liquidsfz-0.2.2 has been released The main goal of liquidsfz is to provide an SFZ sampler implementation library that is easy to integrate into other projects. A standalone jack client and a LV2 plugin is also available. liquidsfz is implemented in C++ and licensed under the GNU LGPL version 2.1 or later. The release tarball can be downloaded here: https://github.com/swesterfeld/liquidsfz#releases Overview of Changes in liquidsfz-0.2.2: ======================================= * Implement filters (fil_type, cutoff, resonance, ...) - all SFZ1 filter types (lpf_1p, lpf_2p, hpf_1p...) - some SFZ2 filter types (lpf_4p, lpf_6p, hpf_4p, hpf_6p) - filter envelope (fileg_attack, fileg_depth, ...) * Support midnam for LV2 to provide controller/key/switch information * Key/Key Switch information: - API: provide key and key switch information (Synth::list_keys) - opcodes: implement key and keyswitch names (sw_label, label_keyN) - hydrogen loader: provide key names for each mapped key - add keys/switches/ccs command in liquidsfz jack client * Improve key switch handling to fix problems with some sfzs #20 * Fix problems with clang++ using libc++ (for instance on macOS) #19 * Minor fixes and cleanups -- Stefan Westerfeld, http://space.twc.de/~stefan

4 years, 8 months

Yoshimi 1.7.4

by Will Godfrey

There are no new features in this release. It is really another maintenance one, with a few more bugfixes and code refinements. However, there is a check for when you save an instrument but haven't set a type. This asks you to do so, and also recommends including copyright information. You can ignore this and save without these, but then it will be very difficult to identify your patch on a search, and impossible to acknowledge you on any songs that use it. Yoshimi source code is available from either: https://sourceforge.net/projects/yoshimi Or: https://github.com/Yoshimi/yoshimi Full build instructions are in 'INSTALL'. Our list archive is at: https://www.freelists.org/archive/yoshimi To post, email to: yoshimi(a)freelists.org -- Will J Godfrey http://www.musically.me.uk http://yoshimi.github.io Say you have a poem and I have a tune. Exchange them and we can both have a poem, a tune, and a song.

4 years, 8 months

B.Schaffl 1.4.0 - MIDI dynamics & vitalization

by Sven Jaehnichen

Hi, The MIDI dynamics and vitalization LV2 plugin just got new features. Now you can share your settings between different instances of the plugin and thus synchronize the instances. Key features: * MIDI velocity amplification and timing manipulation plugin * Swing and shuffle rhythms * Pre-generator dynamics * *Tempo rubato* * Pattern (sliders) or shape-controlled * MIDI filters * Smart quantization * Group / link individual instances of B.Schaffl * Free and open source What's new: * Shared data: Link controllers between different instances * New plugin sub-title * Plugin description * Bugfixes Acknowledgements: * Bart Brouns for the original idea plus subsequent ideas about principle and features * Robin Gareus for ideas to technically solve *rubato*-related problems * Jatin Chowdhury for ideas to technically solve shared data storage Links * Project website: https://github.com/sjaehn/BSchaffl * Features/Tutorial : https://www.youtube.com/watch?v=CBwkYDk5reU Have fun! Sven

4 years, 8 months

Reminder: Quarterly Release Pact (next release day 2021-01-15)

by software＠linuxaudio.org

The release pact is an informal agreement to aim for shared, scheduled release dates. We agree to release at least four times a year: January, April, July and October the 15th. To participate you just need to do a release. There is no need to register in advance or ask for permission to participate. A release is an important step in the development and life of software. Users look forward to updates and improvements, but they mean additional work for developers. It is often very hard to decide if and when to release, so developers tend to wait and postpone. There do not seem to be any objective, measurable reasons that could lead to a decision. Therefore we have decided to use time as a basis. Why should you schedule (at least) four releases per year? Developer side: * Incentive to release something. Releases are better than git progress. They get packaged, they indicate a (relatively) good state of the program. * Momentum/Peer Pressure: Other people are going to release, so will I. * Healthy, Active Community: Being in a developer group that you see working (by their releases) is a good motivation to do something yourself. User side: * Announcements: Keep the software in the public eye * Trust. People see that the software is in development and is cared for. * The "last updated" date should never be more than 4 months away and always the current year. * Swarm Marketing: A small release does not have much impact and won't get featured often by news sites. A whole group of software releases demands more attention. At the moment we simply release on the same date, but in the future this could grow closer together. As in: joined press statements etc. Minimum Viable Release: * "Fixed typo in documentation" should be enough. Especially for software that has huge release intervals, like a year or longer, there is public uncertainty if a project is just "working as intended" or dead. A minor release with minimal changes is still a signal to the public that the software is not forgotten. * There is always something to do: Non-Code accomplishments like writing documentation and user manuals are also a (very good) reason to release Where can you announce a release? * Send a mail to linux-audio-announce(a)lists.linuxaudio.org .No registration needed for posting, the list is moderated. * Also send a mail to linux-audio-user(a)lists.linuxaudio.org and linux-audio-dev(a)lists.linuxaudio.org . Cross-Posting releases is accepted. These two lists need registration though. * Submit your release, or the whole software to https://libreav.org * Post to https://linuxmusicians.com/viewforum.php?f=24 * Submit a new link or text post to https://old.reddit.com/r/linuxaudio/ * Add or update your entry at https://gitlab.com/nodiscc/awesome-linuxaudio (see https://gitlab.com/nodiscc/awesome-linuxaudio/-/blob/master/CONTRIBUTING.md ) * Add or update your software to Wikipedia * Add or update your software on this wikipedia list https://en.wikipedia.org/wiki/List_of_Linux_audio_software * Chat with your developer-peers on freenodes IRC channel #lad ( Libre/Linux Audio Developers ) Miscellaneous * How to give version numbers: Semantic Versioning https://semver.org/ * Provide release notes and a CHANGELOG https://keepachangelog.com/en/1.0.0/ ("Don’t let your friends dump git logs into changelogs.") * Provide a real release as tarball and/or Github Gitlab release (resulting in a tarball). Distributions want a stable set of files for packaging. A git tag alone is not stable. * Check your software and information (like README, .desktop file, your own website etc.) if it is up to date. Take inspiration from one of the many release guides, such as https://radek.io/2015/11/23/release-checklist/ * The Documentation Compendium: "Why must you document your project? - Various templates & tips on writing high-quality documentation that people want to read." https://github.com/kylelobo/The-Documentation-Compendium#why_document * Does your software still create (dot-)files directly in the homedir? Start supporting the XDG Base Directory Specification https://specifications.freedesktop.org/basedir-spec/basedir-spec-latest.html

4 years, 8 months

mioctl: open-source iConnectivity mioXL/mioXM control software

by Panu Matilainen

Hi there, This is the initial announcement of mioctl project, bringing iConnectivity X-series (mioXL, mioXM) configuration to Linux and other platforms: https://codeberg.org/pmatilai/mioctl Whereas the the previous generation interfaces from iConnectivity was well-documented and for which an open-source GUI application already exists [1], the X-series control protocol is completely different and undocumented as of this writing, so this project is reverse-engineered by analyzing RTP traffic between Auracle and a mioXL. It is early days in the project but what it can do right now is - List, load and save (including rename) presets - List, add and remove routes - List device ports by their names - List active remaps and filters - List connected usb hosted devices - View device information (model, serial, firmware version) - View network configuration For many missing functionalities it's merely a matter of finding the time to to implement, USB host reservation looks more complicated but should get there eventually. [1] https://github.com/dehnhardt/iconnconfig - Panu -

4 years, 8 months

Virtual MIDI Piano Keyboard 0.8.0 and Drumstick libs 2.0.0 released

by Pedro Lopez-Cabanillas

Virtual MIDI Piano Keyboard is a MIDI events generator and receiver. It doesn't produce any sound by itself, but can be used to drive a MIDI synthesizer (either hardware or software, internal or external). You can use the computer's keyboard to play MIDI notes, and also the mouse. You can use the Virtual MIDI Piano Keyboard to display the played MIDI notes from another instrument or MIDI file player. Project web site: https://vmpk.sourceforge.io/ Downloads: https://sourceforge.net/projects/vmpk/files/vmpk/0.8.0/ Drumstick is a set of MIDI libraries using C++/Qt5 idioms and style. Includes a C++ wrapper around the ALSA library sequencer interface: ALSA sequencer provides software support for MIDI technology on Linux. A complementary library provides classes for processing SMF (Standard MIDI files: .MID/.KAR), and Cakewalk (.WRK) file formats. A multiplatform realtime MIDI I/O library and a GUI Widgets libraries are also provided. Project web site: https://drumstick.sourceforge.io/ Downloads: https://sourceforge.net/projects/drumstick/files/2.0.0/ License of both projects: GPL v3 or later

4 years, 8 months

[LAU] Guitarix2 release version 0.42.1

by Hermann Meyer

I'm pleased to announce the release of guitarix2-0.42.1 A virtual guitar amplifier for Linux running with jack (Jack Audio Connection Kit) released under the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This is a quick Fix release: * Make new Output Limiter less conservative * Add Indicator Widget for the Limiter to show limiting levels * Increase range for Volume controls on the Power Amp plugin * Fix MultiBandDistortion introduce sonic noise * Add Limiter to the Ladspa plugin * add configure option to build and link libgxw(mm) statically Last release: https://github.com/brummer10/guitarix/releases/tag/V0.42.1 Project Page on github: https://github.com/brummer10/guitarix Project Page on SourceForge: https://sourceforge.net/projects/guitarix/

4 years, 8 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Linux-audio-announce