No.23813
>>23807List your full collection
No.25802
>>23791I care but I'm gonna be honest V4 still sounds a lot better. I'm also disappointed thar V6 is entirely AI, I miss sample based voicebanks.
No.25804
>>25802I know that Rei is getting a sample based V5 and that V6 still works with pre-V6 sample based voicebanks but idk, I don't think anything will ever come close to the V2 / V3 era of Vocaloid.
I guess in terms of voicebanks being released though we are in a V3 era because V6 has so many wholoids that people only use for covers.
No.25826
>>25802Agreed, pre-AI Vocaloid sounds way better in general. The samples are higher quality.
No.25830
>>25804If they keep the FAN-ding stuff going then V6 might end up with more voicebanks than V3
No.25832
>>25830if they release them in the first place lol
No.25837
>>25826At this point, I'm just hoping they'll focus on fixing the sound quality in V7. There's no reason it shouldn't sound better with how rapidly AI technology has progressed.
No.25838
>>25837I always thought the bad quality was intentional, cause you know, vocaloid was always seen as robotic
No.25839
>>25838It might be, but it's also a product of its time. V6 came out after Kafu and before Teto SV, so the popular AI voicebank sound was still pretty unrealistic.
No.25840
>>25839No wonder V6 is on par with Cevio in terms of quality
No.25841
Funny how these days UTAU sounds as good as Vocaloid did back then and DiffSinger can sound like SynthV if trained properly
No.25842
>>25840In fairness to CeVIO, CeVIO AI did improve the sound quality, it’s only the banks that didn’t receive 2.0 updates that still suffer a bit. The difference between 1.0 and 2.0 is literally just the vocoder.
V6 suffers the exact same issue, it needs a new vocoder which ironically already exists but Yamaha just refuses to implement it for some reason. It’s in the omnivocal plug in that comes with Cubase now iirc. Regardless, if we are going to have V6 until next year (which we do), it would be beneficial that they at least consider implementing the new vocoder so V6’s life span becomes reasonably extended.
No.25843
>>25837Not happening until possibly 2028 which is the surprising part of that.
No.25845
>>25843How do you know that
No.25850
>>25845Iori Yuzuru V6 is slated to release early in 2027, while that still leaves half of 2027, when I was talking to a developer at Mirai last year, they seemingly implied a V7 was still a ways off and that the current focus was continuing to bring over certain features from VXB to the main editor. That’s at least what they could tell me, everything else was just “secret”.
No.25851
>>25850How do people on this site just casually talk to devs and producers
No.25852
>>25851autism and connections
No.25853
>>25851I literally just walked up to the Vocaloid booth at Mirai and asked lol
No.25854
>>23813Just seeing this, sorry lol
Been meaning to take a new photo of both my shelf and a spread of my boxes. It’s not done yet but I’ve also been working on a little secret page for my collection on my site so I can link and post them in that one collection thread later.^^
No.25855
>>25842That’s very interesting about the vocoder. Can’t help but wonder if pirates will just swap a new one in the same way people switched Toriko’s vocoder for a big upgrade.
No.25860
>>25855Who knows? They haven’t realized it’s possible to crack SV2 yet last I checked.
No.25982
>>25860SV piracy still kinda sucks. Your choices are a dicksword keylogger virus or SV Flat which might or might not be safe (I honestly trust the Ruskis who have experience cracking VSTs more than a bunch of dicksword kids though).
No.25984
>>25982As long as DT keeps fighting it, it’s gonna suck. They’ve been the most proactive in fighting it.
No.26631
>>26630I hope they eventually release a patch for V6 that makes the voicebanks not sound like crap
That or V7, but I don't see either happening anytime soon.
No.27329
Is it possible to get rid of the engine noise in v6?
No.27330
>>27329EQ and Compression
or just switch to SV No.27333
>>27330I already use both of those but sometimes you can still kinda hear the engine noise
No.27336
>>26396Wasn’t this demo 2019?
No.27377
I don't expect V7 to be as good as Synth V in terms of realism but i do hope its at least on par with Voisona in quality
No.27972
Interestingly, it seems some of the V6s use the same dataset as their SV counterparts. Gumi being one of them.
No.27973
>>27972Goes to show how strong V6 engine noise is
No.27987
People keep mentioning v7 as if they're making a v7 right now when they've spent the last like 2 years improving v6 and actually getting voicebanks for it. They're probably going to keep improving v6 for the foreseeable future instead of just making a new vocaloid
No.27989
>>27987Yeah, I don't really see a reason yet why they'd jump engines. They had the chance when they were making the Beta studio thing but turns out it was just a plugin and all V6 owners got it for free. The V4 to V5 jump is probably the dumbest one in history but we still got the Attack Release effects that are new and arguably warrants a new engine. Every jump in version had something new to it and I don't think Yamaha has anything in mind yet for V7.
No.27994
>>27987>>27989In fairness, they could be in early stages but I can’t guarantee anything. After watching the presentation on OmniVocal, which is basically a further developed version of VXB exclusive to Cubase, there’s definitely ideas and concepts I can see them carrying over to future Vocaloid VST functionalities. This is especially now understanding what the purpose was. The biggest challenge for what could be their vision is universal daw compatibility. They have easy access to Cubase code and API to develop the features and integration they want, but not other daws.
I don’t know when we could see this version but considering we have V6 developments up until early next year, we won’t see it until late 2027 or 2028 at the earliest right now. That being said, I think everyone agrees that updating V6 and reducing the noise will do a lot in terms of longevity.
No.27998
>>27994>updating V6 and reducing the noiseThat's more or less why CeVIO and SynthV have V2s now. I don't see any signs of Yamaha doing it (for V6 or V7 or whatever), but I'd buy it right away if they did.
No.28001
I personally don't mind V6 sticking around for a little longer, especially if they're willing to improve it, which they are. Compare any of the older voicebanks to the new ones and you'll notice they're lot less noisy. So far I think Miko is their best in that regard.
No.28007
>>28001Knowing Miko is basically some of the objectively best on VOCALOID6 right now is making me kinda excited. Even as the cutest VIPPER she never really got time in the limelight but this could kinda be her chance. I'm rooting for her.
No.28010
>>28009It's still funny to me that instead of getting Ritsu on V6 we got a derivative of him
No.28013
>>27998I wouldn’t be surprised if it’s in the todo list considering it’s one of the biggest complaints. That and more languages, though I’d hope we have some native banks if they launch new ones.
No.28025
>>27998Wait when did Cevio get an upgrade?
No.28034
>>28025A few years back. Not all the voices got updates but pretty much anyone in VoiSona got them.
No.28045
>>28007I'd argue Miku V6 is where they went "fuck it we gotta make this sound good" and it shows. It's one of the best sounding Miku voicebanks in years. Miko too sounds very great and I'm looking forward to whatever they do next.