I was tempted to call this the "2025 update" but since I usually take leave in December and spend most of it tinkering, quite likely I'll do some of this before new year or at least by the end of January. The next Tuskfish CMS release will be version 2.1. Core functionality will remain unchanged, but I will add support for blocks, and if I can sort out a couple of issues, native multilanguage. Not a crappy hacked up multilanguage, but one that is baked into the core and seamless. I'll be making use of some of the more recent langauge features in PHP, which will raise the minimum version required to PHP 8.3. Please note that the contemporary versions of PHP are now V8.3 and V8.4, with V8.2 reaching end of life in December.

Tuskfish 2.0.8 is an incremental update with a bunch of small fixes and refinements. New features include an alternate compact template option for collections that displays child content as a list, support for a 3rd Yubikey hardware token, and extension of html toggling of content online status extended to admin search results. There are several improvements to the video templates as well: They are now responsive, and alternate selectable templates are available for common aspect ratios including 16:9, 4:3, 21:9 and 1:1.

TLDR: Quick charging technologies can cause problems. The headphones charge reliably over 5 volt connections, but may cease charging if there is an option to negotiate higher voltage charging as found on many recent chargers. Try using an ordinary USB cable without Power Delivery (PD) capabilities, or a charger that won't output more than 5 volts, and charging may be yours again. Also applies to power banks.

Optional support for ImageMagick V6 is now available. This gives much better quality thumbnails than PHP's native GD2 library, but at the cost of some manual configuration. You need to:

  • Have ImageMagic installed on your webserver (most hosting companies provide this).
  • Access to PHP's exec() function must be enabled (it is often disabled by default through the disable_functions setting in php.ini).
  • Swap in an alternative ResizeImage.php trait file (provided).
  • Configure the file path to an sRGB.icc colour profile on your server (you can download one if necessary).
  • Clear the image cache (html/cache), which will cause thumbnails to be rebuilt.

You can adjust the level of compression and sharpening in the trait file method createThumbnailWithExec().

Update 2: I got annoyed and added optional support for ImageMagick V6, some manual configuration is required.

Update: The PECL extension for ImageMagick is broken for PHP 8.3. It has been busted for over a year and nobody seems to give a damn, so this work is shelved until it gets fixed.

I've never been happy with thumbnails generated by PHP's native GD2 library, so I'm adding optional support for ImageMagick in the next release. If ImageMagick is installed, Tuskfish will use it by default, and if not, it will fall back to GD2. ImageMagick is widely available on most, if not all, commercial web hosts.

ImageMagick offers two benefits over GD2:

  • It generates much better quality thumbnails than PHP's native GD2 library. The thumbnails generated by GD2 are a bit fuzzy, and larger images can actually look pretty bad.
  • ImageMagick is aware of colour profiles and will preserve colour space information. GD2 is not only unaware of colour profiles, but actually discards them, which causes colour shifts in images that can render them drab and washed out.

To keep things simple, I will only be supporting the sRGB colour profile, which is the default for the web. You should already be converting your master images in sRGB before using them on websites anyway, because browsers generally will not be able to render other profiles correctly.

Recommended. I've had a Zoom F3 for a while now, but I've only recently taken it on a field trip. I bought it to record wildlife and environmental ambiences (a hobby), but most of the time I'm recording meetings (work), and pack a Zoom H6 (not the new "essentials" version).

The H6 has a few shortcomings, mainly its size and very average quality preamps. But it is an enormously flexible device and has an intuitive interface with hardware knobs for each microphone input. The X-Y stereo capsule it ships with is great for meetings, if you just want an ok recording to check your facts later.

But this time, I needed something light, so I took the F3 instead, and it worked out far better than I expected. Apart from the obvious advantage (size), the F3 has a few improvements over the H6.

Update: The new Tascam FR-AV2 is the new best portable field recorder, but significantly more expensive.

If you've ever tried make video recordings (screencasts) of PowerPoint presentations at a conference, you know one thing: The normies don't understand and don't care about your requirements related to cable length or sitting in the front row. You might be able to extend their audience reach by 1,000 times what they had in the auditorium, but their eyes will glaze over when you try to explain it. So, here's how how to produce a beautiful recording in an uncooperative environment.

You will need a microphone, a field recorder (preferably 32 bit), any kind of video camera and access to the PowerPoint files afterwards. TLDR: We will scrub through the camera footage in a video editor timeline to quickly mark the slide transition points. We will use those to set manual slide transition times in PowerPoint. Then we will record the automated slideshow in OBS, sync the audio from the field recorder, and we're done.

Ever wondered by many professional YouTubers shoot video at 24 frames per second? You have probably heard it explained away as "the most cinematic" frame rate. You probably also heard that people can't see frame rates beyond about 30 fps. Well, that's wrong (ask a gamer if they notice the difference between 60 and 144 fps).

The real reason why 24 fps is so common is purely historical: It is basically the minimum frame rate that allows a moving image without annoying flickering. Video used to be shot on physical film, so keeping the frame rate as low as possible saved on film costs. Apparently it also helped with sound synchronisation.

Neither of these are valid constraints in the modern era. Sticking to 24 fps just makes panning shots look terrible due to judder, especially on a big screen. You are better off going for 50 or 60 fps depending on your region, which will deliver a far more fluid image.

The default upload file size limit in NGINX is 1 MB, so if you are using it as a reverse proxy for your Tuskfish CMS site, you may need to increase it. You can do this globally for the server itself, or you can do it on a site-by-site basis.

Recommended. I just installed the new Arctic Liquid Freezer III 280 on my AMD 5950x. It is a beast of a cooler. In an OCCT stability test with all 16 cores engaged at 100% workload my CPU sustains 4.5 GHz with a maximum temperature of 63°C, and that's in a warm room (the aircon is broken). There are some reviews showing that it is less effective on Intel CPUs (no idea why) but for AM4/5 it's top tier.

But you are going to hate the AM4/5 installation process. Here's how to make it less painful.