Linux-audio-user January 2021

linux-audio-user@lists.linuxaudio.org

41 participants
36 discussions

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

by Hermann Meyer

Hi Mamba release v2.0 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. Release v2.0: Add recent file manager to have fast access to last used Sound-fonts and MIDI files Allow to append/remove MIDI files to/from the master loop while playing (Recent file menu) Implement 'View' menu to allow show/hide the MDID CC controllers and/or the Channel/Program/Instrument view. Allow to select the key-size for the MIDI keyboard (Big/Normal/Small) to better match the screen settings. 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.0 regards hermann

5 years, 2 months

[LAU] 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.

5 years, 2 months

[LAU] Making OSC Messages from the Terminal/Shell

by Brandon Hale

Hello all, Does anyone on here know about any programs that can create OSC messages from the terminal? My ultimate goal is to take stdout and convert it to OSC messages, but I first want to be able to create OSC messages from the shell first. Thank you all for any help you may have, Brandon Hale

5 years, 2 months

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

by Hermann Meyer

Hi Mamba release v1.9 is out Mamba is a Virtual MIDI keyboard with some extended, unique features. This is a quick fix release as I've forgotten to implement jack MIDI input forwarding to ALSA MIDI output. Also it implement proper French translation thanks to Olivier Humbert. 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/v1.9 regards hermann

5 years, 2 months

[LAU] 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

5 years, 2 months

[LAU] 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 -

5 years, 2 months

2026

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-user January 2021