PianoMeter Android Change log

April 9, 2018 Uncategorized 37 Comments

List of changes in each release

Version 1.0.1

Initial release

Version 1.0.2

Removed unnecessary contacts permission

Version 1.1.0

The spinning “strobe” rings are now more responsive, giving faster and more precise feedback on the instantaneous pitch. The divisions per ring now change based on the frequencies of the harmonics being measured.

Major improvements to the Pitch Raise procedure, including more accurate initial measurements and the addition of a maximum overpull setting.

Many bug fixes and enhancements.

Version 1.2.0

Add support for note names in multiple languages (eg. C, D, E vs. Do, Re, Mi)
Small improvements to file management, including searching, sorting, and sharing tuning files
Bug fix related to custom pitch offsets and the tuning curve display
Add a “Plus” level of functionality between “Free” and “Professional” geared toward hobbyists
Small bug fixes and enhancements

Version 1.2.1

Enhancements for tuning file management: multi-file select and mass export/import
Slightly smoother needle movement for more stable pitch readings
Bug fixes

Version 1.3.0

Better overpull calculation for pitch raise that takes into account string transitions.
Bug fixes

Version 1.3.1

Bug and crash fixes

Version 1.3.2

Improved measurement of inharmonicity (reduce bad measurements)
Allow modification of an inharmonicity weight factor (advanced users)
Bug fixes

Version 2.0.0

New app name: “PianoMeter” and new icon.
Dial/numbers now update 2x as fast (faster response to changes in pitch).
Add support for tuning in unequal temperaments.
Add support for multiple languages.
New (vector) graphics; download size reduced by 75%.
Small tweak to octave weighting in the bass (A1-A3) giving slightly more weight to 5:10 and 4:8 octaves.
Small changes to note detection, inharmonicity measurement, and user interface.

Version 2.0.1

Bug fixes

Version 2.0.2

Improve memory consumption on older tablets
Fix bug that was preventing the modification of tuning files while the tuning curve was locked

Version 2.0.3

Add option for clock in info box
Modify graphic for background wood panel (smaller APK)
Bug fixes (red line position, buffer issue affecting some old tablets)

Version 2.1.0

Introducing Dark Mode: a simple dark layout with no graphs uses less battery.
Refactor file management, making it faster and more efficient.
Long press in the graphing area to delete a data point of inharmonicity, or to reset all points on the tuning curve graph.
Slightly increase “weight” of 6:2 twelfths and decrease weight of 10:5 octaves. This will result in slightly less “stretch” in the lower bass of some pianos.
Expanded range for possible values of the lowest unwound string (down to D2).

Version 2.1.1

Allow all “A” notes to be tuned in the free version (in addition to C3-C5) to aid in evaluation
Minor enhancements to the piano keyboard at the bottom of the screen
Minor fixes

Version 2.1.2

Reduce weight of lower partials in the bass
Various minor fixes

Version 2.1.3

Add graphing to dark mode (by popular request)
Performance improvements
Add a “Global pitch offset” (pro version only)

Version 2.1.4

Bug fix (issue with target frequencies for strobe spinners not updating after exiting pitch raise mode)

Version 3.0.0

Users can now modify tuning style (stretch) by adjusting optimization “weights” assigned to intervals. Some changes to “default” style (less stretch in bass)

Add Dropbox integration for backing up tuning files

Auto note switching is less susceptible to octave jumping and background noise

Add option for Pro subscription (vs. one-time purchase)

Note that the ongoing costs of developing/maintaining the app have made a price increase necessary for the Pro version effective May 1, 2020

Version 3.0.1

Users can now modify tuning style (stretch) by adjusting optimization “weights” assigned to intervals. Some changes to “default” style (less stretch in bass)

Add Dropbox integration for backing up tuning files

Auto note switching is less susceptible to octave jumping and background noise

Add option for Pro subscription (vs. one-time purchase)

Note that the ongoing costs of developing/maintaining the app have made a price increase necessary for the Pro version effective May 1, 2020

Version 3.0.2

Bug fixes

Version 3.0.3

Bug fixes, remember user preference for sort order, add alert for first-time users that “free” version is for evaluation

Version 3.1.0

Dropbox backups now include saved custom temperaments and tuning styles
Minor bug fixes
Add startup screen

Version 3.2.0

Various updates (improved Android 10-11 support, updated crash reporting, billing manager, fixed bug with cent values and temperament screen, refactored default sort order)
Now requires a minimum of Android 4.4 (KitKat) up from Android 4.1 (Jelly Bean)

Version 3.2.1

Fix bug affecting the management of relative partial strengths (may slightly improve calculated tunings, including for previously stored files)
Various compatibility and dependency updates

Version 3.3.0

Added new screen with various options on startup
Tweaked flow of various processes (new tuning file, pitch raise)
Updated non-English localization

Version 3.3.1

Expand possible range of values for “lowest unwound string”
Various minor updates
Bug fix (subscription renewal)

Version 3.3.2

Fix issue with freezing when starting and loading tuning files
Slightly lower threshold for switching notes in Auto mode
Various minor updates

Version 3.3.3

Compatibility for Android 12
Raise minimum required Android version from 4.4 to 5.0 (KitKat to Lollipop)
Bug fixes

Version 3.3.4

Bug fix (file exporting/importing)

Version 3.4.0

New: Tone generator (pro version only) – tune aurally with harmonically accurate reference tones

New: Custom colors – make PianoMeter yours with a custom color scheme

Fix bugs with importing tuning files, temperaments, and tuning file settings.

Pitch offset color in infobox now turns red if not tuning to standard pitch

Other updates and fixes

Version 3.4.1

Improved layout of Tuning Style screen

Version 3.4.2

Added control over which audio inputs to prefer (Menu > Other > Audio Input)
Known bugs: On some devices you must “restart” the audio by exiting and re-opening the app after plugging in a new microphone. Not all Bluetooth headsets are supported. (We recommend not using Bluetooth microphones anyway.)

37 Comments

About Anthony Willey

Anthony Willey began tuning pianos in 2001 with a tuning lever and fork, some mutes, a book, and a lesson from the family piano tuner. Beginning in 2006 he underwent 4 years of training at the Brigham Young University piano shop under Keith Kopp, RPT, and James Busby, RPT. Anthony went on to pass the RPT tuning and technical certification examinations himself, becoming a Registered Piano Technician with the Piano Technicians Guild. Anthony also holds Bachelors and Masters degrees in physics from Brigham Young University, and has 25 years of experience as a classical musician, playing and teaching multiple instruments including the string bass, violin and piano.

37 Comments

Leave your reply.

Ed Sutton
· Reply

February 7, 2019 at 1:21 AM

Anthony-
I’m enjoying Easy Piano Tuner.
I have a suggestion.
Your app gives us three streams of information about pitch: the cents readout, the hand pointing to the dial and the strobe rings.
They are not really in sync with each other, and they compete for attention. I find the effort to ignore the number and hand are mentally exhausting. I had the same problem with TuneLab.
The strobe rings give us complex, but synchronized information. That is what I’d usually want to be focused on, but the numbers and hand keep distracting me.
Could you include the capacity to turn each mode “on” and “off?” It would help me tremendously.
Thanks for considering!
Ed Sutton
- Anthony Willey
  · Reply
  
  Author
  
  February 7, 2019 at 10:03 PM
  
  Yes, that’s something I can do, and you’re not the first person to request something like that, but I’ve held back for a couple of reasons:
  1: The strobes work best for most of the piano, BUT they don’t work for the top octave or so because they either spin too fast or “phase” in the wrong direction if the pitch is too far off, like the wagon wheels appearing to turn backwards in old movies. So you could be 20 cents flat and the strobe would be turning clockwise.
  2: I fear that many users would use the feature to turn off the (“distracting”) strobe rings before realizing that those work better
  3. I am very close to implementing a solution that will significantly speed up the dial so that it will be more in sync with the strobes. I hope to have it in alpha testing within a week, and hopefully released to beta testers within 2-3 weeks. That’s my highest priority at the moment, so after I get that out I can start looking at ways to implement your suggestion.
Andy
· Reply

July 23, 2019 at 9:24 AM

Which Android-Version is required?
- Anthony Willey
  · Reply
  
  Author
  
  August 27, 2019 at 4:11 AM
  
  At least 4.2.2
Andy
· Reply

July 23, 2019 at 8:21 PM

It takes MUCH ressources and eats battery. Is it possible to fix that?
- Anthony Willey
  · Reply
  
  Author
  
  July 24, 2019 at 12:50 AM
  
  To a certain extent higher than normal battery usage is needed for the constant processing and keeping the screen on. Most users I’ve talked to use either a long charging cable or an external battery if they’re going to be tuning multiple pianos. We are also working on an optional “dark mode” that will turn most of the screen black (saving battery on devices with AMOLED screens) and turns off the (non-essential) graphing, which saves on processing time.
Andy
· Reply

July 24, 2019 at 6:57 AM

I belive, it is not caused by the screen but by calculating. My tablet gets hot using Pianometer. I have AMOLED and know, how long it runs width one load.
- Andy
  · Reply
  
  July 24, 2019 at 6:59 AM
  
  Excuse my bad English.
  - Anthony Willey
    · Reply
    
    Author
    
    July 24, 2019 at 11:46 AM
    
    If you haven’t already, you can try out the dark mode by joining the “beta testing” program (using the button on the app’s page in the Google Play Store) and see if it makes any difference. Could you send me an email with the make/model of device you’re using?
Andy
· Reply

July 24, 2019 at 6:08 PM

Yes, I will do so.
Andy
· Reply

July 26, 2019 at 8:08 AM

In fact, darkmode saves energy. But maybe that’s caused by hiding the bottom panel, wich needs calculating power. Interesting would be to know, if users without AMOLED have same experience, because there display doesen’t save energy in darkmode.

I had this idea while testing: a button to pause Pianometer complete (only a big button to wake up remaining). This could be used while tuning unisons by ear.
Darryl
· Reply

December 17, 2019 at 1:29 AM

When sampling notes for inharmonicity and stretch can I play all strings of the note being sampled or do I have to mute to a single string?
- Anthony Willey
  · Reply
  
  Author
  
  February 24, 2020 at 7:03 PM
  
  Either way. If the unison is significantly out of tune I recommend playing a single string, but the app has some built-in filters to allow for accurate inharmonicity measurement even when a full unison is played.
Erco
· Reply

December 28, 2019 at 11:35 AM

I’ve purchased PianoMeter Plus and had a first go to tune my Sauter 122 upright, which is in quite a good shape. The overall result of my tuning efforts is not good. I’m trying to find out where the problem is and how to improve. I’m a bit reluctant to keep testing on the piano in order not to get the pins used.

How precise should a string be tuned? In other words, how many cents or fraction of a cent a string can be off without becoming a problem for the final result? In my experience, it’s very hard to get the string tuned within one cent of the goal, but one cent off seems to give a bad overall result (I’m of course not 100% sure that this is the cause).

This is related to the following. I read in the documentation: tune to the “early” tone as you strike. When I strike a key, the dial/strobe/number at first shake a lot and after a fraction of a second settle down, but still keep moving over time as the sound diminishes. What is the moment during a key strike I should focus on for tuning? After the initial settle down?

I read in the documentation: the strobe is more accurate than the dial/number. What I see on the strobe is that the higher harmonics behave differently from the lower ones. They have different turning speeds and sometimes go in the other direction. Should I focus on the lowest harmonic? Should it become fully motionless for the tuning to be correct?

I read in the documentation: the other two string of a unison should be tuned by ear, listening to the beats. I do hear the beats, but I can’t figure out, without actually trying, whether the second string is flat or sharp compared to the first one (which was tuned using the PianoMeter). Is it possible to hear when the second string of a unison is flat or sharp, or is it just a matter of trying: when the beat becomes faster: change the turning direction of the hamer.

I find it hard to tune the third string of a unison. I tried to tune it, while muting one of the other two already tuned strings, to make it easier. Is this a common practice?

I hope you don’t mind the long text and many questions. Maybe others will also benefit. Thank you in advance for your answer.
- Anthony Willey
  · Reply
  
  Author
  
  February 24, 2020 at 7:24 PM
  
  Erco, sorry for the slow reply. (I don’t check comments here as often as emails.)
  
  If you can get the first string within +/- 1 cent that is perfectly acceptable. Tuning to the first 0.1 second of the attack usually doesn’t work very well because there is a lot of extra noise (key, action, etc.) distorting the sound. Immediately after it settles down is a good time to tune. Tuning into the long late decay is ok, but isn’t as good and is a bit slower for various reasons.
  
  When the strobes are out of sync with each other that’s an indication that the actual inharmonicity of the piano doesn’t precisely match the model. That’s not a big problem—the calculated targets are still good—and the solution is to make the strobes as slow as possible. Typically this means having the outermost strobe turning clockwise and the innermost strobe turning counter-clockwise, with the middle ones stopped. It is also good to look at the needle in this case, as that displays kind of a moving average. (The needle isn’t exactly less-accurate, it is just slower to respond to changes in pitch than the strobes.)
  
  Tuning unisons is where you will probably see the most improvement in the sound of your piano. If a single note is 2 cents off but the unisons are in tune the piano will sound just fine. But if a unison is 2 cents out of tune it will sound noticeably bad and intervals you play that include that note will sound out of tune.
  
  You can’t tell by ear if the second string is sharp or flat. You just have to move it in one direction and see if it gets better or worse. A well-tuned unison will sound the same as a single string, so it’s sometimes helpful to remind yourself what sound you’re looking for by moving the mute to compare the tuned 2 strings to 1 string.
  
  If the 2nd string isn’t perfectly in tune it will be even more difficult to tune the 3rd string. It’s fine if you tune the 2nd and 3rd strings to the 1st string individually. Just make sure you listen to the full unison at the end to make sure it sounds good.
  
  Alternately, if tuning by ear just isn’t working for you, you can tune each string individually to PianoMeter, one string at a time. Make sure the tuning curve is locked before you do that.
Bat
· Reply

July 3, 2020 at 5:08 AM

Hi there,

I have purchased your software and am about to try to tune my piano. When I used the software to calculate the tuning curve, I noticed something strange about the bass. Then I realize that the lowest note on a piano is A0. Its frequency is 27.5Hz. Most of the mic on mobile devices won’t be able to pick up that kind of low frequency. That would explain the strangeness / flatness of the tuning curve.

Do you have a mic that you would suggest we could use on an android phone to pair with your software?

Cheer,
Bat
- Anthony Willey
  · Reply
  
  Author
  
  December 31, 2020 at 2:30 AM
  
  Bat,
  Although the fundamental frequency of A0 is 27.5 Hz, we don’t use that frequency for tuning. We are only using higher partials (harmonics) of A0. I believe for A0 we are using the 4th, 5th, 6th, and 8th harmonics. The frequency of the 4th harmonic is nominally 110 Hz, which is well within the acceptable range of most microphones today. So you don’t need to worry about purchasing a new mic, though you may get slightly clearer readings with one.
Volodymyr
· Reply

June 26, 2021 at 6:00 AM

Great program Pianometer! In my opinion, the author of a recently released program, widely discussed on pianoworld, has applied 80% of the ideas from Pianometer. I think that Pianometer needs to improve the look of the needle and stroboscope: make the needle and strobes move in a straight line instead of a circle. This will make better use of the working area of the display. In the meantime, I only look at the position of the needle and do not look at the strobes at all …
David Rydh
· Reply

August 8, 2021 at 4:21 PM

Hi Anthony,

I really enjoy the app (iOS version). I understand that the strobe rings are most accurate but I’m curious about the difference between the needle position, the cent number in the upper half and the cent number in the railsback curve. The needle and upper cent reading seem to be more or less instantaneous and agree whereas the lower cent number is apparently averaging many (all?) readings. On the other hand:

1) If I lock the note and play a semi-tone above or below, the lower number reads approximately +100.0 or -100.0 as expected whereas the needle and upper number reads approximately +50.0 or -50.0 (but occasionally jumps to -100.0).

2) For small deviations (0-10 cents), the upper and lower cent numbers roughly agree but not always, for instance when playing all strings of a badly tuned unison in the highest octave.

So apparently, the two cent numbers are measured/calculated in two different ways? Is the bottom more accurate but slower? Or just different?

Best,
David
- Anthony Willey
  · Reply
  
  Author
  
  August 9, 2021 at 2:59 AM
  
  The two cent numbers are measured/calculated in two different ways. I wouldn’t say that the bottom is more accurate, but it is slower. The top (dial) number is a fairly instant reading that is calculated using only the harmonics currently present in the tone. The bottom number includes more history, including transient harmonics that are present shortly after the “attack” but that decay quickly.
Vladimír Trejbal
· Reply

September 27, 2021 at 2:25 PM

Hi Anthony,
I have purchased pro version and I am impressed. Thanks for your work.
I have some ideas to improve the allocation.
1. it would be good to put on the main screen a slider to adjust the A4 pitch so that you can quickly adjust the base pitch before you start tuning. Also add the option of automatic setting of the default pitch offset according to the current pitch A4.
2. add the import tuning file function in the main menu.
2a. Maybe I’m doing something wrong, but I can’t import the tuning file. Could you look at it or fix it?
3. enlarge the tuning part of the screen somewhat, there is a lot of unused space under it, where the most important part of the screen could be expanded. It would help especially on phones with a smaller screen.
Thanks again for your work. I can say that the application can be used on a professional level.
- Anthony Willey
  · Reply
  
  Author
  
  October 1, 2021 at 8:52 PM
  
  1. I replied to you by email.
  2. I agree this would be helpful, but I think there would be problems with PianoMeter accessing files out of its own little folder. (Android and Apple really try to prevent apps from accessing files from other apps, as it’s a big security risk.)
  2a. I usually access the backup file using a file manager app. Clicking on it opens it with PianoMeter
  3. I’ll definitely keep this in mind the next time I’m working on layout. (My current goals are to make both the tuning circle and the graph as big as possible.)
Hans Lauesen
· Reply

October 1, 2021 at 5:45 PM

Hi there

Has anybody problems with iOS and iPadOS 25. I have noticed flickering ‘strobe’ rings and bad respondings from the App in recognizing notes on pianos. Please let me hear if you have same type of problems.

H.L.
Hans Lauesen
· Reply

October 1, 2021 at 5:47 PM

Sorry

Of course I ment iOS 15 and not 25

H.L
Hans Lauesen
· Reply

October 1, 2021 at 5:57 PM

Hi there

Sorry! My first comment disapeared. Therefor this again:

I have noticed problems with iOS 15 and iPadOS 15. ‘Strobe’ rings are flickering, App has problems with recognizing notes on the piano. In fact it responds much slower than before.
Let me hear if you have solutions

Regards
HL
- Anthony Willey
  · Reply
  
  Author
  
  October 1, 2021 at 8:48 PM
  
  Yes, there is a compatibility issue with the newly released iOS 15. I’m working on a fix and hope to have it pushed out soon.
Peter Hedelund
· Reply

November 4, 2021 at 4:09 PM

Hi Anthony,

Great product. As an amateur-tuner, the app does a great job at making my piano sound good. 🙂

A small question/suggestion though: As far as I can tell the tuning needles position is calculated from the average of the deviance from the correct tuning from the different partials. Or sort of the average of the motion of the strobe wheels. This works fine for strings, where the partials follow the model of the partials ie. they move in the same way. But for strings where the partials do not behave as the model (ie. the wheels move in opposite directions), this causes the needle to jump, when one or more of the partials are no longer detectable or becomes detectable. Because the average value suddenly changes. (I live in appartment, so I try avoiding banging to much on the piano when tuning to make is as little annoying for the neighbours as possible).

So my suggestion is, that the app in the background would calculate eachs partials deviation form the ideal model. And then take this information into account when calculating the needle position. Say, for instance, that if the 4’th partial is 2 cents flatter than the ideal model, then the needle calculation adds 2 cents to the measured value for this partial before putting it into the average. This way, the neddle wouldn’t jump when the 4’th partial becomes undetectable.

Maybe this isn’t the right way to do it, but something that would make the needle stay in the same place, regardless of wether the microphone is able to detect all of the partials or just some of them would be nice.

Kind Regards,
Peter
- Anthony Willey
  · Reply
  
  Author
  
  October 6, 2022 at 11:38 PM
  
  Strobe rings going different directions: This is an indication that the measured or assumed inharmonicity is different from what it actually is on the piano. Before you start a tuning, you will typically measure several notes to generate a tuning curve for the piano. What is going on here is you’re measuring the inharmonicity of the notes, and then the program interpolates for notes that you haven’t measured using kind of an average curve. You can see a graph of the inharmonicity (measured notes and the average curve) by swiping left or right in the graphing area. It’s the curve shaped somewhat like the Nike swoosh.
  
  Basically the inharmonicity tells you the spacing of the harmonics of each note. The note A3 with low inharmonicity might have harmonics at 220, 440, 660, and 880 Hz, while the same note with high inharmonicity might have harmonics at 220, 440.5, 661.5, and 883 Hz. If the inharmonicity has been measured wrong, or if you’re using a model with just a few measurements that don’t account for abnormalities in the piano’s scale, then the spacing of the tuning targets for the harmonics won’t line up with the spacing of the actual harmonics of the note you’re tuning. So for A3, the targets for the first two harmonics might be 219.8 and 439.9 Hz, but the actual harmonics are such that when you put the second harmonic at 439.9 Hz, the first harmonic is at 219.6 Hz, so it shows up as being flat on the display. (The second ring would be stationary while the first ring would be turning left.) That’s why I tell you to tune it so the middle rings are more stationary while the outer rings are going in opposite directions…you’re still getting the note generally in the right place, even though the targets are spread out wrong.
  
  The other things you can do to fix this problem are:
  1. Measure the inharmonicity of every note, and check the graph to make sure you have decent measurements for every note before you lock the tuning
  2. Increase the “inharmonicity weight factor” in the settings per https://pianometer.com/support/#Inharmonicity_weight_factor
Ann Green
· Reply

February 27, 2022 at 9:44 PM

Hello,
I recently found this app and wondered if it incorporates any extra pull to counteract the inevitable pitch drop that tends to happens overall after a tuning, so that then the final result would be pretty on-pitch?

Thank you.
- Anthony Willey
  · Reply
  
  Author
  
  October 6, 2022 at 11:35 PM
  
  Yes, there is an overpull function in the “pitch raise” mode, however you can only access that in the full Professional version.
Bruce sato
· Reply

November 15, 2022 at 4:36 AM

Hello! I’m a piano tech using the Verituner with success since many years but I’ve always disliked the interface. I hesitate to buy the pro version of Pianometer. What would be the reasons to go with your software (apart the price) ? Thanks and congrats for your work! 🙂
- Anthony Willey
  · Reply
  
  Author
  
  February 19, 2024 at 7:30 AM
  
  Whoops, just saw this. If you dislike the interface of Verituner, this app might not be a great fit either. There are probably more similarities than differences with how you approach a new piano. Like both let you jump in and start tuning right away with minimal time spent pre-measuring, and both have something spinning for phase and a numerical readout. PianoMeter’s strobe readout is more chaotic since it’s showing live results from multiple partials. Maybe one of the biggest differences is how the pitch raises work. Last I remember from Verituner (it’s been several years, so I may be woefully out of date) it does an instantaneous pitch raise calculation note by note, as soon as you play a new note, with percentages you set for different parts of the piano. PianoMeter has you pre-measure sample notes before you start tuning, and calculates its own best estimation of the overpull. If you see this (doubtful) and have more questions, feel free to shoot me an email.
Flo
· Reply

February 11, 2023 at 8:27 AM

Hi, can’t restore purchase ?
Your contact page sends me this again and again :
There was an error trying to send your message. Please try again later.

You could at least share your email address ?
I paid and my piano is half tuned thx.
- Anthony Willey
  · Reply
  
  Author
  
  February 11, 2023 at 3:43 PM
  
  My email is willeypiano@gmail.com
  
  To restore the purchase you need to go to the “upgrade” page, scroll down, and click the text that says “Restore purchases” while the device is connected to the internet. I’m sorry you got stuck in that situation.
Michel Lachance
· Reply

March 21, 2023 at 8:12 PM

Hi, I have a question regarding the pitch raising function. Is the overpull amount calculated exclusively for each note or does it take into account the overall drop curve of the piano? I will try to be more specific. I occasionnely encounter the legacy of an old local tuner who used to tune pianos much too sharp in the bass and much too flat in the treble. With one of the softwares I use, it will start in bass section considering that the WHOLE piano is too sharp, which is counteracting against the general overpull it will need for the rest of the piano. To ask the question differently, in the case where the piano is too flat, where the bass section would be too sharp, is the amount of overpull of a given treble note would be exactly the same as if the whole piano would be too flat, or will it adjust with the bass section going in the opposite direction, hence taking account a different transfer of tension. I hope the question is not too confusing…
- Anthony Willey
  · Reply
  
  Author
  
  March 22, 2023 at 12:10 AM
  
  It would overshoot the bass and treble in opposite directions. The bass would overshoot in the flat direction because it started out too sharp, and the treble would overshoot sharp because it was too flat. But it’s not doing a whole piano calculation. It’s going off of local samples. So for example E4 might overshoot sharp because measured samples C4 and G4 were flat.
Volodymyr
· Reply

August 23, 2023 at 3:57 PM

Good afternoon Anthony! I am using the android version. Got used to making good settings. Wrote a small user manual for myself. It turns out very well if you use the notes A-F#-D#-C in seven octaves to listen. After that, I put it on the ‘lock’.
I have a question: are you planning an update? Thanks for your application!
Sincerely, Volodymyr.

PianoMeter Android Change log

PianoMeter Android Change log

List of changes in each release

About Anthony Willey

37 Comments

Leave your reply.

Leave a Reply

Your email is safe with us.

PianoMeter Android Change log

PianoMeter Android Change log

List of changes in each release

About Anthony Willey

You also might be interested in

PianoMeter iOS Change Log

37 Comments

Leave your reply.

Leave a Reply

Your email is safe with us.