shreeswifty

I have been working for a few days on a jitter patch that pairs freefram with a jit.gl.slab, some chromakeying and i have been fooling a little with adding in syphon too. My problem is that try as i may, segmented patch cords or not my patches turn turn spaghetti so quickly. So i am reaching out to this forum with the hopes someone may take a look at my horrid little patch and give me pointers or even remix the patch so it's neater. I am attaching it so please take a gander at it and maybe suggest or implement how i can make it a little nicer without having to redo the whole shebang

Hi
I have been working for a few days on a jitter patch that pairs freefram with a jit.gl.slab, some chromakeying and i have been fooling a little with adding in syphon too. My problem is that try as i may, segmented patch cords or not my patches turn turn spaghetti so quickly. So i am reaching out to  this forum with the hopes someone may take a look at my horrid little patch and give me pointers or even remix the patch so it's neater. I am attaching it so please take a gander at it and maybe suggest or implement how i can make it a little nicer without having to redo the whole shebang
thanks in advance
Pat


neat-patch-help

I can see at a glance that you have used a sub patch [patcher], I would encourage the use of these more frequently, as they can significantly reduce complications with larger patches. You can assign inlets and outlets to each and then patch directly to them for inputting and outputting data. Alternatively, you can use the [send] and [receive] objects (with an identifier) or even shortened to [s] and [r] objects (again with identifier) for "wireless" transmission of data, audio signals or video around your patch.

For greater ease of use, it is sometimes advisable to use presentation mode to display only the controls that you wish to see in the interface. This way you do not have to look at all of the objects, patch chords and processes constantly.

I can see at a glance that you have used a sub patch [patcher], I would encourage the use of these more frequently, as they can significantly reduce complications with larger patches. You can assign inlets and outlets to each and then patch directly to them for inputting and outputting data. Alternatively, you can use the [send] and [receive] objects (with an identifier) or even shortened to [s] and [r] objects (again with identifier) for "wireless" transmission of data, audio signals or video around your patch. 

1st Creative Labs Support Team
support@1stcreativesolutions.co.uk 

select objects you want to make into a sub-patch hit shift+apple+E (also in Edit menu) and you'll have a tidy patch very quickly without having to redo anything.

Neat patch help