<?xml version="1.0" encoding="UTF-8"?>
	<rss version="2.0"
		xmlns:content="http://purl.org/rss/1.0/modules/content/"
		xmlns:wfw="http://wellformedweb.org/CommentAPI/"
		xmlns:dc="http://purl.org/dc/elements/1.1/"
		xmlns:atom="http://www.w3.org/2005/Atom"

			>

	<channel>
		<title>Cycling 74  &#187;  Topic: Pluggo Broken Things</title>
		<atom:link href="http://cycling74.com/forums/topic/pluggo-broken-things/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/pluggo-broken-things/feed</link>
		<description></description>
		<pubDate>Wed, 19 Jun 2013 18:58:25 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/pluggo-broken-things/#post-44260</guid>
					<title><![CDATA[Pluggo Broken Things]]></title>
					<link>http://cycling74.com/forums/topic/pluggo-broken-things/#post-44260</link>
					<pubDate>Fri, 05 Jun 2009 19:57:23 +0000</pubDate>
					<dc:creator>Leigh Marble</dc:creator>

					<description>
						<![CDATA[
						<p>I am starting this thread to track broken objects and/or issues of platform &#038; format compatibility in Pluggo, post-Cycling &#8217;74 support of Pluggo.</p>
<p>Please, this is not the place for bashing Cycling for their decision to discontinue Pluggo. I would like to keep a line of communication open with other users about what&#8217;s still working, and what&#8217;s starting to break in Pluggo. Although Cycling has discontinued development of Pluggo, it will continue to work for some amount of time&#8230; </p>
<p>When describing issues, please list:<br />
- operating system &#038; version<br />
- host program (Pro Tools, Logic, etc) &#038; version<br />
- plug-in format (VST, RTAS, AU)</p>
<p>Thank you,<br />
Leigh</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/pluggo-broken-things/#post-159099</guid>
					<title><![CDATA[Re: Pluggo Broken Things]]></title>
					<link>http://cycling74.com/forums/topic/pluggo-broken-things/#post-159099</link>
					<pubDate>Fri, 05 Jun 2009 20:15:04 +0000</pubDate>
					<dc:creator>Andrew Pask</dc:creator>

					<description>
						<![CDATA[
						<p>There&#8217;s these for a start</p>
<p><a href="http://www.cycling74.com/twiki/bin/view/FAQs/PluggoIssues">http://www.cycling74.com/twiki/bin/view/FAQs/PluggoIssues</a></p>
<p>-A</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/pluggo-broken-things/#post-159100</guid>
					<title><![CDATA[Re: Pluggo Broken Things]]></title>
					<link>http://cycling74.com/forums/topic/pluggo-broken-things/#post-159100</link>
					<pubDate>Sat, 08 Aug 2009 17:53:52 +0000</pubDate>
					<dc:creator>chaircrusher</dc:creator>

					<description>
						<![CDATA[
						<p>I just installed Ableton Live, Pluggo and Hipno on a brand new Windows XP SP3 machine &#8212; Core2 Quad, 2 GB memory.  When Ableton Live tries to do the initial scan, it hangs up on the first Cycling74 plugin it encounters.</p>
<p>The same is true for Sound Forge.  I haven&#8217;t gotten my response codes back from Cycling74 yet &#8212; I&#8217;ll try reinstalling and authorizing when those come.</p>
<p>On my old studio box, Acid Pro locks up in a slightly different manner when confronted with Cycling74 plugs &#8212; it chugs through the first few before completely grinding to a halt.</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

