From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 7D5771EF7BC; Thu, 9 Oct 2014 17:59:34 -0400 (EDT) Received: from mta1.math.wisc.edu (mta1.math.wisc.edu [144.92.166.23]) by befuddled.reisers.ca (Postfix) with ESMTP id E8CC31EF7AF for ; Thu, 9 Oct 2014 17:59:32 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mta1.math.wisc.edu (Postfix) with ESMTP id 5252249D06B; Thu, 9 Oct 2014 16:59:30 -0500 (CDT) Received: from mta1.math.wisc.edu ([127.0.0.1]) by localhost (mta1.math.wisc.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PsJJVfFnp5lV; Thu, 9 Oct 2014 16:59:30 -0500 (CDT) Received: from mta1.math.wisc.edu (localhost [127.0.0.1]) by mta1.math.wisc.edu (Postfix) with ESMTP id C815549CFF4; Thu, 9 Oct 2014 16:59:29 -0500 (CDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on mta1.math.wisc.edu X-Spam-Level: X-Spam-Status: No, score=-101.0 required=6.5 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=disabled version=3.3.2 Received: from mailhost.math.wisc.edu (erdos.math.wisc.edu [144.92.166.25]) by mta1.math.wisc.edu (Postfix) with ESMTP; Thu, 9 Oct 2014 16:59:29 -0500 (CDT) Received: from [144.92.166.19] (vv507j.math.wisc.edu [144.92.166.19]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailhost.math.wisc.edu (Postfix) with ESMTPS id C17ED42001B; Thu, 9 Oct 2014 16:59:29 -0500 (CDT) Message-ID: <54370541.2050802@math.wisc.edu> Date: Thu, 09 Oct 2014 16:59:29 -0500 From: "John G. Heim" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Icedove/24.8.1 MIME-Version: 1.0 To: Glenn , "Speakup is a screen review system for Linux." Subject: Re: a little sysadmin story References: <86a956i23h.fsf@vibrator.pk5001z> <20141009125200.GI1044@opera.rednote.net> <86ppe1gyed.fsf@vibrator.pk5001z> <543691D1.9050000@tysdomain.com> <543693B5.9060601@tysdomain.com> <5436A145.30001@verizon.net> <478C3EC865774707826A4B0E156AE72B@your2c061f0461> <20141009202940.GO1044@opera.rednote.net> <43ADB90BD8144990877FCBE37F4837C3@your2c061f0461> In-Reply-To: <43ADB90BD8144990877FCBE37F4837C3@your2c061f0461> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Oct 2014 21:59:34 -0000 Poking around amazon seems to show that a vga to usb frame grabber can be had for $270. Add a raspberry pi or similar object. The software is the big thing though. I once had a system to program my VCR similar to your concept. I had the video out from the VCR fed into a video capture board in my PC. I'd capture a frame, run tesseract on it, and redirect the text output to the screen so speakup would read it. In other words, I could press a key and it would re-read the entire VCR screen to me. I always wanted to write something that read just the text that had changed or maybe even recognized the cursor and intelligently read the adjacent text. But I never wrote it. It would be like writing a screen reader without having all the hints from the structure of the document or the window you're working with. I think it could be done though. On 10/09/14 15:59, Glenn wrote: > I think that the optican was different in that it used a video camera. > My thought here is to capture the video signal as it would be going to a > monitor, and send it directly to be processed OCR,, and then it could either > go to a Braille display, or TTS. > Glenn > ----- Original Message ----- > From: "Janina Sajka" > To: "Glenn" ; "Speakup is a screen review system for > Linux." > Sent: Thursday, October 09, 2014 3:29 PM > Subject: Re: a little sysadmin story > > > Glenn, are you talking about the Opticon? Didn't someone start > remanufacturing that relatively recently? > > > Glenn writes: >> What we need is a piece of hardware that does OCR directly from the video >> port. >> It seems like that would be a relatively easy device to produce, given >> what >> we have these days. >> Glenn >> ----- Original Message ----- >> From: "Al Sten-Clanton" >> To: ; "Speakup is a screen review system for Linux." >> >> Sent: Thursday, October 09, 2014 9:52 AM >> Subject: Re: a little sysadmin story >> >> >> First, I thank Janina for raising certain issues better than I could. >> (I also thank others who've made valuable points from different angles.) >> >> Second, where is the equivalent code for kicking in the monitor when we >> boot up? Shouldn't the aim be to treat our access technology in the >> same or an equivalent way, to the degree possible? >> >> Al >> >> On 10/09/2014 09:55 AM, Littlefield, Tyler wrote: >>> I also wanted to point out that most companies and organizations are a >>> bit weird about installing anything. The fact that Speakup is in the >>> kernel, but the entire idea of installing a special program which >>> they're not sure of, be it screen reader or magnification bothers most >>> people, so this isn't just an issue of Speakup possibly being better. >>> There are reasons and there obviously is a need for speakup to get >>> better, perhaps that means coming out of kernel space. But a sad story >>> from once upon a time with a moral unrelated is not quite the point. >>> On 10/9/2014 9:46 AM, Littlefield, Tyler wrote: >>>> This whole story sounds like it needs another couple of bears to make >>>> it all interesting. So speakup crashed the kernel. I've had issues, >>>> but apart from known bugs I've never seen speakup panic the kernel all >>>> the time. Speakup caused a system to crash? Perhaps. People should >>>> also backup their work. >>>> On 10/9/2014 9:34 AM, Deedra Waters wrote: >>>>> Janina, >>>>> >>>>> speakup was the cause because when bossman came down to hook up a >>>>> monitor and look, the panick messages had something to do with >>>>> speakup. >>>>> >>>>> As for backing up their work, they were trying to fix their fuck-up to >>>>> begin with. The initial problem wasn't with speakup. However when i >>>>> was >>>>> helping them debug it, speakup made the kernel panick and crash. >>>>> >>>>> Debian i dont think likes people with root access on their box to >>>>> begin >>>>> with, but i think they kind of didn't like speakup in their kernel to >>>>> begin with. >>>>> >>>>> I suspect on the other hand that if speakup was a user-space app, it >>>>> wouldn't have mattered to them so much. If a userspace program crashes >>>>> it doesn't take down the whole box. When speakup does though, it takes >>>>> down the whole box. >>>>> >>>>> >>>> >>>> >>> >> _______________________________________________ >> Speakup mailing list >> Speakup@linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >> >> _______________________________________________ >> Speakup mailing list >> Speakup@linux-speakup.org >> http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup >