<?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: segmented patch cord neatness and ambiguity</title>
		<atom:link href="http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/feed" rel="self" type="application/rss+xml" />
		<link>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/feed</link>
		<description></description>
		<pubDate>Wed, 19 Jun 2013 11:12:25 +0000</pubDate>
		<generator>http://bbpress.org/?v=2.2.4</generator>
		<language></language>

		
														
					
				<item>
					<guid>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-25087</guid>
					<title><![CDATA[segmented patch cord neatness and ambiguity]]></title>
					<link>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-25087</link>
					<pubDate>Mon, 27 Mar 2006 15:58:53 +0000</pubDate>
					<dc:creator>Dan Nigrin</dc:creator>

					<description>
						<![CDATA[
						<p>Lot&#8217;s of discussion recently on ways of working in Max, efficiently <br />
coding, etc..  So, a question and feature request for segmented patch <br />
cords:</p>
<p>1)  Question &#8211; I notice in many Max help files and in other people&#8217;s <br />
patches that when segmented patch cords are used, people manage to <br />
line up the segments from multiple connections very neatly, so they <br />
all line up, like this example from page 85 of the Max Tutorials <br />
documentation:</p>
<p>Is there any easy way to get the patch cords to &#8220;line up&#8221;?  Ideally, <br />
I&#8217;d like to be able to &#8220;Align&#8221; the patch cords like one can do now <br />
with objects (command Y).  I find myself often trying, and missing by <br />
a pixel or two, and things look ugly (I know, I&#8217;m type A), like this:</p>
<p>
2)  Feature request &#8211; notice in the first example above that there is <br />
ambiguity introduced; one can&#8217;t tell where the number boxes in the <br />
top row are connected to by just looking.  This is the main reason <br />
that I often *don&#8217;t* use segmented patch cords, even though I&#8217;d like <br />
to from a neatness perspective.  I wonder if there isn&#8217;t some smart <br />
UI change that could be implemented to more clearly illustrate what <br />
is connected to what in these types of cases?</p>
<p>Thanks,<br />
Dan<br />
&#8211; <br />
Dan Nigrin<br />
Defective Records<br />
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X<br />
<a href="http://www.defectiverecords.com" rel="nofollow">http://www.defectiverecords.com</a></p>
<p><a href="http://www.jackosx.com" rel="nofollow">http://www.jackosx.com</a></p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73435</guid>
					<title><![CDATA[Re: segmented patch cord neatness and ambiguity]]></title>
					<link>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73435</link>
					<pubDate>Mon, 27 Mar 2006 16:23:28 +0000</pubDate>
					<dc:creator>Peter McCulloch</dc:creator>

					<description>
						<![CDATA[
						<p></p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73436</guid>
					<title><![CDATA[Re: segmented patch cord neatness and ambiguity]]></title>
					<link>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73436</link>
					<pubDate>Mon, 27 Mar 2006 16:48:19 +0000</pubDate>
					<dc:creator>Dan Nigrin</dc:creator>

					<description>
						<![CDATA[
						<p>At 11:23 AM -0500 3/27/06, Peter McCulloch wrote:<br />
>>Is there any easy way to get the patch cords to &#8220;line up&#8221;? <br />
>>Ideally, I&#8217;d like to be able to &#8220;Align&#8221; the patch cords like one <br />
>>can do now with objects (command Y).  I find myself often trying, <br />
>>and missing by a pixel or two, and things look ugly (I know, I&#8217;m <br />
>>type A), like this:<br />
>><br />
>If you align the objects first (in your example, highlight the <br />
>number boxes, then align them), then select the patch cords (using <br />
>option-drag) and do align (to make the segmented patch cords) then <br />
>they should segment at the same y position.  If you segment, then <br />
>align, you&#8217;ll probably have to do the hand-tweaking.</p>
<p>Holy smokes &#8212; I never knew that Align worked like that with patch <br />
cords &#8211; thanks!  Now I feel silly&#8230;</p>
<p>>>2)  Feature request &#8211; notice in the first example above that there <br />
>>is ambiguity introduced; one can&#8217;t tell where the number boxes in <br />
>>the top row are connected to by just looking.  This is the main <br />
>>reason that I often *don&#8217;t* use segmented patch cords, even though <br />
>>I&#8217;d like to from a neatness perspective.  I wonder if there isn&#8217;t <br />
>>some smart UI change that could be implemented to more clearly <br />
>>illustrate what is connected to what in these types of cases?<br />
>><br />
><br />
>Generally speaking, colored patch cords take care of most of these <br />
>issues.  Also, if you wanted to keep the two different paths from <br />
>having the same segment position, move one group up a couple of <br />
>spaces, then segment, then move back down.  The Duplicate trick is <br />
>also useful for making separated patch cords:  Duplicate, move it <br />
>into the x position desired (using the arrow keys), then move it up <br />
>several spaces (4 works well) and keep duplicating.  Segment, then <br />
>align, and you&#8217;ll have patch cords with a small space in between <br />
>each cord.</p>
<p>Thanks Peter, I&#8217;ll give it a shot.</p>
<p>Dan<br />
&#8211; <br />
Dan Nigrin<br />
Defective Records<br />
202 Hack / PC-1600 User / VSTi Host / OMS Convert / Jack OS X<br />
<a href="http://www.defectiverecords.com" rel="nofollow">http://www.defectiverecords.com</a></p>
<p><a href="http://www.jackosx.com" rel="nofollow">http://www.jackosx.com</a></p>
						]]>
					</description>

					
					
				</item>

			
				<item>
					<guid>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73437</guid>
					<title><![CDATA[Re: segmented patch cord neatness and ambiguity]]></title>
					<link>http://cycling74.com/forums/topic/segmented-patch-cord-neatness-and-ambiguity/#post-73437</link>
					<pubDate>Mon, 27 Mar 2006 17:06:07 +0000</pubDate>
					<dc:creator>Peter McCulloch</dc:creator>

					<description>
						<![CDATA[
						<p>Also, be sure to check out &#8220;Extras&#8221; > &#8220;Tips&#8221; for a slew of other very <br />
useful Max shortcuts.</p>
<p>Peter McCulloch</p>
						]]>
					</description>

					
					
				</item>

					
		
	</channel>
	</rss>

