Re: [Finale] Dorico test importing Finale XML

2019-01-31 Thread Jari Williamsson

AFAIK, it's the REVERSE direction that's the problem for Dorico?

Once the data is in Dorico, you'll loose most of it trying to get it 
elsewhere.



Best regards,

Jari Williamsson



On 2019-01-29 04:27, Craig Parmerlee wrote:

OK, here are the results
Score: https://app.box.com/s/n7pi05swx2hve4wk71znvg409geju45b
Parts: https://app.box.com/s/slp2py2olo3404gcpnlq9i30w3m4h0g9

I emphasize I did ZERO EDITING.  All I did was:

1) Open Dorico
2) Import your XML file
3) Print score
4) Print parts

That all took about i minute.  I chose to use Dorico's internal PDF 
creator which is really very nice and extremely fast.  But one 
shortcoming is that it creates a separate PDF for each part, so I also did


5) Opened PdfSAM Visual to merge all the parts into one file.  That took 
about 3 minutes -- longer than it took to create the parts in Dorico.


The layouts aren't perfect.  I'd certainly edit them a little.  But a 
key point is that in almost every case, the parts are usable without any 
editing if you are in a big rush to get something out for rehearsal.



On 1/28/2019 4:21 PM, Thomas Schaller wrote:

Hi Craig,
thanks for volunteering to do a little test.
Here is an orchestra job that has a bit of everything, yet not long. 
Not sure what will translate, maybe there is too much information in 
this XML file.
Let me know if I should prepare it differently to get a better result 
(for test purposes).
But I’m really anxious to see how little one needs to touch to get a 
good result.

Thanks again,
Thomas
PS - I took out title and credits and copyright to be on the safe side.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu


___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu

Re: [Finale] Dorico test importing Finale XML

2019-01-31 Thread Craig Parmerlee

Thanks, Geraldo.

I will keep that in mind.  My only concern is that if this is system 
tempo or tempo markings (i.e. text that will appear for all players), it 
has to be on the downbeat or else it will break up multi-measure rests.




On 1/30/2019 1:35 PM, Gerardo Delgado wrote:

  I can move the elements manually to relieve the stacking,

but the staffs remain spaced apart.  They don't adjust themselves after
I relieve the stacking.  So I may have to adjust some of the staff
spacing manually.


Hi Craig.

I am working in some projects with Dorico and in cases like that I move the
texts ("Trumpet solo" o "legato") in Write Mode in order to assign them to
other elements (for instance, a neighbour note or rest). It makes the
staves to respace automatically. Then, in Engraving Mode, I move the text
to the proper place. Generally, no further manual staff spacing is required.

Kind regards.

Gerardo Delgado
Musician, Music Editor, Conductor
Buenos Aires, Argentina


El mié., 30 ene. 2019 a las 3:01, Craig Parmerlee ()
escribió:



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu

Re: [Finale] Dorico test importing Finale XML

2019-01-31 Thread Gerardo Delgado
>  I can move the elements manually to relieve the stacking,
but the staffs remain spaced apart.  They don't adjust themselves after
I relieve the stacking.  So I may have to adjust some of the staff
spacing manually.


Hi Craig.

I am working in some projects with Dorico and in cases like that I move the
texts ("Trumpet solo" o "legato") in Write Mode in order to assign them to
other elements (for instance, a neighbour note or rest). It makes the
staves to respace automatically. Then, in Engraving Mode, I move the text
to the proper place. Generally, no further manual staff spacing is required.

Kind regards.

Gerardo Delgado
Musician, Music Editor, Conductor
Buenos Aires, Argentina


El mié., 30 ene. 2019 a las 3:01, Craig Parmerlee ()
escribió:

> It seems that Dorico did not include some (maybe all) text expressions
> in its import.  When I ran the XML into Finale, the text expressions
> show but mostly collide with other elements.  Dorico doesn't really have
> "text expressions" in the same sense that Finale uses them.  With
> Dorico, you have regular text (single staff) and system text (applies to
> all staves).  Dorico also has tempo markings and playing techniques.
>
> The things people put into text expressions in Finale would go either
> into regular text , tempo markings or playing techniques with Dorico,
> and evidently there is no such conversion in the XML importer.  But had
> those elements been brought in through the import, they would not have
> collided. By default, nothing collides.  You can forcibly make elements
> collide by manually placing them in ENGRAVE mode, or you can disable the
> "avoid collisions" property.  I have heard of some cases where this
> doesn't perfectly avoid collisions, but I have never seen any collisions.
>
> There is a downside, however.  I tend to use a lot of rehearsal marks,
> and I also often include either a tempo marking or system text at the
> same barline where the rehearsal mark is placed.  For example, rehearsal
> mark C might also say "Trumpet solo".  In those cases, the collision
> avoidance seems to stack these elements vertically.  It doesn't collide,
> but it may place the staffs very far apart in order to avoid the
> collision.  I can move the elements manually to relieve the stacking,
> but the staffs remain spaced apart.  They don't adjust themselves after
> I relieve the stacking.  So I may have to adjust some of the staff
> spacing manually.
>
> But a key point is that by default, the parts are all completely
> playable, even if not ideally laid out. If you are racing to get a piece
> done in time for a rehearsal, you don't have to leave an extra hour or
> two to fiddle with parts just to make them playable.
>
>
> On 1/30/2019 12:08 AM, Raymond Horton wrote:
> > Impressive results! Thanks for sharing!
> >
> > ​Raymond Horton
> > Composer, Arranger
> > Minister of Music, Edwardsville (IN) United Methodist Church
> > Retired Bass Trombonist, Louisville Orchestra, 1971-2016
> > Visit us at rayhortonmusic.com
> >
> > On Mon, Jan 28, 2019, 10:28 PM Craig Parmerlee  wrote:
> >
> >> OK, here are the results
> >> Score: https://app.box.com/s/n7pi05swx2hve4wk71znvg409geju45b
> >> Parts: https://app.box.com/s/slp2py2olo3404gcpnlq9i30w3m4h0g9
> >>
> >> I emphasize I did ZERO EDITING.  All I did was:
> >>
> >> 1) Open Dorico
> >> 2) Import your XML file
> >> 3) Print score
> >> 4) Print parts
> >>
> >> That all took about i minute.  I chose to use Dorico's internal PDF
> >> creator which is really very nice and extremely fast.  But one
> >> shortcoming is that it creates a separate PDF for each part, so I also
> did
> >>
> >> 5) Opened PdfSAM Visual to merge all the parts into one file.  That took
> >> about 3 minutes -- longer than it took to create the parts in Dorico.
> >>
> >> The layouts aren't perfect.  I'd certainly edit them a little.  But a
> >> key point is that in almost every case, the parts are usable without any
> >> editing if you are in a big rush to get something out for rehearsal.
> >>
> >>
> >> On 1/28/2019 4:21 PM, Thomas Schaller wrote:
> >>> Hi Craig,
> >>> thanks for volunteering to do a little test.
> >>> Here is an orchestra job that has a bit of everything, yet not long.
> >>> Not sure what will translate, maybe there is too much information in
> >>> this XML file.
> >>> Let me know if I should prepare it differently to get a better result
> >>> (for test purposes).
> >>> But I’m really anxious to see how little one needs to touch to get a
> >>> good result.
> >>> Thanks again,
> >>> Thomas
> >>> PS - I took out title and credits and copyright to be on the safe side.
> >>
> >>
> >> ---
> >> This email has been checked for viruses by Avast antivirus software.
> >> https://www.avast.com/antivirus
> >> ___
> >> Finale mailing list
> >> Finale@shsu.edu
> >> https://lists.shsu.edu/mailman/listinfo/finale
> >>
> >> To unsubscribe from finale send a message to:
> >> finale-unsubscr...@shsu.e

Re: [Finale] Dorico test importing Finale XML

2019-01-29 Thread Craig Parmerlee
It seems that Dorico did not include some (maybe all) text expressions 
in its import.  When I ran the XML into Finale, the text expressions 
show but mostly collide with other elements.  Dorico doesn't really have 
"text expressions" in the same sense that Finale uses them.  With 
Dorico, you have regular text (single staff) and system text (applies to 
all staves).  Dorico also has tempo markings and playing techniques.


The things people put into text expressions in Finale would go either 
into regular text , tempo markings or playing techniques with Dorico, 
and evidently there is no such conversion in the XML importer.  But had 
those elements been brought in through the import, they would not have 
collided. By default, nothing collides.  You can forcibly make elements 
collide by manually placing them in ENGRAVE mode, or you can disable the 
"avoid collisions" property.  I have heard of some cases where this 
doesn't perfectly avoid collisions, but I have never seen any collisions.


There is a downside, however.  I tend to use a lot of rehearsal marks, 
and I also often include either a tempo marking or system text at the 
same barline where the rehearsal mark is placed.  For example, rehearsal 
mark C might also say "Trumpet solo".  In those cases, the collision 
avoidance seems to stack these elements vertically.  It doesn't collide, 
but it may place the staffs very far apart in order to avoid the 
collision.  I can move the elements manually to relieve the stacking, 
but the staffs remain spaced apart.  They don't adjust themselves after 
I relieve the stacking.  So I may have to adjust some of the staff 
spacing manually.


But a key point is that by default, the parts are all completely 
playable, even if not ideally laid out. If you are racing to get a piece 
done in time for a rehearsal, you don't have to leave an extra hour or 
two to fiddle with parts just to make them playable.



On 1/30/2019 12:08 AM, Raymond Horton wrote:

Impressive results! Thanks for sharing!

​Raymond Horton
Composer, Arranger
Minister of Music, Edwardsville (IN) United Methodist Church
Retired Bass Trombonist, Louisville Orchestra, 1971-2016
Visit us at rayhortonmusic.com

On Mon, Jan 28, 2019, 10:28 PM Craig Parmerlee 
OK, here are the results
Score: https://app.box.com/s/n7pi05swx2hve4wk71znvg409geju45b
Parts: https://app.box.com/s/slp2py2olo3404gcpnlq9i30w3m4h0g9

I emphasize I did ZERO EDITING.  All I did was:

1) Open Dorico
2) Import your XML file
3) Print score
4) Print parts

That all took about i minute.  I chose to use Dorico's internal PDF
creator which is really very nice and extremely fast.  But one
shortcoming is that it creates a separate PDF for each part, so I also did

5) Opened PdfSAM Visual to merge all the parts into one file.  That took
about 3 minutes -- longer than it took to create the parts in Dorico.

The layouts aren't perfect.  I'd certainly edit them a little.  But a
key point is that in almost every case, the parts are usable without any
editing if you are in a big rush to get something out for rehearsal.


On 1/28/2019 4:21 PM, Thomas Schaller wrote:

Hi Craig,
thanks for volunteering to do a little test.
Here is an orchestra job that has a bit of everything, yet not long.
Not sure what will translate, maybe there is too much information in
this XML file.
Let me know if I should prepare it differently to get a better result
(for test purposes).
But I’m really anxious to see how little one needs to touch to get a
good result.
Thanks again,
Thomas
PS - I took out title and credits and copyright to be on the safe side.



---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu

___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu



___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu

Re: [Finale] Dorico test importing Finale XML

2019-01-29 Thread Raymond Horton
Impressive results! Thanks for sharing!

​Raymond Horton
Composer, Arranger
Minister of Music, Edwardsville (IN) United Methodist Church
Retired Bass Trombonist, Louisville Orchestra, 1971-2016
Visit us at rayhortonmusic.com

On Mon, Jan 28, 2019, 10:28 PM Craig Parmerlee  OK, here are the results
> Score: https://app.box.com/s/n7pi05swx2hve4wk71znvg409geju45b
> Parts: https://app.box.com/s/slp2py2olo3404gcpnlq9i30w3m4h0g9
>
> I emphasize I did ZERO EDITING.  All I did was:
>
> 1) Open Dorico
> 2) Import your XML file
> 3) Print score
> 4) Print parts
>
> That all took about i minute.  I chose to use Dorico's internal PDF
> creator which is really very nice and extremely fast.  But one
> shortcoming is that it creates a separate PDF for each part, so I also did
>
> 5) Opened PdfSAM Visual to merge all the parts into one file.  That took
> about 3 minutes -- longer than it took to create the parts in Dorico.
>
> The layouts aren't perfect.  I'd certainly edit them a little.  But a
> key point is that in almost every case, the parts are usable without any
> editing if you are in a big rush to get something out for rehearsal.
>
>
> On 1/28/2019 4:21 PM, Thomas Schaller wrote:
> > Hi Craig,
> > thanks for volunteering to do a little test.
> > Here is an orchestra job that has a bit of everything, yet not long.
> > Not sure what will translate, maybe there is too much information in
> > this XML file.
> > Let me know if I should prepare it differently to get a better result
> > (for test purposes).
> > But I’m really anxious to see how little one needs to touch to get a
> > good result.
> > Thanks again,
> > Thomas
> > PS - I took out title and credits and copyright to be on the safe side.
>
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
> ___
> Finale mailing list
> Finale@shsu.edu
> https://lists.shsu.edu/mailman/listinfo/finale
>
> To unsubscribe from finale send a message to:
> finale-unsubscr...@shsu.edu
___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu

[Finale] Dorico test importing Finale XML

2019-01-28 Thread Craig Parmerlee

OK, here are the results
Score: https://app.box.com/s/n7pi05swx2hve4wk71znvg409geju45b
Parts: https://app.box.com/s/slp2py2olo3404gcpnlq9i30w3m4h0g9

I emphasize I did ZERO EDITING.  All I did was:

1) Open Dorico
2) Import your XML file
3) Print score
4) Print parts

That all took about i minute.  I chose to use Dorico's internal PDF 
creator which is really very nice and extremely fast.  But one 
shortcoming is that it creates a separate PDF for each part, so I also did


5) Opened PdfSAM Visual to merge all the parts into one file.  That took 
about 3 minutes -- longer than it took to create the parts in Dorico.


The layouts aren't perfect.  I'd certainly edit them a little.  But a 
key point is that in almost every case, the parts are usable without any 
editing if you are in a big rush to get something out for rehearsal.



On 1/28/2019 4:21 PM, Thomas Schaller wrote:

Hi Craig,
thanks for volunteering to do a little test.
Here is an orchestra job that has a bit of everything, yet not long. 
Not sure what will translate, maybe there is too much information in 
this XML file.
Let me know if I should prepare it differently to get a better result 
(for test purposes).
But I’m really anxious to see how little one needs to touch to get a 
good result.

Thanks again,
Thomas
PS - I took out title and credits and copyright to be on the safe side.




---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus
___
Finale mailing list
Finale@shsu.edu
https://lists.shsu.edu/mailman/listinfo/finale

To unsubscribe from finale send a message to:
finale-unsubscr...@shsu.edu