Audio Encoder - reason for timeout error?

The audio encoder aborts the conversion after the fourth file, but I can’t find the reason.
The first three files pass through without any problems, but with the fourth, it always produces an error due to a timeout of [200].

It can’t be the file size; at least one of the previous files in the list is larger than this one.
I can also fairly safely rule out an error in the file itself, because even recreating it shows no changes, and the individual files contained within it can be processed without any problems by the encoder. Furthermore, all files are compiled using the same software, and the others work.
I’ve also run longer or more extensive track lists before without any problems.
The original file format is mp3 in each case.

What am I missing?
To me, a noob in this area, the log appears to indicate that the encoder is unable to fully access the file that has already been uploaded?

The log from the Docker container for the track causing the problem:

INFO |server_helpers.c:0484:multipart_handle| Received file ‘pcmData.2.pcm’
INFO |handler_api.c:1871:taf_encode_start| [TAF] new chapter for Pettersson und Findus 02 - 01 Ein Feuerwerk für den Fuchs.mp3
INFO |toniefile.c:0394:toniefile_new_chapter| new chapter at 0x00002454
ERROR|server_helpers.c:0360:multipart_handle| httpReceive failed with error Timeout [220]
INFO |handler_api.c:2116:handleApiPcmUpload| [TAF] Ended encoding

Thanks for your help :slight_smile:

I also get timeouts, but only for big mp3 files. Chrome works better than Edge, so I guess it is related to browser performance.

It would be nice to have the possibility to convert the files locally, and then only upload them. My teddycloud is running on a raspberry pi with 1gb ram and when using the audio encoder it even is sometimes not responsive anymore.

I usually work with Firefox, but I’ll give the others a try - I hadn’t even thought of that.

My Teddy Cloud is on a NAS, but the conversion still takes a long time. There’s an external option, check it out here. I haven’t implemented it myself yet, though; I need to learn more about it first.

Chrome encoded properly.