Hello all! Currently using Dorico 6.2.30.6245 and Cantai v3.0.0 … A few issues …
Whenever I re-open a project that is in Latin, Dorico/Cantai keeps defaulting and re-rendering to ENGLISH on a Latin composition; not a big deal, all I gotta do is CMD+4, go to one of the Cantai voices and re-click. Any idea why it keeps changing to English?
The dreaded “TASK PIES”!!! Sometimes the Task Pies will keep spinning and sometimes when the taskpie is done, the Cantai voices will not sing OR play (that lovely bass and droney LOUD organ rhino yell. A restart usually fixes it until I have to restart again.
Any way to go into some kind of setting to change that lovely bassy and droney LOUD organ rhino yell that loudly plays while the inputting notes? Is there an option to control the volume of that lovely sound as turning DOWN every channel of my Cantai tracks while composing and then having to turn em UP every single time make a happy experience it does not.
FEATURE REQUEST … for compositions with multiple languages, any way for future versions to use some sort of text tool to have Cantai to go between languages?
Great work on Cantai and we are LOVING the Dorico implementation. Keep up the great work!
no 1. has been pointed out numerous times already and is an acknowledged bug. As you say, it’s only a problem if you forget to change back to Latin and wonder why the project is re-rendering. I’m sure that’ll be sorted out for the next update
no. 3. If there is no text yet set to the notes, they play back with an “ah” after you’ve entered them. I fear that if you don’t like the “rhino yell”, you’ll just have to turn down the track volume. This should be done anyway in Cantai as the default is far too high compared to most other instruments.
no. 4. This is on the roadmap, I believe. As things stand, with one work I needed to mix Cantai and SynthV to enable both English and Latin to be used in the same project.
No 1 … is not a huge problem, just a tad concentration breaking.
No 2 … Task Pies still getting stuck with Dorico Quit/Computer Re-start being needed … I keep getting the below and I can’t Force Quit. Also, getting the Steinberg Activation Manager Blues as well <<< weren’t Dorico users supposed to be able to have the ability to use Dorico/Cubase when SAM (Steinberg Activation Manager) and the servers were having a panic attack? The attached Screenshots are obviously a Dorico/Steinberg thing, but I included them in case Cantai’s Media Engine (if that is what the error that I am getting actually is) may be butting heads with Doricos.
No 3 … I understand what you’re saying in “that is the way it is”,… but having your workflow and settings constantly having to move channel volumes up and down … I GET IT! I am a spoiled brat in a world where Cantai is doing AMAZING THINGS in a way composers NEVER had at their finger tips before. I am SO GRATEFUL for what Dorico and Cantai can do, it is beyond my wildest dreams. Having admitting a big baby I am LOL, I would really be nice to not have the Rhino-Submarine sound. If it can be done, I’ll be happy. If not, I’ll still enjoy composing and arranging in a way that no one else in history never could and still not be as great as Bach or Mozart
No 4 … I will PAY for an update to keep TuringOpera to continue doing such amazing work.
Just a hunch. If all was working well before this started, rebooting and force quit your login items like Home and UAD Meter & Control Panel before starting Dorico. Also, always check Continue to Wait when audio engine is taking longer than expected.
My hunch is that UAD Meter & Control Panel is the issue although it could be macOS Home. If Dorico loads without having UAD loaded, then there’s an issue with that app. Make sure it’s up-to-date if that ends up being the issue.
no – all the projects I’ve exported with Cantai v3 (ten in all) have worked fine with one exception. in this case the entire last 6 of 38 minutes were mysteriously truncated but for some reason, the following day it also worked OK.
This doesn’t happen to me on a regular basis but I do occasional have fully rendered voices that simply drop out or never enter to begin with. I typically save and close the project and then reopen it. This solves 90% of those issues.
For the other 10%, I alter and return the notes for the missing voice to force re-rendering. Might want to check your Cantai cache size, too. Yesterday, I had a cache grow from around 5 MB to nearly 13 GB while editing a single 94 measure piece. Once it got so big, all kinds of junk started happening including missing voices on playback and missing voices on exporting audio.
Also be sure that all voices have finished rendering before exporting audio.
I had a project yesterday where mysteriously the tenor and bass simply didn’t sing having worked fine previously. Normally I find a rerender can be triggered just by making a dummy edit and that worked on this occasion as well
@dko22, Another thing to try in those cases is to clear the cache. (I’ve done the dummy edit thing, reset the voice, restarted, and rebooted — all with various degrees of success at various times!)
clearing the cache means re-rendering all the projects so I’d only do that as an absolute last resort – after all it took about 45 minutes to render one of them! But of course it’s a valid approach if you’re not too far advanced with rendering a series of projects.
Indeed. Fortunately, the results I get are usually worth it, but it does take a good bit of time to render bigger works. A 45 minute or so rendering time has happened to me, also. However, once done, it works well.
I have had that happen a couple of times when having a file open for along time with a lot of edits (either vocal or accompaniment). It happened three times today. The first dummy edit didn’t work, the second didn’t work but the third one did. Who knows?
As lovely as “auto” and “AI” can be with Cantai, I do believe there needs to be a master interface with the ability for the end user to force whatever to happen be it re-rendering or changing phonetic sounds, etc. This would certainly save a lot of time on the part of the support team fielding scores of pronunciation issues as well as rendering issues. With an accessible macro API, it might even fuel third-party functions we have yet to consider.
Here is a setting I wrote of Praise to the Lord, the Almighty. I posted it many months ago to show off Noteperformer 5.0 in Dorico. Here it is with Cantai’s Ottetto choir. I didn’t change one word-this is straight ‘out of the box.’ The long ‘Ay-men’ is ok in this context. Surprisingly, it didn’t take too long to render.
I used NP5.0 with BBCSO:
Trpt. 1
Bass Trombone
Timp/Glock/Snare
SSO 2024:
Bone 1
Synchron PRIME:
Trpt 2/Tromb 2
SSO 2024:
Trbn 1
Berlin Free:
Trpt. 3
GPO5:
Pipe Organ-Hauptwerk All Stops
Like others, I sometimes experience a drop of a rendered voice in Cantai. I thought maybe this was just Cantai but I’m beginning to think there is an issue in Dorico.
Scenario: SATB choir with Hauptwerk organ accompaniment (the real Hauptwerk, not the Halion “Hauptwerk”)
I left the project onscreen for several hours without working on it. The Soprano Dorico voice dropped out completely. Even with re-rendering with a dummy edit or to restart that instance via Cantai did nothing to bring it back. Also, the Hauptwerk (controlled via Vienna Ensemble Pro 8 Server) dropped out about half way through the work.
The only way I could get this voice and instrument playing again was to close Dorico and reopen the project. I’m wondering if Dorico has a bit of a memory issue or leak. Only a max of 14% of CPU use was active and memory was only used up to 35% on a 32GB Mac Studio M2Max. I failed to run Dorico diagnostics before restarting…(not a smart move).
DAY TWO (Saturday & Sunday, July 11 & 12, 2026)… When I open Dorico, Cantai is stuck on “Waiting for Rendering Engine”.
I’ve QUIT Dorico, and RESTARTED my Mac many times. I have no Anti Viruses or Firewalls … iLok & SAM working fine so it’s not an Internet connection issue.
Cantai/Turing Opera did reply within hours, but I’ve been playing/directing choirs all morning/afternoon/evening and I’m home now. Turing Opera Support asked me to un-install and re-install, but they gave no instructions.
Since Cantai is not an App that lives in your Application Folder along with an “uninstall” file (nor is there one within the DMG download), might anyone here know how to properly do so without causing any issues?
The MuseScore version of Cantai is working fine … Dorico version is not … So I’ll have to export via XML/mxl or whatever, and re-open in MuseScore to actually have Cantai work which I hate doing, but the Dorico version (while having many more Cantai voices) has been a hot mess.
Also, Dorico’s still does not export XML/MLX correctly … My work around is to export a Dorico score to XML/MLX, then open it up in MuseScore, then export to XML/MLX and THEN the XML/MLX export of the Dorico score to MuseScore will work/render fine in Cantamus or AceStudio (yup, I’m having to bypass Cantai altogether) or Logic. Not sure Will Dorico version 7 fix the XML/MLX export issues? This was the same for my entire life of working in Encore/MusicTime where I would export to XML/MLX, open in Finale and then exports would work correctly in Logic or Dorico.
interesting and I find the instruments well rendered-- but to be honest, I wouldn’t use Ottetto for this kind of music – the original choir gives more of the weight required for jubilant music of this nature. I have a couple of sacred works where I’ve mixed in the (now much improved) original choir for things like Dies Irae which simply sound silly with 8 voices. Taken on the its own merits and used appropriately, I find Ottetto pretty impressive.
Thanks. You are correct. I re-rendered it with the regular male/female choir voices and it does sound much more choir- like-a better fit for a work like this.
Cantal Support replied to me within minutes yesterday and talked me through the un-install via back and forth emails until I got it settled. They are top notch!
The uninstall/reinstall fixed the issue and I was able to make my presentation this morning and hopefully will get this contract. Rendering is working better and faster now. Also, Audio Export is now working as well.
I’m back home and am going to work on my M1 Mac Studio (Sequoia) & M4 MacMini (Tahoe) to see if any issues arise.
