Piano World Home Page Forums Our Most Popular Forums Piano Tuner-Technicians Forum PiaTune Beta Testing

I have uploaded PiaTune Version 4.9 Beta Build 19.

If you are already testing Build 18, you can update to Build 19 through TestFlight App.

If you are interested in testing this new beta please let me know and I will share the TestFlight link with you through PM.

In this version:

User created temperaments can be edited/deleted. Editing built-in temperaments is disabled.

have uploaded PiaTune Version 4.9 Beta Build 20.

If you are already testing you can update to Build 20 through TestFlight App.

If you are interested in testing this new beta please let me know and I will share the TestFlight link with you through PM.

In this version:

Bug fixed that would cause the arcs not to be displayed although inharmonicity measurement is completed, if +/-1 Cent Indicator is active.

Ron, thank you for the screenshot feedback through TestFlight.

Could you please update to Build 20 and try again.

Ron, also could you please restart and open the file again and see if the remaining notes is not over.(applies to free version)

I closed the program and restarted (didn't swipe it away to fully close) and it worked fine. No further problems when I tried the same sequence. It froze right when I double-tapped to get to the A0-C7 note switch because I had been manual note switching for the lowest couple of bass notes and wanted to jump up to the treble.

Tried tuning a very difficult Yamaha GA1 scale and PiaTune seemed to handle going down to the bass break better than most apps.

Ron Koval

Ron, thank you for the update.

Great to hear PiaTune worked well for the GA1.

Meanwhile I realized that I have forgotten to break the relationship between the temperament and the tuning file, after adding the capability to delete user created temperaments.

Therefore, currently if you delete a temperament you created recently and try to open a file that you tuned with the deleted temperament, or delete the active temperament and return back to main screen, the beta will crash.

I am working on a new build which will always load files with equal temperament and would not let the current temperament to be deleted.

Ok, I have fixed the temperament issue and uploaded Build 21.

With this update:

Current temperament cannot be deleted.

But for now, files with user created temperaments are loaded with Equal temperament by default in order not to crash in case the temperament was deleted beforehand.

Files with built-in temperaments load with the temperament set when the file was closed.

If you are interested in testing this new beta please let me know and I will share the TestFlight link with you through PM.

Current testers can update to new build through TestFlight app.

I'm still getting a lot of random iH measurements in the upper octave. I'm only sounding a single string at a time. I am able to remeasure and get more linear results.

I am doing a full measuring pass from A4 down to A0, then A#4 up to C7

Any suggestions on what to try to get it right on the first time through without remeasuring?

Ron Koval

Ron thank you for the update.

Have you tried manual note change for the upper octave?

I think it results in somewhat more consistent measurements.
I know it is slow but that could be a temporary solution.

I am working on this.
.

I didn't do that today. I will give it a try next time - thanks!

Ron

Ron,

I have uploaded Build 22.

This build measures inharmonicity after the initial attack tone.

Please let me know if it helps with upper notes.

Yes, that seemed to help during the measuring today. I only needed to revisit a few notes that looked out of place on the graph.

I got to thinking about the overpull and wondered if you could use a "zone approach"? It is always a trade-off between time and benefit that we consider while everyday tuning...

For those of us that plan on pre-measuring the whole piano before tuning, what if the app would get a current pitch for something like all of the Fs and Es? (That would exclude those pesky to measure low notes) Average out the readings and apply an overpull cents for each area of the piano instead of measuring and applying a specific overpull to each note??

It seems like it might offer a real benefit with minimal time required.

Ron Koval

Ron, thank you for the feedback and suggestion on over pull.

Glad that build 22 worked better on measuring the upper notes.
Were you on auto note change?
I am still working on it to make it better.

As for the over pull suggestion I will look into it. I might not be able to introduce it in the next build of the beta though.
Do you mean all F's or E's or is it and, so regions are F to E?

As I considered overpull, I thought having a few notes in each octave would provide adequate information for general overpull for each section without adding much time from the iH measuring - while still getting enough info to be able to delete outliers or at least average them into the mix.

Those of us working in areas with great seasonal differences would be the one to use this function most often, so it might be good to have it as a settings option to measure iH and overpull data or just measure iH data for those that might not need this as often.

As a general rule, I like to engage an overpull even if the piano is just within 5-10 cents to make the second pass easier and more stable.

For the iH measuring, I was in manual step mode for the bottom and top octave of measuring, though it seems to work well even in auto mode if I gave the app the slightest amount of silence before playing the next note.

The high treble spinner/needle response can still be challenging. I found setting the scale to +-100 helpful.

Ron Koval

Ron, thank you for the update.

You might also consider setting the response to slow for indicator on high treble, or turning Smooth Spinner on for spinner display.

I will try to put over pull measurement as another option when creating a new file. Maybe it might measure the over pull for certain notes skipping others as IH measurements continue in semitones.

BTW, could you please check your PM.

Ron, you might also try setting +/- 1 Cent Indicator to ON, which will show the indicator only if the note is within one cent.

I have uploaded PiaTune Version 4.9 Beta Build 23.

If you are already testing you can update through TestFlight App.

If you are interested in testing this new beta please let me know and I will share the TestFlight link with you through PM.

In this version:

Improved inharmonicity measurements

More overpull time today.

It would be nice to have setting for where the % overpull jumps between tenor and treble amounts. I normally set this around 5 notes above the treble strut. On the Acrosonic spinet today, the jump happened about 4 or 5 notes below the strut. I adjusted on the fly, but that took a few steps to get into the menu and then back when I got above the strut.

The taper % at the top seemed to engage too soon for me. I just like that the last octave or even from about F7 up.

Ron Koval

Ron, thank you for the suggestions on over pull.

I will try to put additional settings to select the tenor/treble break and where the taper begins.

Were you using Build 23? If so, how was your experience with measuring the inharmonicity of upper notes?

No, I didn't get build 23 until after I tuned today. Looking forward to giving it a try.

Ron Koval