Thanks again for this follow up video to your "export to XML" video. Very helpful to see the comparison between Dorico and MuseScore imports versus the original. Love your information, and your easy to understand style and approach, I've subscribed to your channel!
Thank you for taking the time to produce this video. I've been transferring Finale into Dorico and yes, I really wish that Dorico would allow for greater flexibility in arranging the page. This was encouraging. Thanks.
Interesting demonstration. I'm not completely sold on the idea that Steinberg won't create a direct finale to Dorico translation capability. I understand it would be a monumental task, but achieving that task (especially using the proprietary advantage of having access to finale's code) could be very lucrative for Steinberg given the very large number of orphaned finale users who have created immense libraries of finale files over the decades. As someone in my 50s with a large finale library, I would gladly pay a premium for the ability to pull up any of my previous finale files for editing without having to worry much about things like fixing the page layout, because time is money, and the currency of life... And yes, I may just be engaging in wishful thinking, and I am way more stressed about learning a new program than being able to edit my previous files.
The reason the headers didn't import into Dorico is that Dorico stores the headers in a completely different part of the program from the score - it stores them in "Master Pages", whereas Finale and MuseScore don't have this concept of a "Master Page". There isn't enough information for Dorico to use to determine how it would make a master page (with text tokens that auto replace) from a fixed heading in a MusicXML file, so it ignores this header as a result. Although they could program Dorico to forcibly override the first page from the master page and statically set the heading from the MusicXML import, this would be a very bad way of doing it in Dorico actually and could complicate later edits to the file. To elaborate, Dorico essentially is two programs in one - a notation program and a lite Desktop Publishing program, and they are in separate tabs (Write and Engrave mode). The header in Dorico is stored on the desktop publishing side. MusicXML is not meant to convey information from two parts of the program like this (notation side and DTP side) because programs like Finale and MuseScore have no separate DTP engine. This makes Dorico more powerful but at the same time makes import a little less perfect. The good news is that once you set up your master pages the way you want with the header text tokens you want, you can import them into another file to immediately get the header text looking correct.
In Finale, if you have the titles, credits, etc in the File Manager / File Info tab, they will transfer to Dorico’s Project Info dialog. (Ctrl-I on Win, Cmd-I on Mac)You’ll find them under Flow 1. Go to Project then scroll down to the bottom - select Copy and they’ll be copied to the Project area. You then use master pages and tokens to put them where you want on the page.
The problem with data formatted according to some XML standard is lack of rigid formality and semantics, and extensive freedom. It is miles away from generally accepted standards such as pdf, which is almost 99% independent of the program that generated it. Also, it is relatively new, so there are frequently new versions. Short: it is an immature technology, it's even uncertain that it will last. The bare truth is that once you have printed the composition on paper or in PDF format, that is the only thing that will really survive.
To import a MusicXML file with more control, you first have to create the empty Dorico project before importing. If you do it the way just described, Dorico offers you some options for how to handle the information in the file.
In Dorico, select the option to hide flow headers on the first page. In addition, I always reduce the top and bottom margins. I suggest watching the short video in the Dorico channel.
If you click the CC on the video, then click the gear/settings, there is an "Auto-translate" button for the CC. I'm trying to find a service that can translate the video so I can embed it but I'm not having any luck! I hope this helps. I'm going to keep trying to find something for Spanish speakers.
Thanks again for this follow up video to your "export to XML" video. Very helpful to see the comparison between Dorico and MuseScore imports versus the original. Love your information, and your easy to understand style and approach, I've subscribed to your channel!
Thank you for taking the time to produce this video. I've been transferring Finale into Dorico and yes, I really wish that Dorico would allow for greater flexibility in arranging the page. This was encouraging. Thanks.
You’re welcome Michael!! Best of luck to you my friend. Hang in there!!
Interesting demonstration.
I'm not completely sold on the idea that Steinberg won't create a direct finale to Dorico translation capability. I understand it would be a monumental task, but achieving that task (especially using the proprietary advantage of having access to finale's code) could be very lucrative for Steinberg given the very large number of orphaned finale users who have created immense libraries of finale files over the decades. As someone in my 50s with a large finale library, I would gladly pay a premium for the ability to pull up any of my previous finale files for editing without having to worry much about things like fixing the page layout, because time is money, and the currency of life...
And yes, I may just be engaging in wishful thinking, and I am way more stressed about learning a new program than being able to edit my previous files.
The reason the headers didn't import into Dorico is that Dorico stores the headers in a completely different part of the program from the score - it stores them in "Master Pages", whereas Finale and MuseScore don't have this concept of a "Master Page". There isn't enough information for Dorico to use to determine how it would make a master page (with text tokens that auto replace) from a fixed heading in a MusicXML file, so it ignores this header as a result. Although they could program Dorico to forcibly override the first page from the master page and statically set the heading from the MusicXML import, this would be a very bad way of doing it in Dorico actually and could complicate later edits to the file.
To elaborate, Dorico essentially is two programs in one - a notation program and a lite Desktop Publishing program, and they are in separate tabs (Write and Engrave mode). The header in Dorico is stored on the desktop publishing side. MusicXML is not meant to convey information from two parts of the program like this (notation side and DTP side) because programs like Finale and MuseScore have no separate DTP engine. This makes Dorico more powerful but at the same time makes import a little less perfect.
The good news is that once you set up your master pages the way you want with the header text tokens you want, you can import them into another file to immediately get the header text looking correct.
This is FANTASTIC news! Still learning the nuts and bolts of Dorico! I can't wait to be a pro!
In Finale, if you have the titles, credits, etc in the File Manager / File Info tab, they will transfer to Dorico’s Project Info dialog. (Ctrl-I on Win, Cmd-I on Mac)You’ll find them under Flow 1. Go to Project then scroll down to the bottom - select Copy and they’ll be copied to the Project area. You then use master pages and tokens to put them where you want on the page.
watch the 4 Finale to Dorico videos and the Dorico feature update videos. They give you a sense of how Dorico does things.
The problem with data formatted according to some XML standard is lack of rigid formality and semantics, and extensive freedom. It is miles away from generally accepted standards such as pdf, which is almost 99% independent of the program that generated it. Also, it is relatively new, so there are frequently new versions. Short: it is an immature technology, it's even uncertain that it will last. The bare truth is that once you have printed the composition on paper or in PDF format, that is the only thing that will really survive.
To import a MusicXML file with more control, you first have to create the empty Dorico project before importing. If you do it the way just described, Dorico offers you some options for how to handle the information in the file.
Thanks for the tip!!
Supposedly Dorico has a lot of MusicXML import options. You might be able to get better results if you tweak them.
GNU LilyPond is where it's at. None of this GUI soyftware can match the power and beauty of LilyPond.
User picture checks out.
LilyPond does not do MusicXML, I believe.
In Dorico, select the option to hide flow headers on the first page. In addition, I always reduce the top and bottom margins. I suggest watching the short video in the Dorico channel.
KEVIN open up the CC Closed Captioning in Spanish for those speakers! THANKS!
If you click the CC on the video, then click the gear/settings, there is an "Auto-translate" button for the CC. I'm trying to find a service that can translate the video so I can embed it but I'm not having any luck! I hope this helps. I'm going to keep trying to find something for Spanish speakers.
Sorry but you "conjugate" verbs and you "subjugate" those who you oppress.