Beta test of pianoscope v2.0

Frank Illenberger

AlexHutor Thank you Alex for pointing this out. TestFlight somehow had mixed up the builds. I re-uploaded it and now it should work if you download the latest build again.

AlexHutor

Thanks Frank, it's working now. Pianoscope is getting better with every update, although it seems that there is nowhere better

Frank Illenberger

In in build 901 I have also added a tone generation feature which can be used for chipping newly strung pianos or to train auditory matching. I have updated the release notes above.

MilanDka

Hey, Frank,
if I change the tuning style and save, the app crashes.
edit:
the details are in the app report. I traced that this happens if I use a custom debug style.
edit 2:
in this version of the app I can't find switching of algorithm versions (V1, V2) Isn't it lost?
edit 3:
I found this

Frank Illenberger

MilanDka Thanks for reporting this. It should be fixed in the most recent build 908. I could not reproduce a missing v1/v2 switch. Can you check when this happens for you?

MilanDka

Frank Illenberger I already wrote in edit3. I found the switch

Rick

Where is the new version? Beta has stopped working along with the new features.

Frank Illenberger

Rick I am sorry for the inconvenience. I have just provided a new beta build (910).

It contains new options in the more menu of the concert pitch settings panel to reset the concert pitch to the default or 440 Hz.

I am still working on the new tuning curve algorithm v2 and I hope I will be able to issue another update with refinements there in the next days.

Frank Illenberger

In build 911, I have just fixed a regression by which a concert pitch setup when creating a new document was reset back to 440Hz.

Frank Illenberger

In build 921, I further improved the tuning curves in the bass. Thanks to Milan for providing me with reference recordings of his aural master tunings. To get the calculation updated in existing tuning files from previous beta builds, you need to switch to a different tuning style and back once.

MilanDka

Frank Illenberger
Hey, Frank, I'm not that good. 😆 Just because I tuned maybe 30,000 instruments doesn't mean anything. 🤣 Like I said. I'll try the V2 curves in the next few days. I'm looking forward to them.

Frank Illenberger
I've had it too. But I don't remember if I sent you a report. I hope you did.

Frank Illenberger

I received some reports about crashes which occurred when the tuning style panel was opened in an existing document. If someone has a document which reliably produces this crash, I would be happy to get a copy of it.

Frank Illenberger

In build 923, I fixed a crash which occurred in the new tone generator when inharmonicity was not yet measured.

Rick

I did report this but was some time ago. Will send if it happens again.

MilanDka

Hey, Frank,
Can you add a warning that the tuning file has not yet been converted to the new V2 tuning curve type and how to do it? I.e. switch to a different tuning style and back?
Any technician who has more than say 10 files will not know what is already tuned with the new V2 and what with the old V1, plus when you open the tuning curve you only see the V2 info, but you don't know if it counts by V2 or not.

Thank you.
Milan

Frank Illenberger

MilanDka Good idea. I will think about a solution.

MilanDka

Good evening.
Today I tried the new V2 bass tuning calculation. On the Hoffmann T186 and Hoffmann P206 the tuning was fantastic. I couldn't even believe what I was hearing.
I had a little reservation on the T161 - it was a little sharper than I would have expected, but nothing I had a problem with. Compared to the V1, it was great.
Next, I tuned a Raehs piano (about 131) that still had steel strings in the bass. The piano is 130 years old. Serial number 953. The two chords were fine, but the single chords were very sharp. I was putting them very down on the ear. I sent you the recording from Pianoscope. It's true that this piano had extremely ugly inharmonics. And I recorded the bass about five times. I guess you can't take this as a reference piano for adjusting the tuning curve in V2, but rather I sent it to you as a point of interest. The A0 tone after tuning by ear Pianoscope wasn't even able to register in the recording as it must have been low.

Rick

Some piano tuning apps suggest different styles depending on the size of the piano. I take it that the balanced style v2 should work for all pianos. Or am I missing something?

Frank Illenberger

Rick All styles in pianoscope are meant to automatically adjust themselves to an individual instrument. That is the whole point of pianoscope's tuning curve algorithm. The styles in other apps like TuneLab, Verituner or PiaTune use a fixed mix of beat rates for different ranges. But a style defined in such a way will only lead to satisfying results for instruments of not too different sizes (meaning not too different bass inharmonicity). The tuning curve algorithm in pianoscope does two things: It measures how strong the most important tuning intervals are for a given instrument and adjusts the weighting accordingly. And it analyzes whether a tuning interval - like for example 10:5 octaves or 9:3 twelfths - can ever achieve a low beat rate for a given instrument. And if not, it automatically strongly reduces their weights and instead prefers the other tuning intervals tries to lower their beat rates.
So the whole concept is that you only have to decide what the tuning should sound like: Do you for prefer pure twelfths or should the octaves be closer to pure? Then you pick the style accordingly and the rest should happen automatically.
The v1 tuning curve algorithm was not perfect in this regard. The V2 algorithm should perform much better, especially in the bass. I am looking forward to your feedback.

Rick

Many thanks for the comprehensive reply. I was hoping that is what you were going to say!