About Social Code
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLucas Fryzek <lucas.fryzek@fryzekconcepts.com>2024-02-14 08:26:25 -0500
committerLucas Fryzek <lucas.fryzek@fryzekconcepts.com>2024-02-14 08:26:25 -0500
commit1ad743e44bbf7288ef2aa03558c3676b7341f73f (patch)
treee2d064999c3e56483e8b4e972f503c45951b2d33
parentf102b0d4929084204c4228369c33d89ec8603c54 (diff)
Add vulkanised 2024 post
-rw-r--r--html/assets/vulkanised_2024/food_web.jpgbin0 -> 308713 bytes
-rw-r--r--html/assets/vulkanised_2024/opensource_vulkan_web.jpgbin0 -> 401021 bytes
-rw-r--r--html/assets/vulkanised_2024/vulkan_video_web.jpgbin0 -> 358181 bytes
-rw-r--r--html/assets/vulkanised_2024/vulkanized_logo_web.jpgbin0 -> 273587 bytes
-rw-r--r--html/feed.xml114
-rw-r--r--html/graphics_feed.xml114
-rw-r--r--html/index.html8
-rw-r--r--html/notes/vulkanised_2024.html159
-rw-r--r--notes/vulkanised_2024.md46
9 files changed, 437 insertions, 4 deletions
diff --git a/html/assets/vulkanised_2024/food_web.jpg b/html/assets/vulkanised_2024/food_web.jpg
new file mode 100644
index 0000000..d9f3bf8
--- /dev/null
+++ b/html/assets/vulkanised_2024/food_web.jpg
Binary files differ
diff --git a/html/assets/vulkanised_2024/opensource_vulkan_web.jpg b/html/assets/vulkanised_2024/opensource_vulkan_web.jpg
new file mode 100644
index 0000000..74e9e7a
--- /dev/null
+++ b/html/assets/vulkanised_2024/opensource_vulkan_web.jpg
Binary files differ
diff --git a/html/assets/vulkanised_2024/vulkan_video_web.jpg b/html/assets/vulkanised_2024/vulkan_video_web.jpg
new file mode 100644
index 0000000..fbf8ae8
--- /dev/null
+++ b/html/assets/vulkanised_2024/vulkan_video_web.jpg
Binary files differ
diff --git a/html/assets/vulkanised_2024/vulkanized_logo_web.jpg b/html/assets/vulkanised_2024/vulkanized_logo_web.jpg
new file mode 100644
index 0000000..97b1047
--- /dev/null
+++ b/html/assets/vulkanised_2024/vulkanized_logo_web.jpg
Binary files differ
diff --git a/html/feed.xml b/html/feed.xml
index 451dc01..dbcd6f0 100644
--- a/html/feed.xml
+++ b/html/feed.xml
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Fryzek Concepts</title><atom:link href="https://fryzekconcepts.com/feed.xml" rel="self" type="application/rss+xml"/><link>https://fryzekconcepts.com</link><description>Lucas is a developer working on cool things</description><lastBuildDate>Wed, 14 Feb 2024 13:05:33 -0000</lastBuildDate><item><title>Generating Video</title><link>https://fryzekconcepts.com/notes/generating-video.html</link><description>&lt;p&gt;One thing I’m very interested in is computer graphics. This could be
+<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Fryzek Concepts</title><atom:link href="https://fryzekconcepts.com/feed.xml" rel="self" type="application/rss+xml"/><link>https://fryzekconcepts.com</link><description>Lucas is a developer working on cool things</description><lastBuildDate>Wed, 14 Feb 2024 13:24:37 -0000</lastBuildDate><item><title>Generating Video</title><link>https://fryzekconcepts.com/notes/generating-video.html</link><description>&lt;p&gt;One thing I’m very interested in is computer graphics. This could be
complex 3D graphics or simple 2D graphics. The idea of getting a
computer to display visual data fascinates me. One fundamental part of
showing visual data is interfacing with a computer monitor. This can be
@@ -1902,4 +1902,114 @@ application when moving from a “3D homogeneous space” to a “2D
homogeneous space”.&lt;/p&gt;
&lt;p&gt;Hopefully this explanation helps if you are every working on
converting 3D transformation code to 2D.&lt;/p&gt;
-</description><pubDate>Mon, 25 Sep 2023 04:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/converting_from_3d_to_2d.html</guid></item></channel></rss> \ No newline at end of file
+</description><pubDate>Mon, 25 Sep 2023 04:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/converting_from_3d_to_2d.html</guid></item><item><title>A Dive into Vulkanised 2024</title><link>https://fryzekconcepts.com/notes/vulkanised_2024.html</link><description>&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/vulkanized_logo_web.jpg"
+alt="Vulkanized sign at google’s office" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Vulkanized sign at google’s
+office&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Last week I had an exciting opportunity to attend the Vulkanised 2024
+conference. For those of you not familar with the event, it is &lt;a
+href="https://vulkan.org/events/vulkanised-2024"&gt;“The Premier Vulkan
+Developer Conference”&lt;/a&gt; hosted by the Vulkan working group from
+Khronos. With the excitement out of the way, I decided to write about
+some of the interesting information that came out of the conference.&lt;/p&gt;
+&lt;h2 id="a-few-presentations"&gt;A Few Presentations&lt;/h2&gt;
+&lt;p&gt;My colleagues Iago, Stéphane, and Hyunjun each had the opportunity to
+present on some of their work into the wider Vulkan ecosystem.&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/vulkan_video_web.jpg"
+alt="Stéphane and Hyujun presenting" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Stéphane and Hyujun
+presenting&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Stéphane &amp;amp; Hyunjun presented “Implementing a Vulkan Video Encoder
+From Mesa to Streamer”. They jointly talked about the work they
+performed to implement the Vulkan video extensions in Intel’s ANV Mesa
+driver as well as in GStreamer. This was an interesting presentation
+because you got to see how the new Vulkan video extensions affected both
+driver developers implementing the extensions and application developers
+making use of the extensions for real time video decoding and encoding.
+&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-stephane-cerveau-ko-igalia.pdf"&gt;Their
+presentation is available on vulkan.org&lt;/a&gt;.&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/opensource_vulkan_web.jpg"
+alt="Iago presenting" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Iago presenting&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Later my colleague Iago presented jointly with Faith Ekstrand (a
+well-known Linux graphic stack contributor from Collabora) on “8 Years
+of Open Drivers, including the State of Vulkan in Mesa”. They both
+talked about the current state of Vulkan in the open source driver
+ecosystem, and some of the benefits open source drivers have been able
+to take advantage of, like the common Vulkan runtime code and a shared
+compiler stack. You can check out &lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf"&gt;their
+presentation for all the details&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Besides Igalia’s presentations, there were several more which I found
+interesting, with topics such as Vulkan developer tools, experiences of
+using Vulkan in real work applications, and even how to teach Vulkan to
+new developers. Here are some highlights for some of them.&lt;/p&gt;
+&lt;h3 id="using-vulkan-synchronization-validation-effectively"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-john-zulauf-lunarg.pdf"&gt;Using
+Vulkan Synchronization Validation Effectively&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;John Zulauf had a presentation of the Vulkan synchronization
+validation layers that he has been working on. If you are not familiar
+with these, then you should really check them out. They work by tracking
+how resources are used inside Vulkan and providing error messages with
+some hints if you use a resource in a way where it is not synchronized
+properly. It can’t catch every error, but it’s a great tool in the
+toolbelt of Vulkan developers to make their lives easier when it comes
+to debugging synchronization issues. As John said in the presentation,
+synchronization in Vulkan is hard, and nearly every application he
+tested the layers on reveled a synchronization issue, no matter how
+simple it was. He can proudly say he is a vkQuake contributor now
+because of these layers.&lt;/p&gt;
+&lt;h3 id="years-of-teaching-vulkan-with-example-for-video-extensions"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-helmut-hlavacs.pdf"&gt;6
+Years of Teaching Vulkan with Example for Video Extensions&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;This was an interesting presentation from a professor at the
+university of Vienna about his experience teaching graphics as well as
+game development to students who may have little real programming
+experience. He covered the techniques he uses to make learning easier as
+well as resources that he uses. This would be a great presentation to
+check out if you’re trying to teach Vulkan to others.&lt;/p&gt;
+&lt;h3 id="vulkan-synchronization-made-easy"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-grigory-dzhavadyan.pdf"&gt;Vulkan
+Synchronization Made Easy&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;Another presentation focused on Vulkan sync, but instead of debugging
+it, Grigory showed how his graphics library abstracts sync away from the
+user without implementing a render graph. He presented an interesting
+technique that is similar to how the sync validation layers work when it
+comes ensuring that resources are always synchronized before use. If
+you’re building your own engine in Vulkan, this is definitely something
+worth checking out.&lt;/p&gt;
+&lt;h3 id="vulkan-video-encode-api-a-deep-dive"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-tony-zlatinski-nvidia.pdf"&gt;Vulkan
+Video Encode API: A Deep Dive&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;Tony at Nvidia did a deep dive into the new Vulkan Video extensions,
+explaining a bit about how video codecs work, and also including a
+roadmap for future codec support in the video extensions. Especially
+interesting for us was that he made a nice call-out to Igalia and our
+work on Vulkan Video CTS and open source driver support on slide (6)
+:)&lt;/p&gt;
+&lt;h2 id="thoughts-on-vulkanised"&gt;Thoughts on Vulkanised&lt;/h2&gt;
+&lt;p&gt;Vulkanised is an interesting conference that gives you the
+intersection of people working on Vulkan drivers, game developers using
+Vulkan for their graphics backend, visual FX tool developers using
+Vulkan-based tools in their pipeline, industrial application developers
+using Vulkan for some embedded commercial systems, and general hobbyists
+who are just interested in Vulkan. As an example of some of these
+interesting audience members, I got to talk with a member of the Blender
+foundation about his work on the Vulkan backend to Blender.&lt;/p&gt;
+&lt;p&gt;Lastly the event was held at Google’s offices in Sunnyvale. Which I’m
+always happy to travel to, not just for the better weather (coming from
+Canada), but also for the amazing restaurants and food that’s in the Bay
+Area!&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/food_web.jpg"
+alt="Great bay area food" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Great bay area food&lt;/figcaption&gt;
+&lt;/figure&gt;
+</description><pubDate>Wed, 14 Feb 2024 05:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/vulkanised_2024.html</guid></item></channel></rss> \ No newline at end of file
diff --git a/html/graphics_feed.xml b/html/graphics_feed.xml
index 95ccca7..f5d650c 100644
--- a/html/graphics_feed.xml
+++ b/html/graphics_feed.xml
@@ -1,5 +1,5 @@
<?xml version='1.0' encoding='UTF-8'?>
-<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Fryzek Concepts</title><atom:link href="https://fryzekconcepts.com/feed.xml" rel="self" type="application/rss+xml"/><link>https://fryzekconcepts.com</link><description>Lucas is a developer working on cool things</description><lastBuildDate>Wed, 14 Feb 2024 13:05:34 -0000</lastBuildDate><item><title>2022 Graphics Team Contributions at Igalia</title><link>https://fryzekconcepts.com/notes/2022_igalia_graphics_team.html</link><description>&lt;p&gt;This year I started a new job working with &lt;a
+<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Fryzek Concepts</title><atom:link href="https://fryzekconcepts.com/feed.xml" rel="self" type="application/rss+xml"/><link>https://fryzekconcepts.com</link><description>Lucas is a developer working on cool things</description><lastBuildDate>Wed, 14 Feb 2024 13:24:39 -0000</lastBuildDate><item><title>2022 Graphics Team Contributions at Igalia</title><link>https://fryzekconcepts.com/notes/2022_igalia_graphics_team.html</link><description>&lt;p&gt;This year I started a new job working with &lt;a
href="https://www.igalia.com/technology/graphics"&gt;Igalia’s Graphics
Team&lt;/a&gt;. For those of you who don’t know &lt;a
href="https://www.igalia.com/"&gt;Igalia&lt;/a&gt; they are a &lt;a
@@ -664,4 +664,114 @@ application when moving from a “3D homogeneous space” to a “2D
homogeneous space”.&lt;/p&gt;
&lt;p&gt;Hopefully this explanation helps if you are every working on
converting 3D transformation code to 2D.&lt;/p&gt;
-</description><pubDate>Mon, 25 Sep 2023 04:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/converting_from_3d_to_2d.html</guid></item></channel></rss> \ No newline at end of file
+</description><pubDate>Mon, 25 Sep 2023 04:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/converting_from_3d_to_2d.html</guid></item><item><title>A Dive into Vulkanised 2024</title><link>https://fryzekconcepts.com/notes/vulkanised_2024.html</link><description>&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/vulkanized_logo_web.jpg"
+alt="Vulkanized sign at google’s office" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Vulkanized sign at google’s
+office&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Last week I had an exciting opportunity to attend the Vulkanised 2024
+conference. For those of you not familar with the event, it is &lt;a
+href="https://vulkan.org/events/vulkanised-2024"&gt;“The Premier Vulkan
+Developer Conference”&lt;/a&gt; hosted by the Vulkan working group from
+Khronos. With the excitement out of the way, I decided to write about
+some of the interesting information that came out of the conference.&lt;/p&gt;
+&lt;h2 id="a-few-presentations"&gt;A Few Presentations&lt;/h2&gt;
+&lt;p&gt;My colleagues Iago, Stéphane, and Hyunjun each had the opportunity to
+present on some of their work into the wider Vulkan ecosystem.&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/vulkan_video_web.jpg"
+alt="Stéphane and Hyujun presenting" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Stéphane and Hyujun
+presenting&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Stéphane &amp;amp; Hyunjun presented “Implementing a Vulkan Video Encoder
+From Mesa to Streamer”. They jointly talked about the work they
+performed to implement the Vulkan video extensions in Intel’s ANV Mesa
+driver as well as in GStreamer. This was an interesting presentation
+because you got to see how the new Vulkan video extensions affected both
+driver developers implementing the extensions and application developers
+making use of the extensions for real time video decoding and encoding.
+&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-stephane-cerveau-ko-igalia.pdf"&gt;Their
+presentation is available on vulkan.org&lt;/a&gt;.&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/opensource_vulkan_web.jpg"
+alt="Iago presenting" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Iago presenting&lt;/figcaption&gt;
+&lt;/figure&gt;
+&lt;p&gt;Later my colleague Iago presented jointly with Faith Ekstrand (a
+well-known Linux graphic stack contributor from Collabora) on “8 Years
+of Open Drivers, including the State of Vulkan in Mesa”. They both
+talked about the current state of Vulkan in the open source driver
+ecosystem, and some of the benefits open source drivers have been able
+to take advantage of, like the common Vulkan runtime code and a shared
+compiler stack. You can check out &lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf"&gt;their
+presentation for all the details&lt;/a&gt;.&lt;/p&gt;
+&lt;p&gt;Besides Igalia’s presentations, there were several more which I found
+interesting, with topics such as Vulkan developer tools, experiences of
+using Vulkan in real work applications, and even how to teach Vulkan to
+new developers. Here are some highlights for some of them.&lt;/p&gt;
+&lt;h3 id="using-vulkan-synchronization-validation-effectively"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-john-zulauf-lunarg.pdf"&gt;Using
+Vulkan Synchronization Validation Effectively&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;John Zulauf had a presentation of the Vulkan synchronization
+validation layers that he has been working on. If you are not familiar
+with these, then you should really check them out. They work by tracking
+how resources are used inside Vulkan and providing error messages with
+some hints if you use a resource in a way where it is not synchronized
+properly. It can’t catch every error, but it’s a great tool in the
+toolbelt of Vulkan developers to make their lives easier when it comes
+to debugging synchronization issues. As John said in the presentation,
+synchronization in Vulkan is hard, and nearly every application he
+tested the layers on reveled a synchronization issue, no matter how
+simple it was. He can proudly say he is a vkQuake contributor now
+because of these layers.&lt;/p&gt;
+&lt;h3 id="years-of-teaching-vulkan-with-example-for-video-extensions"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-helmut-hlavacs.pdf"&gt;6
+Years of Teaching Vulkan with Example for Video Extensions&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;This was an interesting presentation from a professor at the
+university of Vienna about his experience teaching graphics as well as
+game development to students who may have little real programming
+experience. He covered the techniques he uses to make learning easier as
+well as resources that he uses. This would be a great presentation to
+check out if you’re trying to teach Vulkan to others.&lt;/p&gt;
+&lt;h3 id="vulkan-synchronization-made-easy"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-grigory-dzhavadyan.pdf"&gt;Vulkan
+Synchronization Made Easy&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;Another presentation focused on Vulkan sync, but instead of debugging
+it, Grigory showed how his graphics library abstracts sync away from the
+user without implementing a render graph. He presented an interesting
+technique that is similar to how the sync validation layers work when it
+comes ensuring that resources are always synchronized before use. If
+you’re building your own engine in Vulkan, this is definitely something
+worth checking out.&lt;/p&gt;
+&lt;h3 id="vulkan-video-encode-api-a-deep-dive"&gt;&lt;a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-tony-zlatinski-nvidia.pdf"&gt;Vulkan
+Video Encode API: A Deep Dive&lt;/a&gt;&lt;/h3&gt;
+&lt;p&gt;Tony at Nvidia did a deep dive into the new Vulkan Video extensions,
+explaining a bit about how video codecs work, and also including a
+roadmap for future codec support in the video extensions. Especially
+interesting for us was that he made a nice call-out to Igalia and our
+work on Vulkan Video CTS and open source driver support on slide (6)
+:)&lt;/p&gt;
+&lt;h2 id="thoughts-on-vulkanised"&gt;Thoughts on Vulkanised&lt;/h2&gt;
+&lt;p&gt;Vulkanised is an interesting conference that gives you the
+intersection of people working on Vulkan drivers, game developers using
+Vulkan for their graphics backend, visual FX tool developers using
+Vulkan-based tools in their pipeline, industrial application developers
+using Vulkan for some embedded commercial systems, and general hobbyists
+who are just interested in Vulkan. As an example of some of these
+interesting audience members, I got to talk with a member of the Blender
+foundation about his work on the Vulkan backend to Blender.&lt;/p&gt;
+&lt;p&gt;Lastly the event was held at Google’s offices in Sunnyvale. Which I’m
+always happy to travel to, not just for the better weather (coming from
+Canada), but also for the amazing restaurants and food that’s in the Bay
+Area!&lt;/p&gt;
+&lt;figure&gt;
+&lt;img src="/assets/vulkanised_2024/food_web.jpg"
+alt="Great bay area food" /&gt;
+&lt;figcaption aria-hidden="true"&gt;Great bay area food&lt;/figcaption&gt;
+&lt;/figure&gt;
+</description><pubDate>Wed, 14 Feb 2024 05:00:00 -0000</pubDate><guid>https://fryzekconcepts.com/notes/vulkanised_2024.html</guid></item></channel></rss> \ No newline at end of file
diff --git a/html/index.html b/html/index.html
index 780e3a9..10bd30e 100644
--- a/html/index.html
+++ b/html/index.html
@@ -45,6 +45,14 @@
</a>
</h2>
<div class="notes-container">
+ <a href="/notes/vulkanised_2024.html" class="note-link">
+ <div class="note-box">
+ <img src="/assets/vulkanised_2024/vulkanized_logo_web.jpg">
+ <h2>A Dive into Vulkanised 2024</h2>
+ <p>Vulkanized sign at google’s officeVulkanized sign at
+ google’s officeLast week I had an exciting ...</p>
+ </div>
+ </a>
<a href="/notes/converting_from_3d_to_2d.html" class="note-link">
<div class="note-box">
<img src="/assets/3d_to_2d.png">
diff --git a/html/notes/vulkanised_2024.html b/html/notes/vulkanised_2024.html
new file mode 100644
index 0000000..06de3dd
--- /dev/null
+++ b/html/notes/vulkanised_2024.html
@@ -0,0 +1,159 @@
+<!doctype html>
+
+<html class="html-note-page" lang="en">
+<head>
+ <meta charset="utf-8">
+ <meta name="viewport" content="width=device-width, initial-scale=1">
+
+ <title>A Dive into Vulkanised 2024</title>
+ <meta name="dcterms.date" content="2024-02-14" />
+
+ <link rel="stylesheet" href="/assets/style.css">
+ <link rel="icon" type="image/x-icon" href="/assets/favicon.svg">
+ <link rel="alternate" type="application/atom+xml" title="Fryzek Concepts" href="/feed.xml">
+</head>
+
+<body>
+ <div class="header-bar">
+ <a href="/index.html">
+ <img src="/assets/favicon.svg" alt="frycon logo">
+ </a>
+ <div class="header-links">
+ <a href="/now.html" class="header-link">Now</a>
+ <a href="/about.html" class="header-link">About</a>
+ <a rel="me" href="https://mastodon.social/@hazematman">Social</a>
+ </div>
+ </div>
+ <main>
+<div class="page-title-header-container">
+ <h1 class="page-title-header">A Dive into Vulkanised 2024</h1>
+ <div class="page-info-container">
+ <div class="plant-status">
+ <img src="/assets/evergreen.svg">
+ <div class="plant-status-text">
+ <p>evergreen</p>
+ </div>
+ </div>
+ <div class="page-info-date-container">
+ <p class="page-info-date">Published: 2024-02-14</p>
+ <p class="page-info-date">Last Edited: 2024-02-14</p>
+ </div>
+ </div>
+ </div>
+<div class="note-divider"></div>
+<div class="main-container">
+ <div class="note-body">
+<figure>
+<img src="/assets/vulkanised_2024/vulkanized_logo_web.jpg"
+alt="Vulkanized sign at google’s office" />
+<figcaption aria-hidden="true">Vulkanized sign at google’s
+office</figcaption>
+</figure>
+<p>Last week I had an exciting opportunity to attend the Vulkanised 2024
+conference. For those of you not familar with the event, it is <a
+href="https://vulkan.org/events/vulkanised-2024">“The Premier Vulkan
+Developer Conference”</a> hosted by the Vulkan working group from
+Khronos. With the excitement out of the way, I decided to write about
+some of the interesting information that came out of the conference.</p>
+<h2 id="a-few-presentations">A Few Presentations</h2>
+<p>My colleagues Iago, Stéphane, and Hyunjun each had the opportunity to
+present on some of their work into the wider Vulkan ecosystem.</p>
+<figure>
+<img src="/assets/vulkanised_2024/vulkan_video_web.jpg"
+alt="Stéphane and Hyujun presenting" />
+<figcaption aria-hidden="true">Stéphane and Hyujun
+presenting</figcaption>
+</figure>
+<p>Stéphane &amp; Hyunjun presented “Implementing a Vulkan Video Encoder
+From Mesa to Streamer”. They jointly talked about the work they
+performed to implement the Vulkan video extensions in Intel’s ANV Mesa
+driver as well as in GStreamer. This was an interesting presentation
+because you got to see how the new Vulkan video extensions affected both
+driver developers implementing the extensions and application developers
+making use of the extensions for real time video decoding and encoding.
+<a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-stephane-cerveau-ko-igalia.pdf">Their
+presentation is available on vulkan.org</a>.</p>
+<figure>
+<img src="/assets/vulkanised_2024/opensource_vulkan_web.jpg"
+alt="Iago presenting" />
+<figcaption aria-hidden="true">Iago presenting</figcaption>
+</figure>
+<p>Later my colleague Iago presented jointly with Faith Ekstrand (a
+well-known Linux graphic stack contributor from Collabora) on “8 Years
+of Open Drivers, including the State of Vulkan in Mesa”. They both
+talked about the current state of Vulkan in the open source driver
+ecosystem, and some of the benefits open source drivers have been able
+to take advantage of, like the common Vulkan runtime code and a shared
+compiler stack. You can check out <a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf">their
+presentation for all the details</a>.</p>
+<p>Besides Igalia’s presentations, there were several more which I found
+interesting, with topics such as Vulkan developer tools, experiences of
+using Vulkan in real work applications, and even how to teach Vulkan to
+new developers. Here are some highlights for some of them.</p>
+<h3 id="using-vulkan-synchronization-validation-effectively"><a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-john-zulauf-lunarg.pdf">Using
+Vulkan Synchronization Validation Effectively</a></h3>
+<p>John Zulauf had a presentation of the Vulkan synchronization
+validation layers that he has been working on. If you are not familiar
+with these, then you should really check them out. They work by tracking
+how resources are used inside Vulkan and providing error messages with
+some hints if you use a resource in a way where it is not synchronized
+properly. It can’t catch every error, but it’s a great tool in the
+toolbelt of Vulkan developers to make their lives easier when it comes
+to debugging synchronization issues. As John said in the presentation,
+synchronization in Vulkan is hard, and nearly every application he
+tested the layers on reveled a synchronization issue, no matter how
+simple it was. He can proudly say he is a vkQuake contributor now
+because of these layers.</p>
+<h3 id="years-of-teaching-vulkan-with-example-for-video-extensions"><a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-helmut-hlavacs.pdf">6
+Years of Teaching Vulkan with Example for Video Extensions</a></h3>
+<p>This was an interesting presentation from a professor at the
+university of Vienna about his experience teaching graphics as well as
+game development to students who may have little real programming
+experience. He covered the techniques he uses to make learning easier as
+well as resources that he uses. This would be a great presentation to
+check out if you’re trying to teach Vulkan to others.</p>
+<h3 id="vulkan-synchronization-made-easy"><a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-grigory-dzhavadyan.pdf">Vulkan
+Synchronization Made Easy</a></h3>
+<p>Another presentation focused on Vulkan sync, but instead of debugging
+it, Grigory showed how his graphics library abstracts sync away from the
+user without implementing a render graph. He presented an interesting
+technique that is similar to how the sync validation layers work when it
+comes ensuring that resources are always synchronized before use. If
+you’re building your own engine in Vulkan, this is definitely something
+worth checking out.</p>
+<h3 id="vulkan-video-encode-api-a-deep-dive"><a
+href="https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-tony-zlatinski-nvidia.pdf">Vulkan
+Video Encode API: A Deep Dive</a></h3>
+<p>Tony at Nvidia did a deep dive into the new Vulkan Video extensions,
+explaining a bit about how video codecs work, and also including a
+roadmap for future codec support in the video extensions. Especially
+interesting for us was that he made a nice call-out to Igalia and our
+work on Vulkan Video CTS and open source driver support on slide (6)
+:)</p>
+<h2 id="thoughts-on-vulkanised">Thoughts on Vulkanised</h2>
+<p>Vulkanised is an interesting conference that gives you the
+intersection of people working on Vulkan drivers, game developers using
+Vulkan for their graphics backend, visual FX tool developers using
+Vulkan-based tools in their pipeline, industrial application developers
+using Vulkan for some embedded commercial systems, and general hobbyists
+who are just interested in Vulkan. As an example of some of these
+interesting audience members, I got to talk with a member of the Blender
+foundation about his work on the Vulkan backend to Blender.</p>
+<p>Lastly the event was held at Google’s offices in Sunnyvale. Which I’m
+always happy to travel to, not just for the better weather (coming from
+Canada), but also for the amazing restaurants and food that’s in the Bay
+Area!</p>
+<figure>
+<img src="/assets/vulkanised_2024/food_web.jpg"
+alt="Great bay area food" />
+<figcaption aria-hidden="true">Great bay area food</figcaption>
+</figure>
+ </div>
+</div> </main>
+</body>
+</html>
diff --git a/notes/vulkanised_2024.md b/notes/vulkanised_2024.md
new file mode 100644
index 0000000..1eeaffb
--- /dev/null
+++ b/notes/vulkanised_2024.md
@@ -0,0 +1,46 @@
+---
+title: "A Dive into Vulkanised 2024"
+date: "2024-02-14"
+last_edit: "2024-02-14"
+status: 3
+cover_image: "/assets/vulkanised_2024/vulkanized_logo_web.jpg"
+categories: igalia graphics
+---
+
+![Vulkanized sign at google's office](/assets/vulkanised_2024/vulkanized_logo_web.jpg)
+
+Last week I had an exciting opportunity to attend the Vulkanised 2024 conference. For those of you not familar with the event, it is ["The Premier Vulkan Developer Conference"](https://vulkan.org/events/vulkanised-2024) hosted by the Vulkan working group from Khronos. With the excitement out of the way, I decided to write about some of the interesting information that came out of the conference.
+
+## A Few Presentations
+
+My colleagues Iago, Stéphane, and Hyunjun each had the opportunity to present on some of their work into the wider Vulkan ecosystem.
+
+![Stéphane and Hyujun presenting](/assets/vulkanised_2024/vulkan_video_web.jpg)
+
+Stéphane & Hyunjun presented "Implementing a Vulkan Video Encoder From Mesa to Streamer". They jointly talked about the work they performed to implement the Vulkan video extensions in Intel's ANV Mesa driver as well as in GStreamer. This was an interesting presentation because you got to see how the new Vulkan video extensions affected both driver developers implementing the extensions and application developers making use of the extensions for real time video decoding and encoding. [Their presentation is available on vulkan.org](https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-stephane-cerveau-ko-igalia.pdf).
+
+![Iago presenting](/assets/vulkanised_2024/opensource_vulkan_web.jpg)
+
+Later my colleague Iago presented jointly with Faith Ekstrand (a well-known Linux graphic stack contributor from Collabora) on "8 Years of Open Drivers, including the State of Vulkan in Mesa". They both talked about the current state of Vulkan in the open source driver ecosystem, and some of the benefits open source drivers have been able to take advantage of, like the common Vulkan runtime code and a shared compiler stack. You can check out [their presentation for all the details](https://vulkan.org/user/pages/09.events/vulkanised-2024/Vulkanised-2024-faith-ekstrand-collabora-Iago-toral-igalia.pdf).
+
+Besides Igalia's presentations, there were several more which I found interesting, with topics such as Vulkan developer tools, experiences of using Vulkan in real work applications, and even how to teach Vulkan to new developers. Here are some highlights for some of them.
+
+### [Using Vulkan Synchronization Validation Effectively](https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-john-zulauf-lunarg.pdf)
+John Zulauf had a presentation of the Vulkan synchronization validation layers that he has been working on. If you are not familiar with these, then you should really check them out. They work by tracking how resources are used inside Vulkan and providing error messages with some hints if you use a resource in a way where it is not synchronized properly. It can't catch every error, but it's a great tool in the toolbelt of Vulkan developers to make their lives easier when it comes to debugging synchronization issues. As John said in the presentation, synchronization in Vulkan is hard, and nearly every application he tested the layers on reveled a synchronization issue, no matter how simple it was. He can proudly say he is a vkQuake contributor now because of these layers.
+
+### [6 Years of Teaching Vulkan with Example for Video Extensions](https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-helmut-hlavacs.pdf)
+This was an interesting presentation from a professor at the university of Vienna about his experience teaching graphics as well as game development to students who may have little real programming experience. He covered the techniques he uses to make learning easier as well as resources that he uses. This would be a great presentation to check out if you're trying to teach Vulkan to others.
+
+### [Vulkan Synchronization Made Easy](https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-grigory-dzhavadyan.pdf)
+Another presentation focused on Vulkan sync, but instead of debugging it, Grigory showed how his graphics library abstracts sync away from the user without implementing a render graph. He presented an interesting technique that is similar to how the sync validation layers work when it comes ensuring that resources are always synchronized before use. If you're building your own engine in Vulkan, this is definitely something worth checking out.
+
+### [Vulkan Video Encode API: A Deep Dive](https://vulkan.org/user/pages/09.events/vulkanised-2024/vulkanised-2024-tony-zlatinski-nvidia.pdf)
+Tony at Nvidia did a deep dive into the new Vulkan Video extensions, explaining a bit about how video codecs work, and also including a roadmap for future codec support in the video extensions. Especially interesting for us was that he made a nice call-out to Igalia and our work on Vulkan Video CTS and open source driver support on slide (6) :)
+
+## Thoughts on Vulkanised
+
+Vulkanised is an interesting conference that gives you the intersection of people working on Vulkan drivers, game developers using Vulkan for their graphics backend, visual FX tool developers using Vulkan-based tools in their pipeline, industrial application developers using Vulkan for some embedded commercial systems, and general hobbyists who are just interested in Vulkan. As an example of some of these interesting audience members, I got to talk with a member of the Blender foundation about his work on the Vulkan backend to Blender.
+
+Lastly the event was held at Google's offices in Sunnyvale. Which I'm always happy to travel to, not just for the better weather (coming from Canada), but also for the amazing restaurants and food that's in the Bay Area!
+
+![Great bay area food](/assets/vulkanised_2024/food_web.jpg)