Falcon Programmer - batch configuration application for UVI Falcon

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Post Reply New Topic
RELATED
PRODUCTS

Post

I am pleased to announce the release of Falcon Programmer, a new open source batch configuration application for the UVI Falcon software synthesizer.  Multiple types of configuration change can be implemented in thousands of Falcon programs with a single batch run, taking seconds to minutes.

There is currently an installer only for Windows.  However, the source code should run on macOS; and a macOS installer will be provided as soon as a collaborator can be found to create the installer and test the application on macOS.

The following configuration tasks are available:
  • Restore the program to an original version, ready for the configuration changes to be made.
  • Initialise the program's Info page layout with many options, including converting a script-based layout to the standard layout.
  • Assign MIDI CC numbers to macros and, provided the program uses the standard Info page layout, optionally append each macro's MIDI CC number to its display name.
  • Remove arpeggiators and sequencing script processors and then, provided the program has a standard Info page, remove any macros that consequently no longer modulate anything.
  • Bypass (disable) all known delay effects and then, provided the program uses the standard Info page layout, remove any macro that no longer modulates any enabled effects.
  • If a Release macro is not part of a set of four ADSR macros and the macro is not modulated by the mod wheel, set its initial value to zero.
  • Set the values of known reverb macros, with some exceptions, to zero.
  • Move release and reverb macros that have zero values to the end of the standard Info page layout.
  • Where feasible, replace all modulations by the modulation wheel with modulations by a new 'Wheel' macro on the standard Info page layout.
  • If the modulation wheel's modulations have been reassigned to a Wheel macro (the previous task), reuse MIDI CC 1 (the mod wheel) for a subsequent macro, where feasible.
  • Prepend a line indicating the program's path (sound bank\category\program name) to the program's description, which is viewable in Falcon when the Info page's i button is clicked.
Of these configuration tasks, assigning MIDI CC numbers to macros will be of use to many Falcon players.  And restoring the program to an original version is just a safety feature to facilitate subsequent transformation.  The remainder are merely what the developer has found useful as a Falcon player.  Many more configuration tasks are surely possible.  Users of the application are welcome to suggest some!

The Windows installer can be downloaded from GitHub.  For further information, please refer to the manual.  Potential collaborators may refer to Contributing to Falcon Programmer development.
 
Last edited by SimonORorke on Sun Jul 21, 2024 11:06 pm, edited 1 time in total.

Post

Version 1.0.1 of Falcon Programmer is now available.

Enhancement

MIDI for Macros page: Added advice 'MIDI CC 38 does not work when assigned to a control on a script-based Info page'.

Bug Fix

Fixed a bug where, when the InitialiseLayout task removed a GUI script processor, all other program-level event processors were removed too.

Post

Version 1.1.0 of Falcon Programmer is now available.

Enhancement

New configuration task RemoveArpeggiatorsAndSequencing: Removes arpeggiators and sequencing script processors. Then, provided the program has a standard Info page, removes any macros that consequently no longer modulate anything.

Bug Fix

Fixed a bug where the RemoveDelayEffectsAndMacros task removed toggle macros that were not delay macros but were initially toggled off.

Post

Hi Simon,

Thanks for your work!
I checked the documentation, but pictures are missing in both pfd and word document.
Kind regards,
John

Post

Hello John, are you looking at the manual in GitHub? If so, yes I saw the same problem, and don’t yet know what to do about it. If you download the PDF manual, and look at that, it will be fine. Also, if you install the application and then click the menu button on the main window top right and select manual from the context menu, that will show the pictures too.

I’ll look into why the PDF pictures are missing when you look at the manual in GitHub.

Post

I have fixed the problem where, when the manual PDF was viewed via its GitHub link in a browser, some of the pictures it contains were missing.

Pictures missing from the Word document that is the source of the manual PDF is a different matter. The Word document's pictures are all displayed from links, not embedded in the document. This makes it easier for me to update a picture if required. To see the pictures in the Word document, it is necessary to download the project, or at least the Documentation folder, and open the Word document in situ.

@johhkhf, I would appreciate it if you would check the manual PDF in your browser again, and confirm that it looks OK now.

Post Reply

Return to “Instruments”