Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
josé henrique padovani zepadov...@gmail.com writes: Em 09/06/10 22:04, Graham Percival escreveu: Could you please give some advices about which git / patch flags should I use to apply the patch to my current directories? If you seriously want to learn, then do a google search for patch to learn how to use it. If not, wait a few weeks until it's part of lilypond. This topic is too long to teach in a few emails. I did already used patch and diff in some codes... If you have the output of git diff in a mail file git am filename will do the trick. If you have a single, non-git generated patch, git-apply filename The latter causes more merge trouble when the change eventually appears upstream. It may, however, be the only manner to work with Rietveld patch sets. -- David Kastrup ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
Hey José. If you are willing to learn, you should first try compiling lilypond from the source on the git repository. Google ³compiling lilypond² for the documentation. This takes about a day (if you¹re lucky I was lucky, and I still had to update/download many-a-program and do a manual override on my config file to get it to find certain fonts). Once you have a lilypond git repository established, let me know. If this sounds un-fun, I would very much recommend waiting until this becomes part of lilypond: compiling lilypond requires comfort with the shell Terminal that is rather far adrift from the Mac OS X prefab version of lilypond. Word on the street is that this process will be easier in future versions of lilypond, although that is not a part of lilypond development that I know well, and I am not competent enough to tell you how far away that is from being a reality. I would also not suggest copy-and-pasting my new scheme and postscript files into your working directory it is generally bad practice. If you do this and there winds up being a bug that I didn¹t catch, you will have another problem on your hands that is much more precipitous than the potential problems associated with compiling. Again, compiling is a serious time and learning commitment that you should ONLY bring upon yourself if you want to develop. Otherwise, I will do my best to integrate your recommendations into the work I¹ve already done, and as Carl said, this will be part of lilypond in the not too distant future :-) Cheers, ~Mike On 6/10/10 3:49 AM, josé henrique padovani zepadov...@gmail.com wrote: Em 09/06/10 22:04, Graham Percival escreveu: On Wed, Jun 09, 2010 at 09:41:34PM -0300, josé henrique padovani wrote: Em 09/06/10 21:23, Carl Sorensen escreveu: Unfortunately, it doesn't include the complete files, so it would be fairly difficult for a user who is not familiar with git or patch to make it work. Could you please give some advices about which git / patch flags should I use to apply the patch to my current directories? If you seriously want to learn, then do a google search for patch to learn how to use it. If not, wait a few weeks until it's part of lilypond. This topic is too long to teach in a few emails. Cheers, - Graham Hi Graham, I did already used patch and diff in some codes... but I have no experience about how to use it with git (I have seen that the patch was created with a flag --git for diff, which I didn't found in diff man) and don't know which commands should I use to download from the lilypond's git repository... (just some tips would help me) I mean: I am not sure about which git flags/address/etc should I use to download the code.. (I suppose I should use git to download them and not simply download the diffs with from http://codereview.appspot.com/download/issue1425041_1.diff) Regarding patch, I would like to know if I should simply call it like this: cd /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ (I'm on a Mac) patch path-of-diffile/difffile.diff or if I should use some flags and/or call it from another place... Althought I am new to this process I think I can do it and would really appreciate some help. Thank you, josé ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 6/9/10 5:13 PM, josé henrique padovani zepadov...@gmail.com wrote: forgot to ask: are the diagrams working with the svg backend? Yes. Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 6/10/10 2:09 AM, Mike Solomon mike...@ufl.edu wrote: Hey José. I would also not suggest copy-and-pasting my new scheme and postscript files into your working directory it is generally bad practice. If you do this and there winds up being a bug that I didn¹t catch, you will have another problem on your hands that is much more precipitous than the potential problems associated with compiling. In my experience, as long as a backup copy of the scm/ and ps/ directories are saved, there's no problem with trying to copy in new files. That's how I started developing fret diagrams on Windows, many years ago. But you do need to recognize that your installation may break and that you may need to reset it. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
ok guys, I will setup git here... thanks Em 10/06/10 07:19, Carl Sorensen escreveu: On 6/10/10 2:09 AM, Mike Solomonmike...@ufl.edu wrote: Hey José. I would also not suggest copy-and-pasting my new scheme and postscript files into your working directory it is generally bad practice. If you do this and there winds up being a bug that I didn¹t catch, you will have another problem on your hands that is much more precipitous than the potential problems associated with compiling. In my experience, as long as a backup copy of the scm/ and ps/ directories are saved, there's no problem with trying to copy in new files. That's how I started developing fret diagrams on Windows, many years ago. But you do need to recognize that your installation may break and that you may need to reset it. Thanks, Carl -- http://zepadovani.info ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
2010/6/10 josé henrique padovani zepadov...@gmail.com: ok guys, I will setup git here... thanks Hey, If I install from MacPorts it will have this dev version or an older one?? like: sudo port install lilypond ??? ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
Em 10/06/10 10:04, Bernardo Barros escreveu: Hey, If I install from MacPorts it will have this dev version or an older one?? like: sudo port install lilypond ??? Here it says it is: 2.12.3... port info lilypond lilypond @2.12.3, Revision 2 (textproc) Variants: [+]docs, gui, universal Description: Lilypond is a unix-based automated engraving system that generates beautiful sheet music from input files. Lilypond uses its own input format, .ly, which in many ways is similar to LaTeX. Lilypond can export sheet music to PDF, EPS, SVG, and PNG formats, and can also create MIDI files. Homepage: http://lilypond.org/ Library Dependencies: fontforge, ghostscript, mftrace, guile, texinfo, pango, flex, urw-fonts, netpbm Platforms:darwin License: unknown Maintainers: s...@macports.org, openmaintai...@macports.org -- http://zepadovani.info ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
I can't wait to have this one! :-) Really nice! ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 06/09/2010 11:26 AM, Mike Solomon wrote: There is now a new bass clarinet, low-bass-clarinet, for bass clarinets with low keys (c, cis, d). Further remark here. On such low-C bass clarinets (and basset horns, and some basset clarinets...) it is common (but not universal) to have a _left-hand_ little finger key for low D. I would also separate out the thumb keys more to make it clear they are thumb keys. The fingering systems are not standardized (e.g. on Buffet I think the two extra rh little finger keys are for low Eb [bottom row] and Db [top row] whereas on Selmer I think it's the opposite way round), particularly when it comes to the thumb keys. So, my advice would be to explicitly copy the key layout of a particular well-known manufacturer (Buffet is probably best) and state that this is what you are following. Then as long as a score contains an indication at the start of what key indicates which note, players can adapt the fingering as they need. An alternative is to eschew the use of graphical representation of keys and to instead use (lower-register) note names, located in roughly the same place as the key, to identify which keys should be pressed. This is the system used in e.g. Rehfeldt, 'New Directions for Clarinet'. All that said, thanks for your wonderful effort in bringing beautiful woodwind fingering diagrams to Lilypond! :-) Best wishes, -- Joe ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 6/10/10 7:04 AM, Bernardo Barros bernardobarr...@gmail.com wrote: 2010/6/10 josé henrique padovani zepadov...@gmail.com: ok guys, I will setup git here... thanks Hey, If I install from MacPorts it will have this dev version or an older one?? like: sudo port install lilypond ??? port install will only install the latest stable version. However, it *might* get all the dependencies installed, so that you can then download the latest development binary and install it by copying to to your apps folder, and have it succeed. But I won't promise that it works. HTH, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 06/09/2010 07:26 PM, Mike Solomon wrote: Hey liylpond users, Please see: http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.pdf and http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.ly to see the changes These are excellent and valuable addition to Lilypond -- thanks very much Mike! The markup looks well set out easy to use -- any w/wind player should have no trouble with it. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
Hi Mike, I would suggest to add the possibility of marked keys (to make sing trills or smorzati, for example)... by now I am drawing my diagrams with postscript, but there is what I am talking about (attached)... I would also like to know: is the code of your woodwind diagrams available somewhere? (Does it require to recompile lilypond or can it be used with includes?) Thanks José Em 09/06/10 06:26, Mike Solomon escreveu: Hey liylpond users, Please see: http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.pdf and http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.ly to see the changes proposed by M Watts and Ian Hulin incorporated into the woodwind diagrams. To summarize: There is now a new flute, flute-b-extension, for flutes with the b extension. There is now a new bass clarinet, low-bass-clarinet, for bass clarinets with low keys (c, cis, d). There are separate commands for saxophone-saxohpone, alto-saxophone, tenor-saxophone, and baritone-saxophone. There is a low-a key for bari sax that is only drawn wehn you call it. All graphical comments have been integrated save the low oboe keys - in most examples I've consulted, the keys are not drawn w/ equal sizes. And I think it's prettier w/ the different sizes :-) Bagpipes, tin whistles, simple clarinets, bagpipes and the like will be looked into in the not-too-distant future. For now, I'm going to try and get what already exists into Lilypond ASAP. If any of you want to contribute diagrams, please consult me for the source (which is all in scheme). Cheers, ~Mike On 5/31/10 1:13 PM, Ian Hulini...@hulin.org.uk wrote: Hi Mike, This is really useful, but there's one nit regarding the flute fingerings, Not all flutes have a bottom b, and therefore the right-hand low-end key cluster will only have the bottom C# (cis) key, and one c roller. What is the right-hand x key about on the piccolo chart? If you can add something to use the relevant key-cluster appropriately that would be good. On 31/05/10 02:03, M Watts wrote: On 05/31/2010 02:10 AM, Mike Solomon wrote: Dear lilypond users, I am currently working on adding woodwind diagrams to lilypond, and I would love to hear lilypond users' opinions on this project. An excellent idea -- contrats on the work so far. Specifically, I would like to know from woodwind players and/or enthusiasts: 1) Are the diagrams correct in their nomenclature and positioning? One vital thing:-- The 'one', 'two' thru 'six' for the main keys/holes on all instruments are round the wrong way -- 'one' means first finger, left hand. So 'one' should be at the top, and 'six' at the bottom. 1+ Some w/w tutors also use a L1, L2, L3, R1 R2 R3 numbering system, but the low numbers are *always* at the headjoint end of the instrument and increase down to the footjoint end. Several minor things:-- Could the separator line between lh rh key be a bit longer? I like the way you only include relevant key clusters -- no need to show every key every time. Oboe: rh c cis ees keys are usually of equal size Saxophone: front f could be a bit bigger and closer to lh one; palm keys could be a bit bigger (lh d ees f); rh side keys could be a bit bigger (side bes, side c, high e). Maybe add baritone sax low A thumb key? Similar point to the low-b on the flute. Not all makes have this. Clarinet: maybe T R could be a bit smaller. Bass clarinet: some horns have an additional ees/aes lever in the lh little finger cluster; low c horns might have a 6th key for rh little finger (for low d), as well as 3 keys for rh thumb (low d, des, c) 2) Do the diagrams meet the standard of visual elegance to which you hold lilypond? I reckon so -- they're looking really nice; I like the ability to indicate depressedRing-to-open trills etc. If you are interested in extending this project to other instruments, please let me know. Maybe recorder, tin whistle, bagpipes Baroque flute, Simple-system flute (pre-Boehm keyed - used by 'Irish traditional music flute players). Simple-system clarinet. French-system bassoon. The code is written as such so that someone who knows how to use Scheme should be able to, by observing the way that the instruments are constructed, make their own instrument in the same manner. Very handy. 1+ Cheers, Ian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- http://zepadovani.info attachment: smorz.png___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
forgot to ask: are the diagrams working with the svg backend? thanks josé Em 09/06/10 20:12, josé henrique padovani escreveu: Hi Mike, I would suggest to add the possibility of marked keys (to make sing trills or smorzati, for example)... by now I am drawing my diagrams with postscript, but there is what I am talking about (attached)... I would also like to know: is the code of your woodwind diagrams available somewhere? (Does it require to recompile lilypond or can it be used with includes?) Thanks José Em 09/06/10 06:26, Mike Solomon escreveu: Hey liylpond users, Please see: http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.pdf and http://www.apollinemike.com/lilypond/woodwind-diagrams-text-graphic.ly to see the changes proposed by M Watts and Ian Hulin incorporated into the woodwind diagrams. To summarize: There is now a new flute, flute-b-extension, for flutes with the b extension. There is now a new bass clarinet, low-bass-clarinet, for bass clarinets with low keys (c, cis, d). There are separate commands for saxophone-saxohpone, alto-saxophone, tenor-saxophone, and baritone-saxophone. There is a low-a key for bari sax that is only drawn wehn you call it. All graphical comments have been integrated save the low oboe keys - in most examples I've consulted, the keys are not drawn w/ equal sizes. And I think it's prettier w/ the different sizes :-) Bagpipes, tin whistles, simple clarinets, bagpipes and the like will be looked into in the not-too-distant future. For now, I'm going to try and get what already exists into Lilypond ASAP. If any of you want to contribute diagrams, please consult me for the source (which is all in scheme). Cheers, ~Mike On 5/31/10 1:13 PM, Ian Hulini...@hulin.org.uk wrote: Hi Mike, This is really useful, but there's one nit regarding the flute fingerings, Not all flutes have a bottom b, and therefore the right-hand low-end key cluster will only have the bottom C# (cis) key, and one c roller. What is the right-hand x key about on the piccolo chart? If you can add something to use the relevant key-cluster appropriately that would be good. On 31/05/10 02:03, M Watts wrote: On 05/31/2010 02:10 AM, Mike Solomon wrote: Dear lilypond users, I am currently working on adding woodwind diagrams to lilypond, and I would love to hear lilypond users' opinions on this project. An excellent idea -- contrats on the work so far. Specifically, I would like to know from woodwind players and/or enthusiasts: 1) Are the diagrams correct in their nomenclature and positioning? One vital thing:-- The 'one', 'two' thru 'six' for the main keys/holes on all instruments are round the wrong way -- 'one' means first finger, left hand. So 'one' should be at the top, and 'six' at the bottom. 1+ Some w/w tutors also use a L1, L2, L3, R1 R2 R3 numbering system, but the low numbers are *always* at the headjoint end of the instrument and increase down to the footjoint end. Several minor things:-- Could the separator line between lh rh key be a bit longer? I like the way you only include relevant key clusters -- no need to show every key every time. Oboe: rh c cis ees keys are usually of equal size Saxophone: front f could be a bit bigger and closer to lh one; palm keys could be a bit bigger (lh d ees f); rh side keys could be a bit bigger (side bes, side c, high e). Maybe add baritone sax low A thumb key? Similar point to the low-b on the flute. Not all makes have this. Clarinet: maybe T R could be a bit smaller. Bass clarinet: some horns have an additional ees/aes lever in the lh little finger cluster; low c horns might have a 6th key for rh little finger (for low d), as well as 3 keys for rh thumb (low d, des, c) 2) Do the diagrams meet the standard of visual elegance to which you hold lilypond? I reckon so -- they're looking really nice; I like the ability to indicate depressedRing-to-open trills etc. If you are interested in extending this project to other instruments, please let me know. Maybe recorder, tin whistle, bagpipes Baroque flute, Simple-system flute (pre-Boehm keyed - used by 'Irish traditional music flute players). Simple-system clarinet. French-system bassoon. The code is written as such so that someone who knows how to use Scheme should be able to, by observing the way that the instruments are constructed, make their own instrument in the same manner. Very handy. 1+ Cheers, Ian ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user -- http://zepadovani.info ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On 6/9/10 5:12 PM, josé henrique padovani zepadov...@gmail.com wrote: I would also like to know: is the code of your woodwind diagrams available somewhere? The code is available as a patch at http://codereview.appspot.com/1425041/show Unfortunately, it doesn't include the complete files, so it would be fairly difficult for a user who is not familiar with git or patch to make it work. I hope that it will be part of LilyPond shortly. (Does it require to recompile lilypond or can it be used with includes?) No recompiling is necessary. The files just need to be added to your current LilyPond installation. Thanks, Carl ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
Em 09/06/10 21:23, Carl Sorensen escreveu: On 6/9/10 5:12 PM, josé henrique padovanizepadov...@gmail.com wrote: I would also like to know: is the code of your woodwind diagrams available somewhere? The code is available as a patch at http://codereview.appspot.com/1425041/show Unfortunately, it doesn't include the complete files, so it would be fairly difficult for a user who is not familiar with git or patch to make it work. Hi Carl, I hace used diff and patch only few times, but would really like to try... Could you please give some advices about which git / patch flags should I use to apply the patch to my current directories? (I'm on a Mac, so I would probably need to apply the patch to /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ ... ) or am I wrong? Thank you, josé -- http://zepadovani.info ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
On Wed, Jun 09, 2010 at 09:41:34PM -0300, josé henrique padovani wrote: Em 09/06/10 21:23, Carl Sorensen escreveu: Unfortunately, it doesn't include the complete files, so it would be fairly difficult for a user who is not familiar with git or patch to make it work. Could you please give some advices about which git / patch flags should I use to apply the patch to my current directories? If you seriously want to learn, then do a google search for patch to learn how to use it. If not, wait a few weeks until it's part of lilypond. This topic is too long to teach in a few emails. Cheers, - Graham ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Woodwind diagrams in lilypond w/ changes from M Watts I Hulin
Em 09/06/10 22:04, Graham Percival escreveu: On Wed, Jun 09, 2010 at 09:41:34PM -0300, josé henrique padovani wrote: Em 09/06/10 21:23, Carl Sorensen escreveu: Unfortunately, it doesn't include the complete files, so it would be fairly difficult for a user who is not familiar with git or patch to make it work. Could you please give some advices about which git / patch flags should I use to apply the patch to my current directories? If you seriously want to learn, then do a google search for patch to learn how to use it. If not, wait a few weeks until it's part of lilypond. This topic is too long to teach in a few emails. Cheers, - Graham Hi Graham, I did already used patch and diff in some codes... but I have no experience about how to use it with git (I have seen that the patch was created with a flag --git for diff, which I didn't found in diff man) and don't know which commands should I use to download from the lilypond's git repository... (just some tips would help me) I mean: I am not sure about which git flags/address/etc should I use to download the code.. (I suppose I should use git to download them and not simply download the diffs with from http://codereview.appspot.com/download/issue1425041_1.diff) Regarding patch, I would like to know if I should simply call it like this: cd /Applications/LilyPond.app/Contents/Resources/share/lilypond/current/ (I'm on a Mac) patch path-of-diffile/difffile.diff or if I should use some flags and/or call it from another place... Althought I am new to this process I think I can do it and would really appreciate some help. Thank you, josé -- http://zepadovani.info ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
