<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Video Production on [BETA] NCoT Tech</title>
    <link>https://beta.ncot.uk/tags/video-production/</link>
    <description>Recent content in Video Production on [BETA] NCoT Tech</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Fri, 23 Oct 2026 13:56:58 +0100</lastBuildDate>
    <atom:link href="https://beta.ncot.uk/tags/video-production/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Davinci Resolve Proxy Files</title>
      <link>https://beta.ncot.uk/blog-posts/davinci-resolve-proxy-files/</link>
      <pubDate>Thu, 06 Mar 2025 21:30:39 +0000</pubDate>
      <guid>https://beta.ncot.uk/blog-posts/davinci-resolve-proxy-files/</guid>
      <description>It turns out making proxy files is quite important when editing video across your LAN. Don’t edit video across your LAN, it ends in tears and frustration.

#Graphics #Networking #VideoProduction</description>
    </item>
    <item>
      <title>Davinci Resolve Collaboration</title>
      <link>https://beta.ncot.uk/blog-posts/davinci-resolve-collaboration/</link>
      <pubDate>Mon, 03 Mar 2025 21:59:02 +0000</pubDate>
      <guid>https://beta.ncot.uk/blog-posts/davinci-resolve-collaboration/</guid>
      <description>I’ve worked out how to work on the same Davinci Resolve project from two different computers, at the same time.

#RaspberryPi #VideoProduction #Electronics</description>
    </item>
    <item>
      <title>Figuring out a better video production workflow</title>
      <link>https://beta.ncot.uk/blog-posts/figuring-out-a-better-video-production-workflow/</link>
      <pubDate>Mon, 22 Apr 2024 21:42:23 +0000</pubDate>
      <guid>https://beta.ncot.uk/blog-posts/figuring-out-a-better-video-production-workflow/</guid>
      <description>This is where I figure out a simpler way to make my videos, and it seems really obvious when I explain it. Which generally means it’s a good way to work.

#VideoProduction</description>
    </item>
    <item>
      <title>2022 Review</title>
      <link>https://beta.ncot.uk/blog-posts/2022-review/</link>
      <pubDate>Sun, 01 Jan 2023 11:16:11 +0000</pubDate>
      <guid>https://beta.ncot.uk/blog-posts/2022-review/</guid>
      <description>Let’s briefly look back at last year and see what things were like, then look forward to the coming year and what I want to achieve. I did this last year too, and I’ve just been reading that.

#SpectrumNext #RetroComputing #VideoProduction</description>
    </item>
    <item>
      <title>2021 Review</title>
      <link>https://beta.ncot.uk/blog-posts/2021-review/</link>
      <pubDate>Sun, 02 Jan 2022 20:33:58 +0000</pubDate>
      <guid>https://beta.ncot.uk/blog-posts/2021-review/</guid>
      <description>How was 2021 for you? I mean, compared to 2020 it was a big improvement, but that’s a pretty low bar to aim for. Let’s focus more on the projects that I completed and what I learned from them.

#SpectrumNext #RetroComputing #VideoProduction</description>
    </item>
  </channel>
</rss>
