Yeah, it can take a long time to generate those audio files. The
other night I tried running through a novel by Cory Doctorow. It was
speaking at 400 words, and the file ended up around 5 and a half hours
in length. I think it took somewhere between 15 and 20 minutes to
generate that file.
One thing you could always try for testing purposes is to put some
totally unrelated action after text to audio. Perhapse the launch
application action, and have it bring up something you don't normally
use. When that program popps up, then you know it's finished
generating the audio.
Darcy
On 9-Dec-07, at 11:06 PM, Jane Jordan wrote:
Yes, tghat is the last action. Hmm, I will have to test it againon
a very short file.
Jane
On Dec 9, 2007, at 11:04 PM, Darcy Burnard wrote:
Is the last action text to audio file? If so, keep in mind that
can take a long time to run, especially if what you're converting
is long. Maybe it's not all the way finished.
Darcy
On 9-Dec-07, at 8:59 PM, Jane Jordan wrote:
It has never closed. There's always a window open. have to force-
quit.
Jane
On Dec 9, 2007, at 8:14 PM, Darcy Burnard wrote:
Hi Jane. You have the workflow saved as an application right?
If so, it should close when it's done running. At least that
has been my experience.
Darcy
On 9-Dec-07, at 7:27 PM, Jane Jordan wrote:
Is there an action you can add to an automator workflow to tell
it to close? What is it, and where do I find it? The problem is
that I can't get my work flow that turns text to audio to quit
when the file is done.
Jane
