1- Too CPU demanding
2- It can´t sing a 3 syllable word in a bar note?!
3- If I shorten a note the word should be sang faster to fit the note
4- There should be a way to insert a whole phrase faster than clicking in a note-enter a word-click another note-enter another word-etc. Maybe dividing words with a comma or any symbol or a step entry method.
5- A way to add phonetic sounds
Try entering a whole line of words on the first note.
Feature limitations maybe but not bugs.
In brackets. [k ew l]
yes, did it but it fits one word per note (or sort of) but maybe that´s not what I want.
not working for me, only silence with anything I type in brackets.
Strange, it works for me.
sorry, with single vowels or with a space between consonants I get some of what I need, thanks.
CPU usage is off the charts for me. Makes it unusable for now. I tried it in an empty project with the same result.
I use Emvoice One but I am interested in this technology, so for those who have tried it…
…with Emvoice, it is one syllable per note and I can’t imagine it would be different for anying like what I am currently using.
There’s also another issue when trying to divide a word into multiple notes. It will literally try to fill in that one word on every note following it even when the number of separations is less than the amount of notes available.
The software is in beta.
Emvoice just sings “la” when there is no syllable available, for a given note
sure, that´s way I´m trying to contribute to make it usable remarking things that are not working as expected, at least for me that been working in other similar plugins.
There is another thread in this forum, with a screenshot of a single 3 syllable word on one note.
I cannot see how that would produce anything usable other than monophonic monologues.
A single instance of Omnivocal with the session stopped and nothing else happening hovers between 33% and 50% of my resources. Confirmed this with a blank session, a template from C14, and a brand new template in C15.
Resource usage on this plugin is excessive
The resource requirements depend heavily on the ASIO latency. With a buffer size of 512 samples, they are quite low. With a buffer size of 64 samples, the plugin completely maxes out my Windows system. Of course, this only happens when the plugin is calculated in real time, i.e. when monitoring or record arm mode is active.
Your findings are not the same as mine. My system was set with a 512 buffer, with only the Omni vocal plugin in the session and fully stopped. Not playing, not synthesizing
just having the plugin in a session shoots resource usage up to 50%