[JW Lua] Adding properties to FCGeneralPrefs.

[Robert Patterson]

Here are the settings available. (I am leaning towards adding them.)

- Grace Note Mode (3 values)
- No Voice 2 in Transcription
- Soften Syncopations
- Save Tempo Changes
- Save Note Velocities
- Save Note Start/Stop Times
- Save Midi Expression Changes
- Standard (non-float) Quantization Resolution
- Floating Quantization mode (4 values)
- Floating Quant Sensitivity Level
- Split Key for fixed split point

I have not dug through the Finale menus to find where these are in the U.I.
If you recognize them, it would save me time if you could post them.

Robert


On Tue, Jul 26, 2022 at 7:58 AM Simon Leclerc <simon at prodsl.ca> wrote:

> The initial midi note length for example is kept by Finale when you import
> midi. That value stays. So it’s possible to do a retranscribe using
> different quantization values (smallest note value, mix rythms or not) to
> see if we get a better result. Using 16th notes as the basic value instead
> of 8ths, for example. I hope this answer your question.
> For now, I’ve created shortcuts (with Keyboard maestro) with different
> settings to put different parameters in that window.
>
> For the staff deletion, no the behaviour is the same as it was in JW Lua.
> Always been tricky to delete a staff and being sure it was not considered
> still “around” by some other parameters. For example: you delete a staff
> and then call (in another script) a Staves.Count; the result will be the
> same as before. Unless you go through the step I mentionned before. At
> least, this is what I experienced...
>
>
>
>
>
> ¯\_(ツ)_/¯
>
> Simon Leclerc
>
>
>
>
> On Jul 26, 2022, at 07:43, Robert Patterson <robert at robertgpatterson.com>
> wrote:
>
> Can you be specific about which quantization menu options you hit? I ask
> because the potential settings in FCGeneralPrefs may not be very helpful
> for what you described.
>
> Has the behavior around deleting staves changed from how it was in JW Lua?
>
>
> On Tue, Jul 26, 2022 at 5:57 AM Simon Leclerc <simon at prodsl.ca> wrote:
>
>> Hello Robert,
>>
>> For my part, I really often have to deal with imported midi files. The
>> tools used to quantize and retranscribe are an important part of the
>> process, as sometimes specific measures need to be re-quantized and
>> retranscribed to achieve a better ground result. Until now, I’ve been using
>> shortcuts to those menus to accelerate the process, but to have access to
>> those features through RGP Lua would certainly be a great addition. Many
>> times, I have wished it could be done.
>>
>> Speaking of specific features involving prefs and menus, I noticed that
>> when I delete a staff using RGP Lua (or with JW Lua), the staff is never
>> really gone (in the deep sense of the word) even when I update the
>> surrounding parameters involving the deletion of a staff. The only option
>> is to go through the File Maintenance menu and “Remove Deleted Items”. Only
>> this way the Score manager window will reflect the new reality of the
>> layout and therefore, won’t create subsequent problems. This might be
>> another topic though...
>>
>>
>> My 2 cents
>>
>>
>>
>>
>> ¯\_(ツ)_/¯
>>
>> Simon Leclerc
>>
>>
>>
>>
>> On Jul 25, 2022, at 21:05, Robert Patterson <robert at robertgpatterson.com>
>> wrote:
>>
>> FCGeneralPrefs is the class that provides access to Finale's global
>> program preferences. It is a wrapper around a data structure in the PDK
>> that provides access to some (but not all) preferences. However, currently
>> FCGeneralPrefs provides access to only a subset of that already limited
>> subset.
>>
>> As part of my 0.64 changes, I have been expanding FCGeneralPrefs to
>> include more of what is available. I have added in the easy options, but
>> for the remaining options I am wondering whether they would be useful
>> enough to add. These are
>>
>> - a bunch of quantization options, though I think it probably is not all
>> of them
>> - undo enable/disable (but not undo depth)
>> - UseFloatQuantInEntryMover (not sure if this is still used by Finale.
>> Does anyone know where it is in the U.I.?)
>> - RedrawActiveWindowOnly (same caveats as UseFloatQuantInEntryMover)
>>
>> Can anyone think of reasons why these might be useful? Probably the
>> quantization options would be the most likely to have a use, but I'd like
>> to hear what they might be if you have an idea.
>>
>> _______________________________________________
>> JWLua mailing list
>> JWLua at jwmusic.nu
>> http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu
>>
>>
>> _______________________________________________
>> JWLua mailing list
>> JWLua at jwmusic.nu
>> http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu
>>
> _______________________________________________
> JWLua mailing list
> JWLua at jwmusic.nu
> http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu
>
>
> _______________________________________________
> JWLua mailing list
> JWLua at jwmusic.nu
> http://jwmusic.nu/mailman/listinfo/jwlua_jwmusic.nu
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://jwmusic.nu/pipermail/jwlua_jwmusic.nu/attachments/20220726/eef1db29/attachment.htm>