Unable to train on custom data with multiple speakers about flowtron HOT 6 OPEN

On Mon, Oct 2, 2023 at 3:59 AM Cookie ***@***.***> wrote: https://github.com/NVIDIA/flowtron/blob/d149bc466b8325026aeb68aa2fef24337e7463b2/config.json#L50 Make sure this line is set to 107 or higher in whichever json file your using as your config file. If you are able to, setting the CUDA_LAUNCH_BLOCKING=1 environment variable might give you a more accurate error message. The error message you sent doesn't contain the line the error occured (since the error happened asynchronously on the GPU) — Reply to this email directly, view it on GitHub <#159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIAJSQSH26RTKS5HIT5DU53X5HVFPANCNFSM6AAAAAA5OQKTT4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Mon, Oct 2, 2023 at 4:05 AM Naveed Ahmed ***@***.***> wrote: I changed n_speakers to 107 in config.json and it worked like a charm. But the training is painstakingly low. I am running AWS instance with 16 GB RAM. How much RAM will I need according to you? My goal is to develop multi speaker Indian accent english tts model. Is training with 107 speakers (total of 44k audio files) an overkill? Please suggest me. On Mon, Oct 2, 2023 at 3:59 AM Cookie ***@***.***> wrote: > > https://github.com/NVIDIA/flowtron/blob/d149bc466b8325026aeb68aa2fef24337e7463b2/config.json#L50 > > Make sure this line is set to 107 or higher in whichever json file your > using as your config file. > > If you are able to, setting the CUDA_LAUNCH_BLOCKING=1 environment > variable might give you a more accurate error message. The error message > you sent doesn't contain the line the error occured (since the error > happened asynchronously on the GPU) > > — > Reply to this email directly, view it on GitHub > <#159 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIAJSQSH26RTKS5HIT5DU53X5HVFPANCNFSM6AAAAAA5OQKTT4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

On Mon, Oct 2, 2023 at 4:11 AM Cookie ***@***.***> wrote: Speed should be the same for single speaker and multi speaker datasets. You can change n_speakers to 128 and n_text to 256 to slightly improve performance, but it will be a very small improvement. — Reply to this email directly, view it on GitHub <#159 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIAJSQR752D7WLWPXYYXE6DX5HWQLANCNFSM6AAAAAA5OQKTT4> . You are receiving this because you authored the thread.Message ID: ***@***.***>

On Mon, Oct 2, 2023 at 4:13 AM Naveed Ahmed ***@***.***> wrote: Any suggestions on the batch_size? I have set it to 12 currently. On Mon, Oct 2, 2023 at 4:11 AM Cookie ***@***.***> wrote: > Speed should be the same for single speaker and multi speaker datasets. > You can change n_speakers to 128 and n_text to 256 to slightly improve > performance, but it will be a very small improvement. > > — > Reply to this email directly, view it on GitHub > <#159 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AIAJSQR752D7WLWPXYYXE6DX5HWQLANCNFSM6AAAAAA5OQKTT4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >