Hey hey,
finally - or all too soon - I have uploaded a new song:
https://youtu.be/PP5pGRKmz9c
It's baroque influenced electronica with my friend Ritual Notes playing flute.
The external synths used are the usual analogue and wavetable candidates. On
Linux Csound provided the mbria-like sound and anything drum-like. The latter
was sampled and loaded into LinuxSampler together with strings from the VPO
and a commercial harpsichord. Yoshimi supplied a few basses and stabs.
Enjoy and best wishes,
Jeanette
--
* Youtube: https://www.youtube.com/channel/UCMS4rfGrTwz8W7jhC1Jnv7g
* GitHub: https://github.com/jeanette-c
Hello all,
Has anyone been using csound with -+rtaudio=jack while using pipewire as
their jack backend? I've found that it leads to some weirdness,
including not playing back sound at all sometimes (this was happening in
non-predictable ways). Also, it seems to require the -B buffer size to
be 2048 for my machine, even though pw-top says it's running at 1024 as
its buffer size.
Csound has been working great using -+rtaudio=pulse, but when I want to
use it for live midi stuff, I definitely will need to use the
-+rtaudio=alsa, or -+rtaudio=jack for that lower latency.
Thank you again for your help,
Brandon Hale
This release introduces major improvements to DSP performance and tuning
flexibility.
New Features
*Multithreaded Audio Engine*
Loopino now supports multithreaded audio processing to reduce load on
the main audio thread.
*
Audio processing can be buffered as half-frame or full-frame blocks
*
Buffered DSP blocks are processed in a worker thread
*
Significantly reduces DSP load and xruns in the main audio thread
*
Designed to improve stability under high polyphony and complex
modulation scenarios
*Micro Tuning Support (Scala)*
Loopino now supports microtonal tuning via Scala.
*
Built-in factory tuning scales included
*
Drag & drop support for Scala .scl files
*
Drag & drop support for Scala .kbm key mapping files
*
Flexible keyboard-to-scale mapping for alternative tuning systems
Notes
This update improves real-time performance and expands Loopino’s musical
language beyond standard equal temperament, making it suitable for
high-load sound design and microtonal composition alike.
Project Page:
https://github.com/brummer10/Loopino
Release Page:
https://github.com/brummer10/Loopino/releases/tag/v0.9.5
This release focuses on workflow improvements, clearer signal routing,
and new creative options.
### New Features
- **Drag & Drop Processing Chains**
 - Filter and Machine chains can now be reordered via drag and drop
 - Machine chain changes trigger a full key cache rebuild
 - Filter chain changes apply immediately in real time
- **Reverse Sample Playback**
 - Samples can now be played in reverse
 - Fully integrated into the existing voice and filter pipeline
- **New Machine: Vintage (TimeMachine)**
 - A new offline machine focused on temporal character and coloration
 - Operates during key cache generation
 - Designed for non-destructive experimentation with timing and feel
---
### Architecture & Workflow
- Clear separation between **offline machines** and **real-time filters**
- Deterministic signal flow from sample → machine → key cache → voices →
filters
- Improved internal consistency and predictability
---
### Documentation
- Added a new [**Loopino
Wiki**](https://github.com/brummer10/Loopino/wiki/User-Documentation)
- User-facing documentation covering:
 - Sample loading and destructive trimming
 - Machines vs Filters
 - Signal flow and processing stages
- Documentation aims to be precise, technical, and transparent
---
### Notes
- Existing projects remain compatible
---
Project Page:
https://github.com/brummer10/Loopino
Release Page:
https://github.com/brummer10/Loopino/releases/tag/v0.9.0
As always, feedback is welcome.
Hi all,
just a quick "addendum" to the earlier announcement here:
The organizing team of this year's Linux Audio Conference (see below) has also
given this conference a "theme" that should spark some ideas for papers or
discussion, and has now added the following blurb to the home page
(see https://lac.linuxaudio.org/2026/) -
###
Conference theme:
Large language models and Free/Libre/open source software.
"I am not comfortable contributing to a project that extensively uses AI."
from a post found in a pull request to a github repository.
This year's LAC theme explores questions relating to the (sometimes uneasy)
relationships that may emerge between LLMs and FLOSS. This of course has many
dimensions, from the purely technical, through to the practical, and finally
to the ethical.
As code repositories such as github roll out support for third-party and their
own LLM agents, this is an area that needs vigorous discussion and assessment.
It is probably not a good idea to ignore it, as it is unlikely to go away.
It may be possible to formulate a position from the LAC community, which we might
carry forward for further consideration in other forums.
Even if such a thing cannot exist, it is still important that we put forward
our ideas in relation to this issue. Therefore, it makes good sense to invite
contributions to this theme and make it a central point of discussion at the LAC.
The LAC2026 organising team.
###
Greetings,
Frank
On Fri, 9 Jan 2026 17:33:01 +0100
Frank Neumann <beachnase(a)web.de> wrote:
> Hi all,
>
> just wanted to share the good news here that in 2026 the LAC (Linux Audio Conference) is
> taking place again, on June 18-20 (Thu-Sat), this time coming back to Maynooth (Ireland)
> where it was already hosted in 2011.
>
> Victor Lazzarini, conference organizer, asked me to help in spreading the word about
> it, so here we go.
>
> All details on music&paper submission process, deadlines, travel and accomodation etc can
> be found at the conference web site: https://lac26.mucs.club/
>
> Greetings, and please feel free to spread the word wherever possible,
> Frank
Hello everybody,
Best wishes for the new year! I've made some small changes to the LAU
mailing list that will hopefully reduce the number of bounces that some
members suffer from:
- The unsubscribe footer has been removed.
- The [LAU] prefix to the subject has been removed.
By making these changes the messages sent to the list should go through
unaltered which would make DMARC/DKIM happier. Especially removing the
[LAU] prefix might be problematic for some, hopefully this doesn't mess
up filtering all too much. So apologies beforehand for any inconvenience
these changes might cause. If any other problems arise from these
changes then let me know!
Best regards,
Jeremy
