Exactly…
If you’re already famaliar with instrument tracks and MIDIloops in Cubase, you’ll already know the contents of this post. For those that are not familiar but interested…
Here’s a bit of info on CuBase MIDIloop files (for those who aren’t familiar with them).
These are designed to export complete ‘virtual instrument tracks’ from a CuBase Project. These also include the plug in setup information for the assigned VSTi, as well as anything in the mixer plugin slots, with all their settings intact. You can export them one track at a time, or you can select several instrument tracks and export them as a group into a single MIDIloop file.
Once you export instrument tracks as MIDIloops, they show up in the Steinberg Media Bay. You can click them and audition them without having to load them into a project, and they play back as they were built, using the right plugin and effects. You can import them back into any CuBase project and they load in all your plugins for the track set up and ready to go.
Since ExpressionMaps are similar between Dorico and Cubase (and some day might be nearly identical), it’s easy to share the technique interpretation between Dorico and CuBase as well. I don’t know what Dorcio’s percussion stave system is going to be like, but if it ends up being compatible with CuBase drum maps, then we’ve cut out many minutes, or even hours of manual labor after importing percussion staves.
I don’t know if these MIDIloop files keep up with any scoring relevant information at all (Cubase only or otherwise). I’ll need to run some tests and take a closer look to see if it keeps up with the technique lanes in the native Steinberg native format (and any other scoring technique data), or if it just keeps a pure rendered from of them (I.E. just the key-switch, raw velocity, CC, or Note Expression Data). Either way, if Dorico were to support importing/exporting these MIDIloop tracks it seems to me like it would be a very good short-term bridge between the two apps, that would save a significant amount of work (the stave/track will not necessarily ‘look’ the same after importing cross app, and your added articulation marks and other entered text/techniques might be missing, but it should ‘sound identical’.
To me, this wold mostly be of interest if I want to move a composition (or a stave from a composition) into CuBase. I no longer care so much about the score in this case. I just want it in my tracking DAW so I can power mix it with other things that Dorico can’t do, or otherwise have a 1 to 1 track import where I can easily layer up more virtual instruments and make ultra fine adjustments to the ‘audio stream’. To me, if I want to bring things from CuBase into Dorico, XML might make more sense if I’ve added any score specific information to the piece (articulation marks, etc.), or I might even import both XML and MIDIloops into different flows to mix/match and choose the best bars of each for further scoring refinements).
Contrast this to exporting a plain MIDI or an XML score file from Dorico and loading that into CuBase where:
- Take several minutes to load up the VSTi plugins and/or MIDI instruments.
- Make sure all that is routed to the right places.
- Rebuild the mixer effect chain.
For a decent sized score, it really can take a significant chunk of a day to pull in a raw MIDI file and pick up where you left off.
Once Dorico’s playback tab matures to provide the kind of precision editing and routing we get in our Tracking DAW (and I do believe that Dorico’s own Play Tab will evolve into something extremely versatile/powerful), it may even make more sense to just sync the two apps with something like ReWire or Steinberg’s own System Link protocols. For the ‘short term’, if it’s not too much trouble, MIDIloop support (at least export them), would be a BIG HELP.
Again, I’m just tossing out an idea. It might be way too complicated to build into Dorico the ability to export/import these MIDIloop files. If it takes a ton of time and effort, of course I’d rather see that momentum go into developing Dorico’s own play editor…all the ‘integration stuff’ can wait. In contrast, if it’s something that can be done with a reasonable amount of effort; it sure would be nice for people who want to do the bulk of their composing in Dorico, and port it over to the post production CuBendo environment in much later stages of a project.
Either way, as a user, I don’t expect to see too much focus on the integration for several releases yet (things may be going on under the hood that we won’t get access to from the GUI as users for several releases). Naturally there is plenty of work to be done to add SCORING and playback features and abilities to Dorico itself that is far more important at this time. There is also much that needs to be done internally with features and bugs in CuBase itself, so I’m not holding my breath and expecting anything more than minor improvements (in each release) to the existing XML and MIDI exporting abilities for a while yet. It makes sense to get the existing MIDI and XML export/import working extremely well before diving into even more formats to try to support (Those formats also benefit non Steinberg specific ports).
Still, I can’t help but ‘hope/wish’ it might be pretty easy to at least make Dorico able to ‘export’ a working MIDIloop file (or something similar) that can be imported into CuBendo within a year or so.