Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Knitting with 2 carriages #607

Open
t0mpr1c3 opened this issue Dec 21, 2023 · 0 comments
Open

Knitting with 2 carriages #607

t0mpr1c3 opened this issue Dec 21, 2023 · 0 comments

Comments

@t0mpr1c3
Copy link
Contributor

Not sure if it is a bug or intended behaviour, but currently knitting with 2 carriages can get pretty weird (e.g. LC and KC, https://alessandrina.com/2018/04/13/revisiting-knitting-with-2-carriages-single-bed-910-vs-ayab-so-far/)

Usually you would keep the LC on the extension rails on the LHS while knitting with the KC, and keep the KC on the extension rails on the RHS when doing transfers with the LC.

The issue is that when you have done a sequence of LC passes ending in a pass from R to L, the next pass with the KC is also R to L. It seems that AYAB does not recognize this as a new carriage pass, so the needle selections are retained from the previous row. The same thing happens after the last pass with the KC from L to R.

None of this matters if you are just doing 2 plain rows of knitting between transfers. The issue only arises if the knit rows contain slip or tuck stitches.

I have some ideas for a comprehensive solution to this, but in the mean time it's probably best flagged as a documentation issue: one of the various ways in which AYAB differs from punchcards when knitting lace.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant