Improve memory handling in Read2Go, specifically around VoiceOver usage
1. The text may be displayed on the screen, but vo can't see it. This means that you can't use vo navigation to review the text. This has serious implications: you can't see how something is spelled, you can't use vo speech to read a book, and you can't read a book in braille on a display.
2. As stated in #1, vo can't be used to read the text of a book. While the voices that come with the app do sound good, they take up so much memory that I was advised to close some apps on my iPod Touch 4th gen when I had had a book open for a few minutes. What really worries me, though, is that I only had the "settings" app in the App Switcher, nothing else. It would be great to be able to use vo when my iPod does not have the ram to support the Read2Go tts (which seems to be all the time - switching to Ryan, I was unable to open my book at all because of the low ram alerts).
3. Double tapping a book always goes to a 'details' page, from where you must find the "read" button. There seems to be no setting to just open a book right from the bookshelf.
4. Again, ram is a serious problem. With no other apps running, I tried going into the settings for a book and was told to close other apps. When I tapped OK on that alert, I was returned to my bookshelf, not to my book. This is going to be a deal breaker for iPod users, in my opinion, unless there is some way to not use the third-party tts voices.
I also have a 32GB 4th Gen iPod and find the running out of memory to be a mere show stopper with Read to Go. I agree with the other comments on this thread that if the high quality speech (nice as it sounds) is going to gobble up so much resources, then I want to be able to turn it off and gain back the high performance all other apps provide. Also allowing for good VO performance would enable us to verify content and/or to read with Braille displays.
Also, "being planned" for over eight months is really not acceptable! These are obvious software defects and should be immediately addressed.
Are you able to close all running apps by:
1. Double tap the home button.
2. Press and hold an application at the bottom.
3. The application icons at the bottom will begin to shake.
4. Press the Red - button to shut down the app.
5. Press the home button when complete.
Upgrading from 8GB to 32GB will result in the same experience as both iPods have the same amount of RAM available. I suggest waiting as our engineers are working hard to address this issue in a future release.
I am both a special educator and the parent of a child with a reading disability. At home, we are receiving the same RAM alerts on our IPod touch, 4th generation and are unable to use use R2G for longer than a few minutes or pages. This is occuring on our 8GB IPod Touch. I was wondering if the RAM issues are occuring on devices with higher memory. My school district is looking into purchasing several IPod Touches for our special education students. Would 32GB IPod touches have more RAM, and perhaps solve the problem? Or should I advise them to wait?
HI Ken. how did you manage to vote? voting doesn't seem to be accessible, and maybe i should start a new topic but i don't know how. I agree not being able to save your place with vo is a real problem. It's sometimes handy to be able to use vo when reading a book especiallyif it's either a technical book, or a book with hard names for the tts to pronounce. at least you can look at the speling and see what the word is meant to be. Also I'm not sure but I've heard it's not possible to use read2go with a braille display. I suspect if navigation with vo was fixed then perhaps it would work better with those who use a braille display. Still it's a great app, thanks for all the work, and a way for us to leave feedback.
Ken Petri commented
Amy Ruell identifies the biggest problem with VO in Read2Go: When you leave a book and then return to it, you start at the copyright notice/beginning of the book. This is a major problem, especially since it is not possible to retrieve any bookmarks you have set (that interface is completely broken for VO users).
I am not having any issues with memory usage and sluggishness with VoiceOver and it is possible to read word by word, sentence by sentence, and character by character--just use the rotor to select the mode and flick up or down.
But the problems of always starting at the beginning and not having a VoiceOver accessible bookmarks interface severely limit the utility of Read2Go for users who cannot see the screen and/or need VoiceOver.
I'm spending the rest of my votes attempting to raise this issue. It should not be considered something that is "planned." These problems are, without any question, bugs and need to be corrected quickly.
turning off voice over when reading a book sin't practical if wanting to use navigation. I'm not having memory problems as yet although i possibly haven't tried to read a large book. I am also mostly unable to vote in the forums sometimes double tapping the vote button works, but mostly it doesn't seem to. I still have 10 votes left and it was a fluke i was able to vote once. not sure how i did it though. Hoping a comment is as good as a vote.
I would also like to have the option of being able to read with voice over. the tts voices are ok, but being from australia, i really like the australian Karen voice for some books. I don't read text books on the victor stream anymore because i like the Karen tts much better. if there was a way to save your place using voice over, that would be excellent.
Amy Ruell commented
My place is not saved when attempting to use vo to read a book. If I use VO gestures, I am still returned to the copyright notice for the book and cannot use navigation.
Deborah Armstrong commented
As someone who works with the LD population professionally, I am truly happy that this app will be useful for so many of my students. Do remember though that the majority of recreational readers using the bookshare collection are blind or visually impaired; the typical sighted user with a learning disability reads only when necessary. If this app becomes super accessible, it could potentially generate revenue for bookshare, helping you to further the mission of serving all print impairments.
Please note that VoiceOver users who are having this problem are having problems with the accessibility of this site to post their votes. This is a serious problem that affects the usability of this app for a number of users, who also cannot register votes due to accessibility issues.
My name I Jim Barbour. I work as a systems architect in Sunnyvale, Ca.
I am the one who posted about not being surprised that things were sluggish, given how r2g and voiceover are interacting together.
It looks to me like the entire book is being pasted into one large reading area. My guess is that VO is trying to parse through the entire book, looking for lines, pages, headings, etc and is running out of memory while doing this.
My suggestion was that r2g behave more like ibooks. ibooks presents one page at a time, allowing a VO user to turn the page with a 3-finger swipe left or right. This prevents VO from trying to parse the entire book.
Mary Otten commented
I wonder if having the option to get rid of all the visual highlighting stuff would make a difference when using voice over. Somebody posted that they're not surprised at the sluggishness given how VO works, but since VO isn't sluggish in any other apps I have, including IBooks, where the entire book is loaded, I don't see why that should be different here in this app. Why should only a portion of the book get loaded at a time? That sounds like introducing a hassle as a remedy for getting rid of a hassle. Why not just find a way to fix the problem and let us load the whole book and read with VO as in IBooks?
Sorry, one more thing, the titel of this bug doesn't really describe the problem. May I suggest renaming it to "sluggish VO problems", or something similar.
BTW, overall I think read2go is a really well done app, and I congratulate the developers on an awesome job!
I agree that reading with VO is very sluggish. This isn't all the surprsing to me, given how voiceover works.
I'd love to see this fixed as well.
I'd like to suggest that the best way to fix this would be to not display the entire book in the text display area. Instead, when using VO, break the book up and display a chapter at a time.
Mary Otten commented
I concur with Alex' and Debra's comments. If I could cast all my votes on one thing, it would be this one about the total unusability of this app to read with VO. I have two I-devices, an IPod 3rd gen and a 1st gen IPad. I can't read with VO on either of them, and I find the speech rate with the supplied voices to be rather slow and if I try navigating to next section with the Heather voice, I get kicked out of the book. Sure that is not the expected behavior? I love the search and easy downloads, but the point is reading, and this needs serious work to be a decent experience for a VO user.
Deborah Armstrong commented
I am experiencing exactly the same symptoms. If I understand Apple's thinking, memory management is supposed to be autoMagic, which is why apps don't have close buttons and the app switcher doubles as a list of open and recently used apps. There is no way a user can know which apps in the app switcher are actually consuming memory and need closing so the dialog box in R2G advising users to close other running programs is misleading.
Vo users can typically live without the high-quality voices, and it makes no sense for memory consumption to be higher after they are disabled. Nevertheless, R2G is either sluggish to respond or runs out of memory faster if they are turned off.
I also second the opinion that the interface for VO users should be consistent with iBooks, which is very easy to use. R2G should be tested extensively by someone using VoiceOver wearing sleep shades if necessary.
I now see that VO can be made to read the text, by turning off the app audio in settings. However, this causes extreme slowness and is almost worse than just being told you are out of ram. I figured that, by disabling tts, these ram problems would go away, but it does not seem that way at all.