Skip to content

Create version 0.8.1 for ReaSonus #124

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cfillion merged 1 commit into from
Feb 9, 2026
Merged

Create version 0.8.1 for ReaSonus #124

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 4 additions & 25 deletions Control Surfaces/navelpluisje_ReaSonus Native.ext
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,37 +1,16 @@
@description ReaSonus Native
@author Navelpluisje
@version 0.8.0
@version 0.8.1
@changelog
# What's Changed

## FaderPort 8/16

This release has a lot of improvements for the UI for Plugin Mapping:

- Added the option to set the step size in Plugin Control mode on the device. The step size can be set both on-device as in the settings.
- You can now per control set the invert of the label. This can help you grouping sets of controls.
- All parameters of the plugin are now in the parameters list.
- Parameter list is now searchable.
- Added option to go to a group by number. This way you can go fairly quick to group 100 (or further of course).
- You can now add a new group at any place and delete any group.
- Drag and drop has been implemented to change the order of the groups.
- The limit for the maximum number of groups is set to 1024
- There is an indicator now that tells per group if it has changed or not.
- Added option to undo changes per group or all at once
- Some minor bugs with the UI have been fixed

One more bug has been fixed:

- The automation buttons were not illuminated correct

> During development also an issue was found with not taking the plugin type in account. This can cause issues with the mapping as a VST and VST do not have the same mapping.
> A tool has been created to help you fixing this. In the action list search for plugin type and run it.

## FaderPort V2

- Fixed issue where translations in the UI were not loaded

Thanx a lot to DesertEagleDerek for the code contributions and testing
- Fixed issue where the FderPort could disconnect when an action had a popup like Edit Marker
- Fixed issue where the valuebar looked faded when working with plugins
- Fixed issue where the displays got weird after switching quick between different fader modes

Thanx to anyone reporting issues and help me debug them.
@provides
Expand Down