Thank you for your support! Unfortunately the file is too big…
You are right: When I open the first project (after starting Dorico) it is working fine, when I close the project and I would like to open a second project, I cannot start the playback (Halion 7)… And afterwards I cannot open Dorico again without re-starting the whole computer…
I really hope, you can help again…
Please find the Dorico Diagnostic file in the appendix. It was too big to upload…
Thank you very much for your help!
(Attachment Dorico Diagnostics.zip is missing)
Here is a link with the file: Dorico Diagnostics.zip
I hope you can open it…
Hi @lycalp , thanks for the data.
As I suspected, your crashing issue is different. It is because you have HALion Sonic 7 installed and there is a known bug in the MediaBayServer. For a workaround please read this thread.
Dear @Ulf, dear @Dup
Halion 7 & Halion Sonic 7 were the problem! I un-installed both and now it works perfectly with changing between Dorico 4 & Cubase 12 with Banana Voicemeeter! Thank you @Dup !
Could you please inform me, when Halion 7 & Halion 7 Sonic are ready to use properly? (Without any “workarounds”…)
During this time I use Halion Sonic SE…
Thank you very much and best wishes!
I don’t have Halion 7 & Halion Sonic 7 to test, but sometimes it happened to me when I had vsti problems with Dorico 3, I opened vsti in Vienna Ensemble Pro 7.
What I also do regularly, as I’m not a big fan of keymaps, is to control Cubase as slave via the TXLTimecode plugin and I open the vsti in cubase, which allows me to have more expression, put percussion loops, spoken voices, sound effects,… here is a screenshot of Cubase as slave and play from Dorico:
That looks really interesting…. ! But also complicated…?
I will try out…
… is there a step to step explanation available how to do it in Dorico…?
Should install Timecode Expert or TXL Timecode Plug-in?
quickly because I am teaching today.
I have a pdf summary but not handy. (step by step easy)
You must use TXL Timecode Plugin and install the LoopBe Internal MIDI (midi driver)
already one or two printscreen
- you must have Same frame clock here:30Bps in both program
- Desactivate ( not sure don’t remember now) midi thru in both or in Dorico to avoid midi feedback loop
- The number you must write in Custom Offest is given by the number when you want to start cubase (vertical head) here 00:02:36:00
- put a litlle bit more Host Buffer Size to 512 perhaps in you soundcard configuration
And that’s all
Ask if some problem
Hi Daniel, There has been a lot of back and forth over the years about bringing the two apps closer together, but it appears that this idea is somewhat defunct, and probably rightly so. Dorico should be one thing and Cubase another. They will never have the full functionality of the other; both have their specialities, strengths and weaknesses.
What we need in my opinion, is a ‘bridge’ between the two apps that enables them to be synced or locked together in a really robust way. This would be a game changer. The TXL timecode plugin does enable the programs to run in sync, but tempo changes have to be transferred manually from the master to the slave. I can’t remember whether ‘Rewire’ was similar, but in any case, if we had that type of functionality we could use both programs more effectively at the same time. Passing midi tracks back and forth rather than dragging and dropping might also be part of the ‘bridge’ function, but having the two run almost as one would open up so many additional work flow improvements. We would use both apps to their individual strengths and Dorico would no longer necessarily need audio tracks for example. (Not sure whether that’s in the plans, but it has been mentioned on occasion). Yes, as a consumer you would need to invest in both apps, but the payoff would be so worth it.
I started out with Cubase in the late 80’s with an Atari computer, but switched to Logic for many years. More recently, because of Dorico, I switched back to Cubase, but am still not able to use both apps together in a really convenient way and without a lot of fiddling about. A robust bridge between the two would solve this, so I hope this can give you some insights into what would be (imho) most useful in bringing these two wonderful pieces of software together.
The hint from @Dup with voicemeeter banana works perfectly so far in using Dorico 4 at the same time with Cubase 12!
But I also agree with the comments of @Grainger2001 ! We urgently need an “easy bridge” between Dorico and Cubase software!!!
Now I hope that the bug with Halion 7 / Halion Sonic 7 will be solved soon, so that I can use the newest Halion generation with voicemeeter banana (without any Dorico crashes and needed “workarounds” suggested by @Ulf .)
At the moment I have to use Halion Sonic 3 and it works perfectly so far.
I am really thankful for the help of @Ulf and @Dup! They are amazing experts!!!
Thanks and best wishes!
It’s Cubase sale time again and, although this time I’ll certainly be finally updating my Elements to the latest version, I’m still not sure if there’s a point in going higher currently. Was actually discussing this a bit with @Grainger2001 just prior to his post. As things stand, if you import a MusicXML to Cubase Pro, none of the Expression Map patch changes are recorded so effectively there is no practical way of “finishing off” a Dorico project in Cubase (unless it is something simple like piano or choir without an EM). With Cubase Artist/Elements, the situation is even worse as it only can import MIDI which doesn’t even include tempo information.
Perhaps it is indeed a fools errand that the two should work seamlessly hand in glove. Dorico’s Key Editor has now reached the stage (a few little inconsistencies aside) where you can do most things of importance and I’m sure Dorico 5 will show further progress. Frankly, my use of Cubase is mainly restricted these days to audio organisation which does not require more than a basic version. There are those who use Dorico primarily for notation and then do the playback in a DAW but for me that defeats the purpose of having all the increasingly powerful DAW-like features in Dorico.
Midifile has tempo inside
I just open a midifile that everybody can find
come back in few hours to answer to your post and give precision about TXlTimecode :I suspect the problem
that’s what I thought from previous experience in general but importing a MIDI file exported from Dorico into Elements has lost all the tempo changes. I’ll check again with Cubase Pro (installed the trial) in case something went wrong.
don’t waste you time: it works! I’ve already done it
I just did it again with a different project for both Elements 10.5 and Pro 12 and it doesn’t. The tempo has reset to crochet =120 throughout. I have exported a MIDI file from Dorico 4.3 and imported it into both of these versions . A MusicXML export/import, however, does retain the tempo information. Could I be doing something wrong here?
How weird?! Maybe it’s not an exact science or we don’t do the same manipulations or am I a lucky person?! I’m on windows 10 and you on Mac perhaps
And import in Cubase :
A concern between these two software is the difference in ganguage
- Cubase can export tempotrack as xml with extension *.smt not importable in dorico by file >import tempo track .
- Dorico by doing file>export tempo Track creates a *.mid file not importable by Cubase under file>Import>Tempo track
On the other hand and what I do in general: , you can copy a selection of tempos from Time track and make paste in Cubase
no-- we’re both on windows 10. Could you maybe attach both this mini test project and your MIDI file so we can compare notes?
So I think the difference between us is
In cubase :File>import>Midifile… ask “Do you want want to create a new project?”
- If you say "create " it create a new *.cpr and tempo are written in tempo track
- If you say “no” only notes will be merge to the existing project and bypass the tempo information Unfortunately!
So a xth workaround :copy information from the new create cubase *.cpr and paste it in the cubase project what you are working on!
Can you confirm?
that’s exactly it! I didn’t ask to create a new project. Stupid behaviour in Cubase if you ask me but now I know and many thanks!