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
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
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 -
Hello all,
Release 1.8.0 of the zita-resampler library is now available at
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads>
* Both the Resampler and VResampler classes can now be compiled
to use SSE2 intrinsics. This at least doubles the speed, and
is enabled in the supplied Makefile.
* Some new documented test programs, also showing how to use the
two classes.
* Some (minor) bugfixes.
This should be a drop-in replacement for 1.6.2, which will remain
available for some time in case there are any problems.
Enjoy, and best wishes for the next solar orbit !
--
FA
Greetings !
https://www.youtube.com/watch?v=blAUTXw9tiY
An excerpt from a long moody guitar improvisation with a drone sequence
in VCV Rack. Very simple throughout but maybe a peaceful listen, maybe a
little reflective.
I hope all LAU folk are enjoying a safe and mellow holiday season ! All
blessings upon you all. :)
Best regards,
dp
Hey hey,
is there a way to tell PulseAudio to connect to two SPECIFIC ports, like:
system:playback_17 and system:playback_18 instead of the default which is _1
and _2 ?
I know the output module is called jack_out, but I didn't find any info on
options.
Best wishes and thanks for any pointers,
Jeanette
--
* Website: http://juliencoder.de - for summer is a state of sound
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* Audiobombs: https://www.audiobombs.com/users/jeanette_c
* GitHub: https://github.com/jeanette-c
But tell me what happens when it stops? <3
(Britney Spears)
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/