I have a question regarding the use of multisize tables in seamlyMe combined with patterns in seamly 2d.
When constructing a pattern in seamly2d I use to load a multisize table to the pattern so that grading is included in the first step of the construction. (works like a charm even though a stacked view of the grading would make me feel more secure about my graded patterns:))
to do this i open my patterns and select a range of sizes and heights as well as a base size and height in the pattern and in the multisize file (.vst). My multisize files contain a range of horizontal and vertical grading values. (see screenshot)
as far as i understood the base size selected in the grading file is prioritised from the base values in the pattern.
This leads to the result that i need a grading table for every base pattern with a different base size. Is this correct? Can I somehow avoid the rising amount of multisize files in my database?