jsg
I don't find exporting a SMF type 1 into Sibelius from Sonar a PITA at all. It's easy. Of course the score has to cleaned up, slurs, tempo marks, dynamic marks, have to be added, but this has to be done anyways even if you start a score from scratch. When I import from Sonar, the tied, dotted and nested triplets get displayed correctly in Sibelius.
Let me describe my work flow and you can tell me where I am wasting hours of time.
I produce a composition or arrangement in Finale. For early drafts for the client, I simply render from Finale. That is done in under a minute and sounds pretty good for the purposes of eliciting constructive feedback about the score.
As I get toward the final product, I want to have a more realistic rendering. I have to create all the necessary tracks and synths in Sonar. Often I arrange for similar instrumentation, so I can create a Sonar template that will save a little time. No big complaint there, although I'd much rather give Sonar my Finale MusicXML and have Sonar automatically build the appropriate project for me. All the info is there in the MusicXML.
Next I save all the MIDI from my Finale project. Finale can generate some very elaborate MIDI with its Human Playback feature. I run a plug-in in Finale to capture the HP information into my MIDI file. That's not too bad. Takes about 3 minutes. Before I do that, I will make some basic settings for each voice, such as pan.
Now I have to bring the MIDI into SONAR. I don't what you call a PITA, but this meets my definition of PITA. I have to drag one track at a time to get each instrument into the correct MIDI track in Sonar. Then there are some basic incompatibilities I have to work around by adding some MIDI commands at the beginning of ever single MIDI track. That process takes about 90 minutes, so now I am about 20 hours into the project before I have a reasonable sound coming out. From there, I can make all the additional MIDI tweaks and add the effects I need to make the rendering appreciably better than the file that comes straight out of Finale. That's the whole point, after all. That's 3 hours minimum, and often more like 5, but maybe I an too anal about the tweaking.
So far so good. Now here's the problem. With this better rendering I hear some things that should have been voiced differently, so I go back and fix that in my Finale file. And then what ...
Right. I have to go back through this whole ^$#^ thing -- or at least a good part of it -- again. Likewise with the improved SONAR output, the client hears some additional possibilities he wants to try, so I add that to the Finale score and ...
I hope you are getting the picture This is crap. Time is money. Sound quality is also money. This is not how this software ought to work together in 2015. The expectations from my clients get higher every year and the software is simply not keeping up. And I don't blame Cakewalk exclusively. It is a problem across the board. But somebody is going to make progress here and they will be rewarded for it.
And don't get me started about the brain-dead multi-track MIDI editor that is 100% unusable with MIDI files that use several controllers -- as the Finale Human Playback files do. This is ridiculous. A monumental blunder of UI design by Cakewalk.