Hey Nick, You can open it with iBooks and use it on an IOS device. We print the Bible in Braille, http://biblesfortheblind.org Keith Reedy God gives His best to those who leave the choice with Him. J Hudson Taylor.
On May 21, 2015, at 3:22 PM, Nick Gawronski <n...@nickgawronski.com> wrote: > Hi, In regards to reading the Pro Tools 12 manuals what methods work best as > if I use preview and do a say all I find that the first letter gets cut off > of the text which does not make it very helpful? Is there a good method for > converting the documents to html files or something that the talking book > players can read so I keep the header navigation of the user guides? I > mainly want to brush up on the Pro Tools 12 user guides so I would like some > method for remembering where I left off or setting up preview not to cut off > the first letter of words. Better yet is there a method to convert the > documents to audio files by chapter using the mac voices? Nick Gawronski > On Tue, 19 May 2015, Krister Ekstrom wrote: > >> Date: Tue, 19 May 2015 16:07:46 +0200 >> From: Krister Ekstrom <kris...@kristersplace.com> >> Reply-To: ptaccess@googlegroups.com >> To: ptaccess@googlegroups.com >> Subject: Re: There's much about PT i don't understand despite having RTFM >> Ah ok, thanks Slau for the info, the bits i found in the reference guide >> were a bit over my head but then again it was probably due to the fact that >> i wasn’t particularly interested in that section of it all back then. >> I promise to look it up in the guide should i need it.:-) >> /Krister >> >>> 19 maj 2015 kl. 15:59 skrev Slau Halatyn <slauhala...@gmail.com>: >>> >>> Hi Krister, >>> >>> Beat detective is used for things like generating bar|beat markers to an >>> existing drum track or to separate clips based on transients in drum track. >>> The Clips can then be quantized to the bar|beat grid. I've used Beat >>> Detective only a few times but many years ago. It has recently become more >>> accessible and, yes, you can use it although it'll take some trial and >>> error. With the scope of its capabilities comes a learning curve best >>> attacked by reading the pages devoted to it in the Reference Guide. The >>> concepts are essentially simple but their implementations depend upon what >>> the end result needs to be. In other words, if you're trying to match a >>> tempo map to existing drums, it requires a particular approach and if >>> you're trying to slice up a drum performance to match an existing tempo, it >>> takes a slightly different approach. There are elements that define how the >>> existing audio is categorized in subdivisions and how sensitive the >>> detection will be for the analysis. There are visual markers that help a >>> sighted user determine the desired level of sensitivity which makes it a >>> little more difficult for a blind user but that's where the experimentation >>> comes in. >>> >>> As I said, I've used it in the past but the kind of music I record doesn't >>> call for Beat detective. The music I record is very much not on the grid. >>> If you're doing dance music or hip-hop then it'll be more useful. Keep in >>> mind that anything Beat Detective does, you can do manually. Beat detective >>> is just a tool to make the job easier and less time-consuming. If it's the >>> tool you need to use, then it's worth learning its ins and outs. >>> >>> HTH, >>> >>> Slau >>> >>> On May 19, 2015, at 5:55 AM, Krister Ekstrom <kris...@kristersplace.com> >>> wrote: >>> >>>> Hi there, >>>> Ok, that maybe was a pretty pathetic subject line, sorry for that. Anyways >>>> what i was about to ask is can a blind person use the so called beat >>>> detective and what do you do with it? Is it for imported tracks or such? >>>> /Krister >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "Pro Tools Accessibility" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to ptaccess+unsubscr...@googlegroups.com. >>>> For more options, visit https://groups.google.com/d/optout. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "Pro Tools Accessibility" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to ptaccess+unsubscr...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >> -- You received this message because you are subscribed to the Google Groups "Pro Tools Accessibility" group. To unsubscribe from this group and stop receiving emails from it, send an email to ptaccess+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
