-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upsampling in parts? #133
Comments
I'm not one of the project's creators or maintainers, but I have been using it a lot and, from what I understand, this is totally possible. You would just separate your final top-level
And then you would save your I suspect there will be a sonic "discontinuity" at the breakpoint so it might make sense to build in some overlap -- I'm not 100% sure that will work but it's what I would try if I was doing this! |
Sadly, this results in an error for me when I split it just before the upsampling oneliner. The oneliner looks like this: This is the output I get:
|
@samuel-larsson, I'm not 100% sure what's causing this error for you, but it might be interesting to throw a In the meantime, here are some updated splitting/truncation functions that have been working for me; it might be worth pasting these into your Colab and trying them:
|
@robinsloan I was able to run your code without error (at least the zs_part1), but it didn't work as intended - Jukebox upsampled the full length sample anyway instead of just the first half. This is the code I run:
Maybe it has to do with this part of your explanation that I don't quite understand:
How can you "save" these? I didn't find any files named that way. Sorry if this is a super noob-question, but I don't know much more than the basics of Python. Appreciate your efforts, best regards! |
@Broccaloo Ah, sorry for the confusion; I always save my You know, at the time I wrote the little snippet you quoted & used, I did not quite understand the entire
Following that, if you |
EDIT:
But then I changed the sample_length_in_seconds from the original 60 seconds I generated to 30 seconds to reflect the new length and it worked. Thank you so much! |
I'm glad it worked! In my script, I don't have to change the Ah, okay -- I just actually looked at my standalone upsampling script and noticed these lines:
So, adding those might accomplish the same thing as resetting the If you produce anything interesting, post a link! 😝 Here's my Jukebox-powered EP. |
Good Days Sirs, After finishing this running, I will rename folders level 1 and level 0 to start to upscaling to level 1 and 0 part 1 with top_prior_raw_to_tokens = 64 that already broccaloo test for part 1. Thank you very much for share your knowledge. 🤖🎼🎹👌🐼🥦👨💻👩💻🎼🤖 |
top_prior_raw_to_tokens = 32 The following error message appear at the moment to upsample PART 4, please help ? Sampling level 1
|
@leonardog27, I don't know if this is the root problem, but in the parts where you set If it was me, I would get this up and running with just two parts before expanding to more. Once you have a pattern that works, it's easy to expand, but when you're doing a bunch of different/new things at once -- with more code -- it makes it more difficult to figure out what/where the problem is. |
Hi @robinsloan |
Can I let's say, upsample half of the generated sample on one day, and then continue from the checkpoint and do the other half on the next day?
The text was updated successfully, but these errors were encountered: