Aug 012007
 

A friend in Eng­land got mar­ried, so I decided to knit her a cush­ion. Here­with the pic­tures, and the pat­tern, for those read­ers of my blog inter­ested in my knit­ting posts.

I really must fig­ure out how to take decent pho­tos of my knit­ted art­icles; I nev­er seem to be able to get the col­our just right. This cush­ion, for example, is in a soft lilac; Sirdar Pure Cot­ton Double Knit­ting col­our 30 to be pre­cise. But then I look at online col­our charts and they’re not much (if any) better.

The cush­ion is knit­ted in two pieces, at a slightly firmer ten­sion (since it’s for a cush­ion) than you’d use for a gar­ment. I used the cable cast-on to give a firmer edge as well, though if you’re more com­fort­able with anoth­er cast-on, use that. I used 5 skeins of yarn (double-knit­ting; 185 yds/169 m per 100g skein; 100% cot­ton; recom­men­ded gauge 21 st x 28 r on 4 mm needles) for both sides, with enough for swatch­ing and seam­ing, and with some left over. It’s machine-wash­able, but should be dried flat. It blocked out nicely to a little over 43 cm (17 in) to fit an 46 cm (18 in) cush­ion insert.

Side 1: a stand­ard almost-plaited cable stitch using 4.5 mm needles. You may want to try out cabling without using a cable needle for this one. My gauge over the pat­tern stitch: 36 st x 29 rows to 10.5 x 10.5 cm (4.1 in).

Cast on 146 stitches. 
Row 1: k all st 
Row 2: p all st
Row 3: k1, *6 st right cable (hold st to back so the stitches cross from left to right), repeat from * until 1 st left, k1
Row 4: p all st
Row 5: k all st
Row 6: p all st
Row 7: k4, *6 st left cable (hold st to front so the stitches cross from right to left), repeat from * until 4 st left, k4
Row 8: p all st
Repeat these 8 rows for 132 rows total or until the cush­ion length matches the width; for me that was (unblocked) 42.5 x 42.5 cm (16.7 in), with 16.5 repeats of the pat­tern. Bind off.

The res­ult looks like this: Lilac_Cushion

Side 2: a tra­di­tion­al Aran pat­tern flanked by cables, knit­ted on 3.25 mm needles. My gauge for stock­ing stitch on these needles was 22 st per 10 cm (4 in). “Cable 3 to right” means put 3 stitches on the cable needle, put the needle behind the work, knit the next 3 stitches, knit the 3 from the cable needle. “Cable 3 to left” means put 3 stitches on cable needle, put the cable needle in front of the work, knit the next 3 stitches, knit the stitches from the cable needle.

Cast on 99 stitches.
Row 1: k16, p1, k6, p1, k15, p3, k7, p1, k7, p3, k15, p1, k6, p1, k16
Row 2: p16, k1, p6, k1, p15, k1, p1, k1, p6, k1, p1, k1, p6, k1, p1, k1, p15, k1, p6, k1, p16
Row 3: k16, p1, k6, p1, k15, p3, k5, p1, k3, p1, k5, p3, k15, p1, k6, p1, k16
Row 4: p16, k1, p6, k1, p15, k1, p1, k1, p4, k1, p2, k1, p2, k1, p4, k1, p1, k1, p15, k1, p6, k1, p16
Row 5: k16, p1, k6, p1, k15, p3, k3, p1, k2, p1, k1, p1, k2, p1, k3, p3, k15, p1, k6, p1, k16
Row 6: p16, k1, p6, k1, p15, k1, p1, k1, p2, k1, p2. k1, p3, k1, p2, k1, p2, k1, p1, k1, p15, k1, p6, k1, p16
Row 7: k16, p1, k6, p1, k15, p3, k1, p1, k2, p1, k2, p1, k2, p1, k2, p1, k1, p3, k15, p1, k6, p1, k16
Row 8: p16, k1, p6, k1, p15, k1, p1, k1, p3, k1, p2, k1, p1, k1, p2, k1, p3, k1, p1, k1, p15, k1, p6, k1, p16
Row 9: k16, p1, cable 3 to right, p1, k15, p3, k2, p1, k2, p1, k3, p1, k2, p1, k2, p3, k15, p1, cable 3 to left, p1, k16
Row 10: p16, k1, p6, k1, p15, k1, p1, k1, p4, k1, p2, k1, p2, k1, p4, k1, p1, k1, p15, k1, p6, k1, p16
Row 11: k16, p1, k6, p1, k15, p3, k3, p1, k2, p1, k1, p1, k2, p1, k3, p3, k15, p1, k6, p1, k16
Row 12: p16, k1, p6, k1, p15, k1, p1, k1, p5, k1, p3, k1, p5, k1, p1, k1, p15, k1, p6, k1, p16
Row 13: k16, p1, k6, p1, k15, p3, k4, p1, k2, p1, k2, p1, k4, p3, k15, p1, k6, p1, k16
Row 14: p16, k1, p6, k1, p15, k1, p1, k1, p6, k1, p1, k1, p6, k1, p1, k1, p15, k1, p6, k1, p16
Row 15: k16, p1, k6, p1, k15, p3, k5, p1, k3, p1, k5, p3, k15, p1, k6, p1, k16
Row 16: p16, k1, p6, k1, p15, k1, p1, k1, p7, k1, p7, k1, p1, k1, p15, k1, p6, k1, p16
Row 17: k16, p1, k6, p1, k15, p3, k6, p1, k1, p1, k6, p3, k15, p1, k6, p1, k16
Row 18: p16, k1, p6, k1, p15, k1, p1, k1, p15, k1, p1, k1, p15, k1, p6, k1, p16
Row 19: k16, p1, k6, p1, k15, p3, k7, p1, k7, p3, k15, p1, k6, p1, k16
Row 20: p16, k1, p6, k1, p15, k1, p1, k1, p15, k1, p1, k1, p15, k1, p6, k1, p16 

Con­tin­ue the pat­tern until the cush­ion is square, for me that was 135 rows. Bind off, then block to match the size of the oth­er side. Pin togeth­er right side out, and either crochet around the edges, or stitch them togeth­er. Don’t for­get to put the cush­ion pad in before you close the last side! I used the Armeni­an stitch (a vari­ation on but­ton­hole stitch) from Montse Stan­ley’s Knit­ter­’s Hand­book : A Com­pre­hens­ive Guide to the Prin­ciples and Tech­niques of Handknit­ting (a very good ref­er­ence book, BTW, but prob­ably a bit scary for begin­ning knit­ters); you can also find instruc­tions on the web.

Lilac_Cushion_Reverse

Feel free to use the pat­tern to make items, even for sale, but I do require attri­bu­tion. Please don’t repost the pat­tern on any web­site; link to it instead. Thanks!

  7 Responses to “Knitted Cushion”

  1. You’re not mak­ing the claim that this kind of thing can be copy­righted, I pre­sume? It’s just a “be nice” request?

  2. Of course it’s copy­right­able, as copy­right­able as a com­puter pro­gram, which indeed it is if you are broad­minded about what counts as a computer.

    If you wanted to look at a fin­ished piece and reverse engin­eer the pat­tern, that you can do, but oth­er­wise you are bound by the copy­right license.

  3. Indeed, an algorithm such as this has first pre­ced­ence as a com­puter pro­gram — a set of instruc­tions for one who computes. 

    Lovely cush­ion and great instruc­tions — even I can fol­low them, albeit slowly!

    Col­or rendi­tion is a com­plic­ated mat­ter for every­one. If your digit­al cam­era sup­ports it you can adjust the light tem­per­at­ure and that may help or hinder. You could also try pla­cing the item in dif­fused sun­light, like through a thin sheet. Best of luck there.

  4. Mark, John and Eth­an are cor­rect; you could reverse-engin­eer the pat­tern from the pic­ture (I don’t go so far as to claim it’s a work of art that deserves copy­right in its expres­sion) but the way in which I described the pat­tern is copy­right­able and in fact under the laws of the coun­try in which I live (and many oth­ers) copy­righted (as is the rest of the ori­gin­al con­tent on this site). So I put up the license terms for any­one who may wish to use the pat­tern, or who was think­ing of repro­du­cing it somewhere.

  5. A more con­vin­cing answer would be of the form, “Yes, see Jones v. Smith, 1996, Wis App, 235, 15” or the like.

    This seems pretty sim­il­ar to sew­ing pat­terns, which can­not be copy­righted (and yes, I’m aware of the inter­net urb­an legends to the con­trary; cite case law if you want to dis­agree). When John men­tions reverse engin­eer­ing, what he may be get­ting at is the dis­tinc­tion that although the par­tic­u­lar sequence of words and let­ters in the post is copy­righted, the actu­al “pat­tern” is not protected.

    This makes a cer­tain amount of sense. For instance, the invent­or of the Roller Derby tried to pre­vent com­pet­ing pro­moters from sta­ging roller derby meets, by writ­ing a short story describ­ing the rules. Of course, he was held to own the copy­right to the short story, but, without a pat­ent, not to the rules of roller derby.

    How­ever, even the doc­u­ment itself may end up not being able to be copy­righted. Anoth­er case con­cerned a cer­eal com­pany that had a con­test that it pro­moted on the back of its cer­eal boxes. A com­pet­it­or copied it. This was held not to be a copy­right viol­a­tion on the basis that there are only so many ways to describe the rules of a con­test. If you give per­son A the right to exclus­iv­ity for ver­sion 1, and per­son B the right to ver­sion 2, soon­er or later you run out of sig­ni­fic­antly dif­fer­ent ways of describ­ing the rules. In effect, per­sons A through Z (or whatever) col­lect­ively have a mono­poly over that type of a con­test, which is only per­mit­ted if it is pat­en­ted. Res­ult: no copy­right even for the first ver­sion. This would seem to apply for knit­ting: you can­’t copy­right the design and stitches, so you can­’t have exclus­iv­ity over the straight­for­ward descrip­tion of the stitches — without a pat­ent or design patent.

    To eth­an: com­puter pro­grams can be copy­righted; algorithms must be pat­en­ted (cf. roller derby). If algorithms could be copy­righted, then the whole soft­ware pat­ent brouhaha would not exist (there’d be a soft­ware copy­right brouhaha in its place).

  6. Mark, you’re cor­rect in that the arrange­ment of stitches (i.e., the plain k and p) can­not be copy­righted for tra­di­tion­al stitches, although if I cre­ated my own that might be a dif­fer­ent story. (IANAL) What I can assert copy­right over is the way I describe the pro­cess to knit that cush­ion, or, as you say, the par­tic­u­lar sequence of words and let­ters in the post. I have read up a bit on copy­right law and knit­ting; I’ll pull togeth­er a post on that sub­ject in the next couple of days and hope you can com­ment then.
    [Update: hmm, the arrange­ment of the stitches to form the com­plete pat­tern may also be copy­right­able as it’s ori­gin­al and there­fore poten­tially unique. Not the tra­di­tion­al stitch pat­terns that make up the com­pon­ents, of course, but the way they’ve been put togeth­er. More when I write this up in a new post.]

  7. Most import­antly, under cur­rent U. S. copy­right law, any­thing giv­en expres­sion in a tan­gible form, as described above, and pub­lished after March 1, 1989 is pro­tec­ted by copy­right law wheth­er the copy­right hold­er has included a copy­right notice or not.”
    source: https://yarnaholic.wordpress.com/the-copyright-faq-for-knitters/

    May your life and your yarn sup­ply be limitless!

 Leave a Reply

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>

(required)

(required)

/* ]]> */