خرید بک لینک
I find that for every ruleset I create, there are a few techniques or instructions that aren't covered by Notion's built-in list of techniques (as defined by ExpressionList.tpk). This is not Notion's fault; some of these techniques aren't typical for written music, but are specific to the VST being controlled. For example, ERA Medieval Legends has a traditional recorder that can play legato in two modes: true legato, and portato. From what I've read, to match the style of the era you should use the portato style of legato. Rather than mark every note under slurs with a staccato mark to designate them as portato, it would be nice to just write "Portato" and "Legato" to define and/or switch between the styles so that the ruleset can choose the selected style for notes under slurs. Other examples are vocal libraries with keyswitched vowels or consonants.

This can be accomplished by manually adding techniques to the ExpressionList.tpk, but it is a clumsy workaround because updates might overwrite it, and more importantly, it makes it nearly impossible to share the ruleset with other users, because not everybody is comfortable editing Notion's files like that and they'd have to do it themselves.

The solution I propose is to allow the user to create new techniques within the custom rule GUI, which would then get saved with the custom rules themselves, in the score and also when exporting a ruleset into a prules file. After a technique is defined, it could be setup so that you just grab it from the rules GUI with a "use" button similar to the way rulesets are added to the score, or you can let us define an apostrophe shortcut as we would when manually adding them to expressionlist.tpk. By saving them with the exported rulesets, those VST-specific techniques would then be available when somebody imports somebody else's custom rules.

برچسب: نویسنده: استخدام کار تاريخ: پنجشنبه 12 مرداد 1396 ساعت: 20:38

صفحه بندی