I actually have 1 instance of SSAATTBB using 8 Opus VSTs and 8 VEP ports. Works wonderfully. I might have misinterpreted what you mean by “instance” (VEP instance or Opus instance).
… and yes, port 1-8, channel 1 routing in Dorico.
OT: I’ve also rediscovered Voices of Opera and although they don’t have word builder functionality, they are quite nice as soloists on “ah”.
yes you can do it that way, though if my memory serves me correctly, it used to be problematical in Dorico so I got in the habit of using a separate instance for each part and route all to port 1.
Yes I meant one Choir instance in VE Pro with 6 Opus plugins loaded the first 4 for SATB (Diamond) and the other 2 for Women and Men Choir (Gold). All VE Pro outs routed to MIR. In VE Pro routing to port 1, channel 1, out 1-2, port 2, channel 1, out 3-4 etc.
All Opus plugins with Wordbuilder loaded with the full text for the piece. Played through with Learn to stay synchronized with Dorico. In Opus all internal routing at default. So Opus 1&2 with channels 1-14 channels for the combined multi with WB. This works but at least for me with regular hicups. At least once in a daily session VE Pro will crash which it never does when I do not have the choir instance active in VE Pro. Maybe CPU related.
I’m quite pleased for the most part, but I’ve discovered something that is rather annoying.
It doesn’t do well with “Alleluia” or “Amen.” For starters, anything with a diphthong, like the final syllable of Al-le-lu-ia, it splits it into to equal parts (ee-ah) over the duration of the note it’s attached to. If the final note is a whole note, I get 2 beats of “ee” and 2 of “ah.“ And with Amen, it pronounces the first syllable with a long A rather than Ah-men, which is how most of us would like to to do. I was going to ask if any of you had experienced similar issues and if you knew of any work arounds. I tried various phonetic spellings of alleluia, but it didn’t understand or recognize them. I have to assume it will get better with time. Thoughts?
London Voices joining the Cantai roster. 31 January 2026, Richard deCosta @turingopera announced:
When I started Cantai, the goal was never just to build another “plugin.” It was to bridge the gap between a composer’s manuscript and the breathtaking reality of a world-class vocal ensemble.
To do that, we knew we had to work with the best in the world.
I am thrilled to finally share that London Voices is officially joining the Cantai roster.
If you’ve listened to a major film score or a premier operatic recording in the last few decades, you’ve heard them. Their precision, their power, and their unmistakable blend are the global gold standard. Now, we are capturing that legendary artistry to build the definitive choral library for Sibelius, Dorico, and MuseScore Studio.
We aren’t just sampling notes; we are breathing the musical intelligence of London’s finest singers into the Cantai engine.
This is the sound you’ve been waiting to hear in your studio.
We are currently in the laboratory with the London Voices team, and I cannot wait to show you—and let you hear—what we’ve been working on.
The future of choral synthesis is about to sound a lot more human.
:::: The wait is nearly over @everyone — we have dates. :::: Cantai is officially landing: :: Cantai for Dorico — April 30 :: Cantai for Sibelius — May 30 Both releases ship with local phonemization and rendering — meaning faster turnaround, more reliability, and a smoother experience all around. One license per platform (Dorico and Sibelius are purchased separately). Pre-orders are open here: https://cantai.app/preorder_dorico_sibelius Cheers all and thank you all so much for your continued support! Richard
Good to hear that Dorico version is coming up soon!
Just feel weird that for a very, very early supporter like me that purchased the lifetime license, waiting mainly for using with Dorico, I paid more than the current Dorico lifetime license offer. Am wondering what is my benefit as a early supporter. I’ve not even received my license for Musescore yet(though I don’t use it for anything meaningful). Anyway, hope Cantai can move forward fast to support more languages. I am looking forward to using it seamlessly with Dorico to create more Mandarin sacred and gospel songs!
I paid $19.99 for a month of Musescore Pro, then cancelled the subscription. I have a month of direct access to Cantai with 180 minutes a week of rendering. That experience encouraged me to get the early Dorico license. I had some surprisingly acceptable results with Cantai. Combined with the awesomeness of Dorico, I’m quite optimistic.
Are early (I mean very early) funders going to get an email/download link etc.? Pay structure has changed, how does that affect early funders? I support you, bought into it early but just want to know where I stand.
To clarify: castration was always a violation of canon law, and a mortal sin. Self-castration was banned by the Council of Nicea (325), which is about as “always” as one can get. The problem was that if some poor child appeared with a beautiful voice and no testes, it was a kindness to get him a job, which meant there was a financial incentive. As early as 1748, Pope Benedict XIV tried to ban castrati from churches, but ran into too much opposition. Castration became civilly illegal when Italy was unified (1861). In 1878, Leo XIII prohibited the hiring of new castrati. In 1903, Pope Pius X’s Tra le sollecitudine mandated that high parts be taken by boys, and that was the end of that.
Bringing this back around to our expectations for Cantai, as one of the early investors I’m eagerly awaiting the Dorico version this spring (). I’m sure it will be a cut above the other options for computer realization of vocal music.