<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Community: Message List</title>
    <link>http://line6.com/support/index.jspa?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Mon, 27 Feb 2012 01:18:44 GMT</pubDate>
    <generator>Jive SBS 4.5.7.0 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2012-02-27T01:18:44Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Pod X3 Pro Auto Swell Glitch</title>
      <link>http://line6.com/support/message/359009?tstart=0#359009</link>
      <description>&lt;!-- [DocumentBodyStart:8e74454c-9f21-4ae2-8eab-1ab363f74bcc] --&gt;&lt;div class="jive-rendered-content"&gt;&lt;p&gt;I stumbled across this glitch today and found a couple posts online describing it but no one had posted any solutions. Product of several hours of trial and error here is my solution:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Problem:&lt;/strong&gt; The Auto Swell stops functioning completely&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Cause:&lt;/strong&gt; I have narrowed the cause of this problem down to the 12 additional effects added in the POD X3 Live Flash Memory v2.0 update, specifically the Frequency Shifter&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;&lt;strong&gt;Solution:&lt;/strong&gt; The Auto Swell can be restored by simply reflashing the memory using Line 6 Monkey. Once you select a patch containing the Frequency Shifter, or select that effect in any patch, the Auto Swell will once again become unusable until the memory is reflashed. I have only verified this with the Frequency Shifter but it is possible this glitch may be caused by any of the 2.0 effects. List follows:&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Vocoder&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Dynamic Delay&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Dimension&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Pitch Vibrato&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Voice Box&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;V-Tron&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Octisynth&lt;/strong&gt;&lt;span style="font-weight: normal;"&gt; &lt;/span&gt; &lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Q Filter&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Pattern Tremolo&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Frequency Shifter&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Barberpole Phaser&lt;/strong&gt;&lt;/p&gt;&lt;p&gt;&lt;strong style="font-weight: normal;"&gt;Script Phaser&lt;/strong&gt;&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;Since selecting the Frequency Shifter breaks the Auto Swell (I also noticed other filter effects were effected) you should never save a patch with the Frequency Shifter. If you must use it simply don't save the effect on the patch and flash the memory when you finish playing/recording.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;I have not tried it but I assume rolling back the POD to pre 2.0 flash memory would fix this glitch at the cost of losing the above listed effects and any other fixes included.&lt;/p&gt;&lt;p style="min-height: 8pt; height: 8pt; padding: 0px;"&gt;&amp;#160;&lt;/p&gt;&lt;p&gt;I hope this saves some people aggravation. I wish there was an easier fix, I hope Line 6 addresses this issue in a future update.&lt;/p&gt;&lt;/div&gt;&lt;!-- [DocumentBodyEnd:8e74454c-9f21-4ae2-8eab-1ab363f74bcc] --&gt;</description>
      <pubDate>Mon, 27 Feb 2012 01:18:44 GMT</pubDate>
      <author>support@line6.com</author>
      <guid>http://line6.com/support/message/359009?tstart=0#359009</guid>
      <dc:date>2012-02-27T01:18:44Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:objectType>0</clearspace:objectType>
    </item>
  </channel>
</rss>

