#RVC2 working colab link ? (noUI)
1 messages · Page 1 of 1 (latest)
what's wrong with applio?
like I said its training needs longer than RVC and I don’t really notice significant quality differences. A 45 mins datasets needs like 5 hours to train to 120ep while RVC needs like 1,5 hours.
People on free colab don’t have much time 😛 I wish I could train locally on my macM4pro but there seems to not be an option for it
the only no ui working option is Applio on Colab
you could use Applio Kaggle UI (Kaggle is another cloud computing platform, but gives 30 hours weekly of gpu compared to the max 4 hours of colab)
@karmic umbra may this be because of the fp32 improvement btw?
yeah i dont think theres mac training support locally, maybe Replay but i dont really know
FP32 is slightly slower, but it all depends on the GPU
Not 4x slower
might just be the options they used on rvcdisconnected (old mangio) compared to applio then?
because its google colab
but again we are talking about T4 which is way faster
so 5 hours sounds about right for FP32
Damn, I did not think about this
I still wanna use RVC because applio training takes so long
have you read the above convo? the fp16 vs fp32 thing?
RVC disconnected as well as the og rvc use fp16 precision (enabled for RTX gpus and T4 in colab), and applio uses fp32
fp32 may be slower but doesn't suffer exploding gradients, as explained in:
tl;dr fp32 is generally more stable and less prone to artifacting (mainly caused by exploding gradients)
yes but it doesnt change the fact that it takes longer.... and i was fine with RVC
if there just was a way to train on my mac M4pro 😦
is it apple silicon (ARM)?
there are some issues with math library on ARM, needs to use export OMP_NUM_THREADS=1 to run inference, but I would not try to run training
unless you want to melt it
also MPS is disabled in the latest build due to this nonsense.
so in other words no way to train on mac m4pro? its weird because on github i've seen several people saying they do training on mac
In the latest release it is disabled on mac
but it can be re-enabled
with OMP library limited to just one thread I dont think it will be productinve
i think i have not enough knowledge for this because i don't understand a word
that's what you need to understand why "applio training takes so long" as you said
To wrap it up. "Applio's training takes longer because it uses higher precision for a better training stability and to prevent the model from randomly blowing up. Unfortunately the free T4 on colab has a terrible performance at higher precision, much worse than less precise FP16".
I put the batch size on applio to 15 now. Using colab on T4. Training is now faster (2 mins per epoch). Much better. It’s running since 1 hour and didnt error yet. Maybe I found the solution for my problem
Or is it dumb to do that? Does it make a difference ?
Do you have 50+ hours of audio to use batch 15?
See, I had no clue that the batch has something to do with how much dataset I have 😂😂😂 it’s 29 mins Data
4 to 8 then
Shit.. but what happens when I keep going? It’s low quality model ?