<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Telemetry Compatibility - Action Video Lab Forum				            </title>
            <link>https://actionvideolab.com/community/telemetry-compatibility/</link>
            <description>Action Video Lab Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Mon, 17 Aug 2026 17:11:19 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>Action-camera telemetry compatibility chart: what should we test?</title>
                        <link>https://actionvideolab.com/community/telemetry-compatibility/action-camera-telemetry-compatibility-chart-what-should-we-test/</link>
                        <pubDate>Sat, 15 Aug 2026 01:12:10 +0000</pubDate>
                        <description><![CDATA[A simple &#039;supported / not supported&#039; table seems too vague because the answer can change depending on camera model, recording mode, remote, firmware and editor.

What columns would make a co...]]></description>
                        <content:encoded><![CDATA[A simple 'supported / not supported' table seems too vague because the answer can change depending on camera model, recording mode, remote, firmware and editor.

What columns would make a compatibility chart actually useful?]]></content:encoded>
						                            <category domain="https://actionvideolab.com/community/telemetry-compatibility/">Telemetry Compatibility</category>                        <dc:creator>Telemetry Demo</dc:creator>
                        <guid isPermaLink="true">https://actionvideolab.com/community/telemetry-compatibility/action-camera-telemetry-compatibility-chart-what-should-we-test/</guid>
                    </item>
				                    <item>
                        <title>Telemetry compatibility should include editing operations, not just import</title>
                        <link>https://actionvideolab.com/community/telemetry-compatibility/telemetry-compatibility-should-include-editing-operations-not-just-import/</link>
                        <pubDate>Thu, 13 Aug 2026 15:54:58 +0000</pubDate>
                        <description><![CDATA[A chart can say an editor &#039;supports GPS&#039;, but that does not tell me what happens after trimming, speed changes, proxies or joining clips.

Should compatibility testing include those operatio...]]></description>
                        <content:encoded><![CDATA[A chart can say an editor 'supports GPS', but that does not tell me what happens after trimming, speed changes, proxies or joining clips.

Should compatibility testing include those operations as separate rows?]]></content:encoded>
						                            <category domain="https://actionvideolab.com/community/telemetry-compatibility/">Telemetry Compatibility</category>                        <dc:creator>Telemetry Demo</dc:creator>
                        <guid isPermaLink="true">https://actionvideolab.com/community/telemetry-compatibility/telemetry-compatibility-should-include-editing-operations-not-just-import/</guid>
                    </item>
							        </channel>
        </rss>
		