[itsme]

From https://www.zubersoft.com/mobilesheets/f...12295.html I learned that annotation positions will be lost anyway so I tried just lyrics.
On my HP Detachable ( screen size  800 x 1280 ) I set "fixed page" then I copied the MobileSheets database to my Boox Tab Ultra C ( screen size 1860 x 2480 ).
For the fixed page size I tried 800 x 1208 (that's what "Set to Screen" proposes on the HP Detachable) and 1860 x 2354 (that's what "Set to Screen" proposes on the Boox). 
All tests are so far from anything useful that I doubt if that scenario is intended to be working. Am I mislead somehow? Is it worth the effort to post some screenshots?

[Zubersoft]

If you set the fixed page size to the same size on each device (I'm assuming you meant 1280 and not 1208 on the second device), then the layout of the lyrics should match. They will just be scaled up or down as needed. If you are having a problem with this, yes, I'm going to need to see screenshots. You need to make sure you are using the same display mode and page scaling mode and such as to avoid any confusion with that. I just verified with multiple different chord pro files that the layout was identical on my PC compared to my Android tablet with the same page size assigned (with version 3.9.7).

Mike

[itsme]

YESS - that's it.
After copying the database the page dimensions are -1 / -1 again. 
I think we had the question before, if the page dimensions are stored in the database or not? And the answer was yes, they should be in the database?
Correcting width and height to the original values fixes the displayed lyrics size so that it's the same on both devices. I used "apply to current file" because I'm still experimenting with different settings.

So it seems that page dimensions, at least when applied to current file only, are lost somehow when I copy the database.

It's intentionally 800 x 1208 (not 1280) and 1860 x 2354 (not 2480). That's what "Set to Screen" proposes. It seems that the taskbar or navigation bar is subtracted. I also checked the "Show Next Song Indicator" and "Always Show The Title Bar", they don't have any influence.

I also tried setting page size 1860 x 2354 (the screen size of the Boox) on the HP Detachable.
The behaviour is the same. After copying the database, it's -1 / -1, correcting that makes the song look the same.
Trying that I noticed something else:
As soon as I set fixed page size to 1860 x 2354 the font becomes very small (probably as expected, previous font size 35 is kept unchanged). Auto-size font just increases it to 59. That's limited by "Maximum Auto Font Size" = 60. Setting font size manually to 84 increases the lyrics to the desired size.
So I tried setting "Maximum Auto Font Size" = 200. This setting is taken over (it is still displayed after a restart of MobileSheets) but it has no effect: Auto-size font still sets fonts to 59.
           

I'm not sure how to proceed with preparing the move from the HP Detachable, my current 'active' device that I use on stage to the Boox, that should take over in future.
My gut feeling says that I should better set fixed page size to 1860 x 2354 on the HP and adapt the font sizes, then copy the whole database to the Boox. I guess that would make the best use of the much higher screen resolution of the Boox, but I did not investigate that in detail.
If so, we should find out how to solve the issue that the page dimensions are lost. And we should enable auto-size font to increase the font as necessary, so probaly "Maximum Auto Font Size" needs a fix.

[itsme]

"Maximum Auto Font Size" is also an issue when I work only on the Boox.
When I let "Set to Screen" set the page dimensions, it sets 1860 x 2354 and that requires a font size like 84 to use the whole screen. No difference to setting 1860 x 2354 on the HP. That's what we learned so far. But auto-size font is currently limited to 59, which is not enough.
It's a bit strange, that on the Boox fixed page 1860 x 2354 and font size 84 shows about the same lyrics size as fixed page -1 / -1 and font size 28. But maybe that's how it is and we have to get used to it.

[Zubersoft]

I'll try to investigate the maximum auto font size issue you mentioned. MobileSheets is going to use the fixed page dimensions without scaling to figure out how large the font can be to reach the edges of the page. However, that page may then be scaled up or down to fit the screen. If the font is not reaching the edge of the screen, it's obviously not working as intended and needs to be fixed.

I don't know why copying the database over didn't correctly set the fixed page size across devices. The database should be set up in an identical matter across platforms. I'll try to look into it to see if I can reproduce that.

Mike

[itsme]

some possible reasons for losing page dimensions that came into my mind
1. copying mobilesheets.db vs. copying another database
not checked yet
I always use a separate test.db to avoid affecting my active database that I use on stage
2. overwriting an existing database vs. creating a new one
seems to be no difference
3. copying between the same OS vs. copying between different OSs
3.a When I copy the database from my Win10 HP detachable to my Android smartphone or my Boox tab (_bx) Page Dimensions are reset to default -1 / -1 which causes the issue that I reported before
   
3.b When I copy the database from my Win10 HP detachable (_D2) to my Win10 laptop (_L), Page Dimensions are taken over, nevertheless the layout changes
       
please ignore the annotations, relevant is the additional linebreak on the destination device that causes the song to have 2 pages, as marked in red on the _L screenshot
screenshot Gedanken_quer_2_L.jpg above was taken in full screen mode when "Set to Screen" in landscape orientation sets 1366 x 768 ( which is the native screensize of the laptop)
       
screenshots Gedanken_quer_2a_L.jpg and Gedanken_quer_2b_L.jpg were taken with the windows taskbar visible at the left side and the MobileSheets title bar visible, "Set to Screen" in landscape orientation sets 1285 x 736

[Zubersoft]

It's possible there is some other logic in play that's causing an issue - mainly the fact that MobileSheets detects the file as having changed (as the last modified timestamp will be different), so it scans for changes. This might be resulting some settings being changed or cleared. I'll have to investigate further.

Mike

[itsme]

The files are identical, stored in GoogleDrive and synchronized to local files, on Win10 by the Google Drive program and on the Android devices by FolderSync Pro. I'm not fully aware if something happens with the timestamps during synchronisation, in Windows Explorer and in TotalCommander (both Win10 and Android) they seem identical.

Would it help if I gave you the databases?

[Zubersoft]

Let me try to recreate the problem and I'll get back to you. 

Mike

[itsme]

OK, thank you

[Zubersoft]

I see the issue, and I believe it's due to the last modified timestamp being different so the file is scanned for changes. The fixed page size is being lost as part of that, so I'll work on getting that fixed.

Thanks,
Mike

[Zubersoft]

I have found the incorrect code and fixed it. The code was clearing the fixed width and height in the case that a text/ChordPro/abc file was converted to a different file type or replaced with a different file type that doesn't support a fixed width/height. The same logic was being applied if the file wasn't converted though, so I just had to add a check for that.

Thanks,
Mike

[itsme]

Great. Thank you.

[Zubersoft]

So about the auto-size font - the logic is correct, but there was an artifical limit of 59 for the calculated font size (without the fixed page size feature, I never anticipated anyone needing a font size greater than that due to how the fonts would scale with the screen density). I have now increased this to 100 to match the maximum value that is selectable on the text display settings. I will likely increase this after I redesign the settings dialog.

One thing I want to help explain - without the page size being explicitly set, the font sizes are dynamically scaled based on the density of the screen. Most Android devices use scaling factors between 2 and 3, meaning any lyric/chord text size you pick on the text display settings dialog is actually being multipled by a value between 2 and 3. Once a fixed page size is selected, I cannot scale the font like that, as it would cause completely different results on devices with different screen densities. So I scale the font size based on the difference between the resolution of the screen and the page size resolution. This effectively resizes the resulting image so that it fits the screen. So if you had a page size of 1200x1600 (width by height), and the page size is set to 600x800, then the font will be scaled by a factor of two to ensure that the image is "stretched" to fit the screen, however this provides a much sharper result than me rendering a 600x800 image and just stretching it to 1200x1600, as then the font would be blurry. The reason I'm explaining this is because you mentioned having to significantly increase the font size in the text display settings to get the desired output. That means you basically figured out the display scaling factor of your screen, which is higher due to the high resolution of the screen or the settings you have selected (as the BOOX devices let you choose the DPI for the application in the optimization settings). 

I know that may all be a little confusing, but it's implemented correctly to ensure that the resulting image looks the same across devices of different screen resolutions. If you select 800x1200 as the page size, for example, and you render that file on a 1860 x 2354 screen, it's going to nearly double the size of the image in order to make it fit the screen (which is actually nearly doubling the font size that is used), but the resulting image should appear effectively the same. Conversely, if you specify 1860x2354 as the page size and you put that on a 800x1200 device, it's going to have to shrink things down by a factor close to 2, so it will be harder to read as the font will look smaller. So I might advise using a smaller page size if it's important for things to be more legible on the smaller device, but that just means the font will be larger on the higher resolution device, which may not utilize the available page size effectively. There is no way around having to make this compromise if you have devices with significantly different resolutions.

Mike

[itsme]

Thanks for your explanation. I will test again as soon as a fixed MobileSheets is available.

"I never anticipated anyone needing a font size greater than ..."
btw. it was a request from me long long ago that triggered you to increase the maximum to the current value.
I use ChordPro files as separators because they are really easy to modify without leaving MobileSheets. For a "song" containing just "Set 1" a really big font absolutely makes sense.