<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 06/14/2013 01:03 AM, michael noble
wrote:<br>
</div>
<blockquote
cite="mid:CABf1g_y4oAcdh6CyGEq-thb8Vho9=z=xnoaa6yyhzSYLYHng2A@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">On Fri, Jun 14, 2013 at 1:45 AM,
Jonathan Wilkes <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:jancsika@yahoo.com" target="_blank">jancsika@yahoo.com</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>They improve readability in situations where a
straightforward, structured<br>
patch ends up with a line crossing over and obscuring
text.</div>
</blockquote>
</div>
<br>
I'll go out on a limb as someone who rarely posts here. I've
been working on a single complex patch, with many abstractions
and sub-patches, for a long time now and one of the greatest
pleasures of patching in PD for me is taking the time to avoid
visual clutter within the constraints of working without
right-angles or bezier curves. </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra">There are basically three types of
lines that look any good in PD to me - the horizontal cord,
the vertical cord, and one particular diagonal in which the
pixels just happen to align in a regular pattern. I would go
so far as to say that working with only those three and
sufficient white space one can avoid obscuring text in all
situations. It takes longer because you have to think about
where you place objects as well as what objects you are using,
but I personally find I make better patching decisions based
solely on the fact that I am forced to think longer about the
patching process. </div>
<div class="gmail_extra"><br>
</div>
<div class="gmail_extra" style="">So long story short, I don't
agree that right-angles or beziers are a requirement for
clear, structured and readable patches. They may be helpful
time-saving tools, but using them would come at a cost for me.</div>
</div>
<br>
</blockquote>
While I agree with you that in most cases segmented patch cords are
unnecessary, if you never have a need for them I presume you must be
then using sends and receives for any situation where there is a
feedback loop like:<br>
<br>
[object] x [object]<br>
<br>
Segmented patch cords have their advantages, but like any tool, they
can be also misused to produce even less readable patches. Time
permitting and provided there is enough interest I may look into
adding segmented patch cords into pd-l2ork.<br>
<br>
Cheers!<br>
<pre class="moz-signature" cols="72">--
Ivica Ico Bukvic, D.M.A
Composition, Music Technology
Director, DISIS Interactive Sound & Intermedia Studio
Director, L2Ork Linux Laptop Orchestra
Head, ICAT IMPACT Studio
Virginia Tech
Department of Music
Blacksburg, VA 24061-0240
(540) 231-6139
(540) 231-5034 (fax)
disis.music.vt.edu
l2ork.music.vt.edu
ico.bukvic.net</pre>
</body>
</html>