You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if Surge is in MTS-ESP client mode the Tuning Editor is dormant and not reading data
The request is to have Radial and True Keys provide scale information as it would if Surge was playing from a loaded .scl file
As per our discussion on Discord:
True Keys display would require:
1: The currently pressed keys
2: Their frequency
3: The ability to subtract and take a log
*Since we show actual keys not scale tones. We have all of that in MTS mode
The Radial display would require:
1: The currently pressed key
2: The scale tone for each of those keys
3: The repetition interval of the scale
4: Their frequency
5: The ability to subtract and take a log
*We are missing 2 and 3 in the MTS api but have it in the tuning library
The text was updated successfully, but these errors were encountered:
In MTS-ESP mode you can use a subset of the tuning editor
so rename it tuning visualizer in that mode and show the true
keys and the keyboard display
Closessurge-synthesizer#7146
In MTS-ESP mode you can use a subset of the tuning editor
so rename it tuning visualizer in that mode and show the true
keys and the keyboard display
Closes#7146
Currently if Surge is in MTS-ESP client mode the Tuning Editor is dormant and not reading data
The request is to have Radial and True Keys provide scale information as it would if Surge was playing from a loaded .scl file
As per our discussion on Discord:
True Keys display would require:
1: The currently pressed keys
2: Their frequency
3: The ability to subtract and take a log
*Since we show actual keys not scale tones. We have all of that in MTS mode
The Radial display would require:
1: The currently pressed key
2: The scale tone for each of those keys
3: The repetition interval of the scale
4: Their frequency
5: The ability to subtract and take a log
*We are missing 2 and 3 in the MTS api but have it in the tuning library
The text was updated successfully, but these errors were encountered: