#How do i identify overtraining?

1 messages · Page 1 of 1 (latest)

tepid dust
#

Hey gamers, I've been making models for a little bit, but i've had trouble deciding when overtraining has taken place. I understand you would choose the lowest point in your loss graphs prior to them starting to shift upwards, but in a situation like this, where would the overtraining have taken place? 11k, 17k, 23k, or 31k?

languid finch
# tepid dust Hey gamers, I've been making models for a little bit, but i've had trouble decid...

Overtraining is honestly hard to come by for the most part. You should test and see these low points, but that doesn't really mean the later points are necessarily overtrained. In fact, sometimes, I would say the latest point is the best.

Anyways, the main way to actually see overtraining (or, better yet, model quality being screwed up) is by checking g/mel and g/kl. Mel being how well spectrogram recreation is going in the model vs the original data, and KL being the model vs the original data.

Normally, both of them will be going down, and that's generally when model improvements are still happening. If it's stagnated or going up, it's not improving or getting worse at it's job, respectively.

The lowest G/total point is normally just the best average model from the generator, and not necessarily the best sounding model. This is why testing is basically essential. Try picking up on the models' differences by ear and see what you prefer, and which one has the least amount of noise if it even has noise.

Hope this helps you to identify overtraining and all that stuff.

tepid dust
stiff urchin
#

-gui

languid finch
languid finch
#

pretty sure they're just using Mainline

tepid dust
#

no lmao im currently using rmvpe

stiff urchin
chrome birch
tepid dust
#

im listening to the latest .pth that was saved and it sounds pretty good

loud patrolBOT
#

Ayo? @tepid dust level 1 !!! lfg

chrome birch
#

a modified Imjoy by Vidal

tepid dust
languid finch
tepid dust
languid finch