Blog
- Email woes
I appear to be causing aggravation in the office by not being able to find emails. However, it's not me being dumb; the problem is caused by the people who are asking me not being clear enough:
- If you've forwarded an email on to me, please say so. This is because the email is now from you, not from the customer.
- Please state what the subject of the email message is. I may have received many emails from you and it's not immediately obvious which one you're referring to.
- If you forward a customer's email on, please include that customer's name in the subject line.
Example: When I'm asked to find an email and I'm told it's from $NAME at $COMPANY, then searching for $COMPANY or $NAME will not find the relevant email, now that it's addressed from $COLLEAGUE with the subject "FW: New form".
- Minecraft
So I got into Minecraft, wrote my own server software, called it "Just another Minecraft Server" (JAMS), and set up Fuzzle Forums.
- Cycling
I’ve finally taken up cycling again.
Edit: However, it is -5°C this morning...
- PulseAudio with JACK
These two programs have a reputation of not playing nicely. Here's my setup that makes these two, along with a little help from qjackctl, work together.
Set up PulseAudio so that by default no audio device driver is loaded. This usually just means commenting out bits of the default config. Create a file, I called it paon.sh, with the following content:
#!/bin/sh
pactl load-module module-jack-sink > /tmp/pa-modules.txt
pactl load-module module-jack-source >> /tmp/pa-modules.txt
for i in `cat /tmp/pa-modules-null.txt`; do pactl unload-module $i; done
The next file, paoff.sh, contains this:
#!/bin/sh
pactl load-module module-null-sink > /tmp/pa-modules-null.txt
for i in `cat /tmp/pa-modules.txt`; do pactl unload-module $i; done
Configure qjackctl to execute paon.sh in Execute script after
Startup
, and paoff.sh in Execute script on Shutdown
.
After these changes, by default PA is there and working but has no audio
output. When JACK is started via
qjackctl, it will load the appropriate modules, and cleanly remove them on
(a clean) shutdown.
You could extend this by having letting PA use ALSA by default, and use an on-Startup/after-Shutdown script to remove and load the ALSA drivers. I didn't feel the need to do this.