Skip to content
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

Generate vocals on top of an existing instrumental, or an instrumental on top of existing vocals? #21

Open
iGerman00 opened this issue Jan 29, 2025 · 4 comments
Labels
enhancement New feature or request

Comments

@iGerman00
Copy link

Some commercial music generation services include an option to basically replicate an input audio, then add vocals on top of it.
Would something like that be possible with YuE? This would allow, for example, producers to brainstorm and add vocals to their own music quickly.

Another thing is it would be nice to be able to have a reference for the tone of the vocals, to be able to save specific 'vocalists' in our workflows

@a43992899
Copy link
Collaborator

Yes it is possible without training. We will add it to todos.

@a43992899 a43992899 added the enhancement New feature or request label Jan 29, 2025
@frink
Copy link

frink commented Jan 31, 2025

What about the opposite. You want to add instruments to an existing recording? That would be just as ground breaking!

@migperfer
Copy link

Hi! I'm working on this, but I think that I'm missing some details from the code alone.

The ids vocal and instrumental tokens, can they be the same? Or are they separated?
One example of what I mean:

  • The total number of tokens is 400
  • Vocal tokens ids are below 200
  • Instrument tokens are above 200

@betweentwomidnights
Copy link

me trying to do this by encoding the instrumental and injecting it as the instrumental codebook, then generating vocals step-by-step...

https://github.com/betweentwomidnights/YuE-instrumental-injection

vibe coded as f

so it's a really slop implementation. I have however gotten it to generate vocals...it seems to mostly only want to rap in the current state though. Sometimes it'll produce some really insane outputs too.

I can tell I still haven't figured out the segmentation/context window properly while doing my workaround instead of model.generate()

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants