• 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Pitch black page...
From what I've read with some Google searches, turning off the hardware overlay can have some negative consequences:

Disable HW overlays

Without a hardware overlay every application that is displaying things on the screen will share video memory and will have to constantly check for collision and clipping to render a proper image, this can cost a lot of processing power. With a hardware overlay each application gets its own portion of video memory, getting rid of the need to check for collision and clipping.

Another user said:

rendering a view goes through layers or abstractions, even passing through dedicated hardware doing the job. hardware overlay allows the renderer to take a couple of regions aside and treat them optimized. then theres the cpu and gpu. usually android decides which abstraction is best for each view, taking things like transparency into account and what not. you switch hw overlays off, project butter goes out of the window but cpu and gpu still do the job. you force gpu, the composition will be done by your gfx chip. just don't touch it - its meant for developers picking up debugging output.


So in general, I wouldn't think it would be a good thing to turn that setting off. Having said that, I'd really like another person to try turning it off to see if it really does help for some reason. In that case, it would be exposing a bug in the OS.

Mike
Reply
Thanks for your words of warning - I've also read quite a bit about the negative consequenses of turning off that (and other similar) settings. The decision to try turning it off wasn't completey arbitrary though; during my many google searches for display errors on Samsung devices, I ran across several discussions about flickering screens (mainly related to the Youtube app), where the problem disappeared when that exact setting was disabled. So I thought I'd give it a shot and see if it helped in my case as well (though, of course, a flickering screen isn't exactly what I'm seeing..).

I'd also be very happy if anyone else would try testing this out.
Reply
I still get the black screen issue, always at the most inconvenient time. It actually happened during a Solo & Ensemble contest performance last weekend, which was mortifying. It happened twice today, fortunately during rehearsal. I'm now in the habit of flipping through every page once I get on stage.

As a software engineer, I'm trying to characterize the problem so it can be solved. Clearly, it only happens with PDF files, but the file length seems to be irrelevant. I've had it happen on a 350-page musical score, and I've had it happen on a 6-page choir piece. It has never happened with individual PNGs. Moving forward and back does not solve it, but rotating the screen to landscape and back to portrait does fix it.

It is possible that the cause is running out of resources during PDF rendering. I tend to leave my tablet on 24/7 with MobileSheets Pro running. Today, after it happened in rehearsal, I killed MobileSheets Pro and restarted it, and the concert itself went fine, but that could have been the luck of the draw. But if it is a resource problem, why does it not affect every page from then on?

I have started using PNGs for my critical long pieces, but because PNGs are not as convenient to import, it's not my preferred method. I'll comment about that in another thread.

Tim Roberts
Accompanist
Reply
Hello Tim,

What kind of device are you using. Is it also the Samsung Note Pro 12.2"? i still have yet to experience this issue, but I'm not able to use my Samsung Note Pro nearly as much as you guys, so it could just be an issue that is less likely to show up if you aren't using the app for extended periods of time. I would love it if I could find a way to reliably reproduce the issue...

Thanks,
Mike
Reply
FWIW, I weighed in on this issue, possibly years ago (I have the Samsung 900T 12") and I still occasionally have the problem - although it seems less frequently. I almost always have it when paging through a setlist, and I typically navigate to the setlist via the Setlist top menu option rather than via the "Recent Songs" listing of the setlist name. The colored navigation or jump points (overlays) display but no music. It *can* be resolved by advancing/retreating 3-4 pages. I was not aware of the portrait/landscape fix. It does not happen that often (I've played 4 hour gigs without an occurrence and gone weeks without an occurrence), but, when it does happen it can be jarring. I usually just try to soldier on while advancing and retreating the pages. I actually have more frequent issues with accidental page turns - but those tend to be easier to recover from. I have the latest Android release from Samsung and a pretty up to date if not completely up to date version of MobilesheetsPro. I usually have YouTube, a file transfer, settings and a handful of other stuff suspended in the background.
Reply
Just two tiny observations relating to this (I also agree that the black pages appear less frequently now than they used to, though I still get them occasionally).

Firstly, I guess I have had just 4 or 5 occurrences this whole past year, but common for all these is that usually (as far as I can remember), whenever I have had ONE black page in an open song, I have corrected it (turning a few pages onwards, and then back again), and then continued playing - and I have usually had ANOTHER instance of a black page later in the same song. In other words, maybe 3 months between each time it has happened, but then it has usually happened twice within maybe 30 minutes on those days..

Secondly, I had hitherto only seen this when actually displaying a score. Today, however, I opened the Cropping editor (through the "Edit song" button in the Library screen), and got a black page for the first page of the song (a 3-page PDF). Going to the second page (which was displayed correctly), cropping that page, and then back to page 1, the page was displayed correctly. I guess this eliminates any possibility of this problem relating to page turning method, touching the screen at specific spots, pedals being connected and so on...

Don't know if these observations can shed any light on the cause of the problem..?
Reply


Digg   Delicious   Reddit   Facebook   Twitter   StumbleUpon  


Users browsing this thread:
1 Guest(s)


  Theme © 2014 iAndrew  
Powered By MyBB, © 2002-2018 MyBB Group.