So to transfer by MusicXml - if that is limitied by pure notation in Staff View in Sonar?
 
Or is all midi and every there as it is - so to use in other notation software like you would transferred midi files.
 
There are some showstopper limitations in Sonar notation, like triplets pauses are not allowed or whatever it was.
So you cannot use it if that information is destroyed using MusicXml.
 
Did anybody use MusicXml and transfer to other notation software?
 
Thanks.

lfm
So to transfer by MusicXml - if that is limitied by pure notation in Staff View in Sonar?

 
The MusicXML file produced in SONAR (and probably most DAWs) is based only on the contents of the Staff View.  So, any of the Staff View limitations are reproduced in the notation software when the MusicXML file is imported.
 

lfm 
Did anybody use MusicXml and transfer to other notation software?

I do use MusicXML very successfully for import into MuseScore, but I use another DAW to create the files due to SONAR's Staff View limitations.
 
Like any "standard" transfer protocol, every vendor's interpretation of MusicXML is different.  Success is dependent on the DAW to accurately interpret the displayed notation when creating the file and the notation software to accurately interpret the imported file.
 
Hope this answers your questions,
-- Ron
 
 
 

I think its up to the midi-information and not to the limited staffview.
The website from MusicXML says:
All current versions of SONAR include the ability to export MusicXML files, originally added in SONAR X1 Producer Expanded.
Just try it.

Since MusicXML is exported from the Staff View window, what you see is what you'll get.  So if it's bad in the Staff View, it will be bad in the MusicXML.  And with no import MusicXML functionality, it's not a very useful interchange method with SONAR.
 
Generally better to export as MIDI from SONAR and import that into the other app.  And vice-versa.  Though there are a few odd cases.  For example Guitar Pro 6's MIDI export is kind of broken.  It doesn't do ties correctly.  But its MusicXML export is right.  So I export as MusicXML and then use MuseScore to convert to MIDI that I then bring into SONAR.

Thanks for replies.
 
@SquireBum: I was afraid that was the case.
 
After all - just export the midi stuff and import in notation also makes it easier to make some playback of it as well.
 
@THambrecht: Just felt quicker to ask those that used it, not go through all troubleshooting at this stage.

msorrels
Since MusicXML is exported from the Staff View window, what you see is what you'll get.  So if it's bad in the Staff View, it will be bad in the MusicXML.  And with no import MusicXML functionality, it's not a very useful interchange method with SONAR.
 
Generally better to export as MIDI from SONAR and import that into the other app.  And vice-versa.  Though there are a few odd cases.  For example Guitar Pro 6's MIDI export is kind of broken.  It doesn't do ties correctly.  But its MusicXML export is right.  So I export as MusicXML and then use MuseScore to convert to MIDI that I then bring into SONAR.

You might want to consider an upgrade to GP7. MusicXML import and export were improved in v7.0.6 (current), as was a fix to playing bends in MIDI.