Monday, October 2, 2017

multiple choice...

OMG! You spot a mistake in your lace transfers 6 or 8 rows below! What to do, what to do?
A. Thank the knitting gods you spotted it so soon!
B. Quit and drink wine!
C. Try to rip back only that section.
D. Rip back all 8 rows.
E. All of the above.
I went with E but not in that exact order. After spotting the mistake, I did try unravelling just the stitches of that portion for 8 rows but by then, you’ve got strings all over the place and you’re not quite sure what’s what, especially on this particular pattern because it’s a 24-stitch repeat. The hard part about ripping back lace knitting, whether it is hand transferred or lace carriage, is that you need to untransfer/put the stitches back to the row before, rip out 2 rows, untransfer, rip out 2 rows and keep track of what row you’re going to be on when you finish ripping…
For this project, I actually have 3 row counters, two on the machine and one on my KR11, which is connected to one of the row counters. Sounds complicated but I’ve got a problem with my row counters. Now, bear in mind they are getting quite old, at least 20 years on one anyway. One of them doesn't recognize the cable going to the KR11 but it counts reliably. The other one addresses the KR11 properly but it advances weirdly starting at row 19. Instead of clicking up to 20, it goes to 29 and then 39 and then randomly and if you're not aware of it, you'll never be able to figure out what row you're on! I have taken them apart to see if I could spot the problem but couldn't....I'll be ordering a couple of new ones! Anyway, when I'm ripping out, after pulling out one row, I pull out a needle at the end of the needlebed. Rip one row, pull out another needle...count the needles at the end and turn back the row counter.
Long story even longer, just to be safe, I did rip back all 8 rows, fix the mistake, reset all the row counters and continue!
P.S. If you have a question for me that you would like an answer to, please email me privately – I do not answer comments. ;-)


No comments: