Android 1.6.0 Conversion issues

[AurisStd]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After converting from 1.3.0 to 1.6.0 on android studio, the score was seemingly corrupted, and has started to output Korean text in various different sizes. Sometimes the size of measures change, etc. Restarting the application results in different outputs, but reloading the code without restarting(ie., going to a different fragment, then making the AlphaSynth worker produce the output) does not change the output.

Expected Behavior

This is the code that is being entered into the compiler:

\instrument 0
.
\track
\staff {score} \tuning piano \instrument acousticgrandpiano \clef Treble \ks C
:4
C4 D4 E4 F4 |
G4 A4 B4 C5 |
C5 B4 A4 G4 |
F4 E4 D4 C4
\staff {score} \tuning piano \instrument acousticgrandpiano \clef Bass \ks C
C3 D3 E3 F3 |
G3 A3 B3 C4 |
C4 B3 A3 G3 |
F3 E3 D3 C3

This had previously worked on 1.3.0, and works on the playground on the website, as well.

Steps To Reproduce

Something along the lines of this (in Java)

public View onCreateView(...) {
  AlphaTabView alphaTab;
  alphaTab = view.findViewById(R.id.alphaTab);
  StringBuilder alphaTexCode = ...//shown in expected behavior
  alphaTab.post(() -> alphaTab.getApi().alphaTexCode.toString(), null));
}

This seemed to have worked perfectly fine with no issues in 1.3.0, but 1.6.0 is now causing issues

Link to jsFiddle, CodePen, Project

No response

Version and Environment

[AlphaTab][VersionInfo] alphaTab 1.6.0

Platform

Android (Native)

Anything else?

A photo of the score

[AurisStd]

To note: 1.5.0 has this issue as well, but some of the data does not seem to be corrupted. In this version, the first line of the score is always normal, while the rest of the score, along with tempo markings, seems to be corrupted.
1.4.4 and any prior updates seem to work fine.

[Danielku15]

Sorry for the late reply, I was on holidays and I've overseen this one.

It almost seems that the music font (Bravura) is not available and it falls back to some default system font. Can you increase the log level via the settings and check if there is anything suspicious in the logcat?

The Bravura.otf is embedded in the .aar. Are you using the default render engine (alphaSkia) or do you use the standard Android renderer (configurable via core.engine).

A fully reproducible example project would help investigating this and provide further details on your environment (e.g android version, device used etc.).

The main change in 1.5 related to this problem: We use now OTF instead of TTFs. Maybe the built-in font manager has problems loading the OTFs.

Switching to FreeType could help (via alphaTab.alphaSkia.AlphaSkiaCanvas.switchToFreeTypeFonts()) as a temporary workaround until we narrowed down this problem.

[AurisStd]

When I first tried to use version 1.4.4, my application crashed when opening the score, and logcat stated that the bug was due to Bravura.ttf not being found. I installed that GitHub repo and added it to my assets folder, and everything worked perfectly after that. However, renaming the asset to Bravura.otf and running 1.6.0 does not seem to affect anything.

The android device used is a Samsung SM-T738U Android 14. I would assume that I'm using skia, but I am unsure of how to check this.

[Danielku15]

I could reproduce the problem. I added CoderLine/alphaSkia#66 on the rendering backend repository to address this problem.

Likely "just" a problem with non-terminated strings on the Android platform. Will publish a 1.6.1 as soon I have a fix available.