vall-e-x tts fails with ModuleNotFoundError: No module named 'utils'

[mutschler]

LocalAI version:
Docker Image: quay.io/go-skynet/local-ai:v1.30.0-ffmpeg

Environment, CPU architecture, OS, and Version:
Linux Debian-1201-bookworm-amd64-base 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 GNU/Linux

Describe the bug
Unable to produce audio files with vall-e-x backend

To Reproduce
start container and try to generate some audio file

 curl http://localhost:8080/tts -H "Content-Type: application/json" -d '{
     "backend": "vall-e-x",
     "input":"Hello!"
   }'

Response:

{"error":{"code":500,"message":"grpc service not ready","type":""}}

Expected behavior
generate audio file

Logs

api_1  | 8:16PM DBG Loading model vall-e-x from
api_1  | 8:16PM DBG Loading model in memory from file: /models
api_1  | 8:16PM DBG Loading GRPC Model vall-e-x: {backendString:vall-e-x model: threads:0 assetDir:/tmp/localai/backend_data context:{emptyCtx:{}} gRPCOptions:0xc0002e2d00 externalBackends:map[autogptq:/build/extra/grpc/autogptq/autogptq.py bark:/build/extra/grpc/bark/ttsbark.py diffusers:/build/extra/grpc/diffusers/backend_diffusers.py exllama:/build/extra/grpc/exllama/exllama.py huggingface-embeddings:/build/extra/grpc/huggingface/huggingface.py vall-e-x:/build/extra/grpc/vall-e-x/ttsvalle.py vllm:/build/extra/grpc/vllm/backend_vllm.py] grpcAttempts:20 grpcAttemptsDelay:2 singleActiveBackend:false}
api_1  | 8:16PM DBG Loading external backend: /build/extra/grpc/vall-e-x/ttsvalle.py
api_1  | 8:16PM DBG Loading GRPC Process: /build/extra/grpc/vall-e-x/ttsvalle.py
api_1  | 8:16PM DBG GRPC Service for  will be running at: '127.0.0.1:42511'
api_1  | 8:16PM DBG GRPC Service state dir: /tmp/go-processmanager3649919681
api_1  | 8:16PM DBG GRPC Service Started
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | 8:16PM DBG GRPC(-127.0.0.1:42511): stderr Traceback (most recent call last):
api_1  | 8:16PM DBG GRPC(-127.0.0.1:42511): stderr   File "/build/extra/grpc/vall-e-x/ttsvalle.py", line 13, in <module>
api_1  | 8:16PM DBG GRPC(-127.0.0.1:42511): stderr     from utils.generation import SAMPLE_RATE, generate_audio, preload_models
api_1  | 8:16PM DBG GRPC(-127.0.0.1:42511): stderr ModuleNotFoundError: No module named 'utils'
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | [127.0.0.1]:60044 200 - GET /readyz
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp 127.0.0.1:42511: connect: connection refused"
api_1  | 8:16PM DBG GRPC Service NOT ready
api_1  | [172.30.0.1]:32946 500 - POST /tts

Additional context
configuration of container is the same as in #1173

[Aisuko]

Hi @mutschler. Thanks for your feedback. Yes, the vall-x-e project is not a lib. So, we have cloned it inside container and it should works. And we are also working on the new feature #1147 but it is not working now as you can see from the context of the PR. So, this will be fixed in the future and it also on the schedule.

And now, I think what we can do is:

• The version of image that include the code https://github.com/go-skynet/LocalAI/blob/8ac718618580e1bef524bc167c60b88f7e8eb88c/Dockerfile#L137 should be worked.
• Or replace the entry point of the image, and re-install it manually.