Shift+F10 definitely works here, but you need to enable the keyboard shortcuts first - if you attempt to press Shift+F10, Surge pops up a dialog asking you if you want keyboard shortcuts to be enabled, and also provides a checkbox to remember that setting.
However, due to a JUCE related thing, in order to get keyboard focus you first need to click anywhere on Surge's interface... We'll try and figure this out.
There is no parameter search, but once you enable keyboard shortcuts, Ctrl+F will search for patches by text. However the results list is not accessible to screenreaders yet. We still have a number of things to improve on accessibility front.
Vember Audio Surge is now open-source
-
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
Thanks.
Shortcuts are enabled, and I believe the setting is remembered as I don't get the question any more when relaunching Surge.
and some of my blind friends have no problem with shift F 10. But I can't get it to work here, tried it on Reaper and Samplitude under Windows 10.
I'll try it on logic pro (OSX) and tell you how it goes.
Cheers,
Shortcuts are enabled, and I believe the setting is remembered as I don't get the question any more when relaunching Surge.
and some of my blind friends have no problem with shift F 10. But I can't get it to work here, tried it on Reaper and Samplitude under Windows 10.
I'll try it on logic pro (OSX) and tell you how it goes.
Cheers,
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
All right. As I just posted on your discord channel.
Accessibility is definitely better on Mac. All keystrokes work as expected, and one nice thing to is that parameters are grouped, and therefore much easier to navigate. I guess a good idea for now is to design your patches on Mac, and transfer them to PC if you need.
I wonder though, why shift + F 10 work on some Windows machines and not others, like mine.
Cheers,
Accessibility is definitely better on Mac. All keystrokes work as expected, and one nice thing to is that parameters are grouped, and therefore much easier to navigate. I guess a good idea for now is to design your patches on Mac, and transfer them to PC if you need.
I wonder though, why shift + F 10 work on some Windows machines and not others, like mine.
Cheers,
-
- KVRian
- 1113 posts since 20 Oct, 2018
Maybe your daw is using shift + F 10 as a keyboard shortcut for something else.jprykiel wrote: Wed Feb 23, 2022 8:33 am All right. As I just posted on your discord channel.
Accessibility is definitely better on Mac. All keystrokes work as expected, and one nice thing to is that parameters are grouped, and therefore much easier to navigate. I guess a good idea for now is to design your patches on Mac, and transfer them to PC if you need.
I wonder though, why shift + F 10 work on some Windows machines and not others, like mine. Cheers,
Then you have to deactivate that.
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
I thought so but no. I'm using Reaper, and an other friend also on Reaper doesn't have this problem. The only difference is that he just switched to Windows 11, which I am not ready to do yet.
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
Oh no! What is this?
Okay, today is a new day, restarting my computer and running a new test.
Okay, today is a new day, restarting my computer and running a new test.
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
-
- KVRAF
- 1950 posts since 17 Jun, 2005
If you go into Reaper's action list and try to assign shift+F10 to some action, does it show as expected there? If not, something is intercepting that (and potentially other) key combinations on your system.
-
Danilo Villanova Danilo Villanova https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418331
- KVRian
- 1197 posts since 30 Apr, 2018
Maybe the function keys are inverted?
-
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
OSARA is blocking Shift+F10 by default, which is what JP is using with Reaper.
-
- KVRist
- 135 posts since 2 Mar, 2016 from Paris France
Hey Mr Dragon, bingo. I found out that Osara had an action attached to shift+F 10, which is, show first context menu depending on focus. I removed it and all of a sudden, guess what, the Surge shortcut started working.
-
- KVRist
- 471 posts since 20 Nov, 2021
I couldn't find this issue in the thread so here goes:
In Reaper 6.49 with Surge XT 1.0.0.1
I did midi learn on the cutoff parameter to the mod wheel.
I created a sine curve modulation envelope for mod wheel.
On playback the cutoff slider motion is jerky and so is the actual cutoff in the sound.
Anyone else notice this kind of behavior? Sorry if this has already been covered.
Thanks.
In Reaper 6.49 with Surge XT 1.0.0.1
I did midi learn on the cutoff parameter to the mod wheel.
I created a sine curve modulation envelope for mod wheel.
On playback the cutoff slider motion is jerky and so is the actual cutoff in the sound.
Anyone else notice this kind of behavior? Sorry if this has already been covered.
Thanks.
-
- KVRAF
- 24414 posts since 7 Jan, 2009 from Croatia
How does that MIDI CC lane look in Reaper?
While there is smoothing on MIDI CCs in Surge (and there are options to change the smoothing method!), you should probably use host automation instead, for greater precision.
While there is smoothing on MIDI CCs in Surge (and there are options to change the smoothing method!), you should probably use host automation instead, for greater precision.
-
- KVRist
- 471 posts since 20 Nov, 2021
I tried changing the controller smoothing in Surge and nothing changed.
I have a midi item with a mod wheel cc envelope. Is that what you mean by host automation?
Anyway with this playing the Surge parameter slider moves, but is jerky.
I have a midi item with a mod wheel cc envelope. Is that what you mean by host automation?
Anyway with this playing the Surge parameter slider moves, but is jerky.
You do not have the required permissions to view the files attached to this post.