Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TEXT->REALISED_DURATIONS works, REALISED_DURATIONS->AUDIO doesn't #267

Closed
kjyv opened this issue Jan 5, 2015 · 5 comments
Closed

TEXT->REALISED_DURATIONS works, REALISED_DURATIONS->AUDIO doesn't #267

kjyv opened this issue Jan 5, 2015 · 5 comments
Assignees
Labels
Milestone

Comments

@kjyv
Copy link

kjyv commented Jan 5, 2015

As with other combinations, some of the generated data seem to not be parsed properly.
While it is possible to synthesize REALISED_DURATIONS from TEXT or EMOTIONML,
generating audio from these is not possible (server gets stuck with 100% cpu).
An example input is

0.080000006 125 h
0.14000002 125 a
0.19500002 125 l
0.30500004 125 o:
0.64500004 125 _

It would be very helpful to have this fine grained control over the output.

@psibre psibre added the bug label Jan 6, 2015
@psibre psibre added this to the 5.1.2 milestone Jan 6, 2015
@alishah-ahmed
Copy link
Contributor

Could you please provide us with the following details if possible:

  • Stacktrace
  • Java Version
  • Machine details that you are using along with OS details.

Thanks.

@kjyv
Copy link
Author

kjyv commented Jan 22, 2015

As it "gets stuck", there is no stacktrace, as no error is thrown. At least I couldn't see any on both terminal windows (server or client).

$ java -version
java version "1.7.0_72"
Java(TM) SE Runtime Environment (build 1.7.0_72-b14)
Java HotSpot(TM) 64-Bit Server VM (build 24.72-b04, mixed mode)

Running on OSX 10.10.1.

@psibre
Copy link
Member

psibre commented Jan 22, 2015

Could you please provide the details of your request? Which locale/voice are you using?

@kjyv
Copy link
Author

kjyv commented Jan 22, 2015

Language de or en, and it seems the voice doesn't matter, bits1-hsmm, bits3, bits3-hsmm, dfki-pavoque-neutral-hsmm all produce this behavior.

@psibre
Copy link
Member

psibre commented Jan 22, 2015

I believe that the source of this issue is that REALISED_DURATIONS and REALISED_ACOUSTPARAMS were intended only as output types, but when they were originally introduced (in bd582c8 and eb8807b, respectively), their isInputType parameter was set to true.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants