Skip to content
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.

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

Request: Display current Bank and Patch Name on plugin GUI #209

Open
reggiedrax opened this issue Jun 22, 2022 · 2 comments
Open

Request: Display current Bank and Patch Name on plugin GUI #209

reggiedrax opened this issue Jun 22, 2022 · 2 comments

Comments

@reggiedrax
Copy link

An enhancement request.

Expected behavior

I expected to be able to see which Bank and Patch are currently active displayed somewhere when using amsynth as a plugin.

Actual behavior

I'm not able to see which Bank and Patch are currently active when using amsynth as a plugin. With so many Banks and Patches it's not possible (for me) to remember which of the Bank/Patch combinations I have used for that track - and it's easy to misclick (that's a real word) and load another by mistake, losing the Patch I was using.

Information

  • Which version of amsynth are you using? Built from develop clone 21/6/22
  • Which build of amsynth are you using? (stand-alone application, LV2, DSSI, VST) VST
  • If using amsynth as a plugin, which host application are you using? REAPER v6.61
  • Which operating system & version are you using? Linux Mint,
    uname -a
    Linux HP-Pavilion-Laptop-15-cw0xxx 5.13.0-51-lowlatency #58~20.04.1-Ubuntu SMP PREEMPT Tue Jun 14 12:26:40 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Steps to reproduce the behavior

  1. Start REAPER
  2. Insert track with amsynth VST
@nickdowell
Copy link
Member

This feature has now been implemented on the develop (default) branch!

It's part of a bigger rewrite of the GUI (#37) and not quite ready for release yet but feedback is welcome if you're able to build the latest version from Git.

@nickdowell nickdowell pinned this issue Aug 7, 2023
@reggiedrax
Copy link
Author

reggiedrax commented Aug 8, 2023 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants