<?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: Preventing Slide~ from descending until it has ascended to a value</title>
		<atom:link href="http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/feed</link>
		<description></description>
		<pubDate>Wed, 19 Jun 2013 15:37:31 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-64325</guid>
					<title><![CDATA[Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-64325</link>
					<pubDate>Tue, 11 Sep 2012 14:26:19 +0000</pubDate>
					<dc:creator>DanBennett</dc:creator>

					<description>
						<![CDATA[
						<p>I&#8217;ve been trying to work out how to engineer something like this, but haven&#8217;t got very far.</p>
<p>I&#8217;d like to create an envelope (simple attack, sustain, release) that can also go up to audio spectrum rates, and where I can control the curve of the line.<br />
To go into the audio spectrum without glitchiness it&#8217;ll need to be signal input. Also I want to ensure that the attack segment completes before the release is allowed to kick in.</p>
<p>The way I thought of doing it is using slide~ to turn an incoming &#8220;gate&#8221; signal (either 1 or 0) into a ramp/curve. This is fine so far as it goes, but if the incoming gate signal goes back to 0 before slide reaches 1, then slide begins its descent regardless. </p>
<p>Any ideas on something I could put between the gate signal and the slide input such that once the gate input leaves 0, it is not allowed to fall back down to 0 again until the slide~ output has reached 1?<br />
If the slide output reaches 1 and the gate input is still at 1 it should then hold at 1 until the gate input falls<br />
ie<br />
I&#8217;ve tried a few things with the bitwise operators but I can&#8217;t figure out anything that works.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231953</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231953</link>
					<pubDate>Tue, 11 Sep 2012 17:25:43 +0000</pubDate>
					<dc:creator>Roman Thilenius</dc:creator>

					<description>
						<![CDATA[
						<p>change second argument to 9999999 until you want it to get back to 250?</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231954</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231954</link>
					<pubDate>Wed, 12 Sep 2012 09:11:10 +0000</pubDate>
					<dc:creator>DanBennett</dc:creator>

					<description>
						<![CDATA[
						<p>Not a bad idea as a workaround to try.</p>
<p>I guess, on thinking about it and refining the question, what I think I&#8217;d need to get this (and other things I&#8217;m interested in) working is a signal rate flip-flop switch.<br />
Ie When it receives a 1 (or passes a certain threshold) it goes to (and holds at) 1 until it receives a 0 (or goes below a certain threshold) it outputs (and holds at) 0. </p>
<p>Easy to do at message rate, but I can&#8217;t see how to do it in signal objects.<br />
I&#8217;d be surprised if an object didn&#8217;t exist somewhere &#8211; am I just not looking hard enough.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231955</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231955</link>
					<pubDate>Wed, 12 Sep 2012 09:25:10 +0000</pubDate>
					<dc:creator>Patrick Delges</dc:creator>

					<description>
						<![CDATA[
						<p>Sound like a schmitt trigger. <strong>thresh~</strong> can do that.</p>
<p>p</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231956</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231956</link>
					<pubDate>Wed, 12 Sep 2012 10:50:04 +0000</pubDate>
					<dc:creator>DanBennett</dc:creator>

					<description>
						<![CDATA[
						<p>Ah thanks again Looks like thresh~ would do that. </p>
<p>But I just realised I was on wrong track. I&#8217;m being a bit muddled about this.<br />
Each mistake gets me closer though.</p>
<p>So<br />
I&#8217;ve realised that using a change~ on the output of the envelope I can pick out when it&#8217;s rising (1), falling(-1) or steady (0)<br />
if I put that output through < ~ 1 I get 0 for rising, and 1 for falling or steady</p>
</p><p>So I could combine that output with the gate input and some binary logic to get the desired input to the env.<br />
I just can&#8217;t work out the binary logic operation to get the result I want!</p>
<p>Truth table looks like this:</p>
<p>Change < 1____Gate In__ desired result<br />
0 _____________ 0 ________1<br />
0 _____________ 1 ________1<br />
1 _____________ 0 ________1<br />
1 _____________ 1 ________0</p>
<p>Any ideas what object or combination of objects will get me from the first two columns to the third?</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231957</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231957</link>
					<pubDate>Wed, 12 Sep 2012 10:59:22 +0000</pubDate>
					<dc:creator>DanBennett</dc:creator>

					<description>
						<![CDATA[
						<p>I swear I just needed to write the problem down!</p>
<p>in case anyone else wants to do the same thing:<br />
I think if I invert the gate using ==0, I can then use AND on inverted gate &#038; [change~ into < ~ 1] and invert the final result using another ==0 and get the result I want.</p>
</p>						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231958</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231958</link>
					<pubDate>Wed, 12 Sep 2012 17:42:37 +0000</pubDate>
					<dc:creator>Peter McCulloch</dc:creator>

					<description>
						<![CDATA[
						<p>*~ and ==~ 0 will also produce that truth table.  (*~ works well as a logical and)</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231959</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231959</link>
					<pubDate>Wed, 12 Sep 2012 17:46:24 +0000</pubDate>
					<dc:creator>Peter McCulloch</dc:creator>

					<description>
						<![CDATA[
						<p>Also, you may want to see this thread: <a href="http://cycling74.com/forums/topic.php?id=41966" rel="nofollow">http://cycling74.com/forums/topic.php?id=41966</a> regarding the timing of slide~.  You&#8217;ll find that it&#8217;s WAY off for large values.</p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231960</guid>
					<title><![CDATA[Re: Preventing Slide~ from descending until it has ascended to a value]]></title>
					<link>http://cycling74.com/forums/topic/preventing-slide-from-descending-until-it-has-ascended-to-a-value/#post-231960</link>
					<pubDate>Thu, 13 Sep 2012 12:47:41 +0000</pubDate>
					<dc:creator>DanBennett</dc:creator>

					<description>
						<![CDATA[
						<p>Thanks &#8211; I&#8217;ve always wondered whether there were there any performance benefits in using &#038;&#038;~ over *~ for this function (or vice versa)?<br />
I imagine quite small if so anyway &#8211; simble bitwise operations are meat and potatoes for computers.</p>
<p>Good to know about the timing peculiarities with slide~ also.<br />
I&#8217;ve since realised that deltaclip~ will work better than slide~ since I don&#8217;t want retriggers during the release period to take as long to travel, say, 0.5 to 1 as an attack from 0 would. So in practice, I actually want to control rate rather than period of slew. I&#8217;ll sort curve control by putting a pow~ on the output.</p>
<p>This is all scribbled on the back of an envelope (no pun intended) at the moment but when I actually get a chance to sit in front of a pc with MAX on it, I&#8217;ll build and post for anyone who&#8217;s interested.</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

