----- Forwarded message from Fons Adriaensen <fons(a)linuxaudio.org> -----
Date: Sun, 18 Aug 2024 21:17:59 +0200
From: Fons Adriaensen <fons(a)linuxaudio.org>
To: Juan P C <audioprof2002(a)hotmail.com>
On Sun, Aug 18, 2024 at 03:03:17PM +0000, Juan P C wrote:
> i was having a private conversation about pulseaudio and he almost got a brain aneurysm. LOL
Full story here:
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/JAPA_bug.txt>
Ciao,
--
FA
----- End forwarded message -----
> the very expensive speakers damaged... by gnome cd player...
i was having a private conversation about pulseaudio and he almost got a brain aneurysm. LOL
Hello all,
I spent a lot a time reading whatever docs I could find for Pipewire,
and discuss things with some users, only to get frustrated more and
more.
Below is a description of the configuration I'd want. If anyone knows
how to do this (it shouldn't be that difficult) that person will
receive my eternal admiration and gratitude.
1. Jack2 and some clients are started manually after I login,
and will be running all the time.
2. Currently the ALSA Jack plugin is used to route audio from
web browsers etc. to Jack. PW may take over this role but
that is not a strict requirement.
3. PW will be started manually when required, and I don't expect
that will happen very often. It may remain running when no longer
needed but shouldn't interfere. It will be used to connect apps
to Jack as in (2), or those that even don't support ALSA, or
maybe to route audio from Jack to Bluetooth etc.
4. All Jack ports created by PW should be permanent and exist
as soon as PW is started, so they can be manually connected
and remain connected even when not in active use.
5. PW should never ever access the sound card used by Jack,
not even if accidentally started when Jack is not running.
It must not force Jack to use dbus in order to get access
to that card. It may manage other sound cards, but preferably
only those explicitly listed.
6. PW must never ever interfere with Jack in any way - making
connections, trying to change the period size, etc. Its only
role is to be a well-behaved Jack client.
7. I do not expect anything 'automatic' to happen when things
are plugged in or out.
8. The PW configuration should be done in such a way such that
it can't be modified by drop-in files from the system package
manager. All configuration should be manual and explicit, and
easy to verify without having to scan a myriad of files and/or
directories and trying to understand how they interact. This
is just basic security.
Ciao,
--
FA
Ratatouille is a Neural Model loader and mixer for Linux/Windows.
This release does several small fixes.
Ratatouille allow to load up to two neural model files and mix there
output. Those models could be [*.nam files](https://tonehunt.org/all) or
[*.json or .aidax files](https://cloud.aida-x.cc/all). So you could
blend from clean to crunch for example, or, go wild and mix different
amp models, or mix a amp with a pedal simulation.
Ratatouille using parallel processing to process the second neural model
and the second IR-File to reduce the dsp load.
The "Delay" control could add a small delay to the second model to
overcome phasing issues, or to add some color/reverb to the sound.
To round up the sound it allow to load up to two Impulse Response files
and mix there output as well. You could try the wildest combinations,
or, be conservative and load just your single preferred IR-File.
Each neural model may have a different expected Sample Rate, Ratatouille
will resample the buffer to match that.
Impulse Response Files will be resampled on the fly to match the session
Sample Rate.
Project Page (source code):
https://github.com/brummer10/Ratatouille.lv2
Release Page (binaries):
https://github.com/brummer10/Ratatouille.lv2/releases/edit/v0.8
enjoy
hermann
