<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Projects on RCMZ</title>
    <link>https://rcmz.gitlab.io/projects/</link>
    <description>Recent content in Projects on RCMZ</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rcmz.gitlab.io/projects/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GNOME Display Refresh Rate Indicator</title>
      <link>https://rcmz.gitlab.io/projects/display-refresh-rate-indicator/</link>
      <pubDate>Tue, 29 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://rcmz.gitlab.io/projects/display-refresh-rate-indicator/</guid>
      <description>&lt;p&gt;I love HFR (high frame rate) video, or rather, I find 24–30 fps to just be unpleasant. I know this is a controversial opinion: many film purists find that HFR is a terrible idea, and that 24 fps is the best frame rate that ever was. The argument against HFR is often that &amp;ldquo;it looks like a soap opera / telenovela&amp;rdquo;, and indeed, soap operas were transmitted in splendid 50/60 fps analogue video. I believe that the disdain for HFR comes from the fact that soap operas are not considered high art, and therefore copying any aspect of their presentation is distasteful, even if it is technically better. To my eye, 24–30 fps video just looks choppy, whereas HFR lets me lose myself in the content better. Frame rate interpolation is even more hated than native HFR. Yes, frame rate interpolation is really hard to do perfectly, and it does tend to add many artefacts in complex scenes. But you know what? It is still better than 24 fps choppiness, IMO.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Chroma Launcher</title>
      <link>https://rcmz.gitlab.io/projects/chroma-launcher/</link>
      <pubDate>Wed, 12 Aug 2026 00:00:00 +0000</pubDate>
      <guid>https://rcmz.gitlab.io/projects/chroma-launcher/</guid>
      <description>&lt;table&gt;&#xA;  &lt;thead&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;th&gt;&lt;/th&gt;&#xA;          &lt;th&gt;&lt;/th&gt;&#xA;          &lt;th&gt;&lt;/th&gt;&#xA;          &lt;th&gt;&lt;/th&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/thead&gt;&#xA;  &lt;tbody&gt;&#xA;      &lt;tr&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;https://rcmz.gitlab.io/images/chroma-launcher-1.png&#34; alt=&#34;screenshot&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;https://rcmz.gitlab.io/images/chroma-launcher-2.png&#34; alt=&#34;screenshot&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;https://rcmz.gitlab.io/images/chroma-launcher-3.png&#34; alt=&#34;screenshot&#34;&gt;&lt;/td&gt;&#xA;          &lt;td&gt;&lt;img src=&#34;https://rcmz.gitlab.io/images/chroma-launcher-4.png&#34; alt=&#34;screenshot&#34;&gt;&lt;/td&gt;&#xA;      &lt;/tr&gt;&#xA;  &lt;/tbody&gt;&#xA;&lt;/table&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s face it: most people&amp;rsquo;s phone homescreens are a mess. App icons are haphazardly placed across random pages, sometimes even duplicated, and you have to go through every page and visually scan every icon to find the one you were looking for, because nothing is organized. Default homescreen apps give you a plethora of options to organize your digital life: you can have multiple pages, each with a grid of icons that you have full control over, including making it sparse, and you can also pool icons into folders. For the digitally inclined and organization lovers, this amount of control is amazing; it allows you to really configure your homescreen layout for your personal preferences and use case. But for their moms (and really most people), this is overwhelming and incomprehensible. To combat that, most homescreens have an &amp;ldquo;all apps&amp;rdquo; view that shows all your apps in a single grid sorted alphabetically. This is better, but it adds yet another layer of complexity to homescreens, and I think we can do better.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Who Made This Track ?</title>
      <link>https://rcmz.gitlab.io/projects/whomadethistrack/</link>
      <pubDate>Wed, 07 Jan 2026 00:00:00 +0000</pubDate>
      <guid>https://rcmz.gitlab.io/projects/whomadethistrack/</guid>
      <description>&lt;p&gt;&lt;img src=&#34;https://rcmz.gitlab.io/images/whomadethistrack-screenshot.png&#34; alt=&#34;Screenshot placeholder&#34;&gt;&lt;/p&gt;&#xA;&lt;p&gt;Who Made This Track ? is a visual map of the producers and writers behind pop tracks. The experience is built around discovery: search for a song, choose Producers or Writers, and watch the network grow as you expand leaf nodes. The graph updates live, showing how tracks and collaborators connect, while the sidebar keeps the controls lightweight and easy to reach.&lt;/p&gt;&#xA;&lt;p&gt;The app is designed for quick exploration. You can adjust depth to widen or narrow the neighborhood around a song, toggle light and dark themes, and optionally enable “Color graph” to give each node its own color with blended edges between connections. Your current view (query, mode, theme, depth, and color setting) stays encoded in the URL so it’s easy to share specific maps.&lt;/p&gt;</description>
    </item>
    <item>
      <title>ShaderV</title>
      <link>https://rcmz.gitlab.io/projects/shaderv/</link>
      <pubDate>Sun, 09 Mar 2025 00:00:00 +0000</pubDate>
      <guid>https://rcmz.gitlab.io/projects/shaderv/</guid>
      <description>&lt;p&gt;The 21st century is a difficult time for computer graphic research. OpenGL is still well supported but it does not have access to all the modern programming features that researcher might want to toy with (ray tracing, mesh shaders, &amp;hellip;). Vulkan is the way forward but it is incredibly verbose, we are talking 500+ lines for a barebone &amp;ldquo;HelloTriangle&amp;rdquo; ! Don&amp;rsquo;t get me wrong, Vulkan verbosity forces you to actually understand what you are doing (something that was not required with OpenGL), but it&amp;rsquo;s a real pain when you want to hack something quickly. Such was the conundrum we had in our research team : lots of researchers wanted access to the latest GPU features, but almost no one wanted to go through the hardship of learning Vulkan. And even the brave one that did agreed that was not a great research environment.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Game: The Video Game</title>
      <link>https://rcmz.gitlab.io/projects/the-game-the-video-game/</link>
      <pubDate>Thu, 13 Feb 2020 00:00:00 +0000</pubDate>
      <guid>https://rcmz.gitlab.io/projects/the-game-the-video-game/</guid>
      <description>&lt;p&gt;Sorry, you just lost &amp;ldquo;The Game&amp;rdquo;. If you were not playing it already, &amp;ldquo;The Game&amp;rdquo; is a mental game where the goal is to not think of &amp;ldquo;The Game&amp;rdquo;. The way it is usually played is by saying out loud, &amp;ldquo;Dammit, I just lost&amp;rdquo;, making everyone else in the room also lose.&lt;/p&gt;&#xA;&lt;p&gt;I can&amp;rsquo;t really decide if &amp;ldquo;The Game&amp;rdquo; is an advanced reasoning-level genius idea, or pure stupidity, but I made a video game version of it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
