[Vibraphon]

The %%leftmargin function is normally used to create indentations in the notation. However, this doesn't work in MuseScore.
I suspect this has to do with the automatic page resizing in MobileSheets.

Are there any alternative options?
   

[Bill O]

Sort of. You can use %%staffbreak <number> f. The f is if the break occurs at the beginning of the line. 
The problem that I have with that, is that <number> changes with your device or orientation. For example, with 4 measures per line, indenting to the position of the fourth measure requires <number> ranging from about 420 to 860, and the position changes if you switch from portrait to landscape. 
This is quite different from e.g.,ABCarus

[Vibraphon]

Thank you very much!
The result isn't quite what I had in mind, but I can work with it.
   

[Bill O]

Not my favorite either, but I've started to switch to using it on my Alms for Oblivion site. 
I think that using %%leftmargin
  rjc1.pdf (Size: 59.83 KB / Downloads: 1) is a bit cleaner than using %%stavebreak
  rjc2.pdf (Size: 60.08 KB / Downloads: 1)  but being able to maintain compatibility with MobileSheets just by changing the number is well worth it.

[Zubersoft]

This is because MobileSheets has settings for ABC files, and this allows users to set the page margins on that dialog. I don't currently have an option to only control the margins through the statements in the ABC file. That's something I'll probably add at some point for users that prefer to control things like margins in the ABC file itself.

Mike

[Bill O]

That's something I'd like - BUT - with the %%staffbreak workaround it's a fairly low priority. 

I'd much rather see a way for MS to display elements consistently across orientations and devices.  

As it stands, it is necessary to change the size of the staff break (and other elements that specify horizontal position) for each tune on each device. 

I wonder if there is a way to map, for example, 14cm or 460 (points) to 75% of the distance between the margins.  It seems that something like that must be happening on Jef's site and in ABCarus since neither of those (formerly) physical measurements are actual distance on the display.

Thanks again for all that you do, and good luck with the upcoming release

[Zubersoft]

Did you make sure to set the page size for the song? That is necessary to have the exact same rendering across devices.

Mike

[Bill O]

I had not tried that. I couldn't find an explanation in the manual and I wasn't clear on the scope or effect across devices (and I had not realized that you could just enter the number rather than using the +/- or sliders)
Since you suggested that it might be a solution, I did try it on one tune.  Unfortunately MS crashed after I replied to "Apply to..." and thereafter crashed every time I tried to open that tune. 
Oh well.

(crashes seem to be becoming more frequent.  wondering about memory leaks or some sort of odd interaction with the OS)

[Vibraphon]

After taking a long detour, I finally reached the conclusion that the ABC result is identical on all computers:

• ABC-Setting: Reset to Deflauts and Apply to All files in Library
  
• Set Page Size: Width =750 and Height =1074, Set as Default and Reset To Defaults
  
• Don't use any %%scale - option in ABC
  

Now my songs fit on all computers of my Colleagues including desktop, Surface Pro 3 to 8, Boox max Lumi 2.

HTH

[Bill O]

Looks interesting.  Thanks for the info.  I did manage to get that to, I think, work for one tune and it seems promising.  Then I tried it on another (after I removed the %%scale and %%voicescale)  by trying  :"reset to default".  It showed the 750 x 1074 in the dialog box, bur when I OK'd it , MS crashed and now will not open that tune at all.
Longer term, it's a bit difficult as it would involve editing about 900 tunes to remove scaling directives from each. Still, it's a start. Thanks again

[Vibraphon]

900 tunes! Puh...
But I had used the same header in all my tunes.
Then I could select "*.abc" all files with the win explorer, mark all (strg-A), open them with notepad++.
Then I was able to edit all abc-files at once.

May be you can do the same.

[Bill O]

I think I'm missing something here - and you might be a lifesaver  I was under the impression that it was not possible to get to the abc files created by MS.  If I could do that then it's a piece of cake to point a regex at 'em.  Any idea where they are on a Mac/iPad?

[Zubersoft]

On a Mac, long press/right-click a song to select it on the library screen, tap "Edit Song", go to the Files tab and long-press/right-click a file in the list. It should show a full path to the file. That is where all of the MobileSheets files are stored.

On an iPad, all of the files are stored under the MobileSheets folder, which you can find by going to "On My iPad" in the Files app.

As far as the crashes, I'll address those as quickly as I can early next week. I have one fix in place already, but I need to verify there are no other scenarios where the app can crash with ABC files.

Mike

[RoSong]

Hi, I changed the font directives on all 400-ish of my abc files at one time in windows.

(I bought MS through Mike's fastspring store for my windows laptop specifically so I could choose my directory and access the files outside of MobileSheets - as I understand it, the Microsoft store version doesn't allow that.)

So on windows, I opened Visual Studio Code, and although I don't know much about coding or VS Code, by googling lots of "how-to...?" I successfully changed ALL necessary fonts that I needed to change in the directives on ALL files at the same time. VS Code can do find/replace on multiple files at the same time.

I only use the laptop for stuff like this. After the files were changed, then I synced the windows version back to the ipad and android. It worked great.

I have used Notepad++ in the past for other find/replace situations using regex, but this was so much easier.

[Bill O]

Wonderful! Now there's a workaround that makes life easier.  Thanks to you both.

Good luck with the update.