<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>H264 on Rusty Eddy</title><link>https://rustyeddy.com/tags/h264/</link><description>Recent content in H264 on Rusty Eddy</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 31 May 2026 11:09:14 -0700</lastBuildDate><atom:link href="https://rustyeddy.com/tags/h264/index.xml" rel="self" type="application/rss+xml"/><item><title>Streaming Video is Complicated</title><link>https://rustyeddy.com/notes/streaming-video/</link><pubDate>Mon, 29 Apr 2019 00:00:00 +0000</pubDate><guid>https://rustyeddy.com/notes/streaming-video/</guid><description>&lt;p&gt;I need to stream live video from a moving vehical with a connected
camera and a possibly connected wifi.&lt;/p&gt;
&lt;h2 id="live-high-resolution-video"&gt;Live High Resolution Video&lt;/h2&gt;
&lt;p&gt;Video will stream from the vehicle to be picked up by &lt;em&gt;video
consumers&lt;/em&gt; and processed as required. Examples of &lt;em&gt;consumers&lt;/em&gt; are
Live Video Display on our (Webapp), OpenCV for vision algoritms.&lt;/p&gt;
&lt;h2 id="high-demand-for-low-resolution"&gt;High Demand For Low Resolution&lt;/h2&gt;
&lt;p&gt;It turns out that computer vision alogrithms typically run quite a bit
faster on lower resolution images, the additional information from
these &lt;em&gt;hi-res&lt;/em&gt; images can slow down the type of algorithms we are
interested in by many factors.&lt;/p&gt;</description></item></channel></rss>