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

The frequency indicator in spectrograms are not legible #317

Open
FredrikKarlssonSpeech opened this issue Mar 25, 2022 · 1 comment
Open

Comments

@FredrikKarlssonSpeech
Copy link

I suspect that this is an issue that is made more severe by larger displays but the frequency indicator for the pointer in a spectrogram display is not very easy to use. I attach an image of what I get with max font size settings (200% scaling)

Skärmavbild 2022-03-25 kl  10 39 21

I think it would be great if the frequency value would be displayed in a larger and more legible font, and perhaps against a different background than the spectrogram (a small box?)

Alternatively, you could get a small tag / label near your pointer (floating above to the right of the pointer perhaps) when you press p (=position?) in a spectrogram. And a great feature would then be if the label also gave a local intensity reading.
And a fantastic feature, especially for students, would be that these measurements would also be placed in the clipboard for you directly when pressing the 'p'. (Like the example I added to the image above, but with a less silly type of bubble then of course).

@samgregory
Copy link
Contributor

Hi @FredrikKarlssonSpeech, what value would you want copied into the clipboard - frequency, amplitude or both?
If you want a frequency is it the current cross hairs, the point on a selected track or the nearest track value?
If you want an amplitude are you wanting that based on existing calculations (in some other ssff file) or does it need to be derived on the fly?

If we are going to implement a clipboard feature do we simply stick to the default CTRL+C shortcut?

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

No branches or pull requests

2 participants