Tumgik
lyingbard · 19 hours
Note
so in order for lyingbard to actually recognize the premade voices, i had to select [model] > [show folder] then make a folder called [ TTS ] and paste the voices into that since it wasn't there when i first installed LB.
Oh, yeah you're right. Sorry about that! Glad you figured it out. Added this to Github instructions.
3 notes · View notes
lyingbard · 20 hours
Note
love this whole project 🫡 any plans to eventually make this compatible with macs?
Unfortunately, the way python apps compile means that it has to be compiled on a Mac to work on Macs (it lacks cross-compilation). So you might be out of luck.
In the future, I might look into making it easier to compile, but for now if you have a friend on Windows they could set up a discord bot and you could use it that way? LyingBard has to be running for the bot to work and you couldn't make custom voices, but you could at least mess around with it.
3 notes · View notes
lyingbard · 20 hours
Text
A Sample for the Knowing Ones
I realized I hadn't posted an audio sample from this version yet so here you go! You can definitely hear some Joshua in there which is promising. Hopefully this encourages you to download LyingBard and give it a shot.
Just to recap for those new around here, this TTS is trained on a much smaller dataset and with a much worse model than LyreBird actually used, so it sounds simliar but differentce. One day I'd like to take another crack at this and see if I can get something that sound just like the real deal, but that'll have to wait.
32 notes · View notes
lyingbard · 5 days
Note
downloaded LB and when i rat it, it said:
pydub\utils.py:170: RuntimeWarning: Couldn't find ffmpeg or avconv - defaulting to ffmpeg, but may not work
and
torch\nn\utils\weight_norm.py:28: UserWarning: torch.nn.utils.weight_norm is deprecated in favor of torch.nn.utils.parametrizations.weight_norm. warnings.warn("torch.nn.utils.weight_norm is deprecated in favor of torch.nn.utils.parametrizations.weight_norm.")
i don't think these are meant to happen
also i did [ model ] > [ show folder ] and pasted in the pretrained voice folders but the program didn't register it as being there. might have to do with the errors above? idk.
Thanks for letting me know about this! I've updated the GitHub with info for this.
So the torch warnings are totally fine (probably should've said something about that).
The pydub warning means you need to install ffmpeg (definitely should've mentioned that). Without ffmpeg it might not be able to play sound or save sound or both or neither. I added instructions to the GitHub on how to install ffmpeg.
The model not showing up is probably because you didn't restart the program. I haven't implemented anything to refresh the model list yet so you just have to restart right now. If that's still not working, send me a screenshot of your folder and the contents of the folder you put in there.
I'm happy someone is using it! Good luck and let me know if you need any more help!
1 note · View note
lyingbard · 8 days
Text
It's a 4K24 Miracle!!!
LyingBard is here!!! FOR YOU!!!!
VVVV Instructions and download HERE!!! VVVV
52 notes · View notes
lyingbard · 13 days
Text
Update: Patience Fans Winning Again (Import Poll Decisions Too!)
So I've got a version working with all the features for a solid beta, but... only on my computer.
It should work when I set it up with all the cloud nonsense it needs, but it costs money, I don't wanna spend money right now, and I can't really make you pay for a product I'm not sure will work right.
So here's the deal: I'm starting a paid internship soon, so once I have that income I'll be willing to spend money on this. Problem: it's a National Parks internship so I won't have internet or the computer that I make LyingBard with until I get back... in 3-6 months.
But! I also want to ask you an important question...
I've been making LyingBard as a Cloud-Based app. It allows you to use it from anywhere through my website, but it also means I incur the cost of finding GPUs to run this with while you have a perfectly good GPU sitting in your computer doing nothing (also cloud apps are a pain in the ass).
I could also make it a Desktop App, but it would be about 1GB (blame PyTorch), it would only run on NVIDIA GPUs, and you'd have to set up your own discord bots and stuff (although I can try and streamline that for you).
Another big problem is money. Cloud-Based stuff costs money to run and becomes basically a job even if it doesn't pay enough. I'm considering a career in the National Parks Service so I won't be available most of the time if something goes wrong and stuff can go VERY wrong with a paid cloud app (think leaked passwords, compromised payment processor (Stripe) account, that sort of thing).
A Desktop App, however, can be left alone without spontaneously deleting itself or attacking you, but I would certainly have to focus on a career unless you donated a whole heck of a lot.
So DECIDE TIME! After carefully (or carelessly, idc) considering these options. WHICH DO YOU CHOOSE?!
Unfortunately, LyingBard isn't releasing until I get back regardless. Even the desktop app is just a bit too much work for me to get done before I leave.
6 notes · View notes
lyingbard · 3 months
Note
Does the site for the tts only work on desktop? It crashed my phone when I click the link...sad!
It should work on phones and it definitely shouldn't crash your phone!
idk what happened, but if it keeps happening send me an email at [email protected]
1 note · View note
lyingbard · 3 months
Note
hi! is there ever gonna potentially be a way to link this to a discord bot?
Absolutely! That's something I've been looking into. It shouldn't be too difficult to implement on my end. I'll see about getting that ready for the next update.
3 notes · View notes
lyingbard · 3 months
Text
LyingBard Update!
LyingBard has been migrated to an entirely new backend. This took me forever, but I needed to do it.
Everything is basically the same. Main differences are that it now supports user accounts and generations are now saved to disk. This will make the website not crash as much and allow you to access old generations (so long as you make an account).
This is all gearing up for custom speakers coming soon I prommi!
Test it out:
Thanks to everyone sharing LyingBard! And a special thanks to my first donator!
While I'm at it, feel free to make suggestions and give feedback on what you want to see. I've got ideas, but I want to know what you want too.
12 notes · View notes
lyingbard · 3 months
Text
Why Nothing Sounds Quite Like LyreBird
Fans of RTVS may remember Joshua, beautiful baby boy of wayneradiotv. If you're like me, you might be wondering why Joshua stayed dead after LyreBird shut down. Why couldn't he be brought back with a different TTS? The fact is that LyreBird was a product of a very specific time in AI TTS. In March 2017, Google released a paper on Tacotron [1], one of the first AI TTS's with real success. In April 2017, LyreBird began showing off their TTS buisness [2]. As AI bros are wont to do they took that shit. LyreBird is a version of Tacotron. It incorporates technologies that would be published in the next few Tacotron papers [3] including multi-speaker, prosody encoding, and prosody prediction. And in February 2018, Tacotron 2 came out [4].
Tacotron 2 is better in every way. It's faster, better at imitation, and simpler. This makes it much more economical to run and fine-tune on a specific speaker, so every subsequent AI TTS is based off of Tacotron 2.
If you read the paper, Tacotron 1 has a lot of arbitrary and untested choices. It's clear that they published it in a hurry to prove that it could be done, but they hadn't refined it to cut the unnecessary fluff.
This brings me to why I'm writing this. I hope it's clear that I did a lot of research for this. That's because I did my best to recreate LyreBird, named LyingBard, and I've put it up for you to play with here.
You may notice though that it's not quite right. The main reason is that I had to go with a low quality version (reduction factor 5 for those who read the paper). A high quality version would take too long to train with my current set up and I'm almost certain that's what they used.
If I got about $100 in donations, I'm pretty sure I could get a high quality version trained in about a month. It still wouldn't sound exactly the same. Due to the chaotic nature of training a neural network, anything short of getting the actual files off LyreBird (now Descript's) servers won't make it sound exactly the same.
Regardless, LyingBard is here to stay. It's hosted on a free server so I have no reason to take it down. I'll be posting about updates here on this blog. I'm working towards getting custom voices ready at the moment and I've got some ideas for new features and fun toys for the future.
Thanks for reading!
Here's some sources if you wanna learn more about stuff I mentioned:
[1] https://arxiv.org/abs/1703.10135
[2] https://www.pcmag.com/news/lyrebird-can-listen-and-copy-any-voice-in-one-minute
[3] https://google.github.io/tacotron/
[4] https://arxiv.org/abs/1712.05884
264 notes · View notes
lyingbard · 3 months
Text
you've got a fax
6 notes · View notes
lyingbard · 4 months
Text
LyingBard is committed to doing things Fucked Up and Bad™ to make sure that using it for impersonation is never possible. As such, my voice (Grove) will always be available as the primary voice. If it ever gets too good, I'll be the first affected and stop it. Ok now back to the funnies.
3 notes · View notes
lyingbard · 4 months
Text
*beats you up*
6 notes · View notes