{"id":1239,"date":"2016-02-26T18:07:10","date_gmt":"2016-02-26T18:07:10","guid":{"rendered":"https:\/\/www.qdigitizing.com\/blog\/?p=1239"},"modified":"2016-02-26T18:08:56","modified_gmt":"2016-02-26T18:08:56","slug":"pull-comp","status":"publish","type":"post","link":"https:\/\/www.qdigitizing.com\/blog\/pull-comp\/","title":{"rendered":"Pull Comp"},"content":{"rendered":"<p>Greetings everyone,<\/p>\n<p>Spring has sprung in the Valley of the Sun and things are heating up in Phoenix. \u00a0 I wanted to say a special thank you to all of you that stopped by our booth at the Long Beach ISS Show. \u00a0I counted 15 of you who came by. \u00a0We had a fantastic show and looking forward to the East Coast version in Atlantic City, March 17th through 19th. \u00a0You will find us in booth 524. \u00a0It has been way too long since we were on the East Coast and I can&#8217;t wait to see some of you guys again.<br \/>\n<a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/ISS-Atlantic-City.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-1247\" title=\"ISS Atlantic City\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/ISS-Atlantic-City-300x141.jpg\" alt=\"\" width=\"300\" height=\"141\" srcset=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/ISS-Atlantic-City-300x141.jpg 300w, https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/ISS-Atlantic-City.jpg 653w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<br \/>\nFor this months blog \u00a0I want to discuss a topic we use all of the time at Qdigitizing, Pull Comp. \u00a0While Pull Comp is not a very sexy topic it is critically important in quality embroidery. \u00a0If you aren&#8217;t a programmer or commercial embroiderer it might not be important to understand all of the technical detail related to Pull Comp but it is really good to have a basic understanding of what Pull Comp is and how it impacts your embroidery projects.<\/p>\n<p>Before anything else is said about Push Pull Compensation (commonly referred to as Pull Comp) it should be understood that Pull Comp should never be used as a crutch for poor programming technique or a panacea to correct all design problems.\u00a0 It doesn\u2019t work that way.\u00a0 Furthermore, it should be understood manually programmed Pull Comp should be used proactively to prevent conditions (like poor design registration) from happening and then Auto Pull Comp Tools should be used to edit for minor design flaws or tweaks to improve overall design appearance.<!--more--><\/p>\n<p>With all of that said you might be asking, \u201cWhat is Pull Comp and why is it important?\u201d\u00a0 Pull Comp is the term programmers use to describe techniques used to compensate for the tendencies of fabric to push and pull while being embroidered.\u00a0 Pull Compensation is necessary to offset the tendencies of your fabric to Push Out and\/or Pull In depending on the type of stitches being used, how various design elements interact with each other, the fabric being embroidered and any backing solution used.\u00a0\u00a0 Pull Comp requirements will change if any of these factors (and others) change.<\/p>\n<p>My point is not to overcomplicate the issue but Pull Comp is complicated and understanding why it is important is in a way almost as important as the proper use of Pull Comp.\u00a0 Looking closely at Image 1 you can see two areas where design registration is off.\u00a0 In the area noted black arrows the fill in the design has PUSHED outside the \u201cline\u201d the designer has programmed.\u00a0 In the area circled the stitches have \u201cpulled in.\u201d\u00a0 \u00a0The result is poor design registration and a design rejected by the customer.<\/p>\n<p><a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/pull-comp-1.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-1240\" title=\"pull comp 1\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/pull-comp-1-300x282.png\" alt=\"\" width=\"300\" height=\"282\" srcset=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/pull-comp-1-300x282.png 300w, https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/pull-comp-1.png 385w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>The solution for this problem is pretty easy by using a setting in the software to add width to the blue column that traps the white fill, see Image 2.<\/p>\n<p><strong>Image 2<\/strong><br \/>\n<a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-2.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-1241\" title=\"Pull Comp 2\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-2-300x264.png\" alt=\"\" width=\"300\" height=\"264\" srcset=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-2-300x264.png 300w, https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-2.png 399w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>In this case all that was necessary to correct the registration problem was to add 30% Pull Comp(ensation) to the blue border, see Image 3.\u00a0 This change adds 30% additional width to the column allowing the border to better capture the white fill underneath.\u00a0 When using more sophisticated software it is also possible to tell the software to bias the Pull Comp to one side or the other of center. Other more advanced features are also available for the more seasoned programmer.<\/p>\n<p><strong>Image 3<\/strong><br \/>\n<a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/PUll-Comp-3.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-1242\" title=\"PUll Comp 3\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/PUll-Comp-3.png\" alt=\"\" width=\"230\" height=\"169\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>In Image 4 you can see how the software has added \u201cwidth\u201d to the blue column.\u00a0 The red arrows point to the width the designer originally programmed but as you can see by the black arrows, the software has added column width to either sides of the colum.\u00a0 This extra width is what helps trap the white fill underneath.<\/p>\n<p><strong>Image 4<\/strong><br \/>\n<a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-4.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-1243\" title=\"Pull Comp 4\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-4-297x300.png\" alt=\"\" width=\"297\" height=\"300\" srcset=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-4-297x300.png 297w, https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-4.png 328w\" sizes=\"auto, (max-width: 297px) 100vw, 297px\" \/><\/a><br \/>\n&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>What is really important to understand is this correction may or may not be necessary depending on many factors and it is why (in general) programmers do not use Auto Pull Comp tools until they know there is a problem that needs to be corrected.\u00a0 I understand that might seem to contradict what I wrote earlier in regard to using Pull Comp proactively so let me explain further.<\/p>\n<p>All good programmers understand fabric will shift, compress and expand in the embroidery process.\u00a0 Because of this the programmer will (as a function of their experience level) will manually program Pull Compensation in to their designs.\u00a0 For instance, I have noticed that when a logo is sewing on a shirt it tends to PUSH out on the sides and Pull In at the top and bottom.\u00a0 Because of this when I program a design I will \u201ccheat\u201d in so much as (almost without thought) I will program fills to bias OUT for the left and right edges and bias IN for the top and bottom when a border is meant to capture the fill.<\/p>\n<p>One other area of Pull compensation to consider is a question Programmers often receive, \u201cHow come if I look at the letters you digitized some of the letters are taller or shorter than the letter right next to?\u00a0 How come the letters are not all the same size?\u201d<\/p>\n<p>The answer to this is simple, Pull Compensation. The fix and how much fix to apply is somewhat more complex.\u00a0 Applying the right amount of Pull Comp to get all letters to appear the same size on apparel can be very tricky and is dramatically impacted by the fabric you are embroidering on and the type of backing used.<\/p>\n<p>At actual size (Image 5)<br \/>\n<a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/PUll-Comp-51.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-full wp-image-1245\" title=\"PUll Comp 5\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/PUll-Comp-51.png\" alt=\"\" width=\"141\" height=\"50\" \/><\/a><\/p>\n<p>it might be hard to see the Pull Comp but if you zoom in (Image 6) you can clearly see how the programmer has adjusted for the Push and Lull of the fabric.\u00a0 Look closely and you will see how the Straight line letters H and I are slightly above the blue base line and the round letters C and G are slightly below the blue base line.\u00a0 This is 100% intentional and is meant to counter the effect and FACT that Straight letters tend to PUSH out and round letters tend to PULL in.\u00a0 Hence, Pull Comp.\u00a0 It might not seem like a lot, especially because I have zoomed in so tight here but this adjustment is critical to quality embroidery.<\/p>\n<p><a href=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-6.png\"><img loading=\"lazy\" decoding=\"async\" class=\"alignleft size-medium wp-image-1246\" title=\"Pull Comp 6\" src=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-6-300x140.png\" alt=\"\" width=\"300\" height=\"140\" srcset=\"https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-6-300x140.png 300w, https:\/\/www.qdigitizing.com\/blog\/wp-content\/uploads\/2016\/02\/Pull-Comp-6.png 844w\" sizes=\"auto, (max-width: 300px) 100vw, 300px\" \/><\/a><\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>&nbsp;<\/p>\n<p>Completely understanding Pull Comp is the an area professional programmers spend their careers learning; it is part of the science behind the art of embroidery digitizing.\u00a0 From the non-programmer side of things the most important thing to take away from this conversation is, whenever possible let your programmer know what the design will be embroidered on so they can to the best of their ability manually program the correct amount of pull comp so that if editing is required you or the programmer can use the automated features offered in your software to make quick fixes to adjust for fabric and\/or small programming errors.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Greetings everyone, Spring has sprung in the Valley of the Sun and things are heating up in Phoenix. \u00a0 I<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1239","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/posts\/1239","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/comments?post=1239"}],"version-history":[{"count":4,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/posts\/1239\/revisions"}],"predecessor-version":[{"id":1249,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/posts\/1239\/revisions\/1249"}],"wp:attachment":[{"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/media?parent=1239"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/categories?post=1239"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.qdigitizing.com\/blog\/wp-json\/wp\/v2\/tags?post=1239"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}