On 18.07.2002 16:00 Uhr, Andrew Stiller wrote
>> I assume you've confirmed that all the flag positioning values are the same
>> in both files, right?
>>
>> If so, that is very peculiar. Perhaps it's some sort of rounding error
>> resulting from a different reduction percentage?
>>
>> mdl
>
>
> > My default file is also set to
> >Engraver, and produces perfect 32nd-64th flags, but the orchestral
>>file I'm working on (which I created by clearing the notes from a
>>copy of another such file) requires totally different settings to
>>produce acceptable results. I double-checked, and no,
At 10:18 AM 07/17/02, Andrew Stiller wrote:
>Thank you! That saved me a lot of hair pulling. I did notice, though,
>that it is impossible to set a Secondary Group position that is
>correct for both upstem and downstem flags. I ended up choosing a
>compromise value (14 EVPU) that left the downste
> >I don't know why this problem keeps popping up, but it does: Once
>>again, the thirty-second note flags in a file I'm working with
>>(FinMac 2K2, Engraver Font) are too close to the 16th-note flags.
>>Could some kind soul who knows give me the correct number to enter in
>>whatever DB to fix th
>
>You need to adjust your flag positioning values.
>
Thank you! That saved me a lot of hair pulling. I did notice, though,
that it is impossible to set a Secondary Group position that is
correct for both upstem and downstem flags. I ended up choosing a
compromise value (14 EVPU) that left th
>I don't know why this problem keeps popping up, but it does: Once
>again, the thirty-second note flags in a file I'm working with
>(FinMac 2K2, Engraver Font) are too close to the 16th-note flags.
>Could some kind soul who knows give me the correct number to enter in
>whatever DB to fix this? And
I don't know why this problem keeps popping up, but it does: Once
again, the thirty-second note flags in a file I'm working with
(FinMac 2K2, Engraver Font) are too close to the 16th-note flags.
Could some kind soul who knows give me the correct number to enter in
whatever DB to fix this? And
