This is the first time I have used the new Companion Pro to transfer some new files to the tablet.
I used exactly the same procedure as the original version, basically select a directory on the PC which contains the files to transfer and hit the go button.
All seemed to be fine and I got the transfer complete message, then an error message popped up on the screen (see screenshot). Actually, lots of them - one for each of the 32 files I was transferring.
When I checked the tablet, the new titles were listed, but wouldn't open. I check the storage area and they didn't exist at al, no files and no separate directories.
I then moved the original PC directory to Dropbox and tries to import into MSPro a second time - this worked!
Care is required to backup since the default backup name is as above. This is aggravated by the name entry line color being the same as the rest of the page. Maybe a different color for the text entry along with the right default name?
WHen I opened up MS Pro Companion, there was a message that there was a new version and it asked it I wanted to to update.
I checked it off to update and install the new version.
But, when I went to find the update and make sure everything was right (to make sure I put the new version was on my desktop, etc.), it seemed it had installed a new version of (the original) MS Companion, rather that an updated MS Pro Companion.
This is not really an issue at all but is the MSP Companion icon smaller than it was before? It looks considerably smaller than the MSC icon that I still have on my desktop. I can't make out the "Pro" at all
About 70% of the time, when I do a long press, I will get the overlay page that I expect.
The rest of the time, I have to press several times and in several places before I get it to come up. I don't know if this is an MSP issue or a tablet issue. I never seemed to have the problem on MS.
several times I've noticed that opening a pdf file takes a long time or it doesn't open at all (black screen with no marking that something is happening). This counts for already existing (database import from previous MS version) files as for newly added pdf files. I also removed and installed Pro again and tried it without the database import from previous MS version but that gave the same results....
I've spent some time now using MobilesheetsPro with PDF music scores and have the following feedback:
A. When adding a song via the Companion (Wi-Fi connection) the default is that the name of the file is used as the title. I am finding however that in some cases the name gets truncated. For example the file "Sonata in A D664.pdf" is given the title "Sonata in A D". If the file is changed to "Sonata in A D664A.pdf" the title is assigned correctly. It appears that if the filename ends in digits these get truncated in the title.
B. When a Song is selected and the Remove tab hit the song gets deleted immediately. It would seem better to require a confirmation message (as is the case when recent files are removed) in case of accidental erasure.
C. I have set the overlay trigger to a long press but find this is erratic sometimes requiring several long presses to get the desired response. This of course could be the the fault of my tablet (Samsung Galaxy Note Pro 12.2).
D. When entering text (making bookmarks) the suggestive spelling seems to get in the way. For example if I type "Chopin" and then hit the space bar the text gets changed to "Chop In". I would prefer if what is actually typed was used by default.
Hello
Since new update, when I open a 2 pages song in setlist, the second page appears instead of the first one
It happens only with setlist, and when the setlist load all the songs when you choose one
Hiya! Been using MS and now MSPro for a while now. Good stuff! But, with the 1.0.5 update I have encountered an issue. All my docs are PDF. With the 1.0.5 update, I now due the header/title of a tune, the footer/copy right notice but no body text.
I'm using a Samsung Galaxy 2 tablet, 10.1 running CyanogenMod 12.1 (Lollipop 5. 1). It's an unofficial build. I did not see this issue in MSPro 1.0.3 and if I restore that from a backup the issue goes away.
