Posts: 62
Joined: Mar 2011
Reputation:
0
OK, pulseaudio didn't work. Speech was repeating like echoes, responces were extremely slow. So I uninstalled pulseaudio, wich left me with a broken installation.
But that is what I really like about the pi: Just re-flash the card, install the 1 or 2 extra packages, copy the .kodi-directory back into the home directory, voila! :-) It's nice to have backups! :-)
OK, for now I will live with the missing parts of the text, but I'll keep experementing. Maybe I find something that works.
Regards!
Posts: 20
Joined: Dec 2014
Reputation:
0
Hello folks,
I'm trying to package Kodi Screen Reader for the OSMC distribution. Thing I eventually would like to accomplish is to have this addon integrated by default into OSMC, so that it is possible to have speech in every OSMC installation with a single key stroke, like on the Mac. Only problem I'm facing is that Kodi Screen Reader starts by default when it's put into the addons folder. Is there a way to change the addon in a way that it doesn't start by default, while not having to tweak the addon database or the addon settings in userdata?
Posts: 258
Joined: Jun 2013
Reputation:
8
2015-12-22, 21:34
(This post was last modified: 2015-12-22, 21:37 by Traker1001.)
That would be awesome. I think the Addon being enabled or disabled by default is a function that is central to kodi itself and not the Addon itself. So you might get a better answer to this question by posing it in the Development forum.
donkamillo
My experience with Pulse was not the same as yours, It actually worked pretty well for me, to the point it was pretty usable. However, When I tried it, It was on the Pi1 so something may have changed. I have a New Pi sitting here, as was planning to get into testing it again myself, I just have to get to it.
Posts: 258
Joined: Jun 2013
Reputation:
8
On thing I thought of though, Is you want the addon to start the first time at least to load the keyboard layout. So maybe it would be possible to create a script to init the addon, load the KB lay out and then disable itself.
Posts: 20
Joined: Dec 2014
Reputation:
0
That sounds good. If someone could assist in getting such a thing in operation, that'd be great. I have some Python knowledge but currently not that into Kodi Addon coding yet.
Posts: 258
Joined: Jun 2013
Reputation:
8
Unfortunately I don't know enough about coding to do such a thing, Otherwise I'd help out. And I think Ruuk is pretty busy with other projects at the moment. So I am not entirely sure who'd be able to do so. Maybe someone on the development forum, Or the OSMC forum might even be a better bet.
Posts: 2,293
Joined: Aug 2005
Reputation:
202
ruuk
Team-Kodi Member
Posts: 2,293
One thing I could do is create a check in the addon for the existence of another addon. For example, I could make it so that if the addon service.xbmc.tts.pre is installed, the screen reader will disable itself on first run. The service.xbmc.tts.pre would basically be a dummy addon - you would include it with with the normal addon when pre-installing just for this purpose. This is first thought for something both simple for me to implement in code and simple for the packager to implement.
Posts: 8
Joined: May 2015
Reputation:
0
update on OSMC and screen reader:
In the new updated OSMC (2015-11-29 image) if you Change 'Play Speech Directly Via eSpeak' to Yes, the screenreader won't speak anymore. I don't know if this is a new issue to OSMC, to kodi to debian or what. I reinstalled and tried again, same result.
Posts: 20
Joined: Dec 2014
Reputation:
0
@ruuk: it might be enough to check whether an OSMC specific module, such as script.module.osmccommon or service.osmc.settings is running? That feels a bit cleaner than creating a dummy addon just for this purpose. Only drawback that would create is that on a new OSMC install, everyone always has to manually enable the screen reader with the hotkey. I will experiment with the dummy addon approach regarding the question whether it is auto activated by Kodi and will report on that later today.
Posts: 20
Joined: Dec 2014
Reputation:
0
Have created a service.xbmc.tts.pre addon which succesfully loads when in /usr/share/kodi/addons. Also tried putting service.xbmc.tts in /usr/share/kodi/addons, but observed the following. It seems that the addon sounds don't play and the keymap doesn't load correctly. Now, util.py contains:
def playSound(name,return_duration=False):
wavPath = os.path.join(xbmc.translatePath('special://home'),'addons','service.xbmc.tts','resources','wavs','{0}.wav'.format(name))
#wavPath = os.path.join(xbmc.translatePath(xbmcaddon.Addon().getAddonInfo('path')).decode('utf-8'),'resources','wavs','{0}.wav'.format(name))
xbmc.playSFX(wavPath)
I wonder whether the second wavPath is commented out? This way, playing of sounds is hard coded to the addon in the home directory, which shouldn't be the case I think.