Dear list,
please excuse the following for being largely offtopic to linux audio. I
can't seem to find any useful information via startpage.com nor can I
think of a list I am subscribed to to ask the following:
I sometimes have the need to show pdf slides in presentations and like
using pdfpc[1], a "presenter console with multi-monitor support for PDF
files" using an extended X display. I do as well have the need to show
the (single) desktop I am working on. The only way I can achieve this is
to switch back and forth between the two setups using xrandr.
I am using a display manager (fluxbox) with multiple virtual desktops.
I am wondering if there is a smarter less interrupting way.
What if I had one extended display, whose left side is on my laptop's
screen and right side on the video projector, and had something like a
vnc-client on the right side, mirroring what is going on on the left
side of the screen. I could then show what I am working on on the left
screen but also have the pdf presenter console span the left and right
side of this extended display together.
I hope my description and question do make (some) sense.
If anyone has an idea I'd be happy to know!
thanks, and exuse the OT post,
Peter
[1] https://pdfpc.github.io/
Hi.
Since I rely on accessibility and haven't found a "DJing tool" for Linux
which doesn't require a graphical interfaces...
I used to do offline mixes with a bunch of sox instances piped into each
other, orchestrated with a shell script...
Which is rather tedious, so...
I recently came back to this and decided it is a great opportunity
for having a tool vibe-coded.
For playing with vibe-coding, and actually solving a problem I always had.
So I had GPT-5(.1) scratch my itch.
And out came
https://github.com/mlang/clmix
It has a built-in player + metronome for working out bpm, offset
of the main beat grid and start/end cue points.
Seeking works with bars, so you dont have to fiddle with time.
Once you worked out a track by ear, you can do a "snap-to-grid"
using aubio as a beat/onset detector to refine the offset if necessary.
Once you are happy with the track timing, you save it to your DB.
If you have a number of tracks in your DB, you then can
generate a (shuffled) mix. Selection of tracks from the DB
uses a tag expression language, so you can do things like
clmix music.json --random "dnb | jungle" --export beats.wav
clmix will determine the mean bpm, bring all track to the same
tempo and align cue points for you.
Thats basically its main use case for me.
I use mpd with crossfade a lot for playing music at home,
and kind of wanted something that actually can generate good crossfades.
So when I want a "club mix" at home, I now simply
generate it from my favourites I added to the clmix db.
Nothing special, just a tool to get a particular job done,
for a particular user group (command-line junkies).
Vibe-coding was fun.
From idea to first executable code was just a few hours.
However, I have a particular taste when it comes to C++,
so after a while of being amazed that much apparently correct code
was written by the AI, I started to play the "let me fix this" game.
Ended up doing a lot of bikeshedding. OTOH, I still feel
that kind of ping-pong was necessary to keep the code half-way decent.
If you let the AI do its thing without supervision, the code
ends up pretty unreadable after a while.
In any case, I make the fact this is vibe coded clear because
I do definitely not claim the fame. While I love to play
with programming, this is neither my dayjob nor do I have a lot of
(recent) practice. So I likely wouldn't have written this
if I didn't have some help. So with all the war around AI use
on the net, I can say this was a nice outcome for me.
Nobodies job was taken away, and I got something nice for maybe $30 of
API costs.
I got what I wanted, and I didn't have to waste a lot of time on it.
In any case, if this is helpful to anyone, enjoy.
--
CYa,
⡍⠁⠗⠊⠕
Hi,
I am trying to locate the firmware for RME HDSP Multi- and Digiface on
Debian stable, as referenced on https://wiki.debian.org/Firmware/List
but it seems none of the packages firmware-linux-nonfree
firmware-linux-free nor alsa-firmware-loaders
do provide these files (anymore). Is this intenional, and is there
another official source for
multiface_firmware.bin
multiface_firmware_rev11.bin
digiface_firmware.bin
digiface_firmware_rev11.bin
?
Thanks for all pointers,
best, Peter
Loopino — New Release: Faster Workflow, Deeper Control, More
Sound-Shaping Power
The latest Loopino update brings a major boost in workflow, sampling
flexibility, and creative sound design tools. Built for fast
experimentation and musical expression, Loopino now makes it easier than
ever to load, capture, shape, and export unique audio textures.
Effortlessly drag and drop samples or browse your files directly inside
Loopino. Record new material on the fly, trim to precise clip marks, and
refine your sounds with non-destructive fade-outs and integrated pitch
tracking. The Micro Loop Generator has been expanded to let you choose
loop count and duration, turning any waveform into evolving rhythmic
fragments or playable micro-textures.
For deeper shaping, Loopino includes non-destructive wave sharpers
(square & saw), a full ADSR envelope, and a versatile LP/HP ladder
filter with cutoff and resonance control. Phase modulation sources
(sine, triangle, noise, Juno-style), vibrato, tremolo, and root
frequency control open the door to expressive synthesis possibilities.
And with up to 48 voices, Loopino handles dense, layered sounds with ease.
Export your processed samples or micro-loops as WAV files—automatically
tuned to your selected key—and save or load presets to build your own
library of sounds.
Key Features
* Drag-and-drop sample loading
* Integrated file browser
* On-the-fly audio recording
* Trim samples to clip marks
* Non-destructive fade-out processing
* Integrated pitch tracker
* Micro Loop Generator with selectable loop number & duration
* Square & sawtooth wave sharpers (non-destructive)
* Full ADSR envelope
* Preset save/load system
* Export processed samples/loops as WAV in selected key
* LP/HP ladder filter with resonance & cutoff
* Phase modulators: sine, triangle, noise & Juno-style
* Vibrato & tremolo
* Root frequency control
* Up to 48 voices for polyphonic playback
Loopino continues to evolve into a flexible, creative sampler-synth
hybrid—perfect for sound designers, experimental musicians, and anyone
who loves transforming audio into something new.
Availability
* Linux: Standalone application, CLAP plugin, VST2 plugin
* Windows: CLAP plugin, VST2 plugin
Project Page:
https://github.com/brummer10/Loopino
Release Page:
https://github.com/brummer10/Loopino/releases/tag/v0.0.2
Halle,
is there any OS softwre which I can run om ny
webserver to handle communications withon a choir,
looking around I only see commersial ones ?
Regards,
/Karl Hammar
Hi all,
I'm Lorenzo, and together with Steven Goodwin, I'm one of the managers of
the newly formed "Music Production" devroom at the upcoming FOSDEM event in
Brussels.
I'm not sure how many of you are aware of FOSDEM or know what it is, but in
a nutshell it's the biggest event in Europe completely devoted to free and
open source software: it's completely free to attend, and it hosts dozens
of devrooms dedicated to different topics over the course of two days, each
with its own sessions, which means hundreds of presentations available to
watch. Plus, there's many stands from popular open source projects
scattered over the campus that hosts the event, and home to thousands of
attendees every year.
https://fosdem.org/2026/
Long story short, music had rarely seen any representation at FOSDEM (since
I started 10 years ago, for sure). Whenever I had a music related topic I
wanted to present, I always had to find a devroom that had some vague
alignment to the topic, hoping my submission would not be seen as too out
of scope. As such, I was really happy when they finally accepted our
proposal to host a devroom purely devoted to Music Production as well.
We'll only have half a day on Sunday afternoon, but it's a great start
IMHO, and that might be plenty of time if we'll have enough content and
many interested attendees!
Which is why I'm writing on the list here too. As I'm writing, we still
have a few days to go for the Call for Proposals, which you can find here:
https://music.lminiero.it/fosdem/
If you have anything interesting you'd like to talk about during the
session, please do consider submitting a talk! The official deadline is the
1st of December.
In general, I hope you'll all consider attending the event. FOSDEM will
take place on the 31st of January and the 1st of February, and as I was
anticipating, our session should take place during the afternoon of the
second day. Whether you've attended FOSDEM before or not, it's an
experience I always recommend to anyone who loves open source: if not to
attend our session, to experience the event as a whole.
In case you have any question, please don't hesitate to get in touch.
Thanks,
Lorenzo
*Loopino — Creative Micro-Loop Sampler Now Available*
Loopino is a lightweight yet powerful sampler designed for experimental
sound design, rhythmic exploration, and fast musical sketching. Load any
audio file and instantly slice, extract, and transform it—Loopino lets
you isolate multiple micro-loops from a single sample and play them like
instruments.
At its core, Loopino features a musical architecture built for tone
shaping and performance. A built-in Moog-style ladder filter and a
flexible “Sharper” saturator add warmth, grit, or bite. Pitch and
fundamental frequency control enable precise tuning, while dedicated
ADSR envelopes allow expressive dynamics. Save and load your own presets
to build a library of playable textures, loops, and sonic ideas.
*Key Features*
*
Load a sample and automatically carve out multiple micro-loops
*
Per-loop playback, manipulation, and performance
*
Integrated Moog-style ladder filter for classic analogue character
*
Sharper module for tonal shaping, saturation & edge
*
Fundamental frequency control for accurate tuning
*
ADSR envelope system for dynamic expression
*
Full preset save/load system for creative workflows
*Availability*
*
*Linux:* Standalone application + CLAP plugin
*
*Windows:* CLAP plugin
Loopino is free, open, and built for musicians, sound designers, and
curious audio explorers. Whether you want evolving textures, rhythmic
fragments, or new sample-based instruments—Loopino turns any sound into
inspiration.
Project Page (Source):
https://github.com/brummer10/Loopino
Release Page(Binaries):
https://github.com/brummer10/Loopino/releases/tag/v0.0.1
Regards
Hermann
Hey all!
I am excited to announce SampleWorks, a cross-platform* sound sample
manager inspired by the concept of a light table.
The main objective of the project is to facilitate a highly efficient and
intuitive workflow in working with large collections of samples. I'll
attach a copy of the README at the end of this message to give you a little
more info.
PLEASE NOTE that the current version is just a demo, but useful
functionality will be coming soon! But if you want a taste of what's in the
works, visit the GitHub repo at https://github.com/caelia/sampleworks
* It's theoretically cross-platform, but so far has only been tested on
Linux
README.md
----------------------------------------------------------------------------------------
# SampleWorks
SampleWorks is a cross-platform sound sample manager inspired by the
concept of a [light table](https://en.wikipedia.org/wiki/Light_table). The
main objective of the project is to facilitate a very efficient workflow
when organizing and processing collections of samples.
**IMPORTANT: the current version is just a demo!**
## Running the demo
1. Clone the repo and `cargo run`. If that's not enough info for you, please
be patient - we're just getting started here!
2. In addition to compiling a bunch of code, SampleWorks needs to generate
waveform images for 59 audio samples. It's pretty slow in debug mode.
3. Once the GUI comes up, you can: (1) click on a waveform image to play the
corresponding sound; (2) stop playback by clicking again; or (3) click on a
different image to play a different sound.
*Please note that this program has only been tested on my own Manjaro Linux
system. Let me know if it doesn't work for you!*
## Features planned for v1.0
* Quick A/B comparisons
* An organizer window for sorting and grouping related samples
* Comprehensive metadata management. Metadata will be used for filtering and
sorting, and can be set through:
- extracting embedded metadata from files
- automated analysis of audio content
- tagging of individual files or groups of files by the user
* Automated export of sample packs, ensuring consistency and conformance
to the requirements of the target system or device (e.g. maximum length
or file size, file format, stereo or mono, etc.)
* The ability to extract and process regions of a source file. So, for
example, if you have a recording that includes multiple drum hits, you
will be able to select a region of the source file with your mouse, apply
changes to just that region, and eventually export it as a new sample.
* Some form of editing/filtering capability (but see Open Questions).
## Open questions
* Should SampleWorks have its own sound editing/filtering capabilities? I do
not want to reinvent the wheel, so it would be nice to leverage an existing
sound editor such as Audacity, but I'm not sure this can be done in a way
that
supports the efficient workflow that I'm aiming for.
* What, if anything, should be the relationship between SampleWorks and
other
audio production software such as DAWs? Does it make sense to have a plugin
version of SW?
* Is it feasible to generate waveform images that use color to distinguish
different pitches? Or should we maybe use spectrograms?
* How much work should we put into analysis tools? For example, it would be
possible and maybe desirable to do a visual comparison between the waveforms
or spectrograms of two similar samples. Is that worth the extra effort, or
should we just focus on listening?
* What's the best way to manage in-process sound objects? E.g. if the user
extracts a region from a source file, it becomes its own object in the GUI.
If that object is cloned (in order, for example, to compare how two
different
FX plugins affect the sound), then another object is created. So a
medium-sized
project can potentially have hundreds of sound objects, some of which may be
duplicates. From the POV of storage and memory efficiency, it would be best
to represent each object as a reference to an audio source + changes, but at
some point a new audio file should be saved to disk, for two reasons: (1) to
prevent discrepancies between the audio referenced in a project and that
which
is saved on disk, and (2) to preserve content in case of a crash.
* Given that the objects to be displayed will include both sound files on
disk,
and derived objects, consisting of files or regions of files with
modifications
applied, what is the best way to assign object IDs?
## Last but not least ...
Thanks for your interest! If you have any feedback, please use the
Discussions and Issues sections of this repository.
