https://wiki.ccarh.org/index.php?title=Special:NewPages&feed=atom&limit=50&offset=&namespace=0&username=&tagfilter=&size-mode=max&size=0CCARH Wiki - New pages [en]2024-03-29T10:28:21ZFrom CCARH WikiMediaWiki 1.33.0https://wiki.ccarh.org/wiki/Music_254/CS_275b_Spring_2024_SyllabusMusic 254/CS 275b Spring 2024 Syllabus2024-03-26T20:43:19Z<p>Craig: </p>
<hr />
<div><br />
<br />
<font size=+1><b>Music 254/CS 275b "Computational Music Analysis " <br> Stanford University (Spring 2024).</b></font><br />
<br />
This music information retrieval course (previously listed as "Music<br />
Query, Analysis, and Style Simulation") builds on the foundation<br />
of [[Music 253|Music 253/CS 275A]] (Symbolic Musical Information).<br />
Using an open-source analysis platform (such as the<br />
[https://github.com/humdrum-tools/humdrum-tools Humdrum Toolkit]<br />
(unix/bash shell), [[Humdrum Extras]] (C++), [https://humlib.humdrum.org<br />
humlib], [https://verovio.humdrum.org VHV]. [[HumdrumR]], or<br />
[[Music21]] (Python), or their preferred programming language/environment)<br />
students plan and design their own applications involving symbolic<br />
musical data. See Online Resources after syllabus.<br />
<br />
The first four weeks cover basic areas of music analysis and retrieval<br />
and introduce basic principles of using the Humdrum Toolkit. Students<br />
may be assigned individual reading assignments pertinent to their<br />
research topic areas. The remaining six weeks are spent on individual<br />
project development, with weekly reports and discussions. Extensive<br />
help is available in the lab during hours allotted to class time.<br />
Students give verbal and written reports on their research at the<br />
end of the quarter. Some projects may be appropriate for continuation<br />
in independent-study modules.<br />
<br />
{| class="wikitable"<br />
|-<br />
! For class Zoom link<br />
|-<br />
| Please contact esfield@stanford.edu or craig@ccrma.stanford.edu<br />
|}<br />
<table style="background:white;" cellpadding=0 cellspacing=0 border=0><br />
<br />
<br />
<tr><br />
<td align=right><b>Meeting&nbsp;times:</b><br />
<td width=15></td><br />
<td>Tuesdays & Thursdays 1:30&ndash;3:00</td><br />
</tr><br />
<br />
<tr><br />
<td align=right><b>Location:</b></td><br />
<td></td><br />
<td> Online </td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Instructors:</b></td><br />
<td></td><br />
<td> Eleanor Selfridge-Field (esfield<small>&#64;</small>stanford.edu)<br>Craig Sapp(craig<small>&#64;</small>ccrma.stanford.edu)<br />
<br />
<tr valign=baseline><br />
<td align=right><b>Office Hours:</b></td><br />
<td></td><br />
<td> after class and by appointment on Zoom/Skype/Google Hangouts </td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Credits:</b></td><br />
<td></td><br />
<td>2&ndash;4</td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Grading:</b></td><br />
<td></td><br />
<td><br />
25% class participation, 75% project<br />
<ul> <li> Project proposal: 2+ pages, due Thursday. 18 April 2024<br />
<li> Project progress report: 4+ pages, Thurs. 9 May 2024<br />
<li> Project presentation in class: Tues. 4 June 2024<br />
<li> Project writeup: 10&ndash;20 pages <br />
* <b>Graduating</b> in June 2024: Due on <b>7 June 2024</b> 11:59pm.<br />
* <b>Not graduating</b>: Due on <b>11 June</b> 2024 11:59pm.<br />
</ul><br />
</td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Website:</b></td><br />
<td></td><br />
<td>[http://music254.stanford.edu music254.stanford.edu]<br>[http://wiki.ccarh.org/wiki/Music%20254 wiki.ccarh.org/wiki/Music 254] [[Music 254|Overview]] of topics presented in Music 254.<br />
</td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Prerequisites:</b></td><br />
<td></td><br />
<td> Completion of [[Music 253|Music 253/CS 275b]], or demonstrated ability to use notation and sound software and associated requirements. <br />
<td><br />
</tr><br />
<br />
<tr valign=baseline><br />
<td align=right><b>Textbook:</b></td><br />
<td></td><br />
<td> E. Selfridge-Field, ed., <i>Beyond MIDI: The Handbook of Musical Codes</i> (MIT Press, 1997). [http://beyondmidi.ccarh.org/beyondmidi-600dpi.pdf Available online] by permission of the publisher.<br />
</td><br />
</tr><br />
<br />
</table><br />
<br />
<br />
<br />
<br />
== Syllabus ==<br />
<br />
Go to week: <font color="gray" size="-1">Harmony</font> [[#week1|1]] | <font color="gray" size="-1">Melody</font> [[#week2|2]] | <font color="gray" size="-1">Rhythm</font> [[#week3|3]] | <font color="gray" size="-1">Harmony</font> [[#week4|4]] | <font color="gray" size="-1">RegEx</font> [[#week5|5]] | <font color="gray" size="-1">Programming</font> [[#week6|6]] | [[#week7|7]] | [[#week8|8]]<br />
<br />
See also [[Music 253/CS_275a_Winter_2024_Syllabus | Music 253/CS 275a Syllabus]]<br />
<br />
=== Week 1 === <br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 1<div id="week1"></div> || 2 April, 4 April 2024 || <br />
<br />
<b>Lectures</b><br />
<br />
* Lecture 1A. [https://esf.ccarh.org/CS275B-Mus254/01A_Symbolic_Music_Analysis_2023.pdf Computational Musicology]<br />
* Lecture 1B. [https://esf.ccarh.org/CS275B-Mus254/01B_MelodicSearch_2023.pdf Melodic Search: Fundamentals] <br />
<br />
* [https://docs.google.com/presentation/d/1DULWG7P81Qk8QpKXlisgPxRpxRSmujuzkLZrxkz2Kec/edit?usp=sharing%5D Verovio]<br />
<br />
<!--<br />
* [http://wiki.ccarh.org/wiki/Humdrum_Lab_1 Humdrum Lab 1]<br />
* [https://docs.google.com/presentation/d/1YmKGR1hfU7XP8kPEbC6yYuCfAJnn_PvlnedTjqSvHWA/edit?usp=sharing Humdrum data]<br />
* [https://docs.google.com/presentation/d/1KFSNGbIsaXhuVpuapms1eUUrhJU7XPDt2lXMvopMYrY/edit?usp=sharing Composite Rhythm] (29 March 2022)<br />
* [https://docs.google.com/presentation/d/1-3OiSNj-hpSEfJf_O6xOQOqMGtvpLjpe98Hx0tbbQDg/edit#slide=id.g120f92c5e2e_0_0 Computational Style Analysis] (31 March 2022)<br />
<br />
--><br />
<br />
<b> Homework for new students </b><br />
<br />
* For new students, enter [[Media:KernEncoding.pdf| this music]] in [http://verovio.humdrum.org Verovio Humdrum Viewer]. Try saving them as HTML scores from the File menu. Also useful, see this [http://doc.verovio.humdrum.org/humdrum/getting_started/ introduction to encoding music in Humdrum].<br />
|-<br />
|}<br />
<br />
=== Week 2 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 2<div id="week3"></div> || 9 April 2024 || <br />
<b>Lectures: Approaches to melodic and other musical-similarity assessment</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/02A_TimbralSimilarity_2023.pdf Timbral Similarity]<br />
* [https://docs.google.com/presentation/d/1F71dwp-Q467WBL0yBSz6QkEk5fDkTEksYKi5xTfXGR8/edit#slide=id.g4cd0be3fa2_2_75 Sonic Visualiser]<br />
<br />
|-<br />
| 2 || 11 April 2024 || <br />
<br />
* [https://esf.ccarh.org/CS275B-Mus254/02b_Cope1-2023.pdf Cope (1): Experiments in Musical Intelligence]<br />
<br />
* [https://docs.google.com/presentation/d/1ZuPHnMlSMHHitmYtSvtMRLkVDvFkd1ob82sO5pdLrXs/edit#slide=id.p Humdrum file parsing in C++]<br />
<br />
|-<br />
|}<br />
<br />
=== Week 3 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 2<div id="week2"></div> || 16 & 18 April 2024 || <br />
<b>AI Audio Compositions, Emily Howell Lectures (Style Synthesis)</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/03a_AIMusGen-2023.pdf AI-audio-based music generation]<br />
* [https://esf.ccarh.org/CS275B-Mus254/03b_Emmy-Emily-2023.pdf Cope (2): From Emmy to Emily Howell] <br />
<br />
*[https://docs.google.com/presentation/d/1PydXSxNBRelI8frIUGP9UwD7DoZ5r5QUiLZCEupjC2A/edit#slide=id.g5700a91e56_2_18 Performance similarity in Chopin mazurkas]<br />
<br />
* [https://docs.google.com/document/d/1KC8cJIHYe5WW9Tji_Heq5iYpmwCA_Nt59TIC1CKoiyA/edit# Class programming notes]<br />
<br />
|-<br />
|}<br />
<br />
=== Week 4 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 4<div id="week4"></div> || 23 April 2024 || <br />
<br />
<b>Lectures: Practical Realities of Research</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/04a_Search-Effectiveness.pdf Search Effectiveness]<br />
* [Tony demo] by Robert.<br />
* [https://docs.google.com/presentation/d/1jOJa7CTm8O5y-RxXDV9wboGFEgXJifG2O4QxJhtHe_o/edit?usp=sharing Keyscapes]<br />
|-<br />
| 4 || 25 April 2024 || <br />
<b> Audio Similarity</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/04b_Audio-similarity.pdf Audio similarity]<br />
*[https://docs.google.com/presentation/d/10f3kKhbv1R5S07Dzh6NBNHpm85BWUzhJBEymqRe2qUA/edit#slide=id.gd0281746a5_2_404 Similarity with Normalized and Unnormalized Correlation]<br />
|-<br />
|}<br />
<br />
=== Week 5 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 5<div id="week5"></div> || 20 April 2024 ||<br />
<b>Audio similarity</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/04b_Audio-similarity_2023.pdf Audio similarity]<br />
<br />
* [https://docs.google.com/presentation/d/1D8dGfuqJK0x6eEYoirkExsP5XCgz7hszNo8IJ_kRTgs/edit#slide=id.gcc08b2512a_0_28 Harmony analysis tools]<br />
<br />
<br />
|-<br />
| 5 || 2 May 2024 ||<br />
* [https://esf.ccarh.org/CS275B-Mus254/05b_Datasets-music-research23.pdf Datasets for music research]<br />
<br />
<br />
<br />
<b> Regular Expressions </b><br />
* [https://docs.google.com/presentation/d/1H_bjIvY0tr4XAs0g1fWi1DHARD-YKkOWpi0j5GXNSwc/edit#slide=id.p21 Regular Expressions]<br />
<br />
<br />
|-<br />
|}<br />
<br />
=== Week 6 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 6<div id="week6"></div> || 7 May 2024 ||<br />
<b>Compositional schemata</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/06A_CompositionalSchemata-2021.ppt Compositional schemata]<br />
<br />
* Quality Control in Research: Heinz Roggenkemper (guest lecture)<br />
* Project report: Adaptive tuning (Shray Alag)<br />
<br />
<b>Counterpoint II</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/06A_Artificial-Counterpoint_2019.pptx Counterpoint II]<br />
<b>Rhythm and Meter</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/06B_RhythmMeter_2019.pptx Rhythm and Meter]<br />
<b> Programming for Humdrum files </b><br />
* [[Humdrum Extras]] &mdash; C++ library for processing Humdrum files<br />
* [https://ratioscore.humdrum.org Ratioscores: A text-based system for just intervals], Julie Zhu and Craig Sapp<br />
|-<br />
| 6 || 9 May 2024||<br />
<br />
* Project reports: Leon Bi and Charles Tsai (DJ transitions); Sammy Park (Guqin Digital Scores); Dominic DeMarco (Orchestral Pairings in Band Music)<br />
<br />
<b> Sonority distributions by bass-line scale degrees </b><br />
* [[Media:CorelliBassline.pdf | Corelli & Rule-of-the-octave data selection]] (PDF slides)<br />
<br />
* [https://docs.google.com/presentation/d/13MO-frSYbk5eIcC8Vi-o6Gxv3g7n5ktNLuo1e2Xi4bE/edit?usp=sharing Melodic aspects of barbershop quartet music]<br />
|-<br />
|}<br />
<br />
=== Week 7 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 7 || 14 May 2024 ||<br />
<ul><li>Wolfgang Drescher, guest lecture</li><br />
<li>Katherine Wong, guest presentation</li><br />
</ul><br />
|-<br />
| 7 || 16 May 2024 ||<br />
<b>Recent developments in MIR</b><br />
* [https://esf.ccarh.org/254/06a_CompositionalSchemata-2022.ppt Compositional Schemata] <br />
07A_RecentWork_SymbolicMIR_2021.ppt 07A. Recent Work in Symbolic MIR]<br />
<b>Recent Work in Harmonic Analysis</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/07B_HarmonicModels_2021.ppt 07B. Harmonic Models]<br />
* [https://docs.google.com/presentation/d/1adjEeWXmypmti8HjjqUXBrgrV2RyDG-UP3T7Gcj_mEA/edit?usp=sharing Keyscapes]<br />
|-<br />
|}<br />
<br />
=== Week 8 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 8 || 21 May 2024 ||<br />
<br />
<b>Recent Research (and Challenges) in MIR</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/08A_SearchEngines-EncodedScores_2023.pdf Score search engines]<br />
* HumdrumR <br />
<br />
<b> Project development</b> <br />
<br />
|-<br />
| 8 || 23 May 2024 ||<br />
<b>Rhythm and Meter</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/08B_Rhythmic%20perception_2023.pdf Rhythm, meter, and their perception]<br />
<br />
<b> Project development</b><br />
<br />
|-<br />
|}<br />
<br />
=== Week 9 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 9a || 28 May, 30 May 2024 ||<br />
<b> Vocal clones</b><br />
* [https://esf.ccarh.org/CS275B-Mus254/09_Vocal-clones-2023.pdf Vocal clones]<br />
<br />
<b> MEI</b><br />
* MEI (Music Encoding Initiative) Release 2.0<br />
|-<br />
|}<br />
<br />
=== Week 10 ===<br />
<br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" <br />
|- {{Style|table header}}<br />
! scope="col" width="20px" | Week<br />
! scope="col" width="95px" | Dates<br />
! scope="col" width="500px" | Topics<br />
|-<br />
| 10 || 4 June 2024 ||<br />
<b> Project presentations in class.</b><br />
|-<br />
| 11 || 7 June 2024 ||<br />
<b> Project write-ups</b> for students <b>taking a degree</b> in June 2024.<br />
|-<br />
| 12 || 11 June 2024 ||<br />
<b> Project write-ups</b> for students <b>continuing</b> at Stanford.<br />
|-<br />
|}<br />
<br />
== Online resources for this class ==<br />
<br />
<b>Data/Data entry</b><br />
* [[Media:dataentry.pdf | Data/Data entry in Humdrum]] (PDF slides)<br />
** [http://kern.ccarh.org KernScores]: digital library of scores in the **kern format<br />
*** [http://kern.ccarh.org/help/data] introduction to KernScores<br />
*** [http://kern.ccarh.org/cgi-bin/kscuts] shortcuts to data in KernScores<br />
*** [http://kern.ccarh.org/browse] browse collections in KernScores<br />
** [http://jrp.ccarh.org]: Josquin Research Project: digital library of early Renaissance polyphony<br />
** [http://extras.humdrum.org/man/xml2hum xml2hum]: MusicXML to Humdrum converter<br />
** [http://museinfo.sapp.org/examples/humdrum/mid2hum.cpp mid2hum]: MIDI to Humdrum converter (works in many cases, but better to convert MIDI first to MusicXML then import).<br />
<br />
<b>Humdrum & MIDI</b><br />
* [[Media:Humdrum2Midi.pdf | Humdrum to MIDI]] (PDF slides)<br />
<br />
<br />
<b>Harmony II</b><br />
* [https://docs.google.com/presentation/d/1o2zHVB7VWBbFHdz3-3GOvGl7GDOiyjRdDlvicnfE4vg/edit?usp=sharing Harmony II] Key analysis<br />
** Key-cycles:<br />
*** [http://kern.ccarh.org/browse&l=hummel/preludes Hummel Op. 67 preludes]<br />
*** [http://kern.ccarh.org/browse&l=hummel/preludes Chopin Op. 28 preludes]<br />
*** [http://kern.ccarh.org/browse&l=wtc J.S. Bach Well-Tempered Clavier]<br />
** [http://extras.humdrum.org/man/keycor keycor]: harmonic structure plots.<br />
** [http://extras.humdrum.org/man/mkeyscape mkeyscape]: harmonic structure plots.<br />
*** [http://extras.humdrum.org/man/mkeyscape/beet-sonata Beethoven piano sonata keyscapes]<br />
*** [http://extras.humdrum.org/man/mkeyscape/moz-sonata Mozart piano sonata keyscapes]<br />
*** [https://ccrma.stanford.edu/~craig/keyscape/class Lots of keyscapes]<br />
** [http://extras.humdrum.org/man/transpose transpose]: Transpose score to specific key or by interval.<br />
<br />
<br />
<b>Regular Expressions (Text-based searching)</b><br />
* [https://docs.google.com/presentation/d/1H_bjIvY0tr4XAs0g1fWi1DHARD-YKkOWpi0j5GXNSwc/edit?usp=sharing Introduction to Regular Expressions]<br />
<br />
<b> Harmony-related Humdrum tools </b><br />
<br />
* [https://docs.google.com/presentation/d/1D8dGfuqJK0x6eEYoirkExsP5XCgz7hszNo8IJ_kRTgs/edit?usp=sharing Humdrum Harmony I]<br />
<br />
* [http://www.humdrum.org/Humdrum/commands/hint.html hint]: Harmonic intervals.<br />
* [http://extras.humdrum.org/man/tntype tntype]: twelve-tone chord prototypes.<br />
* [http://www.humdrum.org/Humdrum/commands/key.html key]: Krumhansl-Schmuckler key-finding algorithm.<br />
* [http://extras.humdrum.org/man/keycor keycor]: generalization of key command.<br />
* [http://extras.humdrum.org/man/sonority sonority]: triadic chord descriptions of sonorities.<br />
* [https://docs.google.com/presentation/d/1-zZf8ti35jR4l-wcAdrvD6mP91-6aYvaV12Sf-7YPSM/edit?usp=sharing prange and cint tools]<br />
<br />
<b>Rhythm and score manipulation tools</b><br />
* [https://docs.google.com/presentation/d/1gynqYYWm9EEBD1PfHS48YuEokeC4VeABOzI3c_RiZWI/edit?usp=sharing Rhythm Tools available in Humdrum]<br />
** [http://www.humdrum.org/Humdrum/commands/timebase timebase]: create uniform duration for each Humdrum file data line.<br />
** [http://extras.humdrum.org/man/beat beat]: label metric beats in Humdrum file.<br />
** [http://extras.humdrum.org/man/gettime gettime]: calculate performance time in seconds (according to tempo markings).<br />
** [http://extras.humdrum.org/man/thrux thrux]: expand repeats to performance sequence<br />
** [http://extras.humdrum.org/man/minrhy minrhy]: identify minimum integral rhythmic unit in score<br />
** [http://www.humdrum.org/Humdrum/commands/assemble assemble]: merge parts into a single score<br />
** partjoin: automation script to merge parts into a single score (preserves grace notes, uses minrhy and timebase)<br />
** [http://www.humdrum.org/Humdrum/commands/ditto ditto]/[http://extras.humdrum.org/man/dittox dittox]: resolve null tokens<br />
** [http://extras.humdrum.org/man/hgrep hgrep]: search for patterns in Humdrum file data.<br />
<br />
<b> Performance analysis tool </b><br />
<br />
* [https://docs.google.com/presentation/d/1F71dwp-Q467WBL0yBSz6QkEk5fDkTEksYKi5xTfXGR8/edit#slide=id.g4cd0be3fa2_2_75 Sonic Visualiser]<br />
<br />
** Support tools:<br />
*** [http://www.humdrum.org/Humdrum/commands/assemble.html assemble]: merge separate spines into single data stream.<br />
*** [http://extras.humdrum.org/man/serialize serialize]: convert Humdrum data into single spine.<br />
*** [http://extras.humdrum.org/man/humcat humcat ]: concatenate multiple scores together (download data from web).<br />
*** [http://extras.humdrum.org/man/ridx ridx]: remove various components of Humdrum file structure<br />
*** [http://www.humdrum.org/Humdrum/commands/ditto.html ditto]: resolve meaning of null tokens.<br />
*** [http://extras.humdrum.org/man/humsplit humsplit]: split segmented Humdrum file streams into separate files.<br />
** Unix tools:<br />
*** [http://en.wikipedia.org/wiki/Command_line command line]<br />
*** [http://en.wikipedia.org/wiki/List_of_Unix_utilities list of command-line programs]<br />
*** [http://en.wikipedia.org/wiki/Sort_(Unix) sort]: sort lines of data alphabetically or numerically.<br />
*** [http://en.wikipedia.org/wiki/Uniq uniq]: Remove/count successively repeated lines of text.<br />
* [[Media:pitchmix-markov.pdf|Pitchmix and Markov analysis of composite sonorities]]<br />
<br />
<b>Melody Lab</b><br />
* [[Humdrum Lab 2]]<br />
<br />
* [https://docs.google.com/presentation/d/1vjQdN2bdK5-YJmkSIcYmnF6Z8v6PkimIV-Jl8ZCmmeQ/edit?usp=sharing Melody Tools available in Humdrum]<br />
** melody tools:<br />
*** [http://www.humdrum.org/Humdrum/commands/mint mint]: Melodic intervals<br />
*** [http://extras.humdrum.org/man/scaletype scaletype] Simple scale type categorizer<br />
*** [http://extras.humdrum.org/man/tindex tindex]: Thema indexer.<br />
*** [http://extras.humdrum.org/man/themax themax]: Thema search.<br />
*** [http://extras.humdrum.org/man/theloc theloc]: Thema localizer.<br />
*** [http://www.humdrum.org/Humdrum/commands/context context]: melodic n-grams<br />
*** [http://extras.humdrum.org/man/prange prange]: Pitch range tool.<br />
** support tools:<br />
*** [http://www.humdrum.org/Humdrum/commands/kern kern]: remove rhythms from note data.<br />
*** [http://extras.humdrum.org/man/myank myank] Yank measures from a full score.<br />
*** [http://www.humdrum.org/Humdrum/commands/extract extract]: extract spines from Humdrum file.<br />
*** [http://extras.humdrum.org/man/extractx extractx]: Humdrum Extras version of extract<br />
*** [http://extras.humdrum.org/man/hgrep hgrep]: Humdrum-aware greep.<br />
*** [http://extras.humdrum.org/man/autostem autostem]: automatic stemming of notes.<br />
** unix:<br />
*** [http://en.wikipedia.org/wiki/Head_(Unix) head]: show only starting lines of text.<br />
*** [http://en.wikipedia.org/wiki/Grep grep]: search text for generalized regular expressions.<br />
*** [http://en.wikipedia.org/wiki/Grep egrep]: enhanced grep (adds additional wildcards).<br />
*** [http://en.wikipedia.org/wiki/Sed sed]: Stream editor (search and replace).<br />
** graphics (unix):<br />
*** [http://netpbm.sourceforge.net/doc/pstopnm.html pstopnm]: a converter from PostScript to bitmaps.<br />
*** [http://www.imagemagick.org/script/convert.php convert]: Imagemagick tool for manipulating images.<br />
*** [http://ghostscript.com/doc/current/Ps2pdf.htm ps2pdf]: convert PostScript into PDF files.<br />
<br />
== General Policies and University Rules ==<br />
<br />
General policies and university rules:<br />
<br />
# <i>Delivery times</i>:<br />
##Assignments: by the start of the class for which they are due.<br />
## <i>Project writeup</i>: by 11 p.m. 7 or 11 June 2022 by 11p.<br />
# <i>Honor code</i>: We will act and expect you to act according to the [http://studentaffairs.stanford.edu/judicialaffairs/policy/honor-code Stanford Honor Code].<br />
# <i>Students with disabilities</i>: Students who may need an academic accommodation based on the impact of a disability must initiate the request with the Student Disability Resource Center (SDRC) located within the Office of Accessible Education (OAE). SDRC staff will evaluate the request with required documentation, recommend reasonable accommodations, and prepare an Accommodation Letter for faculty dated in the current quarter in which the request is being made. Students should contact the SDRC as soon as possible since timely notice is needed to coordinate accommodations. The OAE is located at 563 Salvatierra Walk (phone 723-1066).<br />
# <i>Students in distress</i>: Stanford offers an abundance of resources for students dealing with problems of a personal nature. <br />
## <i>Confidential support</i>: <b>(650) 736-6933</b> <br />
## <i>Crisis hotline</i>: <b>(650) 725-9955</b><br />
## <i>Title IX questions</i>: <b>(650) 497-4955</b></div>Craighttps://wiki.ccarh.org/wiki/Using_SCORE_in_BoxerUsing SCORE in Boxer2024-02-14T04:47:34Z<p>Craig: </p>
<hr />
<div>Below are instructions for running SCORE in Boxer, which is an MS-DOS emulator for MacOS (based on DosBox).<br />
<br />
== Download the Boxer app ==<br />
<br />
* The most recent version I can find is located on the GitHub page:<br />
<br />
https://github.com/MaddTheSane/Boxer/releases/tag/AS-beta-4.1<br />
<br />
This version is compiled for both Intel and ARM64 (Apple M1, aka "Silicon") CPUs.<br />
<br />
Download the Boxer.zip file on that page:<br />
<br />
https://github.com/MaddTheSane/Boxer/releases/download/AS-beta-4.1/Boxer.zip<br />
<br />
* Then unzip and save in /Applications<br />
<br />
=== Related links ===<br />
<br />
* The homepage for Boxer is: http://boxerapp.com. The version of the Boxer program was last updated in 2016, and as I recall, it is compiled for 32-bit (MacOS no longer allows 32-bit programs after version 10.15).<br />
<br />
* A 64-bit compiled version can be found on https://boxer.thec0de.com. I successfully have used version 2.0, but trying the 4.1 beta on that page, there was some annoying bug where it continually asked for permissions in the MacOS settings, even after it was granted permission (I even tried rebooting). The related Boxer executable found at https://github.com/MaddTheSane/Boxer/releases/tag/AS-beta-4.1 behaved better, so that is the best to install.<br />
<br />
== Installing scor4.boxer ==<br />
<br />
* Download the emailed location to this file, then unzip and move to where you want to store it (I placed it in my home directory (~/scor4.boxer), or you can place it on the Desktop, etc.).<br />
<br />
== Setting up D drive for saving SCORE files ==<br />
<br />
* Create a directory to save your SCORE files. It can have any name/location. I am using ~/score-files.<br />
<br />
mkdir ~/score-files<br />
<br />
* Run ~/scor4.boxer either by double-clicking on it in the Finder, or from the command line:<br />
<br />
open ~/scor4.boxer<br />
<br />
* The first time you run it, it might suggest or ask for a command to run when you start Boxer (I don't see this prompt because maybe there is a setting remembered from a previous installation of Boxer). If there is a prompt, you want Boxer to run:<br />
<br />
C:\scor4.bat<br />
<br />
* Next you need to set up a D drive for saving SCORE files. Go to the Drives menu for Boxer at the top of the window and select "Add DOS Drive...":<br />
<br />
[[File:drive-menu-options.png|200px|thumb|center|Drives &rarr; Add DOS Drive]]<br />
<br />
* Then select the directory/folder that you created for saving SCORE files:<br />
<br />
[[File:drive-selection.png|500px|thumb|center|Select diretory/folder for use as D drive]]<br />
<br />
* Then click on the blue button labeled "Přidat disk" (Czech for "Add disk").<br />
<br />
* In order to access the new D drive, quit Boxer and restart scor4.app again.<br />
<br />
== Test the SCORE files directory ==<br />
<br />
* You should now be able to read and write to the D drive you set up (~/score-files for me).<br />
<br />
* If you want to do a basic test, save the following text to a file called ~/score-files/exam1.pmx, or ~/score-files/exam1.txt (since it is plain text):<br />
<br />
8 1<br />
3 1 1.500<br />
17 1 9.500 0 1<br />
18 1 14.000 0 99 1<br />
1 1 23.000 9 20 0 1.5 0 10<br />
1 1 38.703 8 20 0 0.5 0 1<br />
1 1 43.938 7 20 0 1.0<br />
1 1 54.406 5 10 0 1.0<br />
14 1 64.875 1<br />
1 1 68.375 4 10 0 1.0<br />
1 1 78.844 6 10 0 1.0<br />
1 1 89.313 5 10 0 1.0<br />
1 1 99.781 7 20 0 1.0<br />
14 1 110.250 1<br />
1 1 113.750 6 10 0 1.0<br />
1 1 124.219 8 20 0 1.0<br />
1 1 134.688 9 20 0 1.0<br />
1 1 145.156 8 20 0 1.0<br />
14 1 155.625 1<br />
1 1 159.125 2 10 0 1.0<br />
1 1 169.594 4 10 0 1.0<br />
1 1 180.063 5 10 0 1.0<br />
1 1 190.531 5 10 0 1.0<br />
14 1 200.000 1 2<br />
<br />
(Next Tuesday we will look at this form of SCORE data which is derived from the text you type in in input mode.)<br />
<br />
* Then in the SCORE editor type this command to load the data:<br />
<br />
re exam1.pmx<br />
<br />
or<br />
<br />
re exam1.txt<br />
<br />
And if successful, you should see this view in SCORE:<br />
<br />
<br />
[[File:score-exam1.png|500px|thumb|center|Viewing loaded PMX data in SCORE (if the D drive is successfully set up).]]<br />
<br />
* You can also try the "dir" command in SCORE to look at a list of files on the D drive:<br />
<br />
[[File:score-dir.png|500px|thumb|center|Use "DIR" to list files on the D drive (or ~/score-files in MacOS Finder]]<br />
<br />
There are three files: "#MUSDIR#.TMP" which is some temporary file that SCORE uses, "EXAM1.PMX" which is the test file, and "SCORE.SAV" which is also a temporary file that is the default name for saving data to (don't save data there as it will likely get overwritten at some point by SCORE).<br />
<br />
<br />
Compare the "parameter matrix" text above to the original input-mode data:<br />
<br />
IN1 0 0 1.0000 200<br />
0 200<br />
tr/k1s/com/d5/pc/b/g/m/f/a/g/b/m/a/c/d/c/m/d4/f/gx2/mh;<br />
q./e/qx2/qx12;<br />
g<br />
<br />
You can also save this to a file and use "RE" to read it into the SCORE editor.<br />
<br />
The two lines above the 5-stage input data are the options set in the top menu in input mode. IN1 means place on staff 1. The second line, "0 200" means the staff will cover the entire page width.<br />
<br />
== Keyboard shortcuts in Boxer ==<br />
<br />
Boxer has better support for emulating keystrokes than DosBox. Here are some of the more important ones:<br />
<br />
<br />
<center><br />
{| class="wikitable" cellpadding="5" cellspacing="0" border="1" style="width:700px"<br />
|- {{Style|table header}}<br />
! scope="col" width="150px" | Key sequence<br />
! scope="col" width="100px" | Meaning<br />
! scope="col" width="400px" | Description<br />
|-<br />
| {{keypress|{{command}}|F}} || Full screen||Toggle between full-screen and window display modes.<br />
|-<br />
| {{keypress|Fn|M}} || Insert|| Equivalent to {{keypress|Insert}} key in MS-DOS / Windows.<br />
|-<br />
| {{keypress|Fn|&larr;}} || Home || Equivalent to {{keypress|Home}} key in MS-DOS / Windows.<br />
|-<br />
| {{keypress|{{command}}|V}} || Paste || Paste text copied from OS X environment with {{keypress|{{command}}|C}}.<br />
|-<br />
| {{keypress|{{command}}|Shift|S}}|| Screenshot || Screen capture. PNG file written to desktop. But this can also be done using MacOS command-shift-4).<br />
|-<br />
| {{keypress|Click}} || Capture mouse || Clicking in the MS-DOS window passes control of the mouse cursor to the MS-DOS window.<br />
|-<br />
| {{keypress|{{command}}|Click}}|| Mouse out || Release the mouse from the DOS environment back to the OS X system.<br />
|}<br />
</center><br />
<br />
* The most important action is command-click, which releases the mouse from Boxer.app.<br />
<br />
* The next most important is Fn-m (press and hold the Fn key and then press m). This toggles between insert and overwrite mode. Insert mode allows you to use the arrow to to back to some text in input mode and then delete/add next text. Overwrite mode would cause you to have to type in everything afterwards as well.<br />
<br />
* It is easy to resize the boxer window (unlike DosBox).<br />
<br />
* And most importantly, you can copy-and-paste into the Boxer.app window.<br />
<br />
== Next steps ==<br />
<br />
* An important thing to be aware of is that MS-DOS files can only have 8+3 characters in their names: 8 characters for the filename, and 3 for the file extension. So when saving files in SCORE, limit the length of the filenames to this. Also in order to load a file from the MacOS filesystem, preferably give it an 8+3 filename (otherwise there will be a strange name that needs to be loaded in SCORE).<br />
<br />
* Try entering the short SCORE examples as a warm-up exercise for the first SCORE homework: [[SCORE User Input]]<br />
<br />
* A useful reference for getting started with using the SCORE interface: [[SCORE Survival Guide]]<br />
<br />
* Here is a list of useful SCORE commands: http://bit.ly/score-commands<br />
<br />
* The first homework for SCORE typesetting is: [[SCORE user input 2]]</div>Craighttps://wiki.ccarh.org/wiki/Using_SCORE_in_DosBoxUsing SCORE in DosBox2024-02-13T04:45:23Z<p>Craig: /* MacOS installation */</p>
<hr />
<div><br />
= Windows installation =<br />
<br />
Installation should be nearly identical to installing in MacOS, so tell me if there are any significant differences.<br />
<br />
= MacOS installation =<br />
<br />
There seems to be a bug in the emulator related to showing slurs at the end of data entry:<br />
<br />
[[File:dosbox-crash.png|400px|thumb|center|DosBox crash after adding a slur input mode.]]<br />
<br />
The last line of input for the slurs was a single slur from the first note to the laste ("1 8;"). Here is the input for the test:<br />
<br />
tr/c4/pd/e/f/g/a/b/c/mh;<br />
qx8;<br />
;<br />
;<br />
1 8;<br />
<br />
If there are no slurs added in input mode, then there is no crash:<br />
<br />
[[File:dosbox-nocrash.png|400px|thumb|center|DosBox with no slurs added in input mode.]]<br />
<br />
Here are the input stages used:<br />
<br />
tr/c4/pd/e/f/g/a/b/c/mh;<br />
qx8;<br />
;<br />
;<br />
;<br />
<br />
So using SCORE with DosBox should not be used unless you don't want to add slurs. Trying to add the slur later in the main editor also causes a crash:<br />
<br />
[[File:dosbox-crash-command.png|400px|thumb|center|DosBox with no slurs crash in command mode.]]<br />
<br />
<br />
<br />
<br />
== Download and install DosBox ==<br />
* Install DosBox for Mac OS X version 0.74-3-3 dmg (Universal) from the download page of DosBox: [https://www.dosbox.com/download.php?main=1]<br />
<br />
[[File:dosbox-download-page.png|400px|thumb|center|DosBox download page.]]<br />
<br />
* The Mac OS X link takes you to sorceforge [https://sourceforge.net/projects/dosbox] to download the application:<br />
<br />
[[File:sourceforge-download-page.png|400px|thumb|center|DosBox download page on sourceforge.]]<br />
<br />
* Open the downloaded dmg file:<br />
<br />
[[File:dosbox-dmg.png|200px|thumb|center|Downloaded DoxBox dmg file.]]<br />
<br />
* The following files will be displayed. Copy the DOSBox.app program to "/Applications" or "~/Applications".<br />
<br />
[[File:dosbox-files.png|500px|thumb|center|Downloaded files for DosBox.]]<br />
<br />
== Download SCORE file == <br />
<br />
* Unzip the SCORE zip file and store where you want it to be stored. It should be able to go anywhere such as in your home directory, the Desktop, or a class-related folder. I would avoid having the full path contain any spaces, which could potentially cause problems. I place it at "/Users/craig/score-dosbox". (i.e., in the home directory).<br />
<br />
[[File:dosbox-score.png|500px|thumb|center|Unzipped SCORE folder for DosBox.]]<br />
<br />
* Run score by typing without quotes: "c:\scor4\scor4.bat". You should then see the SCORE splash page:<br />
<br />
[[File:dosbox-score-splash.png|500px|thumb|center|SCORE splash page after starting SCORE.]]<br />
<br />
== Run DosBox ==<br />
<br />
* Note that there may be access permissons required the first time DosBox is run (so accept any security permission requests).<br />
<br />
* Open the DosBox app (double click on "/Applications/DOSBox.app" or put in your Dock). You should see this view after a brief splash page:<br />
<br />
[[File:dosbox-open.png|500px|thumb|center|Starting window for DosBox.]]<br />
<br />
* Make note of where you installed the score-dosbox directory/folder. There are two directories that need to be connected to DosBox as the C: and D: drives. For me the C: drive is /Users/craig/score-dosbox/c_drive, and the D: drive is /Users/craig/score-dosbox/d_drive.<br />
<br />
* You need to type these two commands in DosBox:<br />
<br />
mount C /Users/craig/score-dosbox/c_drive<br />
<br />
and<br />
<br />
mount D /Users/craig/score-dosbox/d_drive<br />
<br />
[[File:dosbox-mount.png|500px|thumb|center|Mounting C: and D: drives in DosBox.]]<br />
<br />
* Now you can start score with the command:<br />
<br />
c:\scor4\scor4.bat<br />
<br />
and you should see the SCORE splash page:<br />
<br />
[[File:dosbox-score-splash.png|500px|thumb|center|Score splash page]]<br />
<br />
Press the space bar (or any key) to skip the splash page faster.<br />
<br />
* You will end up in the SCORE editor after the splash page is closed:<br />
<br />
[[File:dosbox-score-open.png|500px|thumb|center|Main SCORE editor.]]<br />
<br />
* You can type "exit" (then the return key) to close score and go back to the initial DosBox window:<br />
<br />
[[File:dosbox-score-exit.png|500px|thumb|center|Exiting SCORE.]]<br />
<br />
<br />
== Preference file ==<br />
<br />
* You can automatically mount the C: and D: drives by adding these lines at the bottom of "/Users/craig/Library/Preferences/DOSBox 0.74-3-3 Preferences":<br />
<br />
mount C /Users/craig/score-dosbox/c_drive<br />
mount D /Users/craig/score-dosbox/d_drive<br />
<br />
(This should be in the "[autoexec]" options region.). After adding this, the mounting commands will be done automatically when opening DosBox:<br />
<br />
[[File:dosbox-mount-auto.png|500px|thumb|center|Automatic mounting of C: and D: drives in DosBox.]]<br />
<br />
* You can also add the command "C:\SCOR4\SCOR4.BAT" to the preference file after the mount commands to automatically start SCORE when DosBox is opened:<br />
<br />
[[File:dosbox-mount-start.png|500px|thumb|center|Setting up SCORE to run automatically when DosBox is started]]<br />
<br />
* Note that you must use back-slashes (\) and not forward slashes (/) for the command to start SCORE.<br />
<br />
<br />
== Tips ==<br />
<br />
=== Mouse capture disabling === <br />
* To prevent DosBox from capturing the mouse, add this option to the Preference file:<br />
<br />
autolock=false<br />
<br />
within the "[sdl]" region of the preferences file:<br />
<br />
[[File:dosbox-autolock.png|500px|thumb|center|Setting the autolock preference for DosBox.]]<br />
<br />
Then you do not need to use control-F10 to release the mouse for DosBox.<br />
<br />
=== Full screen view ===<br />
<br />
* In order to get full screen mode by pressing option-return (and pressing again to go back to smaller window), I had to add this settings in the "[sdl]" region of the preference file:<br />
<br />
fullresolution=1920x1080<br />
<br />
The MacOS full resolution is probably too large, and otherwise DosBox will quite if I try to go to full screen.<br />
<br />
<br />
=== Keyboard notes ===<br />
<br />
See: https://www.dosbox.com/wiki/Special_Keys<br />
<br />
* option-m toggles display of the menu at the bottom of the screen in the SCORE editor.<br />
* option-i will show the arrow key increment for parameter editing<br />
* Most keyboard shortcuts do not seem to work in MacOS.<br />
<br />
* To use function keys in MacOS. press and hold the Fn key (bottom right of keyboard). The function keys can be switched to default meanings so that you do not need to type the Fn key, by going to the System Settings in the apple menu and searching for "function", Here is the window for setting function keys in MacOS, where the option to use function keys as function keys:<br />
<br />
[[File:macos-function-keys.png|500px|thumb|center|MacOS function keys in system settings.]]<br />
<br />
== Continue ==<br />
<br />
* Go to [[SCORE user input]] to start entering the first SCORE exercises.<br />
<br />
* Also refer to the [[SCORE survival guide]] for step-by-step instructions on how to enter the exercises.<br />
<br />
* When you save files, they will be placed in the /Users/craig/scores-dosbox/d_drive directory (at least for me). You can view the files in the Finder at the same location:<br />
<br />
[[File:dosbox-score-finder.png|500px|thumb|center|SCORE files in Finder.]]<br />
<br />
The files "#MUSDIR#.TMP" and "SCORE.SAV" are temporary files that SCORE uses. The file "EX1.MUS" is a binary file that stores the music notation prepared in SCORE.<br />
<br />
* You can create readable ASCII versions of MUS files in SCORE by using the PMX command. Also you can use a command-line tool to convert binary MUS files into ASCII PMX (parameter maxtrix files), both show the internal format of the musical data which contain rows of numbers, each row representing a particular musical object on the page.<br />
<br />
https://github.com/craigsapp/mus2pmx</div>Craighttps://wiki.ccarh.org/wiki/Installing_SCORE_with_WineskinsInstalling SCORE with Wineskins2024-02-13T02:47:00Z<p>Craig: </p>
<hr />
<div>Under construction. Do not follow since Wineskins is having problems running. Use [[MacOS installation of SCORE]]<br />
<br />
== Windows ==<br />
<br />
Install [DosBox https://www.dosbox.com] which is an MS-DOS emulator for windows (needed for Windows version above Windows 2017).<br />
<br />
Unzip the SCORE file on the base directory of the C: drive.<br />
<br />
Run DosBox and connect the C: drive (command to be added here).<br />
<br />
See: [[https://www.dosbox.com/wiki/DOSBox_and_Mac_OS_X]]<br />
<br />
== MacOS ==<br />
<br />
SCORE is a 16-bit program and requires running in an emulator that can handle this. Wineskins is a good method for doing this, in a similar manner to [[Installing SharpEye | SharpEye]]. If you have already installed Wineskins for running SharpEye, then you do not need to install again.<br />
<br />
=== Install Wineskins ===<br />
<br />
<br />
On MacOS, first install Wineskins according to the instructions in this video: https://www.youtube.com/watch?v=vkQj0lZFz6I<br />
<br />
As explained in the video, the Wineskin software is on Github: https://github.com/Gcenx/WineskinServer<br />
<br />
Note that the Github software installation recommends using [https://brew.sh Homebrew] for installation. This is a linux-like package manager for MacOS that I would recommend (provided you do not already have a similar system installed such as MacPorts).<br />
<br />
* Install Homebrew from https://brew.sh<br />
* Run the command `brew install --cask --no-quarantine gcenx/wine/wineskin`<br />
* This will install the app in `/Applications/Wineskin Winery.app`, open it up.<br />
* The following window will appear:<br />
<br />
[[File:wineskinwinery1.jpg|300px|thumb|center|Initial Wineskin Winery window.]]<br />
<br />
* Click on the "Update" button to install a Wrapper, the following window appears (most recent version is Wineskin-2.9.1.9):<br />
<br />
[[File:wineskinwinery2.jpg|300px|thumb|center|Update wrapper.]]<br />
<br />
* After installing the updated wrapper, the original window will look like this:<br />
<br />
[[File:wineskinwinery3.jpg|300px|thumb|center|Initial Wineskin Winery window with update.]]<br />
<br />
* Then click on the "+" button to add a new Engine. This window will appear:<br />
<br />
[[File:wineskinwinery4.jpg|300px|thumb|center|Add engine window.]]<br />
<br />
* Choose the most recent 64-bit version, which is probably the default. In this case "WS11WineCX64Bit23.7.1_D3DMetal" from the top of the list. Then click on the "Download and Install" button to install the engine.<br />
<br />
* You are then returned to the original window, but there will now be an engine installed:<br />
<br />
[[File:wineskinwinery5.jpg|300px|thumb|center|Engine installed.]]<br />
<br />
=== Setting up a new Wineskin wrapper for SCORE ===<br />
<br />
* If skipping installation of Wineskin, open the app "/Applications/Wineskin Winery.app":<br />
<br />
[[File:wineskinwinery5a.jpg|300px|thumb|center|Wineskin Winery App icon.]]<br />
<br />
You should see this window when the app opens:<br />
<br />
[[File:wineskinwinery5b.jpg|300px|thumb|center|Wineskin Winery App after opening.]]<br />
<br />
* Now click on the "Create New Blank Wrapper" button near the bottom of the initial window.<br />
<br />
[[File:wineskinwinery6a.jpg|300px|thumb|center|Installing Wrapper.]]<br />
<br />
* And give the name to the App: SCORE. Press "OK" and wait a while (about a minute) for the installation to finish. Click only once on the "OK" button (it will take a while).<br />
<br />
* SCORE.app will be installed in "~/Applications/Wineskin/SCORE.app" ("~/" means your home directory).<br />
<br />
* There will be a window that appears after creating the wrapper:<br />
<br />
[[File:wineskinwinery7a.jpg|300px|thumb|center|View Wrapper in Folder.]]<br />
<br />
* Click "View Wrapper in Folder" button to view the newly created app file:<br />
<br />
[[File:wineskinwinery8a.jpg|500px|thumb|center|File browser with SCORE app.]]<br />
<br />
* Right-click on the App and select "Show package contents" to view the files in the app:<br />
<br />
[[File:wineskinwinery9a.jpg|300px|thumb|center|Show package contents.]]<br />
<br />
* Then open the Drive C folder:<br />
<br />
[[File:wineskinwinery10a.jpg|500px|thumb|center|Open Drive C.]]<br />
<br />
<br />
* Then place the unziped SCOR4 directory inside the C drive of the Wineskin app.<br />
<br />
[[File:wineskinwinery11a.jpg|500px|thumb|center|Copied SCORE directory in C drive of SCORE Wineskin app.]]<br />
<br />
=== Initial running of the SCORE.app ===<br />
<br />
* Open ~/Applications/Wineskin/SCORE.app. You should see this window:<br />
<br />
[[File:wineskinwinery20a.jpg|300px|thumb|center|Opening SCORE.app the first time.]]<br />
<br />
* Click on Advanced to select the startup script:<br />
<br />
[[File:wineskinwinery21a.jpg|500px|thumb|center|Advanced settings for SCORE.app.]]<br />
<br />
In this case the startup script is "C:\scor4\scor4.bat". (You can type that in directly or use the "Browse" button to find it in the Wineskin app C: drive.)<br />
<br />
* Close the Advanced options and restart SCORE.app.<br />
<br />
* You will probably see this permissions option, which you should accept by clicking on "OK":<br />
<br />
[[File:wineskinwinery22a.jpg|200px|thumb|center|First-time permissions.]]</div>Craig