DLNA Media Controller plugin - version 1.4 released

lolodomo · September 12, 2015, 5:58pm

Version 1.4 is released.

You can download it here (ZIP archive at the bottom of this page): http://code.mios.com/trac/mios_dlna-cntroller/browser/tags/1.4

This version will be available in the MiOS app store later.

What’s new in version 1.4:

[ol][li]
Fix: compatibility with Vera firmware 7.0.11
[/li]
[li]
Fix: Google TTS engine
[/li]
[li]
New Microsoft Translator TTS engine
[/li]
[li]
New MaryTTS engine
[/li]
[li]
New language per country for TTS
[/li][/ol]

lolodomo · September 12, 2015, 6:08pm

V1.4 has just been submitted for approval in the store. Should be available in few days.

n0ir · September 13, 2015, 11:54am

The Say-button under the TTS option in the created devices is not responsive. I can’t seem to send test TTS to devices.

lolodomo · September 13, 2015, 2:30pm

Did uou setup and control your renderer ?

Of course I tested before releasing. It is working with XBMC as renderer and UI5 firmware.

n0ir · September 15, 2015, 6:33pm

Got it to work again!

I don’t know why but the first sentence isn’t spoken using Google TTS. I needed to add a “dummy” sentence first (i.e. “Good morning! Good morning!”), to get the renderer to read the announcement properly. Probably something not relating to the app, but I haven’t had the issue before.

cw-kid · September 15, 2015, 9:27pm

[quote=“n0ir, post:5, topic:188794”]Got it to work again!

I don’t know why but the first sentence isn’t spoken using Google TTS. I needed to add a “dummy” sentence first (i.e. “Good morning! Good morning!”), to get the renderer to read the announcement properly. Probably something not relating to the app, but I haven’t had the issue before.[/quote]

I’ve had a similar problem before, but not an entire sentence. I have several Kodi PCs and on some of them it works OK on others it misses off the first few letters of the first word and I had to pad it out with other characters at the beginning, so my sentence was then spoken out correctly.

The Google TTS seems to be working again when sent to my Kodi PC in the living room, just tested it.

When you manually upload the plug-in files to Vera, the version has stayed on 1.3* and not changed to 1.4 is that normal?

Many thanks.

cw-kid · September 15, 2015, 9:47pm

One thing I noticed after sending a Google TTS to the Kodi PC, I was playing a TV Show at the time, the DLNA device in Vera on the Control tab it still says

Playing…Google TTS

After the TTS is spoken the TV Show resumes playback OK but the DLNA device in Vera does not update its playing status to the name of the TV Show episode that is playing etc.

However if I look on the Help tab it does say the name of the playing episode in a path. I can also see the plug-in version is 1.4 on the Help tab.

If I look in the Advanced tab I can see:

TransportState
STOPPED
TransportStatus
ERROR_OCCURRED

CurrentStatus
Google TTS
CurrentTitle
Google TTS

If I Reload Vera these values change:

TransportState
PLAYING
TransportStatus
OK

CurrentStatus & CurrentTitle are now blank.

The Control tab now says just: Playing…

Not sure if this is expected behaviour or not.

Thanks

cw-kid · September 15, 2015, 10:05pm

Another strange thing I have two Kodi PCs that say Upnp Proxy is in use. But one Kodi PC says Proxy not in use and I can’t seem to make it change.

EDIT: Rebooted that PC and now it says Proxy in use so seems to have fixed it.

lolodomo · September 16, 2015, 6:27am

[quote=“cw-kid, post:6, topic:188794”][quote=“n0ir, post:5, topic:188794”]Got it to work again!

I don’t know why but the first sentence isn’t spoken using Google TTS. I needed to add a “dummy” sentence first (i.e. “Good morning! Good morning!”), to get the renderer to read the announcement properly. Probably something not relating to the app, but I haven’t had the issue before.[/quote]

I’ve had a similar problem before, but not an entire sentence. I have several Kodi PCs and on some of them it works OK on others it misses off the first few letters of the first word and I had to pad it out with other characters at the beginning, so my sentence was then spoken out correctly.

The Google TTS seems to be working again when sent to my Kodi PC in the living room, just tested it.

When you manually upload the plug-in files to Vera, the version has stayed on 1.3* and not changed to 1.4 is that normal?

Many thanks.[/quote]

You certainly forgot to upload the updated I_***.XML file. If you check the beginning of this file, you will see 1.4.

lolodomo · September 16, 2015, 11:38am

V1.4 was approved and so should be available in the store.

cw-kid · September 16, 2015, 3:46pm

I did upload all the files.

In one place in the Vera GUI it says version 1.3 and in another place it says version 1.4

Please see attached

lolodomo · September 16, 2015, 5:05pm

That just means you installed 1.3 from the store and then overwrited it manually by 1.4 files.

cw-kid · September 16, 2015, 5:10pm

OK thanks, so I don’t need to worry about it then.

Cheers

cw-kid · October 20, 2015, 10:42am

Hi

The Google TTS rarely seems to work for me these days, so I am trying the Microsoft TTS with the DLNA plug-in.

It works initially for like 4 or 5 times using the SAY option in the TTS tab. I am using UI7 on a Vera Edge for testing.

However it then seems to just stop working and I see this in the logs:

02 10/20/15 11:29:33.252 luup_log:24: DLNA: warning: Microsoft TTS: failed! <0x74ece520> 02 10/20/15 11:29:33.253 luup_log:24: DLNA: warning: Microsoft TTS: trying again with a new session token <0x74ece520> 02 10/20/15 11:29:34.623 luup_log:24: DLNA: warning: Microsoft TTS: failed! <0x74ece520> 35 10/20/15 11:29:34.640 ImplAction::HandleActionRequest SDLNAMediaController1_DLNAMediaController1_Say_run returned 0 <0x74ece520> 10 10/20/15 11:29:34.641 luvd_get_info_data_request creating file buffer /data_request?id=lu_action&output_format=xml&DeviceNum=24&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Say&Text=Beer%20Assistant&Language=en&Engine=MICROSOFT&Volume= pMem 0xd65000/14045184 diff: 5697536 <0x74ece520> 10 10/20/15 11:29:34.642 luvd_get_info_data_request done /data_request?id=lu_action&output_format=xml&DeviceNum=24&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Say&Text=Beer%20Assistant&Language=en&Engine=MICROSOFT&Volume= ret 0 size 124 pMem 0xd65000/14045184 diff: 5697536 took 0 info 0x74ecdd28 <0x74ece520> 10 10/20/15 11:29:34.643 luvd_open /data_request?id=lu_action&output_format=xml&DeviceNum=24&serviceId=urn:dlna-org:serviceId:DLNAMediaController1&action=Say&Text=Beer%20Assistant&Language=en&Engine=MICROSOFT&Volume= FileBuffer 0xba9830 <0x74ece520> 10 10/20/15 11:29:35.000 GlobalLog: mongoose ctx2: 0x866c68 s: d:4929 <0x742b2520>

If I delete the application on the Microsoft Azure website and create a new one it then works again but only for a little while and then stops working again.

Reloading or rebooting Vera doesn’t seem to get it working again either.

EDIT:

This might have fixed it, seems to be working better now, fingers crossed

http://forum.micasaverde.com/index.php/topic,33223.msg252458.html#msg252458

lolodomo · December 26, 2015, 11:42am

We have to forget Google TTS. The service is now only partially available.
Rather use Microsoft engine. Works well.

paros · December 27, 2015, 7:52pm

[quote=“lolodomo, post:15, topic:188794”]We have to forget Google TTS. The service is now only partially available.
Rather use Microsoft engine. Works well.[/quote]

Can you please change Microsoft tts server as default when running scenes?
This text is found at http://code.mios.com/trac/mios_dlna-cntroller: “Two accepted values for the engine: “GOOGLE” for the Google Internet service and “OSX_TTS_SERVER” for a personal OSX TTS server.”

Now it’s not even posible to use the Microsoft speech engine?

By the way, this app is really good!

lolodomo · December 28, 2015, 10:02am

Open the TTS tab, select “Microsoft” as defaut engine, fill your client id and client secret and finally push the Set button at the bottom. That’s all, Microsoft translator is now your default engine.

This text is found at http://code.mios.com/trac/mios_dlna-cntroller: "Two accepted values for the engine: "GOOGLE" for the Google Internet service and "OSX_TTS_SERVER" for a personal OSX TTS server."

You’re right, the wiki was not updated.

Now it's not even posible to use the Microsoft speech engine?

Of course, it is possible with version 1.4.

lolodomo · December 28, 2015, 11:02am

I just updated the wiki page to describe how to setup and use the new TTS engines (Microsoft Transmator and MaryTTS).
I added a note relative to Google service:

Google service is already not working every time (generally only few times per day) and may be removed at any time

paros · December 28, 2015, 11:45am

I tried the default Lua code when creating a scene (from the wiki) but it doesn’t work. I can manually send message to the Kodi dlna player with Microsoft.

What can I do wrong?

lolodomo · December 28, 2015, 12:58pm

[quote=“paros, post:19, topic:188794”]I tried the default Lua code when creating a scene (from the wiki) but it doesn’t work. I can manually send message to the Kodi dlna player with Microsoft.

What can I do wrong?[/quote]

First does everything work well from the plugin UI (play/pause, TTS, …) ?

Of course you have to substitue 666 by your real device id.
Then check the logs (enable the debug logs eventually)