ebook img

Learning the Code PDF

56 Pages·2003·5.9 MB·
by  KingJames L.
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview Learning the Code

Learning the Code ™ Student’s Name a method for piano study http://www.learningthecode.com Book 1 written and edited by James L. King III ©2003 James Legrand King III. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with the Invariant Sections being “Introduction for teachers,” with the Front-Cover Texts being “http://www.learningthecode.com”, and with the Back-Cover Texts being “Contact the editor at [email protected] for information regarding supporting and contributing to the further development of this piano method series.” A copy of the license is included in the section entitled "GNU Free Documentation License". “Learning The Code” is a trademark of James L. King III. history 02-01-2003 release of book 1, published by James L. King III ([email protected]). 02-05-2003 minor fixes and corrections. 04-08-2003 additional extremely minor fixes, and additions to dedications page, added storefront URL on back cover. 05-06-2003 removed forum URL from back cover. 07-21-2003 major revisions on progress charts. URL and email address changed on license notices. (The old email and URL will remain active until at least January 1, 2006) 2 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. GNU free documentation license Version 1.1, March 2000 create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. Copyright (C) 2000 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA. Everyone J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section.You may omit a network location for a work that was published at least four years 0. PREAMBLE before the Document itself, or if the original publisher of the version it refers to gives permission. K. In any section entitled "Acknowledgements" or "Dedications", preserve the section's title, and preserve in the section all The purpose of this License is to make a manual, textbook, or other written document "free" in the sense of freedom: to the substance and tone of each of the contributor acknowledgements and/or dedications given therein. assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the noncommercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while equivalent are not considered part of the section titles. not being considered responsible for modifications made by others. M. Delete any section entitled "Endorsements". Such a section may not be included in the Modified Version. N. Do not retitle any existing section as "Endorsements" or to conflict in title with any Invariant Section. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do We have designed this License in order to use it for manuals for free software, because free software needs free this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct documentation: a free program should come with manuals providing the same freedoms that the software does. But this from any other section titles. License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. You may add a section entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the 1. APPLICABILITY AND DEFINITIONS authoritative definition of a standard. This License applies to any manual or other work that contains a notice placed by the copyright holder saying it can be You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, distributed under the terms of this License. The "Document", below, refers to any such manual or work. Any member of to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover the public is a licensee, and is addressed as "you". Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the or with modifications and/or translated into another language. old one. A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and or to assert or imply endorsement of any Modified Version. contains nothing that could fall directly within that overall subject. (For example, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical 5. COMBINING DOCUMENTS connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice. in the notice that says that the Document is released under this License. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of notice that says that the Document is released under this License. each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is the license notice of the combined work. available to the general public, whose contents can be viewed and edited directly and straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, In the combination, you must combine any sections entitled "History" in the various original documents, forming one and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text section entitled "History"; likewise combine any sections entitled "Acknowledgements", and any sections entitled formatters. A copy made in an otherwise Transparent file format whose markup has been designed to thwart or discourage "Dedications". You must delete all sections entitled "Endorsements." subsequent modification by readers is not Transparent. A copy that is not "Transparent" is called "Opaque". 6. COLLECTIONS OF DOCUMENTS Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML designed for human You may make a collection consisting of the Document and other documents released under this License, and replace the modification. Opaque formats include PostScript, PDF, proprietary formats that can be read and edited only by proprietary individual copies of this License in the various documents with a single copy that is included in the collection, provided that word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine- you follow the rules of this License for verbatim copying of each of the documents in all other respects. generated HTML produced by some word processors for output purposes only. You may extract a single document from such a collection, and distribute it individually under this License, provided you The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim the material this License requires to appear in the title page. For works in formats which do not have any title page as copying of that document. such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. 7. AGGREGATION WITH INDEPENDENT WORKS 2. VERBATIM COPYING A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, does not as a whole count as a Modified Version of the Document, provided no You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this compilation copyright is claimed for the compilation. Such a compilation is called an "aggregate", and this License does License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all not apply to the other self-contained works thus compiled with the Document, on account of their being thus compiled, if copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to they are not themselves derivative works of the Document. obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than conditions in section 3. one quarter of the entire aggregate, the Document's Cover Texts may be placed on covers that surround only the Document within the aggregate. Otherwise they must appear on covers around the whole aggregate. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 8. TRANSLATION 3. COPYING IN QUANTITY Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of If you publish printed copies of the Document numbering more than 100, and the Document's license notice requires Cover section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the You may include a translation of this License provided that you also include the original English version of this License. In publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. case of a disagreement between the translation and the original English version of this License, the original English You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve version will prevail. the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. 9. TERMINATION If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine- under this License. However, parties who have received copies, or rights, from you under this License will not have their readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a publicly-accessible licenses terminated so long as such parties remain in full compliance. computer-network location containing a complete Transparent copy of the Document, free of added material, which the general network-using public has access to download anonymously at no charge using public-standard network protocols. 10. FUTURE REVISIONS OF THIS LICENSE If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either 4. MODIFICATIONS of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided as a draft) by the Free Software Foundation. that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In ADDENDUM: How to use this License for your documents addition, you must do these things in the Modified Version: To use this License in a document you have written, include a copy of the License in the document and put the following A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous copyright and license notices just after the title page: versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts has less than five). being LIST. A copy of the license is included in the section entitled "GNU Free Documentation License". C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. If you have no Invariant Sections, write "with no Invariant Sections" instead of saying which ones are invariant. If you have E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. no Front-Cover Texts, write "no Front-Cover Texts" instead of "Front-Cover Texts being LIST"; likewise for Back-Cover F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version Texts. under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under license notice. your choice of free software license, such as the GNU General Public License, to permit their use in free software. H. Include an unaltered copy of this License. I. Preserve the section entitled "History", and its title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section entitled "History" in the Document, 3 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. dedications The editor wishes to thank all people who have tested the material, made submissions, suggestions, and comments. Some of these people are recognized below: Axel Ortiz Gisela Perez Allan Gabay Odie Carandang Jeanette De Lisa Keith Mead Dan Gillogly Betty Zornosa Kristene Gore Kathy Miller Paulette Hanchett 4 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. introduction Learning to play the piano or keyboard is fun. At each lesson, your teacher will give you some songs for you to learn at home. If you want to get really good, you need to play these songs every day. At first, you might not play the pieces well. But as you play the songs some more, you’ll find that you get better and better as you play them. After a while you will play your pieces very well. Soon, you may play these songs not only for your teacher, but also for your parents and for your friends and relatives. In the future, you may play in a band. People may hear your music on the radio, or see your video on televison! You might become a concert pianist who plays very hard music in front of many people. Think about how excited you’ll be when everyone stands up and cheers for you when you finish playing! You could play the organ or piano at a church or temple. Perhaps you will become a teacher! Even if you never do any of those things, you can still have fun playing your favorite songs anytime you want. You can play for yourself or maybe for a few friends, too. Many musicians know how to read a secret code. This code tells them all about the musical sounds they should play. This code is really easy and fun to learn, but only if you take some time every day to practice using it, so let’s get started! James Legrand King III (Lee) Introduction for teachers: This method book is designed to provide a solid approach to piano study and music reading, using a “landmark” system of note-reading. It is unique in using the paradigm of music as a “secret code” throughout the book. Please inform the author/editor at [email protected] with your comments, criticisms, suggestions, and praise. It is important for the editor to know what works and does not work well and how the students respond, both good and bad. Every single comment and suggestion is cherished and considered. If you obtained this book free, and would like to support further development in this method series, contact the editor at the email address given above. Book 1 is designed not only as the beginning of the Learning The Code series, but can also be used as a primer before beginning with any method book that has little or no pre-reading exercises. It may also be used as supplemental study material for students using other method books before they begin note reading on the staff. This book is released under the GNU free documentation license. Under the license, you may submit material to the editor for inclusion in later editions, or you may use the material to create your own method, provided it is also released under the GNU free documentation license. 5 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. have a seat! There are many types of keyboards. There are pianos, synthesizers, organs, and portable keyboards, not to mention harpsichords, clavinets, celestas, and clavichords. Regardless of the keyboard you use, you must sit properly if you want to play it well. Sit up straight, with your feet flat on the ground. If your feet do not touch the ground, then put a small stool on the floor (or even some books) and place your feet there. Your elbows should be just a little higher than the keyboard. Adjust the piano bench or the keyboard stand until you are sitting at the correct height, or place books on your bench and sit on them. When you play any type of keyboard, you should keep your hand relaxed and your fingers curved.Wrap your fingers around a tennis ball to see how curved your fingers should be, Play with your fingertips. Don’t let your wrists fall down on the front of the keyboard. Many people sit too close to the piano. Be sure that your knees are just underneath the keyboard. If you have to twist your wrists to play, you’re sitting too close. Some people play keyboards while standing up. If you do this, be sure that you adjust the height of your keyboard stand so that your forearms are level with the keyboard. Don’t stand too close to the keyboard when you play. Some keyboard instruments, like some synthesizers with guitar straps, and accordians, are meant to be played standing up. Even with these keyboards, curved, relaxed fingers are important. How long should I practice? It’s not really how long you practice (although that helps) but it’s what you do when you practice. At first, try to play each of your assigned pieces correctly at least 5 times every day. If you practice every day, you’ll get better much faster. Your teacher will help you learn the best way to practice. 6 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. coding the fingers Sometimes you have to use a certain finger to play a certain key when you play the piano. Pianists and keyboardists use a number code for their fingers so they know exactly which finger to use. The thumb of the left hand is called finger number 1, and the thumb of the right hand is also called finger number 1. 3 2 2 3 4 4 5 5 1 1 Left Right Hand Hand There are several ways to help you learn and remember how your fingers are numbered: 1) Place your hands together as if you are praying. Tap fingers 1 together, then fingers 2 together. While you do this, say the finger number out loud. 2) Trace an outline of your hands on a sheet of paper and number the fingers. 3) Place your hands on a table. Have someone say a finger number, then tap that finger number on the table. Later, the person calling out the numbers can also say whether to tap the right or the left hand. 4) No matter what, your thumb is finger 1. Always. Do you know right from left? The easiest way to figure out which hand is which (if you still have trouble with right and left) is to hold out your hands in front of you, making sure you’re looking at the backs of your hands. Fingers 1 and 2 on one hand will make a capital “L”. That hand is your left hand. 7 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. the keyboard All keyboards have white and black keys. The black keys are found in groups of two and three. Sometimes there is an “orphan” black key on one side of the keyboard. Low High IMPORTANT! In the secret code of music, high and low do not mean loud and soft! Playing groups of 2 black keys etc. 3 Use the right hand fingers 3 and 2. Play groups of two black keys, 2 starting from the highest group. Say “play down” as you play each key and move down to the next group of two black keys. Keep playing until you get to the lowest group of two black keys. Playing groups of 3 black keys etc. 3 2 4 Use the left hand fingers 4, 3 and 2. Play groups of three black keys, starting from the lowest group. Say “play-ing up” as you play each key and move up to the next group of three black keys. Keep playing until you get to the highest group of three black keys. Experiment with playing up and down the groups of black keys.You might even try making up a song using just the black keys! 8 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. keep the beat! Music follows a steady pulse, just like your heart does. Some sounds last just a short time and other sounds last longer. Mixing these short and long sounds together creates rhythm. The steady pulse is sometimes called the beat. Clap a steady pulse with your teacher. Then, while you’re clapping, say “ONE” with each clap. Many musicians know how to read a secret code. This code tells them about the sounds they are supposed to play and how they are supposed to play them. The rhythm you just clapped with your teacher would look like this in that secret code: q This code symbol is called a quarter note. When you are clapping once q per pulse, click, or beat, you are clapping quarter notes. Quarter notes get ONE count or beat or click. The stem of the quarter note can go either up or down. When the stem points up, it’s on the right side of the notehead. When the stem points down, it’s on the left side: Draw 3 quarter notes with stems up and 3 quarter notes with stems down. Start with Fill it in ... Add the stem ... an oval ... Now you’re done! 9 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions. count to two! Clap a steady pulse with your teacher. Then while you’re clapping a steady pulse for a while, begin to count “ONE-TWO” and clap on “one” and hold your hands together on “two.” The secret code looks something like this: This code symbol is called a half note. When you are playing one note h h and holding it for two pulses, clicks, or counts, you are playing half notes. Half notes receive TWO counts or beats or clicks. Half notes last twice as long as quarter notes. Sometimes musicians write in the counts under notes to help get the rhythm right. Under the line of notes below, write down how you would count the rhythm. Write “1” for every quarter note and “1 - 2” for every half note. Then clap and count the rhythm. Keep it slow and steady. Draw 3 half notes with stems up and 3 half notes with stems down. Start with an oval ... Add the stem ... Now you’re done! 10 ©2003 James Legrand King III. This page is part of “Learning The Code.” See the front cover for copying conditions.

See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.