|
|
MakeMusic Forum > Public Forums > Finale - Windows - FORUM HAS MOVED! > Music spacings, numerous questions | Forum Quick Jump
|
| N. Grossingink Registered Member
Date Joined Nov 2002 Total Posts : 3991 | Posted 12/13/2016 9:12 AM (GMT -6) | | Dr. Wiggy said... 3. I'm not entirely sure what effect the reference width has. In theory, I would expect it to have no effect, as "it's all relative" within the same system. But a quick test suggests there is some change. A larger Scaling Factor suggests a wider spacing, of course. Tighter spacing is achieved with a smaller factor.
If the systems are not locked, the reference width should have a very noticeable effect on the spacing, depending on the amount chosen.
For what it's worth, I use the following settings for instrumental parts as at least a starting point:
Jazz and commercial music: .35" reference width, 1.618 scaling (gives 4 measures per system of running eighth notes) Orchestral, Band, Chamber: .3" reference, 1.4 scaling (.25" reference tight spacing, .33" or more looser spacing)
N. OSX El Capitan 10.11.6 Finale 2011c, 2012c for production work
Finale 2014.5, not used by my clients
(Finale v25 - not interested yet)
TgTools, Patterson Plugins, JW Change and Staff Polyphony, QuicKeys 4 Mac Mini 2.4 Ghz Intel, 8GB RAM New Belgium Fat Tire Ale
"At last, fortissimo!" –Gustav Mahler, on visiting Niagara Falls | Back to Top | |
| Dr. Wiggy Early music: modern methods
Date Joined Jun 2006 Total Posts : 12628 | Posted 12/14/2016 4:13 AM (GMT -6) | | My understanding, which may not be perfect, of most computer algorithms for music spacing is:
The computer assigns the reference width to the reference duration. E.g. Every quarter note gets 21pt of space after it. Other note values get a space calculated by the scaling factor. So with a factor of 1.5, a half note gets 21 x 1.5 = 31.5 pt. An eighth gets 14pt.
Thus, you get a total distance for each measure. You can then see how many measures you can fit on a system. But let's say your print area is 8 inches wide, and 3 measures add up to 7 inches, and 4 measures is too much at 9 inches. The algorithm then has to "justify" the spacing, stretching it out to make 8 inches. (Or indeed, if you add another measure, it has to squeeze everything down a bit.)
And then it has to shiggle things about a bit to avoid clashes of articulations and lyrics, and everything else! To be honest, I try not think about it to much.
If you're looking for a cure for insomnia this Christmas, there's some heavy reading about notation spacing algorithms in the GUIDO notation project, and the research papers of Donald Byrd.
tuprints.ulb.tu-darmstadt.de/265/1/kai_renz_diss.pdf homes.soic.indiana.edu/donbyrd/Papers/DonDissScanned.pdf Finale v.25.1, 2012 MacMini; 2012 MacBook Pro (10.11.6 / 10.12.1) Edirol FA-66; Roland A-49, HP Laserjet 5200 DTN Ancient Groove Music www.ancientgroove.co.ukPost Edited (Dr. Wiggy) : 12/14/2016 5:03:04 AM (GMT-6) | Back to Top | |
| N. Grossingink Registered Member
Date Joined Nov 2002 Total Posts : 3991 | Posted 12/15/2016 11:00 AM (GMT -6) | | I like Fred's 1.5 ratio. I think I'm going to start using it for selected jobs.
So far as an appropriate ratio/reference width combination on a denser layout, I would start with 1.5/.3" (84evpu) and if needed, increase the width by small increments (.3", .325", .35" .375"). It's a process of trial and error.
Don't forget you can use different spacing widths on different passages in the same file, as needed.
N. OSX El Capitan 10.11.6 Finale 2011c, 2012c for production work
Finale 2014.5, not used by my clients
(Finale v25 - not interested yet)
TgTools, Patterson Plugins, JW Change and Staff Polyphony, QuicKeys 4 Mac Mini 2.4 Ghz Intel, 8GB RAM New Belgium Fat Tire Ale
"At last, fortissimo!" –Gustav Mahler, on visiting Niagara Falls | Back to Top | | Forum Information | Currently it is Tuesday, December 19, 2023 6:03 PM (GMT -6) There are a total of 403,820 posts in 58,165 threads. In the last 3 days there were 0 new threads and 0 reply posts. View Active Threads
|
Forum powered by dotNetBB v2.42EC SP3 dotNetBB © 2000-2023 |
|
|