<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>
	<title><![CDATA[Design the Media's forums]]></title>
	<description><![CDATA[Design the Media's forum RSS flow]]></description>
	<link>http://designthemedia.com</link>
	<pubDate>Sun, 12 Feb 2012 16:21:33 +0000</pubDate>
	<ttl>240</ttl>
	<image>
		<title><![CDATA[Design the Media's forums]]></title>
		<url>http://designthemedia.com/favicon.ico</url>
		<link>http://designthemedia.com</link>
	</image>
	<item>
		<title><![CDATA[[SOLVED&#62; upgrade] LFO 2.01 does not store custom wave]]></title>
		<link>http://designthemedia.com/topic/94-solved-upgrade-lfo-201-does-not-store-custom-wave/</link>
		<description>Using last ableton version 8.2.8 and Max 5, the LFO doesn`t store its custom wave. Using Matrix too, so I will not update Max 6.</description>
		<pubDate>Sun, 12 Feb 2012 16:21:33 +0000</pubDate>
		<guid>http://designthemedia.com/topic/94-solved-upgrade-lfo-201-does-not-store-custom-wave/</guid>
	</item>
	<item>
		<title>smooth paramter</title>
		<link>http://designthemedia.com/topic/92-smooth-paramter/</link>
		<description><![CDATA[Hi Julien,<br />
<br />
loving the LFO2! Great that you can have high sync values like 64 bars and I really like the way the  "offset" parameter is implementet. You can still "play and twist" the knob while its modulated!<br />
<br />
But I noticed a issue in combination with filters or volume. That said, it's of course not our LFO in particular, but a problem a lot LFOs have.<br />
<br />
When I modulate the volume or a filter with the LFO I get stepping or zipper noise. It's obvious why, but maybe it would be an idea to add a high resolution mode or a smooth parameter to interpolate the "stair steps" from the modulation signal away? Too bad that we cant have a LFO at sample rate with low CPU consumption. :-)<br />
<br />
Best regards]]></description>
		<pubDate>Thu, 09 Feb 2012 15:45:18 +0000</pubDate>
		<guid>http://designthemedia.com/topic/92-smooth-paramter/</guid>
	</item>
	<item>
		<title>LFO 2.0 Problem</title>
		<link>http://designthemedia.com/topic/86-lfo-20-problem/</link>
		<description><![CDATA[Ok, is there something I am doing wrong?  I have ableton live 8.2.7 with max for live, and when I use this LFO 2.0, it does not work.<br />
<br />
The select function doesn't work, and whe I press track, device, or parameters, it turns blank.  Is anyone having the same problem?]]></description>
		<pubDate>Wed, 08 Feb 2012 20:57:25 +0000</pubDate>
		<guid>http://designthemedia.com/topic/86-lfo-20-problem/</guid>
	</item>
	<item>
		<title><![CDATA[[LFO] feature requests list]]></title>
		<link>http://designthemedia.com/topic/14-lfo-feature-requests-list/</link>
		<description><![CDATA[- modulation of devices in return & master tracks<br />
- parameters storage]]></description>
		<pubDate>Mon, 06 Feb 2012 12:59:21 +0000</pubDate>
		<guid>http://designthemedia.com/topic/14-lfo-feature-requests-list/</guid>
	</item>
	<item>
		<title>one more improvement - longer LFO cycles</title>
		<link>http://designthemedia.com/topic/85-one-more-improvement-longer-lfo-cycles/</link>
		<description><![CDATA[Hi Julien<br />
<br />
While you're at it , I think LFO would really benefit from some longer cycles , like 8. 16, 32 or even 64 bars would be nice , just as long as they don't step ladder as they move ....just a thought , I'm having a lot of fun with this tool!!]]></description>
		<pubDate>Sun, 05 Feb 2012 11:12:42 +0000</pubDate>
		<guid>http://designthemedia.com/topic/85-one-more-improvement-longer-lfo-cycles/</guid>
	</item>
	<item>
		<title>An improvement to LFO would be a shrinkable width</title>
		<link>http://designthemedia.com/topic/84-an-improvement-to-lfo-would-be-a-shrinkable-width/</link>
		<description><![CDATA[Hey Julien, is there anyway to add a "twisty" to LFO so that it gets skinny when you don't need to see its details like in a Live rack?  I frequently load up 4 or more instances on a channel and it takes a LOT of horizontal real estate.]]></description>
		<pubDate>Wed, 01 Feb 2012 20:04:43 +0000</pubDate>
		<guid>http://designthemedia.com/topic/84-an-improvement-to-lfo-would-be-a-shrinkable-width/</guid>
	</item>
	<item>
		<title>Auto-mapping with APC40</title>
		<link>http://designthemedia.com/topic/82-auto-mapping-with-apc40/</link>
		<description><![CDATA[I just have bought an APC 40, so i use the 8 banks of 8 knobs available on it<br />
<br />
As many m4l devices, parameters are automatically mapped on APC 40 , but in a non-logical order<br />
<br />
Do you know how to config those parameters in m4l ? (i can use instrument rack of course, but with APC40, in this case, all default mapping with Live integrated devices are gone , because manual mapping has the priority against default mapping)]]></description>
		<pubDate>Wed, 01 Feb 2012 11:35:52 +0000</pubDate>
		<guid>http://designthemedia.com/topic/82-auto-mapping-with-apc40/</guid>
	</item>
	<item>
		<title><![CDATA[[LFO] Additional controls for return and master tracks]]></title>
		<link>http://designthemedia.com/topic/11-lfo-additional-controls-for-return-and-master-tracks/</link>
		<description><![CDATA[Hello,<br />
<br />
In addition to the "tracks" devices parameters available, would it be possible to add the "return_tracks" and "master_track" objects collection ?<br />
<br />
Refering the LOM, I understand objects structure remains the same whether in "tracks" or "return_tracks", same goes for the unique "master_track".<br />
I guess it's the query feeding the track (first) dropdown list, the rest of the logical implementation should remain the same, however could be nice to distinguish easily the different families: tracks, returns and master when opens up the track (first) dropdown list.<br />
<br />
Thanks.]]></description>
		<pubDate>Fri, 27 Jan 2012 20:59:28 +0000</pubDate>
		<guid>http://designthemedia.com/topic/11-lfo-additional-controls-for-return-and-master-tracks/</guid>
	</item>
	<item>
		<title>APC40 : default mapping</title>
		<link>http://designthemedia.com/topic/83-apc40-default-mapping/</link>
		<description><![CDATA[I just have bought an APC 40, so i use the 8 banks of 8 knobs available on it<br />
<br />
As many m4l devices, parameters are automatically mapped on APC 40 , but in a non-logical order<br />
<br />
Do you know how to config those parameters in m4l ? (i can use instrument rack of course, but with APC40, in this case, all default mapping with Live integrated devices are gone , because manual mapping has the priority against default mapping)]]></description>
		<pubDate>Thu, 26 Jan 2012 17:19:29 +0000</pubDate>
		<guid>http://designthemedia.com/topic/83-apc40-default-mapping/</guid>
	</item>
	<item>
		<title>Feature Requests</title>
		<link>http://designthemedia.com/topic/50-feature-requests/</link>
		<description><![CDATA[First request!<br />
 <br />
The ability to copy all the parameters from one channel to another. <br />
 <br />
Obviously the probabilistic features of Uncanny Seq are what sets it apart, but i'm sure there are going to be a few lines in there that might be somewhat static. It would be nice to set some default settings, copy them to a few channels, and then start tweaking the probabilistic features.<br />
 <br />
 <br />
Also, when UnSeq fires up, the default settings are completely different than if you hit the Reset ALL button on each channel.]]></description>
		<pubDate>Sun, 08 Jan 2012 12:30:34 +0000</pubDate>
		<guid>http://designthemedia.com/topic/50-feature-requests/</guid>
	</item>
</channel>
</rss>
