• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[3.9.37] Transposition involves unnecessary octave jumps and changes in clef
#1
When transposing ABC files (without ChorPro integration), unnecessary clef changes and octave jumps occur.
   
Using the same file in ABCarus or Michael Eskin’s online tool, it works as expected.
   
---------------------------------------------------------
13" - Point of View POV_TAB-P1325, Android 4.1.1
Microsoft Surface Pro 4; Windows 10
Microsoft Surface Pro 8; Windows 11
Reply
#2
see  https://www.zubersoft.com/mobilesheets/f...15027.html
It`s the same issue, no matter if it's plain ABC or embedded into ChordPro.
It' s already fixed for the next version.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#3
Ok
I hope the update will come sonn as it is a critical issue for my use.
---------------------------------------------------------
13" - Point of View POV_TAB-P1325, Android 4.1.1
Microsoft Surface Pro 4; Windows 10
Microsoft Surface Pro 8; Windows 11
Reply
#4
Yes, same here on ipad. It worked great before the update. Now, if I have a song in C and press the right arrow once, it shows C# but the music does nothing. Pressing it again to Db, there's a +1 under where it says "starting key" and the entire music jumps to Db but an octave higher. Pressing several more times and a notice appears that the file can't be opened. 

It's completely unusable as is.

(The file I checked worked properly going down.)
Reply
#5
@RoSong: I could not reproduce "I have a song in C and press the right arrow once, it shows C# but the music does nothin
When I do the same, clicking the right arrow once shows Offset +1 and 6 sharps, once again it still shows Offset +1 but 5 flats. Both is correct.
But the notes in the ABC section are one octave too high.
Some songs transpose correctly, sometimes "one octave too much" happens when transposing down, in some cases there are unwanted octave jumps and / or the clef changes to bass clef.

I agree that there are cases where transposing creates unusable results so that releasing an official version that fixes this bug is pretty important.
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#6
I can help users update on Android immediately if needed, but otherwise I'll try to get a small update out tomorrow to address this and put all the other work on hold.

Mike
Reply
#7
The "small update" would be great, as I am using windows.
Thank you Mike!
---------------------------------------------------------
13" - Point of View POV_TAB-P1325, Android 4.1.1
Microsoft Surface Pro 4; Windows 10
Microsoft Surface Pro 8; Windows 11
Reply
#8
The problem is solved with [3.9.38]!
Thank you very much!
---------------------------------------------------------
13" - Point of View POV_TAB-P1325, Android 4.1.1
Microsoft Surface Pro 4; Windows 10
Microsoft Surface Pro 8; Windows 11
Reply
#9
I'm glad to hear that! Thanks for following up.

Mike
Reply
#10
A quick note:
1. Since I often play with singers, I frequently use a song in its transposed form. The app saves this transposition setting—which is great.

However, with the latest update, all songs saved with transposition now display an error message: “Error opening and reading the text file.”
To fix this, I have to “reset” the transposition setting for these songs.
Is it possible to do this centrally for all ABC songs maybe via a database query?
(I curently have 119 ABC-songs in my database)

2. Sometimes the “A” icon at ABC-files is orange, and sometimes it's white. What does that mean?
       
---------------------------------------------------------
13" - Point of View POV_TAB-P1325, Android 4.1.1
Microsoft Surface Pro 4; Windows 10
Microsoft Surface Pro 8; Windows 11
Reply
#11
I went through around 20 transposed songs and never had that error message. I tested on 3.38 eink, Android and Win11, all songs are in ChordPro format with embedded ABC sections (my preferred format).

But i can reproduce the reported bug with ABC files on Win11 (it works as expected in 3.38 eink).
It doesn't matter if the songs are transposed or not.
It doesn't matter if the songs have been already imported with my previous MobileSheets installation or if I import them again.
When I open the transpose dialog, the starting key is correct, but the offset is wrong.
As reported: pressing "Reset" in the transpose window displays the song correctly.
   
first language: German
Acer A1-830, Android 4.4.2 - HP x2 210 G2 Detachable, Win 10 22H2 - Huawei Media Pad T5, Android 8.0 - Boox Tab Ultra C, Android 11
www.moonlightcrisis.de - www.basdjo.de - www.frankenbaend.de


Reply
#12
Thanks I'll look into it.

Mike
Reply




Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2026 MyBB Group.