08-01-2022, 04:13 AM
(This post was last modified: 08-01-2022, 04:38 AM by YellovvYoshi.)
Hi everyone,
I use a Microsoft Surface Pro 6 (Intel Core i7, 8GB RAM, 256 GB) for MobileSheets. For the most part, it has worked great, and despite a bug where sometimes the following page doesn't load when I turn the page, I feel comfortable using it in performance because it's very, very rare.
However, now that I'm playing for my first opera since covid (and since using my tablet instead of physical paper), I'm noticing that MobileSheets has more problems dealing with big PDF files. Opera piano/vocal scores tend to be in the hundreds of pages, and this is no exception. This is also a newer opera with literally hundreds of errata, so I've made countless annotations. I can't flatten these annotations because it's likely there will be even more changes during the rehearsal period, and I can't predict where.
Unfortunately, with such gigantic PDFs and so many annotations, I've noticed a bit of lag when turning pages, and noticeably more lag when making new annotations. Here are some of the problems I'm facing:
1) Sometimes regular page turning (with my bluetooth pedal) takes almost a second, and that's way too long in this context to be acceptable. This is not the case with most other smaller PDFs
2) When trying to jump from one page to another one far away (such as straight from page 1 to page 100), the app inevitably freezes for several seconds. (up to 10!!)
3) In annotations mode, sometimes when writing with my Surface Pen I have to wait about a second before the drawing actually shows up, and then it's not even what I actually drew. For example, if I draw a "C", it'll end up looking more like an "l" because it draws a straight line from my first point of contact to the last, when I release the pen.
4) In annotations mode, sometimes after trying to draw several strokes quickly, the app freezes for several seconds. Sometimes it force closes after freezing, others it resumes just fine.
The app usually doesn't force close unless I'm in annotations mode actively drawing or erasing, thankfully. However, even that is unacceptable in a fast-paced rehearsal setting.
I already split the PDF into separate acts, so Act I is only about 160 pages and Act II about 120, but it only helped minimally. I made sure the PDFs were as efficient as possible, as well.
Is this just a matter of needing more RAM? Or is MobileSheets simply not built to handle such big files and thousands of annotations? My annotation settings, as far as I can tell, are also as efficient as possible, with "Combine freeform annotations" checked.
Having a flawless experience is so important that I've just purchased a Surface Pro 8 (i7, 32 GB RAM, 1TB), but after spending over $2000, I'm wondering if this will actually be worth it or if it's more of a MobileSheets issue. It particularly worries me that even when there's lag, actively looking at the Task Manager in my current Surface Pro 6 shows that MS is only using about 600MB of RAM, far less than what I actually have available. This makes me think more RAM may not solve the problem. Same thing with CPU - it doesn't actually quite reach what is available.
Please advise.
I use a Microsoft Surface Pro 6 (Intel Core i7, 8GB RAM, 256 GB) for MobileSheets. For the most part, it has worked great, and despite a bug where sometimes the following page doesn't load when I turn the page, I feel comfortable using it in performance because it's very, very rare.
However, now that I'm playing for my first opera since covid (and since using my tablet instead of physical paper), I'm noticing that MobileSheets has more problems dealing with big PDF files. Opera piano/vocal scores tend to be in the hundreds of pages, and this is no exception. This is also a newer opera with literally hundreds of errata, so I've made countless annotations. I can't flatten these annotations because it's likely there will be even more changes during the rehearsal period, and I can't predict where.
Unfortunately, with such gigantic PDFs and so many annotations, I've noticed a bit of lag when turning pages, and noticeably more lag when making new annotations. Here are some of the problems I'm facing:
1) Sometimes regular page turning (with my bluetooth pedal) takes almost a second, and that's way too long in this context to be acceptable. This is not the case with most other smaller PDFs
2) When trying to jump from one page to another one far away (such as straight from page 1 to page 100), the app inevitably freezes for several seconds. (up to 10!!)
3) In annotations mode, sometimes when writing with my Surface Pen I have to wait about a second before the drawing actually shows up, and then it's not even what I actually drew. For example, if I draw a "C", it'll end up looking more like an "l" because it draws a straight line from my first point of contact to the last, when I release the pen.
4) In annotations mode, sometimes after trying to draw several strokes quickly, the app freezes for several seconds. Sometimes it force closes after freezing, others it resumes just fine.
The app usually doesn't force close unless I'm in annotations mode actively drawing or erasing, thankfully. However, even that is unacceptable in a fast-paced rehearsal setting.
I already split the PDF into separate acts, so Act I is only about 160 pages and Act II about 120, but it only helped minimally. I made sure the PDFs were as efficient as possible, as well.
Is this just a matter of needing more RAM? Or is MobileSheets simply not built to handle such big files and thousands of annotations? My annotation settings, as far as I can tell, are also as efficient as possible, with "Combine freeform annotations" checked.
Having a flawless experience is so important that I've just purchased a Surface Pro 8 (i7, 32 GB RAM, 1TB), but after spending over $2000, I'm wondering if this will actually be worth it or if it's more of a MobileSheets issue. It particularly worries me that even when there's lag, actively looking at the Task Manager in my current Surface Pro 6 shows that MS is only using about 600MB of RAM, far less than what I actually have available. This makes me think more RAM may not solve the problem. Same thing with CPU - it doesn't actually quite reach what is available.
Please advise.