Trying to sync Dorico 5 to Nuendo 13 via TXL Timecode plugin - no joy yet

There is a thread in the Dorico forum that shows some users have had success in doing this on Windows 10/11 with Cubase as the slave.

However the sychronisation dialogue box on Cubase 13 is different to Nuendo 13. See shot below:
CUBASE 13

NUENDO 13

These are just the screenshots from the manuals - I also ticked all the other appropriate boxes etc to try and get the sync up to work.

So Cubase 13 has a tickbox for MMC Slave Active whereas Nuendo 13 does not. So far I can’t seem to get any sync linkup to happen when I press play in Dorico and have tried to follow instructions using loopMIDI and The TXL timecode plugin to make things happen.

I would be a bit disapointed if this can’t work in Nuendo as one of the reasons I upgraded from Cubase was that I would not be losing any features by doing so. Not even sure which versions of Cubase I could still use with a Nuendo 13 licence.

Any thoughts on work arounds on this gratefully recieved Thanks.

You need MTC, not MMC. TXL nor Dorico use MMC.

MMC is more about having various wheels/buttons/pots/faders shared between devices. It shouldn’t hurt anything to have it enabled and connected to a MTC MIDI port, but Dorico/TXL doesn’t use the protocol. Unless you have some ‘other device’ in your setup that uses MMC, you can just turn that option off. If you do have an MMC controller (like a BOSS porta studio, MIDI keyboard with MMC transport controls and jog wheel, or something similar), be aware that it can control Cubendo, but it won’t do anything for Dorico (unless you set up some sort of extra software that snoops the MMC and translates it to regular MIDI events bound in Dorico’s command list).

MTC is simply a digital time code shared over a MIDI connection.

Find the timing ‘source’ tab and set it to MTC (MIDI Time Code). Connect whatever MIDI port you are using to send the time code from TXL.

Frame rate and such can be set in TXL. Seems like the default is 24fps, which should be high enough resolution for most of us. Cubendo can automatically detect the settings. Anytime they change Cubendo will throw up a dialog asking if you want it to configure itself to match.

Project Synchronization Setup Dialog (steinberg.help)

Overview…
Setting up Synchronization for a Personal Music Studio (steinberg.help)

1 Like

Thanks that is very hopeful - this was my first go at this so I probably have not read your posting closely enough. I’ll take another look tomorrow. Does anything have to happen with Doricos Port or Channel settings - i left both set to 1 I think.

As i said I’m not using Cubendo but Nubendo but Tomorrow I’ll download a Cubase 13 trial and check that set up out more.

9Brings back memories of the late 1980s syncing tape machines via XRi hardware to good old Voyetra on a PC :grinning::grinning:)

It should be the same or very similar between Nuendo and Cubase.

No need to get a Cubase trial if you already have Nuendo.

Load TXL in Dorico.
Enable MTC and set it to use a virtual MIDI port.
Connect this virtual MIDI port to the MTC input of Nuendo.
Set Nuendo to slave to the time code.

Check that first link you posted in this thread for a more detailed walkthrough.

Thanks Brian - today I got everything going nicely in the cubase trial version which was no big deal to download. Tomorrow I’ll have another go with Nuendo focussing more on getting MTC going right.

UPDATE
Yep got it working roughly with Dorico and Nuendo locked together now - so GREAT. Still gotta check out things like any frame offset needed etc.

Really opens up working simultaneously in both applications :+1::+1::+1:

Best wishes and Thanks.

Working with TXL plugin is going well. I got the dorico tempo map working within Nuendo and am expanding my piece incrementally between Dorico and Nuendo.

One thing I do wonder about is how does the ability to sync affect the approaches to final mixdown. Accepted views are that Cubase and Nuendo provide the full breadth of options for effects etc. at a mixdown point - so this suggests import of Dorico tracks either as audio, midi, or music.xml for final finishing.

But are there ways of keeping the Dorico composition gestation process open for longer and not locked down. For example, can one try direct routing of individual Dorico tracks into more than one stereo channel on Cubase/Nuendo mixer (not sure if Dorico can do this well - and possibly a latency cost in trying this). I notice Some Blue Cat apps like Connector focus on shoving audio/midi around the system but have not really tried using it.

Be interested to hear about any approaches to this. It does seem that the Sync approach does challenge the Score to Daw and Daw to Score approaches a wee bit. It would be great to get a nice mix balance between the channels in both Dorico and Cubase/Nuendo, and nicer to do this in Nuendo as the Dorico mixer seems a little less fine grade at times.

(I recollect mucking around with Sibelius and rewire in Cubase years ago but i can’t remember using more than a basic piano track in Sibelius).

For me it mainly comes in handy for making pure audio tracks in the DAW to go with a score that’s pretty much done and fairly well mixed and blended in Dorico itself. Sometimes it comes in handy for transcribing stuff from the audio world into a score/parts world.

It’s great for when I want to use outboard gear along side VSTi plugins.

Another time it can come in handy is any other time you want to get real time Note Performer audio output sounding through a tracking DAW mixer for some reason, as that sound engine only works in Dorico/Sibelius/Finale. I personally haven’t invested too much time experimenting in the many new ways NP can host advanced sample libraries, but those who do might find it highly desirable to get the mix it produces out of Dorcio and onto their DAW mixing desk, with the added benefit of the transports being synced.

As far as I know Dorico can only mix down to stereo. It doesn’t have a way to set up more outputs than 2 into the ASIO backend. Depending on your system, you ‘might’ have luck with something like reaStream hosted in Dorico mixer slots to get ‘audio streams’ diverted from Dorico mixer channels over to a DAW. For me there’s a considerable amount of latency in my experiments, but it might work for some? As far as I know, reaStream is VST2 only. I haven’t invested much time trying such a thing but it ‘might’ work for some people.

It is possible to set up virtual MIDI ports, and use it to route staves from Dorico into your DAW of choice, and host your instruments there instead of in Dorico. Is it worth it? In general, probably not; however, I can think of a few scenarios where that kind of real time hosting/mixing while composing in Dorico might be useful.

Personally I just go with a bidule plugin hosted directly in Dorico to get at such abilities. Examples are things like experimenting with multiple plugins/instruments layered together, or building hybrid monster orchestra templates (mixing and matching stuff from multiple instruments).

I.E. Say you’d like to have a stave from Dorico use arco from HALion for faster passages, something from Opus for acro on slower passages, something from Kontakt for short bows, and a pizzicato from your Yamaha MX keyboard…

I.E. Maybe you want to ‘layer up’ a spiccato from HALion with a sustain from a fiddle sound in ARIA to give it some more ‘bite’ on the attack, and also throw in some filtered out overtones from a viola sound in a Roland keyboard to ‘invent’ a new string sound.

Dorico can channel bounce within the same plugin or MIDI port, but not yet among different plugins. Generally we get around this by simply using a new player/section/stave. It works, but stopping play back, building a new stave, moving notes around, etc…isn’t something you can easily ‘tweak and try’ in real time in search of a sound that works for your arrangement.

By diverting a single player/section/stave to a virtual MIDI port, and into a DAW with a lot more real time routing capabilities, you could effectively pull off actual ‘plugin bounces’ from a single stave.

I’ve been using bidule for this sort of thing since Dorico 1 (and unlike the external DAW approach, you can quick-render flows directly from Dorico)…but if you don’t have bidule, and you do have a nice DAW…you can get into some fun sound design activities with the MIDI output directly from Dorcio, in real time.

Sometimes it obviously makes more sense to just export a MIDI file and go to work in the DAW, but yeah, there are times when it’s convenient, and fun, to play with your sounds in real time without tearing yourself too far away from your Score in Dorico.

Fabulous answer thanks Brian - covers everything I was thinking about and thanks for the quick response. I’ll probably have a wee fiddle with the Blue Cat Connector and see if it does anything for me. TXL does a great job with the sync. Does feel like we get a glimpse of the ‘broad sunlit uplands’ of a closer integration between Dorico and Cubase/Nuendo. I feel sure it is a priority for Steinberg from all they have said, and they have had surveys out on this before - just hope it might be there in the next full version releases.

Almost all of the time, when you get to the mixing stage (no more editing / changing parts / etc.) you want to render EVERYTHING into audio files, and preferably only use one DAW / playback device for the mix. In this case, Nuendo, as it has better functionality for mixing.

We have standards. NARAS published the Grammy Producers & Engineers delivery standards years ago. You can find them online, if you want to see how the pros in the US do it. Typically: Broadcast Wave format, three copies in two or more different devices, like hard drive or optical disc. That goes for final delivery as well. And we also always have to have two backups plus the working copy at all times.