Just testing the latest Companion against 3.9.7 on Android (Galaxy Tab S7+) and Companion on Linux. Everything connects flawlessly, and the 2.2 GB backup comes across fast and with no "stuttering" but always fails with 1 to 4 KB remaining. Wireless are a pair of Netgear WAX220 access points (version 1.0.3.5) on a flat network to the Companion system (Gigabet network) with no routers in play. These AP's are AX4200, 2 and 5 Gig, and signal strength on the tab is full, and connect speed is typically 200 to 400 Mbps (The companion system is wired). If I run the backup on the Tab and FTP it to the same server, it's clean 100% of the time and when sent to my other tab with FTP, restoresvflawlessly.Testing/monitoring on the network reveals no retries, errors, or drops, and nothing else has any issues, so feeling good about the network.
Let me know what else I can provide you with this that may help.
Bonjour,
Nouvelle utilisatrice de MobileSheets, j'ai du mal à comprendre comment annoter simplement des partitions àl'aide d'un stylet et comment les corriger au besoin.
Comment paramétrer les outils ?
Où trouver un mode d'emploi ?
Merci pour votre aide !
As soon as chord grids and lyrics are involved, Auto-Size Fonts produces strange results, depending on the device.
AintMisbehavin_bx.jpg
Lyric 12
Chord 12
Grid 12
Boox Tab Ultra C "bx", my future main device
1860 x 2480 4:3 10,3"
AintMisbehavin_D2.jpg
Lyric 31
Chord 31
Grid 13
HP x2 210 G2 Detachable "D2", my current main device
800 x 1280 / 16:10 / 10"
AintMisbehavin_T2.jpg
Lyric 10
Chord 10
Grid 10
Huawei MediaPad T5 "T2", my backup device
1200 x 1920 16:10 10,1"
Currently Auto-Size Font for normal ChordPro files (containing lyrics & chords) calculates a font size so that the longest line fits on the width of the page.
The calculated size is applied to Meta Size , Lyric Size , Chord Size , Tab Size and Chorus Size. Title Size is a bit bigger.
Expected behaviour:
Font size for grids should be independent from the size above.
The calculated Grid Size value should produce a grid that uses the full width of the page so that grid sections and lyrics & chord sections have more or less the same width.
The Grid Size that is calculated in V 3.9.7 is slightly too small.
Additional feature request:
Subtitles should have their own independent font size (instead of being part of "Meta" as it is today).
It would be great if a fix could be part of one of the next MobileSheets versions. I'm working currently on a series of about 200 ChordPro files like the example shown in this post. I'd really appreciate if a batch import of these files (where Auto-Size Font is applied to all of them) would produce nice looking songs. Otherwise I had to fiddle around with each and every song to fix the font sizes.
Thanks in advance.
On my Boox Tab trying to import the attached ChordPro file via Import - Local File fails in case the tablet is in portrait orientation.
The tablet hangs as if the import took very very long. When I forcefully stop it "MobileSheets isn't responding" is reported, the song is not imported.
If the tablet is in landscape orientation the import works fine.
Other ChordPro files that I'd consider being similar can be imported in both landscape and portrait.
I can import the same file on other devices without problems
- Very strange -
In the deep recesses of my mind I seem to recall the old version of Companion allowing you to edit entries in a column as if each line was a cell in a spreadsheet.
Am I imagining that or was it real?
What I'm hoping for is the ability to put a cursor in a column and just edit the contents of that column for each song.
E.G. - Say I want to edit the Custom field for each song in a collection. Select that field for the first song, make my change, move to the next song (<DnArrow>?), make the next change etc.. Think moving down cells in a spreadsheet, making changes as you go.
If that is how it was, can we have it back please? If I'm imagining things, is it something we can get please? As it is now, I have to <RtClick>, select edit, navigate to the field, change the field contents, and click OK, rinse and repeat...
For my particular use case, in one library I have about 2800 songs, just over 2000 of which are in three particular collections that happened to be CSV imports. They were the first CSVs I ever built for MS and poor choices were made If I didn't want to keep the existing database entries in order to maintain the integrity of some set lists, and more importantly crop and annotation data, I'd just modify the CSVs, delete the songs and re-import. If I have to do it the long way it's gonna get old real fast
When in half page display mode, if the pages aren't tall the app will display multiple at the same time e.g. both pages 1 and 2 on the same screen (this is good).
But when the next page button is pressed it will move page 2 up to the top and display page 3 underneath. would it be possible to have an option
to have next page display the next page that is not on the screen and maintain layout of currently displayed pages (as if all the displayed pages are on larger composite page). e.g. pg. 1 on top pg. 2 on bottom, next page is tapped, page 3 is now on top and page 2 is still on bottom in same place.
The current default is sensible to have as a default, but it can be confusing when all the pages shift around.
Hi All,
I'm very new to MSP.
Using an Android Tablet.
I have successfully loaded many songs into multiple collections; so far so good.
One of my files was a large song book with 150 songs and it loaded just fine.
The problem is it's a lot of scrolling to get to page 150 or song 150.
Is there an easy way to break this book down into individual songs please, or do I have to just bite the bullet and photo each page and use the NEW button to load as a new song.
All help gratefully received
Geoffr
I have been using MS with great satisfaction since October 2022, on my Sansung S8+ tablet.
To control my Quad Cortex and my Boss GT-10B, I use the Midi Luminite Graviton system (with the F10 footswitch in particular).
Using MS -> Graviton -> multi-effects works very well : when I select a song on MS, the song's midi controls adjust the multi-effects. Using Graviton -> multi-effects works very well with the F10.
My problem : I want to use the F10 for : - skip to next/previous song on MS - move to the next/previous page on MS - start/stop audio on MS. It works, but... it's not stable and too random : need to click 1 or 2 or 3 times for audio, page change doesn't always work or skips several pages, etc.
I already tested : - CC commands - PC controls - addition of a pause - addition of a second command (as to stop the first) - linked via USB and Bluetooth I always have the same unstable result and therefore unusable in concert.
Hello:
I am a choir director and I am a newbie to using Mobile Sheets.
In my case, I bought a foot pedal to turn pages directly via bluetooth and it works perfectly.
But I love the auto-scrolling option to keep my hands free and I've seen many musicians use it.
I have tried auto-scrolling both ‘Scroll and Pause’ and ‘Scroll Entire Song in Fixed Time’.
These solutions are ideal when we have the same number of measures per page.
However, when we sing with orchestras or bands, we have pages with different numbers of measures, so the option to wait the same time on all pages does not work.
I have searched a solution in the manual, read the forums, tried some features like ‘Scroll amount % of screen’ but I can't find a solution.
Also, on long tracks there are quite a few tempo changes which makes it more complicated.
Is there a way to manage this?
I had thought that maybe the easiest way is to manually record the page turning changes so that it memorises the tempos but I don't know if this is possible.
I just got Companion onto my Linux box, and no issues whatsoever running it (Slackware 15 based, fwiw . . .) One question though . . . I happened to look at "manually connect" (first try gave no popup . . . flat network, no firewalls, just an access point . . . ) and the prompt was for "Server IP address" . . . . Uh, since there is no server involved, just the desktop and the tablet, not sure that this is the desired prompt (or I missed something).
If I didn't want to keep the existing database entries in order to maintain the integrity of some set lists, and more importantly crop and annotation data, I'd just modify the CSVs, delete the songs and re-import. If I have to do it the long way it's gonna get old real fast 
