<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Beelink on 412Linux</title>
    <link>https://412Linux.io/categories/beelink/</link>
    <description>Recent content in Beelink on 412Linux</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Thu, 04 Apr 2024 09:31:27 +0100</lastBuildDate>
    <atom:link href="https://412Linux.io/categories/beelink/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>N100 Media Serving Efficiency with Quick Sync</title>
      <link>https://412Linux.io/article/beelinks12pro-quicksync/</link>
      <pubDate>Thu, 04 Apr 2024 09:31:27 +0100</pubDate>
      <guid>https://412Linux.io/article/beelinks12pro-quicksync/</guid>
      <description>In my quest to optimize media serving capabilities, one feature that stood out for testing was Quick Sync, particularly its hardware acceleration potential. I embarked on a comparison between Jellyfin and Emby, evaluating the efficacy of Quick Sync and its impact on system performance.&#xA;Utilizing a sample of media encoded at 2160p via x265, I conducted several tests, the results of which are presented in the accompanying charts. Without Quick Sync enabled, the CPU resources of the system were pushed to their limits.</description>
    </item>
    <item>
      <title>Beelink Mini S12 Performance</title>
      <link>https://412Linux.io/article/beelinks12pro-performance/</link>
      <pubDate>Fri, 15 Mar 2024 09:31:27 +0100</pubDate>
      <guid>https://412Linux.io/article/beelinks12pro-performance/</guid>
      <description>Thus far, my journey with the Beelink N100 mini PC has been fantastic. Intrigued by its performance capabilities, I embarked on a quest to evaluate its CPU prowess in comparison to other available processors at my disposal. To maintain simplicity in my assessment, I opted for the null output functionality within ffmpeg. Selecting a file from Netflix&amp;rsquo;s open content, I harnessed its data for my analysis. Below, you&amp;rsquo;ll find both the link to the file and the command I employed.</description>
    </item>
    <item>
      <title>Beelink Mini S12 pro first look</title>
      <link>https://412Linux.io/article/beelinks12pro-firstlook/</link>
      <pubDate>Fri, 08 Mar 2024 09:31:27 +0100</pubDate>
      <guid>https://412Linux.io/article/beelinks12pro-firstlook/</guid>
      <description>Recently, I took the plunge and acquired the Beelink MINI S12 Pro, primarily driven by my curiosity about the capabilities of the N100. As an avid enthusiast of all things tech, I saw this device not only as a potential infrastructure and testing hub for 412linux but also as a promising candidate for serving as a home media server. Having had positive experiences with Beelink devices in the past, I embarked on this journey with high hopes and eager anticipation.</description>
    </item>
  </channel>
</rss>
