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

Allow to only show the amount of keys needed for given song #38

Open
othello777 opened this issue May 7, 2023 · 7 comments
Open

Allow to only show the amount of keys needed for given song #38

othello777 opened this issue May 7, 2023 · 7 comments

Comments

@othello777
Copy link
Contributor

Optional Feature: Different songs use a different amount of the piano. no point in showing all 88 keys if the song doesn't use it all. some such as myself may see it as a waste of screen real estate. Would be a cool feature to have it show "Only song keys" + a user defined number of padding keys or to next C.

@PolyMeilex PolyMeilex pinned this issue Dec 17, 2023
@PolyMeilex PolyMeilex added this to the 0.2.0 milestone Dec 17, 2023
This was referenced Dec 30, 2023
@PolyMeilex PolyMeilex removed this from the 0.2.0 milestone Jan 14, 2024
@PolyMeilex
Copy link
Owner

This got partially implemented in 0.2, but I'm leaving this open as the idea of auto sizing based on a song is still not there, and would be cool to have.

@PolyMeilex PolyMeilex changed the title Allow to only show custom amount of keys Allow to only show the amount of keys needed for given song Jan 14, 2024
@JoeAckroyd
Copy link

JoeAckroyd commented Mar 26, 2024

@PolyMeilex is the note range settings available in the cli app?

@PolyMeilex
Copy link
Owner

@PolyMeilex is the note range settings available in the cli app?

Yep, but only in the config file (not tested tho)

@JoeAckroyd
Copy link

@PolyMeilex is the note range settings available in the cli app?

Yep, but only in the config file (not tested tho)

hmm ok i changed it to
fn default_piano_range() -> (u8, u8) { (27, 101) }

in the config, but it's not worked. I just changed that line, and re compiled the cli. am i missing anything (never used rust before 😬)

thanks!

@PolyMeilex
Copy link
Owner

What's your platform? The config is a .ron file, in the .config/Neothesia directory on Linux, on windows it's just in the same dir as the binary run director.
You essentially changed the default config rather than the config itself.
Another way would be to run neothesia edit the settings and then run the cli, they share the same .ron config file

@JoeAckroyd
Copy link

JoeAckroyd commented Mar 28, 2024

Hey @PolyMeilex ! I'm on mac, it was in the .github/app/Neothesia.app/Contents/Resources dir.

however, now ive changed it, the waterfall doesn't line up with the keys? is there another setting i need to change?

thanks so much for the help!!!

@PolyMeilex
Copy link
Owner

That's a bug, I belive this is now fixed on main.

Although looking at the code I'm supprised that the config loaded succesfully in CLI mode at all. It was written in a way that assumes that the app has a macOS bundle, and noethesia-cli does not have one, so I'm not sure how macOS knows where to look for the config. I suppose I should change it to look for config.ron in current working directory like it is done on Windows.

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

3 participants