jorgenmodin.net - Blog
See other options on Linux than Ardour, such as ffmpeg, sox and Audacity below, with examples.
Ardour, Jack and the Calf plugins are all in the Ubuntu repositories if you are using Ubuntu.
However PulseAudio in Ubuntu does not play well with Ardour, and you would probably prefer a Linux distribution that natively uses Jack instead, and not PulseAudio. The problems with PulseAudio and Jack together are listed here:
One option is to use the Ubuntu Studio Linux distribution directly on your computer, or in a virtual machine for Ardour/Jack on a pulseaudio host OS (Linux) . The latter works surprisingly well; I'm using it!
Ardour's plugin system is just gorgeous. Above two of the "Calf" series plugins in the foreground: An equalizer and a compressor. Effects can be stacked and signals routed in different ways. If you use Ardour 5 in Ubuntu studio, there are hundreds of effects plugins to choose from.
Apply the compressor twice. The effect was better I felt when using a moderate compression twice instead of a stronger once, as mentioned here:
"If you want to heavily compress a voice recording without making it sound too unnatural, use two or three compressors in series. This will sound better than using drastic settings on a single compressor"
That page has a lof of other useful advice as well.
Before you compress
Clipping is accentuated by compression in my limited experience. So if you record with clipping it may be a good idea to re-record. It's better to redo a recording until the suond is good, than try to fix it afterwards. Gigo.
- Audacity has and can use a set of effects plugins
- ffmpeg has and can use a set of effects plugins
- sox has a set of effects
But after having seen Ardour, who cares? :D Although sox and ffmpeg can be used from scripts, it must be said.
Here are the settings that worked for me, in Audacity's compress effect:
Threshold: -16dB first time (I think), -13dB second time
Noise floor: -30dB
Attack time: lowest (0.10 secs)
Release time: 1.0 secs first time, 2.2 secs second time
sox has compression. I am toying with this one, basically lifted from the man page. At least it looks a bit complex:
sox audio-in.wav soxied.wav gain -28 mcompand "0.005,0.1 -47,-60,-34,-55,-17,-33,0,-10" 100 "0.003,0.05 -47,-60,-34,-55,-17,-33,0,-10" 400 "0.000625,0.0125 -47,-60,-34,-50,-15,-33,0,-10" 1600 "0.0001,0.025 -47,-60,-34,-50,-31,-31,-0,-30" 6400 "0,0.025 -38,-60,-28,-28,-0,-25" gain 15 highpass 22 highpass 22 sinc -n 255 -b 16 -17500 gain 9 lowpass -1 17801
ffmpeg -i screncast-audio.wav -vf "compand=points=-80/-105|-62/-80|-15.4/-15.4|0/-12|20/-7.6" comptest.wav
Tested by me:
ffmpeg -i in.mov -vf "transpose=2,transpose=2" -c:a copy -t 10 out.mov
Currently I use this:
Recording - Kazam, can record region of the desktop, among other things
Editing - KDEnlive, shows the sound graph very well and makes it easy to punch in markers with just typing "*", and to then remove pauses and extraneous and erroneous words. You make cuts by typing "x" and then cut in a good place. Cut once more, then type "s" to get the selection tool, select the cut part, delete it. Finally right click in the empty space and choose "Remove empty" space from the context menu. That will move all clips in that channel to the right of the cut left in order to close the space.
KDEnlive is no good in my tests at compressing though, so I render it losslessly, and procede to the next step:
Compressing - Handbrake - still fiddling with the settings here. I want no JPEG artefacts since It's a screencast with sharp edges and few colors, so one would assume some kind of GIF or PNG encoding would be good.
Here are my settings right now for producing a screen cast:
Sound: Mono, mp3, bitrate: 96
Video: Bitrate 150kb/s. Encoder: H264. Tune: still image. Variable frame rate, 2-pass encoding.
PHINCS-256 is a high-security post-quantum stateless hash-based signature scheme
Read more: Link - SPHINCS: Introduction
Chacha20 is a secure, fast, and amazingly simple encryption algorithm. It's author Daniel J. Bernstein explains it well in his Salsa20 and Chacha20 design papers (which I recommend), but did not dwell on details experts already know. Filling the gap took me a while.
Read more: Link - The design of Chacha20
Found an option in Compiz manager -> General options -> Focus and raise behaviour
Changed the 'Focus prevention level' from "Low" to "Normal" and it seems to have worked
Game theory credibility, could be interesting for smart contracts:
I really like it.
Read more: Link - Discourse