2014-05-03, 21:35
Hi,
I must say, I am quite impressed! When I last looked at accessibility with XBMC, probably the beginning of this thread, there was no forward movement. Then, within 2 months, this project went to a usable project.
some observations
I'm using on the PI, so I put the addon in on my existing 3.95.6 build. It was crashing on large wav files and so it was difficult to get the gist of things. I then grabbed the current build from snapshots (about a couple hours ago I guess) and not only is the crashing gone, but the chomping on the end of files appears to be gone too.
I put both the 0.0.48 and speech.server.zip in the addons dir, but I'm guessing I don't need the speech.server. It doesn't look like an addon anyway, now that I look through it a bit better.
I must say, I'm not a fan of the keyboard input method with the ridiculous remote I got, who ever heard of a remote that doesn't have numbers on it anyway! and in the end I just went in and edited the .xml settings file and added the proper values since the ip address input method was really annoying. There did not seem to be a way to make the pi read the input field so I could tell exactly what was in there. I can't imagine the fun I would have if I had to type in a WPA key or something.
The initial dialogue boxes (welcome to openelec etc) did not properly speak, and since this remote has no f2 or f3 buttons on it I didn't try to make it read, simply clicked on next until the main gui showed up. (previously I had used google goggles to get an idea on what might be going on)
Then I enabled live tv and enabled a pvr backend. There are 1,434 channels in my backend with 2 weeks of EPG for each, undoubtedly that caused the pi to be unhappy over memory. I scrolled down the list until I found a channel and clicked on it. The channel began playing, but suddenly speech was aborted and would not play I'm guessing because media was playing? Is there a way to pause the media or something so that it will speak long enough to figure out how to get out of it?
My wife had walked in while I was battling with the IP address input madness and offered to help. At some point the thing stopped speaking, which was just fine for us since it was being a pest. We kept clicking on ok until we got to the 'enable' stage of turning on the addon. Since clicking enable did not work, I walked to a computer, looked in the settings.xml file and rebooted the pi.
Maybe one solution to not reading the input is if you pause without moving the selector around for more than 3 seconds after the last sniffy sound, it will read the input value. At least then you could figure out what was going on. and then of course if you hit backspace, it could read immediately. I don't know whether the input field can be polled or if you just have to keep track of it on event or something, but it makes that sniffy noise all the time, I'm guessing you could hook onto that callback to determine what was clicked.
The last thing that happened when I was trying to click the 'back' button (or the one that I think is the back button, it seems to go back) the PI kept playing the content pulling from the PVR, stuttered for a few seconds, went red, and then we gave up for a while since my wife wanted to watch 'nonrmal' tv.
So, I'm quite pleased with the project so far. I'm guessing if you use a wireless keyboard or something it will be easier to input things.
I must say, I am quite impressed! When I last looked at accessibility with XBMC, probably the beginning of this thread, there was no forward movement. Then, within 2 months, this project went to a usable project.
some observations
I'm using on the PI, so I put the addon in on my existing 3.95.6 build. It was crashing on large wav files and so it was difficult to get the gist of things. I then grabbed the current build from snapshots (about a couple hours ago I guess) and not only is the crashing gone, but the chomping on the end of files appears to be gone too.
I put both the 0.0.48 and speech.server.zip in the addons dir, but I'm guessing I don't need the speech.server. It doesn't look like an addon anyway, now that I look through it a bit better.
I must say, I'm not a fan of the keyboard input method with the ridiculous remote I got, who ever heard of a remote that doesn't have numbers on it anyway! and in the end I just went in and edited the .xml settings file and added the proper values since the ip address input method was really annoying. There did not seem to be a way to make the pi read the input field so I could tell exactly what was in there. I can't imagine the fun I would have if I had to type in a WPA key or something.
The initial dialogue boxes (welcome to openelec etc) did not properly speak, and since this remote has no f2 or f3 buttons on it I didn't try to make it read, simply clicked on next until the main gui showed up. (previously I had used google goggles to get an idea on what might be going on)
Then I enabled live tv and enabled a pvr backend. There are 1,434 channels in my backend with 2 weeks of EPG for each, undoubtedly that caused the pi to be unhappy over memory. I scrolled down the list until I found a channel and clicked on it. The channel began playing, but suddenly speech was aborted and would not play I'm guessing because media was playing? Is there a way to pause the media or something so that it will speak long enough to figure out how to get out of it?
My wife had walked in while I was battling with the IP address input madness and offered to help. At some point the thing stopped speaking, which was just fine for us since it was being a pest. We kept clicking on ok until we got to the 'enable' stage of turning on the addon. Since clicking enable did not work, I walked to a computer, looked in the settings.xml file and rebooted the pi.
Maybe one solution to not reading the input is if you pause without moving the selector around for more than 3 seconds after the last sniffy sound, it will read the input value. At least then you could figure out what was going on. and then of course if you hit backspace, it could read immediately. I don't know whether the input field can be polled or if you just have to keep track of it on event or something, but it makes that sniffy noise all the time, I'm guessing you could hook onto that callback to determine what was clicked.
The last thing that happened when I was trying to click the 'back' button (or the one that I think is the back button, it seems to go back) the PI kept playing the content pulling from the PVR, stuttered for a few seconds, went red, and then we gave up for a while since my wife wanted to watch 'nonrmal' tv.
So, I'm quite pleased with the project so far. I'm guessing if you use a wireless keyboard or something it will be easier to input things.
