Question about Pipeline 2

[Greg Kearney]

So I am undertaking to cange my production of Books from Pipeline 1 to Pipeline 2

I am getting errors related to the encoder. See the log file enclosed.

This is on a MacOS computer I am also enclosing the speech conjuration file as well as the speech log file. Any help would be appreciated

[Bert Frees]

Hello Greg,

I have investigated this.

The reason why it doesn't work out of the box is because when the desktop application is launched, the "PATH" environment variables is reset.

You have lame installed at /usr/local/bin/lame, which is not a standard location and therefore the Pipeline can't find it. Unfortunately there is nothing we can do about this at the moment since we use a 3rd party tool to generate the launcher which sets the PATH.

You should be able to set the location of lame through your speech configuration file. Your configuration file is correct, however by default most TTS properties can not be set "dynamically" through a configuration file supplied via the job. They can only be set through a static configuration file. There are two options:

1. Make a static configuration file. This is done by setting the system property "tts.config" (explanation of how to set system properties below). For example:

    tts.config=/Users/greg/Desktop/say.xml

2. The second option is to set the system property "host.protection" to "false", which will enable you to set TTS properties through a "dynamic" configuration file:

    host.protection=false

Currently the only way to set system properties is to manually edit a file called "system.properties". In your case, you can find this file at /Applications/DAISY\ Pipeline\ 2.app/Contents/Java/etc/system.properties (assuming you've installed to /Applications).

Hope this helps,

Bert

[Greg Kearney]

Thank you.

I tried option 2 below. This time I didn't get any error messages from within Pipeline itself but I also did not get any recording either. There are errors in the TTS log file. I am enclosing copies of the various files for your review below:

[Bert Frees]

There seems to be a timeout happening somewhere while invoking the "say" command. I can't figure out why that is though. Could you please also send us the server log? Should be in `/Applications/DAISY\ Pipeline\ 2.app/Contents/Java/data/log` I think.

Also, could you confirm that running "say greg" from the command line works?

2017-02-24 16:59 GMT+01:00 Greg Kearney <gkea...@gmail.com>:

Thank you.

I tried option 2 below. This time I didn't get any error messages from within Pipeline itself but I also did not get any recording either. There are errors in the TTS log file. I am enclosing copies of the various files for your review below:

--
You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



Do we have any further ideas?

> --
> You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Greg Kearney]

say is working, I use it all the time for other projects and I just tested it.

Here is the only log in the log directory:

[Bert Frees]

Could this possibly a one-off error? I can see in the logs that on the 19th of February, the OSX speech engine did initialize correctly:

2017-02-19 18:45:08,369 [INFO ] o.d.p.tts.synthesize.SynthesizeStep - Number of working TTS engine(s): 1/3

This suggests that sometimes it works and sometimes not. There is not more information in the log that could explain why. Could you maybe try it once again and see if you have more luck this time?

2017-02-28 16:51 GMT+01:00 Greg Kearney <gkea...@gmail.com>:

say is working, I use it all the time for other projects and I just tested it.

Here is the only log in the log directory:

Hope this is a help.

> On Feb 28, 2017, at 9:32 AM, Bert Frees <bert...@gmail.com> wrote:
>
> There seems to be a timeout happening somewhere while invoking the "say" command. I can't figure out why that is though. Could you please also send us the server log? Should be in `/Applications/DAISY\ Pipeline\ 2.app/Contents/Java/data/log` I think.
>
> Also, could you confirm that running "say greg" from the command line works?
>
>
>
> 2017-02-24 16:59 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> Thank you.
>
> I tried option 2 below. This time I didn't get any error messages from within Pipeline itself but I also did not get any recording either. There are errors in the TTS log file. I am enclosing copies of the various files for your review below:
>
> --
> You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.
>
>
>
> Do we have any further ideas?
>
>
> > On Feb 24, 2017, at 4:44 AM, Bert Frees <bert...@gmail.com> wrote:
> >
> > Hello Greg,
> >
> > I have investigated this.
> >
> > The reason why it doesn't work out of the box is because when the desktop application is launched, the "PATH" environment variables is reset.
> >
> > You have lame installed at /usr/local/bin/lame, which is not a standard location and therefore the Pipeline can't find it. Unfortunately there is nothing we can do about this at the moment since we use a 3rd party tool to generate the launcher which sets the PATH.
> >
> > You should be able to set the location of lame through your speech configuration file. Your configuration file is correct, however by default most TTS properties can not be set "dynamically" through a configuration file supplied via the job. They can only be set through a static configuration file. There are two options:
> >
> > 1. Make a static configuration file. This is done by setting the system property "tts.config" (explanation of how to set system properties below). For example:
> >
> >     tts.config=/Users/greg/Desktop/say.xml
> >
> >
> > 2. The second option is to set the system property "host.protection" to "false", which will enable you to set TTS properties through a "dynamic" configuration file:
> >
> >     host.protection=false
> >
> >
> > Currently the only way to set system properties is to manually edit a file called "system.properties". In your case, you can find this file at /Applications/DAISY\ Pipeline\ 2.app/Contents/Java/etc/system.properties (assuming you've installed to /Applications).
> >
> >
> >
> > Hope this helps,
> > Bert
> >
> >
> >
> > 2017-02-20 2:19 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> > So I am undertaking to cange my production of Books from Pipeline 1 to Pipeline 2
> >
> > I am getting errors related to the encoder. See the log file enclosed.
> >
> > This is on a MacOS computer I am also enclosing the speech conjuration file as well as the speech log file. Any help would be appreciated
> >
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.
>
>
>
> --
> You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

[Bert Frees]

---------- Forwarded message ----------
From: Greg Kearney <gkea...@gmail.com>
Date: 2017-02-28 17:39 GMT+01:00
Subject: Re: Question about Pipeline 2
To: Bert Frees <bert...@gmail.com>


I have never seen this work at all. I just tried deleting the logfile and runningthe job again. This time however I got no log file in the log directory at all.

Greg

> On Feb 28, 2017, at 10:03 AM, Bert Frees <bert...@gmail.com> wrote:
>
> Could this possibly a one-off error? I can see in the logs that on the 19th of February, the OSX speech engine did initialize correctly:
>
> 2017-02-19 18:45:08,369 [INFO ] o.d.p.tts.synthesize.SynthesizeStep - Number of working TTS engine(s): 1/3
>
> This suggests that sometimes it works and sometimes not. There is not more information in the log that could explain why. Could you maybe try it once again and see if you have more luck this time?
>
>
>
>
>
> 2017-02-28 16:51 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> say is working, I use it all the time for other projects and I just tested it.
>
> Here is the only log in the log directory:
>
>
>
>
> Hope this is a help.
>
>
> > On Feb 28, 2017, at 9:32 AM, Bert Frees <bert...@gmail.com> wrote:
> >
> > There seems to be a timeout happening somewhere while invoking the "say" command. I can't figure out why that is though. Could you please also send us the server log? Should be in `/Applications/DAISY\ Pipeline\ 2.app/Contents/Java/data/log` I think.
> >
> > Also, could you confirm that running "say greg" from the command line works?
> >
> >
> >
> > 2017-02-24 16:59 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> > Thank you.
> >
> > I tried option 2 below. This time I didn't get any error messages from within Pipeline itself but I also did not get any recording either. There are errors in the TTS log file. I am enclosing copies of the various files for your review below:
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > Do we have any further ideas?
> >
> >
> > > On Feb 24, 2017, at 4:44 AM, Bert Frees <bert...@gmail.com> wrote:
> > >
> > > Hello Greg,
> > >
> > > I have investigated this.
> > >
> > > The reason why it doesn't work out of the box is because when the desktop application is launched, the "PATH" environment variables is reset.
> > >
> > > You have lame installed at /usr/local/bin/lame, which is not a standard location and therefore the Pipeline can't find it. Unfortunately there is nothing we can do about this at the moment since we use a 3rd party tool to generate the launcher which sets the PATH.
> > >
> > > You should be able to set the location of lame through your speech configuration file. Your configuration file is correct, however by default most TTS properties can not be set "dynamically" through a configuration file supplied via the job. They can only be set through a static configuration file. There are two options:
> > >
> > > 1. Make a static configuration file. This is done by setting the system property "tts.config" (explanation of how to set system properties below). For example:
> > >
> > >     tts.config=/Users/greg/Desktop/say.xml
> > >
> > >
> > > 2. The second option is to set the system property "host.protection" to "false", which will enable you to set TTS properties through a "dynamic" configuration file:
> > >
> > >     host.protection=false
> > >
> > >
> > > Currently the only way to set system properties is to manually edit a file called "system.properties". In your case, you can find this file at /Applications/DAISY\ Pipeline\ 2.app/Contents/Java/etc/system.properties (assuming you've installed to /Applications).
> > >
> > >
> > >
> > > Hope this helps,
> > > Bert
> > >
> > >
> > >
> > > 2017-02-20 2:19 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> > > So I am undertaking to cange my production of Books from Pipeline 1 to Pipeline 2
> > >
> > > I am getting errors related to the encoder. See the log file enclosed.
> > >
> > > This is on a MacOS computer I am also enclosing the speech conjuration file as well as the speech log file. Any help would be appreciated
> > >
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.

> > > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.

[Greg Kearney]

Did you mean to reply

Sent from my iPhone

Greg Kearney

Commonwealth Braille and Talking Book Cooperative

To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-...@googlegroups.com.

[Bert Frees]

2017-02-28 18:17 GMT+01:00 Greg Kearney <gkea...@gmail.com>:

Did you mean to reply

No, just forwarded so the others could follow.

Still I think it's odd that on the first six times (five times on 19/2 and one time on 20/2) the TTS engine started correctly. Of course, this was still at the time where you hadn't applied the fix for the encoder issue (set host.protection to false), so that explains why you didn't see it work.

I'm still interested to see what happens if you run the job a few times more. I don't know what happened to the log file. Maybe by deleting it you broke something? If needed try to reinstall the Pipeline to get the log working again (and of course after reinstalling set host.protection again).

 

On Feb 28, 2017, at 10:51 AM, Bert Frees <bert...@gmail.com> wrote:

---------- Forwarded message ----------
From: Greg Kearney <gkea...@gmail.com>
Date: 2017-02-28 17:39 GMT+01:00
Subject: Re: Question about Pipeline 2
To: Bert Frees <bert...@gmail.com>


I have never seen this work at all. I just tried deleting the logfile and runningthe job again. This time however I got no log file in the log directory at all.

Greg


> On Feb 28, 2017, at 10:03 AM, Bert Frees <bert...@gmail.com> wrote:
>
> Could this possibly a one-off error? I can see in the logs that on the 19th of February, the OSX speech engine did initialize correctly:
>
> 2017-02-19 18:45:08,369 [INFO ] o.d.p.tts.synthesize.SynthesizeStep - Number of working TTS engine(s): 1/3
>
> This suggests that sometimes it works and sometimes not. There is not more information in the log that could explain why. Could you maybe try it once again and see if you have more luck this time?
>
>
>
>
>
> 2017-02-28 16:51 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> say is working, I use it all the time for other projects and I just tested it.
>
> Here is the only log in the log directory:
>
>
>
>
> Hope this is a help.
>
>
> > On Feb 28, 2017, at 9:32 AM, Bert Frees <bert...@gmail.com> wrote:
> >
> > There seems to be a timeout happening somewhere while invoking the "say" command. I can't figure out why that is though. Could you please also send us the server log? Should be in `/Applications/DAISY\ Pipeline\ 2.app/Contents/Java/data/log` I think.
> >
> > Also, could you confirm that running "say greg" from the command line works?
> >
> >
> >
> > 2017-02-24 16:59 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> > Thank you.
> >
> > I tried option 2 below. This time I didn't get any error messages from within Pipeline itself but I also did not get any recording either. There are errors in the TTS log file. I am enclosing copies of the various files for your review below:
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > Do we have any further ideas?
> >
> >
> > > On Feb 24, 2017, at 4:44 AM, Bert Frees <bert...@gmail.com> wrote:
> > >
> > > Hello Greg,
> > >
> > > I have investigated this.
> > >
> > > The reason why it doesn't work out of the box is because when the desktop application is launched, the "PATH" environment variables is reset.
> > >
> > > You have lame installed at /usr/local/bin/lame, which is not a standard location and therefore the Pipeline can't find it. Unfortunately there is nothing we can do about this at the moment since we use a 3rd party tool to generate the launcher which sets the PATH.
> > >
> > > You should be able to set the location of lame through your speech configuration file. Your configuration file is correct, however by default most TTS properties can not be set "dynamically" through a configuration file supplied via the job. They can only be set through a static configuration file. There are two options:
> > >
> > > 1. Make a static configuration file. This is done by setting the system property "tts.config" (explanation of how to set system properties below). For example:
> > >
> > >     tts.config=/Users/greg/Desktop/say.xml
> > >
> > >
> > > 2. The second option is to set the system property "host.protection" to "false", which will enable you to set TTS properties through a "dynamic" configuration file:
> > >
> > >     host.protection=false
> > >
> > >
> > > Currently the only way to set system properties is to manually edit a file called "system.properties". In your case, you can find this file at /Applications/DAISY\ Pipeline\ 2.app/Contents/Java/etc/system.properties (assuming you've installed to /Applications).
> > >
> > >
> > >
> > > Hope this helps,
> > > Bert
> > >
> > >
> > >
> > > 2017-02-20 2:19 GMT+01:00 Greg Kearney <gkea...@gmail.com>:
> > > So I am undertaking to cange my production of Books from Pipeline 1 to Pipeline 2
> > >
> > > I am getting errors related to the encoder. See the log file enclosed.
> > >
> > > This is on a MacOS computer I am also enclosing the speech conjuration file as well as the speech log file. Any help would be appreciated
> > >
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> > > For more options, visit https://groups.google.com/d/optout.
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

> > For more options, visit https://groups.google.com/d/optout.
>
>
>

--
You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Greg Kearney]

Ok I'll try this from scratch. I would point out however that at no time did I ever get a recording in all of this. Also just where does pipeline 2 expect to find lame installed?

Sent from my iPhone

Greg Kearney

Commonwealth Braille and Talking Book Cooperative

To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-...@googlegroups.com.

[Bert Frees]

I presume you have it installed at /usr/local/bin/lame, since that is what you have in your configuration file (say.xml).

[Greg Kearney]

OK a fresh install, enclosed are all the log files from the run. I run it but get no audio back into the output folder. I'm rather lost at this point.

Greg

[Greg Kearney]

OK a fresh install, enclosed are all the log files from the run. I run it but get no audio back into the output folder. I'm rather lost at this point. I am adding the messages from the GUI at the end of this email.

Greg

[Bert Frees]

Hi,

This looks much better already.

I've looked further into it. The "Resource not found: partxxxx_xx_xxx.mp3" warnings indicate a bug. The audio is synthesized but the resulting mp3 files are not copied over to the right folder. I have fixed this now and we'll make a bug release for you. We'll let you know when it is ready for you to try.

Sorry for the inconvenience.

Bert

2017-03-01 20:08 GMT+01:00 Greg Kearney <gkea...@gmail.com>:

OK a fresh install, enclosed are all the log files from the run. I run it but get no audio back into the output folder. I'm rather lost at this point.  I am adding the messages from the GUI at the end of this email.

Greg

>>>>> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsub...@googlegroups.com.
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>>
>>>>>

[Greg Kearney]

Do we have any word on the fix to Pipeline to get the TTS narration working?

I have a project on hold waiting for that bug to be addressed.

Thanks you.


Commonwealth Braille & Talking Book Cooperative
Greg Kearney, General Manager
#320, 185-911 Yates Street
Victoria, BC V8V 4Y9
CANADA
Email: in...@cbtbc.org
Web: www.cbtbc.org

U.S. Address
2219 Melholland Road
Lawrence, KS 66047
UNITED STATES
Email: gkea...@gmail.com

[Greg Kearney]

[Greg Kearney]

say is working, I use it all the time for other projects and I just tested it.

Here is the only log in the log directory:

Hope this is a help.

[Bert Frees]

Hello Greg,

The bugfix release is now available, not as a new download, but as an update. In the user interface, from the "Help" menu, choose "Check updates" and hit "Check for updates" button. (You might have to restart the application after the update has finished, I'm not sure about that.)

Let us know if you're having trouble with the update process.

Regards,

Bert

[Bert Frees]

Forwarding to the mailing list...

---------- Forwarded message ----------
From: Greg Kearney <gkea...@gmail.com>
Date: 2017-03-21 16:39 GMT+01:00
Subject: Re: Question about Pipeline 2
To: Bert Frees <bert...@gmail.com>

That seems to work however I have now found another issue. When building an ePub with text to speech enable I seem not to get the media overlay of the recordings.

Greg

[Bert Frees]

When you say you don't get the media overlays, do you mean that you're not getting any sound from your EPUB player, or are there simply no SMIL files inside the EPUB?

[Greg Kearney]

There are no SMIL or MP3 audio files in the book. I am enclosing the book that was generated. which is only 246KB along with the source XML file.

Greg

[Bert Frees]

That is strange. I had converted the same book and got an EPUB with MP3 and SMIL files. Are you sure there are no error messages anymore?

2017-03-21 17:26 GMT+01:00 Greg Kearney <gkea...@gmail.com>:

There are no SMIL or MP3 audio files in the book. I am enclosing the book that was generated. which is only 246KB along with the source XML file.

Greg

[Bert Frees]

This is the same timeout error we saw earlier that causes the OSX speech engine to not initialize correctly, which is why you see the following in the log:

INFO: Number of working TTS engine(s): 0/3

I have no idea why this happened again. Could you try the conversion a couple more times, like you did before?

---------- Forwarded message ----------
From: Greg Kearney <gkea...@gmail.com>
Date: 2017-03-21 17:36 GMT+01:00
Subject: Re: Question about Pipeline 2
To: Bert Frees <bert...@gmail.com>

None that I see is the the output from the GUI: I'm also enclosing the TTS.log file




INFO: ZedAI file name: The-Idea-of-Canada.xml
INFO: MODS file name: zedai-mods.xml
INFO: CSS file name: zedai-css.css
INFO: Renaming certain elements to span with @role
INFO: Renaming code and kbd elements to reflect block or phrase variants.
INFO: Renaming annotation elements to identify block or phrase variants.
INFO: Convert br to lines
INFO: Grouping contents of a definition list into items
INFO: Move out inlined image groups
INFO: Move out inlined lists
INFO: Move out inlined definition lists
INFO: Move out inlined prodnotes
INFO: Move out inlined divs
INFO: Move out inlined poems
INFO: Move out inlined linegroups
INFO: Move out inlined tables
INFO: Move out inlined sidebars
INFO: Move out inlined notes
INFO: Move out inlined epigraphs
INFO: Move out inlined annotation blocks
INFO: Move out inlined code blocks
INFO: Normalize mixed block/inline content
INFO: Normalize mixed section/block content
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level2
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Normalize mixed section and block content model for level1
INFO: Translate to ZedAI
INFO: Generating CSS
INFO: Input document is valid
INFO: Validating ZedAI
INFO: ZedAI output is valid.
INFO: Conversion complete.
INFO: Converted to XHTML.
INFO: Navigation Document Created.
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Total number of language(s): 1
INFO: LexService for language '<ANY>': omnilang-lexer
INFO: LexService for language 'en': rule-based-lexer
INFO: could not find the builtin lexicon for language: en
INFO: End SSML generation for EPUB3
INFO: Number of working TTS engine(s): 0/3
INFO: Number of synthesizable TTS sections: 0
INFO: Number of encoding threads: 4
INFO: Number of regular text-to-speech threads: 4
INFO: Number of reserved text-to-speech threads: 0
INFO: Max TTS memory footprint (encoding excluded): 318MB
INFO: Max encoding memory footprint: 159MB
INFO: Text-to-speech threads started.
INFO: Encoding threads started.
INFO: Text-to-speech finished. Waiting for audio encoding to finish...
INFO: Audio encoding finished.
INFO: number of synthesized sound fragments: 0
INFO: audio encoding unreleased bytes : 0
INFO: TTS unreleased bytes: 0
INFO: writing TTS logs...
INFO: Package Document Created.

> > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-dev+unsubscribe@googlegroups.com.

[Greg Kearney]

I have tried this three times with the same results.

Greg

> > > To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-...@googlegroups.com.

> > > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
>
>
>
>

> --
> You received this message because you are subscribed to the Google Groups "DAISY Pipeline Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to daisy-pipeline-...@googlegroups.com.

> For more options, visit https://groups.google.com/d/optout.

> <tts-log.xml>