Open Issues Need Help
View All on GitHubAbout Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
AI Summary: Debug and fix a bug in the ReaSonus FaderPort Native plugin where creating a new track or importing media causes the fader to malfunction, requiring a workaround to regain control. The issue specifically affects users with a FaderPort v2 on Windows 11. The solution likely involves investigating how the plugin handles track creation and media import events to ensure proper fader initialization and control.
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended
AI Summary: Debug and fix a bug in the ReaSonus Faderport Native plugin where using the pan envelope on a FaderPort v2 unexpectedly creates a volume envelope instead. This requires investigating the code to identify why pan envelope selection isn't correctly handled and implementing a fix.
About Control REAPER with your FaderPort 8, 16 or V2 as it was intended