Maybe, i'm mostly busy with studiesI wonder if this will get updated by the time Miku V6 gets an official announcement and release date. =w=
Maybe, i'm mostly busy with studiesI wonder if this will get updated by the time Miku V6 gets an official announcement and release date. =w=
For the time being no. Sorry.Sorry to bother with the nudge, but have there been any update in development? I recently got v6 with Nurse Robo and I'm worried to downgrade the version in worries that she will stop working. I understand being busy with studies, and feel free to take your time, I just wanna know if there has been anything :3

I think I kinda made something like this a while ago but i haven't updated it so it likely doesn't work on the new version, but i could look into updating it.I was thinking, what about adding user dictionary support too? Some dictionaries, like the one from Ruby, can’t be used anymore in VOCALOID 5/6, and then you could just can use English phonemes to make one, you could add support for all the current VOCALOID languages, Japanese, English, Korean, Chinese, and Spanish, and if writing the dictionaries directly in the editor like in V4 isn’t possible, maybe just create them outside the editor and then load those dictionaries into the editor, this would be especially useful for Chinese and Korean because it would let you create a dictionary for writing in Hangul for Korean or Hanzi for Chinese, or even make a dictionary that lets you write in a completely different language based on the voicebank's phonemes, like using a custom Thai dictionary with a Japanese voicebank
Mmm, that makes sense. Maybe a solution for the suggested phonemes when writing could be to simply not select any of the suggestions and let the engine fall back to the dictionary instead, and If the user doesn't select a suggestion and the word isn't in the dictionary, it could just default to the first phonemes suggestion, or maybe make a shortcut key to apply a dictionary after writing the lyrics, like you load the dictionary to the engine and it only runs if the shortcut key is pressed, tho, I feel that even like this, it would be hard to implement. I made a small udc manager a month ago to read udc files, but it works just like a phoneme conversion pluginwhen it comes to direct integration of custom dictionaries right into V6's dictionary handling... I wouldn't say it's "impossible" but i'd say it would be fairly difficult at least.
The main issue is that vocaloid 5 and 6 don't handle the dictionary at the editor level, they handle it at the engine level. when you type lyrics and it gets the possible phonemes for it, Vocaloid 6 directly requests the lists of phonemes from the C/C++ synthesis engine, which is inaccessible to me due to being natively compiled. All I can do is likely intercept calls to it in order to try to load alternative code paths when it tries to grab the phonemes, but it would be a fairly demanding task i think to implement
at the very least the ability to trigger a specific job plugin when a shortcut key is pressed is one thing that's planned, and applying a specific dictionary based on shortcut key is also likely the easiest way to go about it as it would avoid conflicting with vocaloid's core implementationMmm, that makes sense. Maybe a solution for the suggested phonemes when writing could be to simply not select any of the suggestions and let the engine fall back to the dictionary instead, and If the user doesn't select a suggestion and the word isn't in the dictionary, it could just default to the first phonemes suggestion, or maybe make a shortcut key to apply a dictionary after writing the lyrics, like you load the dictionary to the engine and it only runs if the shortcut key is pressed, tho, I feel that even like this, it would be hard to implement. I made a small udc manager a month ago to read udc files, but it works just like a phoneme conversion plugin
and what about adding custom breath audios? The male and female breath audio files are in the "Explib/brrfr", and if you manually replace the audio files with others with the same name, you can have custom breath sounds. Maybe you could make a path similar to custom backgrounds and add the custom breaths linked to voicebank compID, and/or style presets, and on that topic, I think I mentioned this at one point, what about adding custom backgrounds to style presets, too? Since the custom singer option is gone and the only way to get a custom singers now is through the style presets, I think it would be cool to have a custom backgrounds based on the name of the singing style or the name of the vsstyle file, the logic would be, if there’s no custom background added (for example, there is a custom background for "Ruby_Natural", but not for "RubySoft", which would be a custom style preset name), then the background defaults to the standard background for "Ruby_Natural" based on her compID or if "Ruby_Natural" does have a custom background it defaults to that instead, but , if "RubySoft" does have a custom background, it replaces the background that "Ruby_Natural" has for the "RubySoft" custom background insteadat the very least the ability to trigger a specific job plugin when a shortcut key is pressed is one thing that's planned, and applying a specific dictionary based on shortcut key is also likely the easiest way to go about it as it would avoid conflicting with vocaloid's core implementation