I have most humanization features turned off in Dorico and the expression map keyswitches match Studio One’s sound variations for each instrument. Basically, aside from some additional effects, hitting play in Studio One is no different than Dorico.
Dorico has come a long way with the key editor and NotePerformer + NPPE gives more than satisfactory results these days, so tweaking has been needed less frequently.
The last thing this forum needs is any controversy at the moment.
I own VEP. I used it most when was I pushing both my machines (Mac and Windows) past their limits. I was wasting so much time on work arounds, and for me I would put my use of VEP in that category. It might not be exactly fair of me to say, as when you’re near the edge things aren’t stable anyway.
The (maybe? ) adult answer for me was to stop my denial. I had a machine built based on the way I was using Dorico that was fast enough for an evil laugh. Kinda chagrined that it wasn’t really that expensive.
That more than anything is what limits my interest in VEP. I don’t need it. Whereas working directly in Dorico is immediate, and like you streamlining is a major goal.
(Added) I should clarify- what’s coming out of Dorico is good enough to be exported as an audio track. I wouldn’t have a reason for the same VSTi to be in Dorico and Cubase so I have no reason to use VEP to share that way. JMO though.
For Dorico going to Cubase (or another DAW), what I do is host absolutely everything in a single Vienna Ensemble Pro instance and send the entire complete mix back to Dorico on a single stereo return.
If I need to move to Cubase, what I do is export all the MIDI tracks from Dorico, bring them into Cubase, and connect the same Vienna Ensemble Pro project to Cubase. When I hit play in Cubase, everything sounds completely identical to how it did in Dorico, since my entire mix transfers, but it is still raw MIDI where I can do more edits etc.
The only disadvantage of this approach is you can’t really make use of time saving tools in the mixing engine in Cubase since you end up not really using the mixer at all in Cubase (you use the VE Pro mixer instead). The VE Pro mixer has basically the same feature sets as any DAW mixer including Cubase (and way more features than the Dorico mixer) so this is generally not a big deal. It is nice to have a workflow where I can bring MIDI from Dorico to Cubase and have as a starting point everything sounding 100% identical.
In the US it is the standard to show pricing information always without tax, because they are different between states (some states like New Hampshire do not have a sales tax). This is different to Germany, where you have to show always the price including VAT.
Because MakeMusic is in the US, I guess this is correct.
It probably depends on which state you live in and whether they tax digitally-delivered goods. California doesn’t, but apparently a number of other states do.
It’s browser based, there are instructions on which file to open it.
Hopefully this html will work for years. A PDF might be useful, could not find one.
As far as I remember, if you use Adobe Acrobat, you can generate a PDF from a .html site, specifying how many levels down it should include. That said, there will be other tools, which are able to do so, may be even online services.
Like many, I prefer searchable pdf files to the Finale html User Guide… The last one that MakeMusic provided was 2014—not finding a download link at the moment but I believe it’s still out there… It’s not bad for many users but doesn’t include any of the new features from 25/26/27, of course…