Hello all,
Zita-resampler 1.11.2 is now available on
<http://kokkinizita.linuxaudio.org/linuxaudio/downloads/index.html>
This release adds Arm64 NEON code for the Resampler and Vresampler
classes, contributed by Nicolas Belin. On an Rpi3b this improves
throughput by a factor of around 2.5.
Ciao,
--
FA
Hi,
I was frustrated by the font sizes in Calf when used with a high
resolution screen. So, I made new styles with bigger font sizes
and I put them on github.
https://github.com/domichel/calf_big_styleshttps://github.com/domichel/calf_big_styles/archive/refs/tags/1.0.0.tar.gz
The only differences from the original styles are the font sizes.
To run 'make' will show you how to install them. If Calf was installed
into /usr, it should be as easy than
su -c "PREFIX=/usr make install"
The next time you run Calf, these styles will appear into the
preferences widget.
Enjoy,
Dominique
Calf Studio Gear: https://calf-studio-gear.org/
Hello all,
I get this error when starting any program using jack (1.9.22):
BDB2034 unable to allocate memory for mutex; resize mutex region
Cannot open DB environment: Cannot allocate memory
This occurs only after the system and jackd have been running for
a long time (weeks or months). Restarting jackd doesn't help,
a reboot is required.
I assume this is related to jackd using a Berkeley Database to
store optional application and port data.
I don't need this functionality, but there seems to be no option
to disable it. Also it seems that BDB is no longer maintained.
Any hints as to how to avoid this problem ?
Ciao,
--
FA
Hi,
I have just released python-alsa-midi version 1.0.2. The only change
since 1.0.1 is Python 3.11 support added.
python-alsa-midi provides pythonic bindings to ALSA MIDI – both
sequencer and rawmidi APIs. It allows Python programs to use most of
Linux MIDI functionality, without the limitations of the portable MIDI
libraries.
Greets,
Jacek
Hi all,
I just have released SoundTracker v1.0.4-pre2. Comparing to 1.0.4-pre1
it contains some bugfixes (including that for critical bugs) and minor
improvements.
SoundTracker download page:
https://sourceforge.net/projects/soundtracker/files/
Regards,
Yury.
Hi LAD,
I'm working on a (very simple) EQ-matching plugin and wanted to check my
understanding/approach and I also have a question. Here's what I do:
1. Analyze spectrum 1 using 50% overlapping blocks each windowed with a
Hann window followed by an FFT and then using the absolute value to get
the magnitude response of each block. Then finally I calculate the
average of all those magnitude responses.
2. Analyze spectrum 2 using the same approach as for spectrum 1
3. Calculate the bin-wise ratio of spectrum 2 / spectrum 1
4. Calculate a linear phase filter response by using the IFFT of the
aforementioned magnitude response ratio and then doing the ifftshift dance
5. Calculate a minimum phase filter response from the magnitude response
ratio by
taking the complex log followed by an IFFT, then folding the negative
time components onto the positive ones, followed by an FFT, complex
eponentiation and a final IFFT. In code:
f = IFFT(exp(FFT(fold(IFFT(log(s))))))
where s is the magnitude response ratio.
The code implementing this is found here:
https://github.com/fps/fps-plugins.lv2/blob/master/eq_match.h
The plugin using it is not done yet.
So here are my questions:
1. Are there any glaring oversights with this approach?
2. What is a sensible approach to regularize this approach. If spectrum
1 has any components near zero magnitude then the division is ill
suited. It works fine for my experiments with distorted guitars, but I
wonder whether I should e.g. just clamp the values of spectrum 1 to
something like -70 dB?
3. If the user wants to smooth the spectrum before calculating the
responses what would be sensible approaches? I thought about smoothing s
with a filter that has a varying bandwidth when expressed in FFT bins or
Hz, but constant, when expressed in e.g. octaves or decades. I'm not
sure how to do that though. Any thoughts?
To finish this email, here is one example (you can play them e.g. by
using mplayer on the console):
1. A guitar recording played through some distortion:
https://github.com/fps/fps-plugins.lv2/blob/master/input.wav?raw=true
2. The same guitar recording played through some distortion and then a
cabinet IR:
https://github.com/fps/fps-plugins.lv2/blob/master/output.wav?raw=true
3. The same guitar played through the recovered filter after matching 1
to 2:
https://github.com/fps/fps-plugins.lv2/blob/master/matched.wav?raw=true
Kind regards,
FPS
--
https://fps.io