Lukas Dhont’s Close – Film and Blu-ray review

Introduction

Director Lukas Dhont’s Close is simply one of the most powerful films that I have seen, not just recently, but ever. Before getting into my thoughts about the film itself, I’ll cover some of the technical aspects of the Blu-ray release by UK-based label Mubi. I have provided many of the details on the Blu-ray.com page for the film, but will go into a more subjective review of them here. If you’re not interested in the technical aspects, feel free to skip to my review of the film itself at the end of the post.

Close - Leo and Remi riding bicycles

Blu-ray details

Video Quality

The BD50 disc is encoded as MPEG-4 AVC with an average bitrate of 31.80 Mbps in 1080p with a resolution of 1.66:1.

I captured all of the screenshots in this post directly from the Blu-ray, without any modifications except to crop the black bars from the sides (down from 1920×1080 to 1800×1080). Click them to see the full-resolution.

Overall the video quality is outstanding throughout, and fine detail is excellent. The colour palette is expansive and vibrant, yet natural with only a couple notable exceptions. Firstly, some interior scenes have a yellowish cast to them. They tend to be scenes with natural light coming into an otherwise dimly-lit room, but the cast is not distracting. Rather, I believe it was likely an intentional choice to intensify the warmth of the scene. Secondly, many exterior scenes are shot in direct sunlight, resulting in some highlight clipping and, less often, washed out colours. As said, these are very minor nit-picks that certainly do not detract from the outstanding video quality on this Blu-ray release.

Close - Eden Dambrine - Leo picking flowers

Audio Quality

This release features 4 French audio tracks (DTS-HD lossless in both 5.1 surround and 2-channel, as well as lossy DTS), and 1 English audio track (lossy Dolby Digital 2-channel). I used the DTS-HD lossless 5.1 surround French audio track for my review, and found it to be centre-channel driven resulting in dialogue that’s consistently crisp and clear. The use of surround is subtle but very effective in adding nuance, especially to outdoor nature scenes where birds chirping can be heard to the left and right of the viewer. The surround was also successful in creating an encompassing sound stage in sequences with periphery elements, such as school scenes or during Léo’s hockey games.

Close - Leo's hockey practice

Extras

Mubi’s Blu-ray release comes with 2 on-disc extra features, and 1 physical extra:

Both of the Q&A sessions are wonderful supplements worth watching, as they give additional insights into the writers’ perspectives on the film. The art cards are beautiful screen captures, but given their size ratio (1.26:1), they are cropped down from the original video format (1.66:1) which results in some of the scene being omitted.

Close - Leo and Remi resting at school

Additional Blu-ray Notes

This release by Mubi is locked to Region B, which is mainly EMEA (Europe, the Middle East, and Africa), but also includes Australia, New Zealand, and some other territories. That means that playing the disc outside of those regions will require a region-free standalone Blu-ray player or alternative method of video playback such as extraction.

The subtitles are in PGS (Presentation Graphic Stream) format, which is fairly standard for Blu-ray releases. However, since they are graphic-based instead of directly text-based, application playback enhancements (e.g. changing font size or weight) will not be available as they would be with SRT subtitles.

Film Review

Now that I’ve covered the technical merits of the Blu-ray release, I will share my thoughts regarding the film itself (no spoilers, but I will reference some particular scenes and dialogue).

Close focuses on two 13-year-old boy protagonists—Léo (played by Eden Dambrine) and Rémi (played by Gustav De Waele) —who, judging by their interactions on-screen, have been best friends most of their lives. After a schoolmate questions their relationship, Léo begins to distance himself more and more from Rémi, despite both boys missing what they once had. When a chain of events dramatically exacerbates this rift, the fragility of love becomes devastatingly apparent.

Close - Leo and Remi laughing

Though the premise of the film may be simple and undemanding, the execution of that premise is anything but. There are those films that one understands in the mind, and there are those that one understands in the heart. Close is exceedingly rare in that it gratifies both.

From the opening sequence illuminating the playful innocence of childhood, to the tenderness of Léo’s impromptu story to Rémi at a sleepover, to the connection between people who are hurting, the film eloquently portrays the myriad facets of human emotion. Further, the character development—especially of the two leads—is astonishing, in that I felt like I knew them and was a part of their world. Additionally, the juxtaposition between the boys’ affection for one another and their confusion spurred by the ignorance of others forces the viewer to relive the peaks and valleys of growing up.

There are two scenes that stand out to me as perfectly capturing the blissful aura of love. The first is the aforementioned sequence where Léo makes up a story to help Rémi fall asleep:

Imagine… you’re a very small duckling. You just came out of your shell. You’ve just opened your eyes for the very first time. All the ducks are yellow. And so are you… but you’re much more beautiful than the others. You’re special.

Close - Leo and Remi sleeping

The other is Rémi’s oboe concert, which Léo attends in order to show support for his friend. At the start of the scene, Rémi is looking at his sheet music for the performance, and he’s visibly nervous. That is, until he looks up and realises that Léo is there. Though this isn’t a pivotal scene in terms of plot progression, I find it to be incredibly important for two reasons: 1) it thwarts an element of societal gender normativity by showing that boys also need to feel supported; and 2) that the affirmation of a caring smile is all that it takes to completely quell someone’s anxiety and fears.

Close - Remi's oboe concert

Close - Remi's oboe concert - Leo smiling

To elaborate on the first of these two points, many gender ideologies define a divergent set of “appropriate” emotional needs and responses for girls as opposed to boys. Some examples of these differing standards are the notion that “boys don’t cry” or that the need for physical affection as a form of support is warranted for girls, but boys who exhibit this need are somehow weak, effeminate, and inferior. This disparity is such a common theme throughout the film, that Léo even refutes his classmates who question his relationship with Rémi by pointing out that two girls can be close without it being suspect.

Of equal significance is the second point that a smile or other simple gesture of care has a radical impact. All too often, people go about their business paying little regard to the opportunities they have to improve another’s day. It takes nothing more than a quick smile to shift someone’s bad day into a good one simply by showing them that someone outside of “their world” has taken notice. It costs nothing to the giver and yet can mean everything to the receiver.

Conclusion

Given the recent societal politicisation of personal identity issues such as gender roles, sexual orientation, and LGBTQ+ rights, Lukas Dhont’s Close is aptly timed. Whether Léo and Rémi’s relationship is a childhood friendship, a deep yet platonic love for one another, or would have developed into something more, the overarching message is that we as people need to show one another understanding, empathy, compassion, and love in every plausible situation. I’m reminded of Ralph Waldo Emerson who said “You cannot do kindness too soon, for you never know how soon it will be too late“. Our lives and the experiences we have are fragile and ephemeral. Though some of them fade prematurely—and those voids can be the sources of great pain—we can and should hold onto the memories, for those memories are mirrors that can reflect what’s behind us even whilst we try desperately to move forward.

Close - Leo looking at the car window into the rearview mirror

Perfect 10/10:
Filled starFilled starFilled starFilled starFilled starFilled starFilled starFilled starFilled starFilled star

Personal reflection

I have been fortunate enough to see many wonderful films throughout my life thus far, and a select few of them have remained pertinent to me and my life. Never, though, have I had one speak to me remotely as much as Close. Even having watched it countless times now, the message, the impact, the beauty… they all resonate profoundly and deeply within me. It has caused me to reflect on my past experiences and how they have shaped the person that I am today; and to come to terms with who that person is—the goodness that I can offer others; the areas for growth and improvement; and the pain of recognising my immense shortcomings, flaws, and ashamedly ignoble nature.

I can only hope that one day I may have the honour of thanking Lukas Dhont in person for his work and this beautiful microcosm of humanism that resulted. Thank you so very much.

Photos from my March 2023 trip to New Zealand’s South Island

In the beginning of March 2023, I took my best friend to the South Island of New Zealand as a celebration of 20 years of friendship. Though we flew into Auckland (on the North Island), we took the next flight to Queenstown, which is quite far south on the South Island. We then rented a car and worked our way back north from Queenstown to Christchurch, then onto Blenheim (with a stop in Kaikoura on the way), and lastly to Nelson before departing.

For a photographer who especially enjoys landscapes, I had to resist photographing every beautiful area because that’s essentially the entire country. I took thousands of photos (not an exaggeration), but the ones below were some of my favourites. I have organised them according to the area and timeline of our trip.

Feel free to click on any of the thumbnails to see larger versions (though, even the larger versions are still only 25% of the original size).  If you would like to use the full-resolution image, please leave a comment and I will contact you to discuss.

Queenstown

The first three photos (of Lake Wakatipu) were taken from right down the street from our hotel.  Needless to say, the views were wonderful from our balcony as well.

Lake Wakatipu in Queenstown - just after sunrise
Lake Wakatipu in Queenstown – just after sunrise

Lake Wakatipu in Queenstown - at the rocky shoreline
Lake Wakatipu in Queenstown – at the rocky shoreline

Lake Wakatipu in Queenstown - trees hanging over the shore
Lake Wakatipu in Queenstown – trees hanging over the shore

Halfway Bay in Queenstown - radiant blue-green waters
Halfway Bay in Queenstown – radiant blue-green waters

Halfway Bay in Queenstown - much more dramatic clouds
Halfway Bay in Queenstown – much more dramatic clouds

Moke Lake, which is a short drive northwest of Queenstown, ended up being my favourite place not only in the area, but on the entire trip.  It was so beautifully serene and peaceful, and the hike around the lake was magnificent.

Moke Lake in Queenstown - looking back at the entryway
Moke Lake in Queenstown – looking back at the entryway

Moke Lake in Queenstown - broader scope of the entryway
Moke Lake in Queenstown – broader scope of the entryway

Moke Lake in Queenstown - facing north to the mountains
Moke Lake in Queenstown – facing north to the mountains

Moke Lake in Queenstown - a storm brewing
Moke Lake in Queenstown – a storm brewing

Wānaka

The town of Wānaka is about a 1-hour drive northeast of Queenstown, but it is a challenging drive as the road twists and turns through the mountains.  I had to see it, though, primarily because of the infamous tree.

Wānaka Lavender Farm - a bench to take in the views
Wānaka Lavender Farm – a bench to take in the views

The infamous Wānaka Tree
The infamous Wānaka Tree

Christchurch

The trip from Christchurch to Akaroa (where many go to dolphin watch) is lovely through and through.  Approximately halfway, there is an offshoot into the Kaituna Valley.  That’s where I found the beautiful St. Kentigern’s Anglican Church.

St. Kentigern's Anglican Church in Kaituna - from the street
St. Kentigern’s Anglican Church in Kaituna – from the street

St. Kentigern's Anglican Church in Kaituna - opening the gate
St. Kentigern’s Anglican Church in Kaituna – opening the gate

St. Kentigern's Anglican Church in Kaituna - front view
St. Kentigern’s Anglican Church in Kaituna – front view

Nelson

All around “Sunny Nelson” are beautiful beaches and pristine waters.  Making the ~3-hour drive each way to see Cape Farewellthe farthest north spot on the South Islandmay seem daunting (and it is in spots), but it is worth the time.  I wish we could have stayed the night there so that we could have walked more of the trails.

 

The stunning waters at Cable Bay in Nelson
The stunning waters at Cable Bay in Nelson

 

 

Looking north across the vast Pacific Ocean at Cape Farewell
Looking north across the vast Pacific Ocean at Cape Farewell

 

 

At the edge of the world - Cape Farewell
At the edge of the world – Cape Farewell

 

 

Windswept trees on the trail to Wharariki Beach
Windswept trees on the trail to Wharariki Beach

 

Closer to Nelson, the Riwaka Resurgence (which is the source of the Riwaka River) proved to be one of the most gorgeous areas that I saw.  The waters throughout New Zealand were otherworldly colours, but this spot in particular was unlike anything I’ve ever seen.

 

The underground source of the Riwaka River (The Riwaka Resurgence)
The underground source of the Riwaka River (The Riwaka Resurgence)

 

 

The Riwaka River flowing from its source
The Riwaka River flowing from its source

 

Though there were tons of other beautiful spots throughout the trip, these were taken with my digital SLR and were the shots for which I took a substantial amount of time setting up (e.g. positioning a tripod, taking light meter readings, multiple exposures, et cetera). At some point, I may go through the photos that I took with my mobile and post some of them as well.

Cheers,

Nathan Zachary

Fixing Intel Wi-Fi 6 AX200 latency and ping spikes in Linux

Recently, I purchased a mini-PC with an embedded Intel Wi-Fi 6 AX200 wireless chipset and installed Gentoo Linux on it. The reason I purchased the mini-PC was to replace my ageing music server (running MPD), but I also wanted to use it for playing retro video games through my entertainment centre. Everything went well with the OS installation, but during that time, I had it plugged into my router via a wired connection. Once I moved the mini-PC into place in my sitting room and started using the wireless connection, I noticed that there was substantial lag even when doing something simple like typing in a terminal via SSH.

A quick ping test showed that there was clearly a problem with the wireless. For my home network, I consider any ping response time of >=5ms to be unacceptable and indicative of an underlying network problem:

$ ping -c 20 192.168.1.120
PING 192.168.1.120 (192.168.1.120) 56(84) bytes of data.
64 bytes from 192.168.1.120: icmp_seq=1 ttl=64 time=214 ms
64 bytes from 192.168.1.120: icmp_seq=2 ttl=64 time=30.7 ms
64 bytes from 192.168.1.120: icmp_seq=3 ttl=64 time=54.4 ms
64 bytes from 192.168.1.120: icmp_seq=4 ttl=64 time=75.1 ms
64 bytes from 192.168.1.120: icmp_seq=5 ttl=64 time=97.8 ms
64 bytes from 192.168.1.120: icmp_seq=6 ttl=64 time=122 ms
64 bytes from 192.168.1.120: icmp_seq=7 ttl=64 time=142 ms
64 bytes from 192.168.1.120: icmp_seq=8 ttl=64 time=2.46 ms
64 bytes from 192.168.1.120: icmp_seq=9 ttl=64 time=2.30 ms
64 bytes from 192.168.1.120: icmp_seq=10 ttl=64 time=4.72 ms
64 bytes from 192.168.1.120: icmp_seq=11 ttl=64 time=26.3 ms
64 bytes from 192.168.1.120: icmp_seq=12 ttl=64 time=2.30 ms
64 bytes from 192.168.1.120: icmp_seq=13 ttl=64 time=71.7 ms
64 bytes from 192.168.1.120: icmp_seq=14 ttl=64 time=94.6 ms
64 bytes from 192.168.1.120: icmp_seq=15 ttl=64 time=116 ms
64 bytes from 192.168.1.120: icmp_seq=16 ttl=64 time=139 ms
64 bytes from 192.168.1.120: icmp_seq=17 ttl=64 time=161 ms
64 bytes from 192.168.1.120: icmp_seq=18 ttl=64 time=184 ms
64 bytes from 192.168.1.120: icmp_seq=19 ttl=64 time=205 ms
64 bytes from 192.168.1.120: icmp_seq=20 ttl=64 time=23.5 ms

Though 4 of the 20 ping response times were under my 5-millisecond threshold, the other 16 were not only above it, but many of them were nonsensically high for a small home network (e.g. 214ms).

In this type of scenario, the first thing that I consider is the driver and/or firmware for the wireless adapter (namely, the Intel Wi-Fi 6 AX200). For nearly all modern Intel wireless chips the Linux driver is the in-kernel iwlwifi driver, so I didn’t pay too much attention there. That driver has two possible modules to use in conjunction:

  • DVM (iwldvm)
    • The module that supports the firmware for a specific group of (primarily) AGN chips
  • MVM (iwlmvm)
    • The module that supports the firmware for a much broader scope of Intel wireless chips

I had chosen the iwlmvm module and built it into my kernel for convenience. I also then chose to load the corresponding firmware directly into the kernel as well. The gigantic linux-firmware package contains all the various options for the iwlwifi supporting firmware, and from that table, I saw that the original firmware for the Intel Wi-Fi 6 AX200 was named:

iwlwifi-cc-46.3cfab8da.0.ucode

Looking at the current linux-firmware git tree (at the time of this writing), the relevant firmware packages were:

  • iwlwifi-cc-a0-50.ucode
  • iwlwifi-cc-a0-59.ucode
  • iwlwifi-cc-a0-66.ucode
  • iwlwifi-cc-a0-72.ucode
  • iwlwifi-cc-a0-73.ucode
  • iwlwifi-cc-a0-74.ucode
  • iwlwifi-cc-a0-77.ucode

Using my trial-and-error approach of rebooting and looking at the output of dmesg | grep iwlwifi to find the first version the kernel attempted (but failed) to load, I found that the correct version was iwl-cc-a0-72.ucode, and passed via the kernel’s firmware loader.

After trying various options (such as switching from wpa_supplicant to iwd, and using an older firmware blob), I finally found the fix for the latency and ping spikes: power saving. By issuing iw wlan0 set power_save off, and then starting a new ping test, I could immediately see that the problem was fixed:

$ ping -c 20 192.168.1.120
PING 192.168.1.120 (192.168.1.120) 56(84) bytes of data.
64 bytes from 192.168.1.120: icmp_seq=1 ttl=64 time=2.90 ms
64 bytes from 192.168.1.120: icmp_seq=2 ttl=64 time=1.68 ms
64 bytes from 192.168.1.120: icmp_seq=3 ttl=64 time=2.43 ms
64 bytes from 192.168.1.120: icmp_seq=4 ttl=64 time=2.68 ms
64 bytes from 192.168.1.120: icmp_seq=5 ttl=64 time=3.08 ms
64 bytes from 192.168.1.120: icmp_seq=6 ttl=64 time=2.80 ms
64 bytes from 192.168.1.120: icmp_seq=7 ttl=64 time=3.25 ms
64 bytes from 192.168.1.120: icmp_seq=8 ttl=64 time=3.17 ms
64 bytes from 192.168.1.120: icmp_seq=9 ttl=64 time=2.83 ms
64 bytes from 192.168.1.120: icmp_seq=10 ttl=64 time=3.01 ms
64 bytes from 192.168.1.120: icmp_seq=11 ttl=64 time=2.77 ms
64 bytes from 192.168.1.120: icmp_seq=12 ttl=64 time=2.80 ms
64 bytes from 192.168.1.120: icmp_seq=13 ttl=64 time=3.37 ms
64 bytes from 192.168.1.120: icmp_seq=14 ttl=64 time=2.52 ms
64 bytes from 192.168.1.120: icmp_seq=15 ttl=64 time=2.71 ms
64 bytes from 192.168.1.120: icmp_seq=16 ttl=64 time=2.83 ms
64 bytes from 192.168.1.120: icmp_seq=17 ttl=64 time=3.25 ms
64 bytes from 192.168.1.120: icmp_seq=18 ttl=64 time=2.78 ms
64 bytes from 192.168.1.120: icmp_seq=19 ttl=64 time=2.48 ms
64 bytes from 192.168.1.120: icmp_seq=20 ttl=64 time=3.37 ms

--- 192.168.1.120 ping statistics ---
20 packets transmitted, 20 received, 0% packet loss, time 19036ms
rtt min/avg/max/mdev = 1.679/2.834/3.371/0.379 ms

Now that I had found the solution to the problem, the next task was to make the changes persistent across reboots. Of course, I could throw that iw command command into an rc.local script or something like that, but that seemed hackish to me. Instead, I decided to change my approach for loading the iwlwifi driver and firmware. Rather than having both the driver and the firmware built-in to the kernel, I chose to load them as kernel modules. Doing so allowed me to pass configuration options to the modules when they load. I made a configuration file at /etc/modprobe.d/iwlwifi.conf with the following contents:

$ cat /etc/modprobe.d/iwlwifi.conf 

## Has the same effect has running `iw wlan0 set power_save off`
## Both options sets are needed as iwlmvm will override iwlwifi :(
options iwlwifi power_save=0
## iwlmvm 1=always on, 2=balanced, 3=low-power
options iwlmvm power_scheme=1

As I mentioned in the comments there, BOTH options need to be set: one option passed to the iwlwifi module and the other option passed to the iwlmvm module. Also note the available parameters for the iwlmvm power_scheme:

  • 1 = always on
  • 2 = balanced
  • 3 = low-power

I have validated that these settings work across reboots, and that I no longer see the latency or ping spikes when connecting to this mini-PC over the Intel Wi-Fi 6 AX200. Some of these instructions may be specific to Gentoo and/or the OpenRC init system that I choose to use, but they should be readily adaptable to other distributions and init systems.

Cheers,
Nathan Zachary