Lilypond Informations Générales

Total Page:16

File Type:pdf, Size:1020Kb

Lilypond Informations Générales LilyPond Le syst`eme de notation musicale Informations g´en´erales Equipe´ de d´eveloppement de LilyPond Copyright ⃝c 2009–2020 par les auteurs. This file documents the LilyPond website. 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 no Invariant Sections. A copy of the license is included in the section entitled “GNU Free Documentation License”. Pour LilyPond version 2.21.82 1 LilyPond ... la notation musicale pour tous LilyPond est un logiciel de gravure musicale, destin´e`aproduire des partitions de qualit´e optimale. Ce projet apporte `al’´edition musicale informatis´ee l’esth´etique typographique de la gravure traditionnelle. LilyPond est un logiciel libre rattach´eau projet GNU (https://gnu. org). Plus sur LilyPond dans notre [Introduction], page 3, ! La beaut´epar l’exemple LilyPond est un outil `ala fois puissant et flexible qui se charge de graver toutes sortes de partitions, qu’il s’agisse de musique classique (comme cet exemple de J.S. Bach), notation complexe, musique ancienne, musique moderne, tablature, musique vocale, feuille de chant, applications p´edagogiques, grands projets, sortie personnalis´ee ainsi que des diagrammes de Schenker. Venez puiser l’inspiration dans notre galerie [Exemples], page 6, 2 Actualit´es ⟨undefined⟩ [News], page ⟨undefined⟩, ⟨undefined⟩ [News], page ⟨undefined⟩, ⟨undefined⟩ [News], page ⟨undefined⟩, [Actualit´es], page 103, i Table des mati`eres Introduction ................................................... ..... 3 Fonctionnalit´es................................................... ....................... 3 Exemples ................................................... ............................ 6 Libert´e ................................................... ............................. 22 Contexte ................................................... ........................... 23 Productions................................................... ......................... 23 T´emoignages................................................... ........................ 25 Entr´ee sous forme de texte ................................................... .......... 29 Facilit´es d’´edition ................................................... ................... 37 T´el´echargement ................................................... 43 Unix................................................... ................................ 43 MacOS X ................................................... ........................... 45 Windows ................................................... ........................... 51 Sources ................................................... ............................. 57 Anciennes versions ................................................... .................. 58 GPL................................................... ................................ 58 Manuels ................................................... ........ 68 Initiation ................................................... ........................... 69 Glossaire ................................................... ........................... 69 Essai ................................................... ............................... 69 Notation................................................... ............................ 70 Utilisation ................................................... .......................... 70 Morceaux choisis................................................... .................... 71 FAQ ................................................... ................................ 71 Web ................................................... ................................ 72 Nouveaut´es ................................................... ......................... 72 Extension................................................... ........................... 73 Propri´et´es internes ................................................... .................. 73 Traductions................................................... ......................... 73 Tous................................................... ................................ 79 FDL ................................................... ................................ 80 Communaut´e ................................................... ... 87 Contact................................................... ............................. 87 Exemples minimalistes ................................................... .............. 89 Signalement de bogue ................................................... ............... 90 Participation................................................... ........................ 91 M´ec´enat ................................................... ............................ 92 D´eveloppement ................................................... ..................... 93 Google Summer of Code ................................................... ............ 95 Auteurs................................................... ............................. 99 Publications ................................................... ....................... 102 Actualit´es ................................................... ......................... 103 Grenier ................................................... ............................ 103 3 Introduction Notre objectif L’inspiration pour LilyPond provient de deux musiciens qui s’´etaient lass´es de l’aspect fade et ennuyeux des partitions musicales produites avec un ordinateur. Tous les musiciens pr´ef`erent lire de belles partitions de musique, pourquoi donc les programmeurs ne d´evelopperaient-ils pas un logiciel capable d’en produire ? C’est justement ce que fait LilyPond : ce logiciel grave de la musique selon le meilleur de la tradition typographique. Dans la mesure o`uil s’occupe de tous les d´etails de mise en forme, compositeurs, transcripteurs et imprimeurs peuvent se concentrer sur la musique plutˆotqu’`a am´eliorer ce que produit par d´efaut leur logiciel. Les interpr`etes obtiendront quant `aeux des parties grˆace auxquelles ils pourront se concentrer sur leur jeu plutˆotque sur du d´echiffrage. Ce que LilyPond sait faire • [Fonctionnalit´es], page 3, : de quoi LilyPond est capable. • [Exemples], page 6, : je veux voir des partitions ! • [Libert´e], page 22, : LilyPond est un logiciel libre. • [Contexte], page 23, : notre esth´etique de la gravure informatis´ee. Ceux qui utilisent LilyPond • [Productions], page 23, : cas d’utilisation de LilyPond. • [T´emoignages], page 25, : que disent les gens sur LilyPond ? LilyPond en action • [Entr´ee sous forme de texte], page 29, : vous ´ecrivez de la musique comme du texte ? • [Facilit´es d’´edition], page 37, : autres fa¸cons de travailler avec LilyPond. Fonctionnalit´es Excellente gravure de la musique classique L’int´erˆet d’utiliser LilyPond est de produire des partitions ´el´egantes et fonctionnelles, c’est-`a- dire `ala fois agr´eables et faciles `alire. La communaut´edes d´eveloppeurs a consacr´edes milliers d’heures `aconstruire ce puissant logiciel. Tous les d´etails de style, la conception des polices et les algorithmes ont ´et´einspir´es des meilleures gravures manuelles de partitions. Les partitions produites par LilyPond ont le mˆeme aspect robuste, ´equilibr´eet ´el´egant que les partitions les mieux grav´ees avec des m´ethodes traditionnelles. Pour plus de d´etails, consultez notre [Essai], page 69. Entr´ee textuelle Introduction 4 Tout est explicit´e LilyPond prend en entr´ee du texte brut qui contient toutes les informations sur le contenu de la partition et peut ˆetre compris par n’importe qui ou un autre programme. Il n’y a pas de r´eglages masqu´es par des options de menu ou un format d’enregistrement binaire. Pour plus de d´etails, consultez [Entr´ee sous forme de texte], page 29. Les retouches sont robustes et tra¸cables Quelle que soit la modification apport´ee `ala mise en forme, cette retouche sera lisible en toutes lettres dans le fichier source ; vous saurez toujours ce qui a ´et´efait. Si quoi que ce soit vient mettre tout sens dessus dessous, vous pourrez toujours revenir en arri`ere sans ˆetre `ala merci d’une fonction annuler. Un fichier textuel est sans faille et p´erenne Les fichiers texte r´esistent plus facilement `ala corruption. Leur nature les rend lisibles et, de fait, interpr´etables mˆeme en l’absence du programme qui les a cr´e´es. Gestion des partitions avec un contrˆole de version Les fichiers texte se prˆetent facilement `aune gestion par contrˆole de version. Vous pourrez ainsi exp´erimenter des m´ecanismes de d´efaire et refaire `al’infini ou s´electifs et suivre l’int´egralit´edu montage de la partition. Le contrˆole de version permet mˆeme d’envisager un flux de travaux de mani`ere collaborative. Utilisation Moins de bricolage Perdez moins de temps `aretoucher la mise en page. En effet, LilyPond tend `ad´eterminer la meilleure mise en page d`es le d´epart, en d´eterminant l’espacement, les sauts de syst`eme et de page, afin de produire une mise en page compacte et homog`ene. Le logiciel r´esout les collisions entre paroles, notes et accords, et calcule la courbure des liaisons, tout cela automatiquement ! Introduction 5 Association de musique et texte Introduisez des fragments de partition musicale sans avoir besoin de copier-coller manuellement A des images. Int´egrez de fa¸con transparente des partitions dans un document LTEX ou HTML, ou bien ajoutez des
Recommended publications
  • Proceedings 2005
    LAC2005 Proceedings 3rd International Linux Audio Conference April 21 – 24, 2005 ZKM | Zentrum fur¨ Kunst und Medientechnologie Karlsruhe, Germany Published by ZKM | Zentrum fur¨ Kunst und Medientechnologie Karlsruhe, Germany April, 2005 All copyright remains with the authors www.zkm.de/lac/2005 Content Preface ............................................ ............................5 Staff ............................................... ............................6 Thursday, April 21, 2005 – Lecture Hall 11:45 AM Peter Brinkmann MidiKinesis – MIDI controllers for (almost) any purpose . ....................9 01:30 PM Victor Lazzarini Extensions to the Csound Language: from User-Defined to Plugin Opcodes and Beyond ............................. .....................13 02:15 PM Albert Gr¨af Q: A Functional Programming Language for Multimedia Applications .........21 03:00 PM St´ephane Letz, Dominique Fober and Yann Orlarey jackdmp: Jack server for multi-processor machines . ......................29 03:45 PM John ffitch On The Design of Csound5 ............................... .....................37 04:30 PM Pau Arum´ıand Xavier Amatriain CLAM, an Object Oriented Framework for Audio and Music . .............43 Friday, April 22, 2005 – Lecture Hall 11:00 AM Ivica Ico Bukvic “Made in Linux” – The Next Step .......................... ..................51 11:45 AM Christoph Eckert Linux Audio Usability Issues .......................... ........................57 01:30 PM Marije Baalman Updates of the WONDER software interface for using Wave Field Synthesis . 69 02:15 PM Georg B¨onn Development of a Composer’s Sketchbook ................. ....................73 Saturday, April 23, 2005 – Lecture Hall 11:00 AM J¨urgen Reuter SoundPaint – Painting Music ........................... ......................79 11:45 AM Michael Sch¨uepp, Rene Widtmann, Rolf “Day” Koch and Klaus Buchheim System design for audio record and playback with a computer using FireWire . 87 01:30 PM John ffitch and Tom Natt Recording all Output from a Student Radio Station .
    [Show full text]
  • Arxiv:2006.14147V2 [Cs.CR] 26 Mar 2021
    FastSpec: Scalable Generation and Detection of Spectre Gadgets Using Neural Embeddings M. Caner Tol Berk Gulmezoglu Koray Yurtseven Berk Sunar Worcester Polytechnic Institute Iowa State University Worcester Polytechnic Institute Worcester Polytechnic Institute [email protected] [email protected] [email protected] [email protected] Abstract—Several techniques have been proposed to detect [4] are implemented against the SGX environment and vulnerable Spectre gadgets in widely deployed commercial even remotely over the network [5]. These attacks show software. Unfortunately, detection techniques proposed so the applicability of Spectre attacks in the wild. far rely on hand-written rules which fall short in covering Unfortunately, chip vendors try to patch the leakages subtle variations of known Spectre gadgets as well as demand one-by-one with microcode updates rather than fixing a huge amount of time to analyze each conditional branch the flaws by changing their hardware designs. Therefore, in software. Moreover, detection tool evaluations are based developers rely on automated malware analysis tools to only on a handful of these gadgets, as it requires arduous eliminate mistakenly placed Spectre gadgets in their pro- effort to craft new gadgets manually. grams. The proposed detection tools mostly implement In this work, we employ both fuzzing and deep learning taint analysis [6] and symbolic execution [7], [8] to iden- techniques to automate the generation and detection of tify potential gadgets in benign applications. However, Spectre gadgets. We first create a diverse set of Spectre-V1 the methods proposed so far are associated with two gadgets by introducing perturbations to the known gadgets. shortcomings: (1) the low number of Spectre gadgets Using mutational fuzzing, we produce a data set with more prevents the comprehensive evaluation of the tools, (2) than 1 million Spectre-V1 gadgets which is the largest time consumption exponentially increases when the binary Spectre gadget data set built to date.
    [Show full text]
  • Markdown Markup Languages What Is Markdown? Symbol
    Markdown What is Markdown? ● Markdown is a lightweight markup language with plain text formatting syntax. Péter Jeszenszky – See: https://en.wikipedia.org/wiki/Markdown Faculty of Informatics, University of Debrecen [email protected] Last modified: October 4, 2019 3 Markup Languages Symbol ● Markup languages are computer languages for annotating ● Dustin Curtis. The Markdown Mark. text. https://dcurt.is/the-markdown-mark – They allow the association of metadata with parts of text in a https://github.com/dcurtis/markdown-mark clearly distinguishable way. ● Examples: – TeX, LaTeX https://www.latex-project.org/ – Markdown https://daringfireball.net/projects/markdown/ – troff (man pages) https://www.gnu.org/software/groff/ – XML https://www.w3.org/XML/ – Wikitext https://en.wikipedia.org/wiki/Help:Wikitext 2 4 Characteristics Usage (2) ● An easy-to-read and easy-to-write plain text ● Collaboration platforms and tools: format that. – GitHub https://github.com/ ● Can be converted to various output formats ● See: Writing on GitHub (e.g., HTML). https://help.github.com/en/categories/writing-on-github – Trello https://trello.com/ ● Specifically targeted at non-technical users. ● See: How To Format Your Text in Trello ● The syntax is mostly inspired by the format of https://help.trello.com/article/821-using-markdown-in-trell o plain text email. 5 7 Usage (1) Usage (3) ● Markdown is widely used on the web for ● Blogging platforms and content management entering text. systems: – ● The main application areas include: Ghost https://ghost.org/
    [Show full text]
  • Using NROFF and TROFF
    Using NROFF and TROFF Part Number: 800-1755-10 Revision A, of 9 May 1988 UNIX is a registered trademark of AT&T. SunOS is a trademark of Sun Microsystems, Inc. Sun Workstation is a registered trademark of Sun Microsystems, Inc. Material in this manual comes from a number of sources: NrofflTroff User's Manual, Joseph F. Ossanna, Bell Laboratories, Murray Hill, New Jersey; A Troff Tutorial, Brian W. Kernighan, Bell Laboratories, Murray Hill, New Jersey; Typ­ ing Documents on the UNIXSystem: Using the -ms Macros with Troff and Nroff, M. E. Lesk, Bell Laboratories, Murray Hill, New Jersey; A Guide to Preparing Documents with -ms, M. E. Lesk, Bell Laboratories, Murray Hill, New Jersey; Document Formatting on UNIXUsing the -ms Macros, Joel Kies, University of California, Berkeley, California; Writing Papers with Nroff Using -me, Eric P. Allman, University of California, Berkeley; and Introducing the UNIXSystem, Henry McGilton, Rachel Morgan, McGraw-Hill Book Company, 1983. These materials are gratefully acknowledged. Copyright © 1987, 1988 by Sun Microsystems, Inc. This publication is protected by Federal Copyright Law, with all rights reserved. No part of this publication may be reproduced, stored in a retrieval system, translated, transcribed, or transmitted, in any form, or by any means manual, electric, electronic, electro-magnetic, mechanical, chemical, optical, or other­ wise, without prior explicit written permission from Sun Microsystems. Contents Chapter 1 Introduction . 1.1. nrof f andtrof f . Text Formatting Versus Word Processing TheEvolutionof nr of f andt ro f f Preprocessors and Postprocessors 1.2. tr of f, Typesetters, and Special-Purpose Formatters ............ 1.3.
    [Show full text]
  • Automatic Benchmark Profiling Through Advanced Trace Analysis Alexis Martin, Vania Marangozova-Martin
    Automatic Benchmark Profiling through Advanced Trace Analysis Alexis Martin, Vania Marangozova-Martin To cite this version: Alexis Martin, Vania Marangozova-Martin. Automatic Benchmark Profiling through Advanced Trace Analysis. [Research Report] RR-8889, Inria - Research Centre Grenoble – Rhône-Alpes; Université Grenoble Alpes; CNRS. 2016. hal-01292618 HAL Id: hal-01292618 https://hal.inria.fr/hal-01292618 Submitted on 24 Mar 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Automatic Benchmark Profiling through Advanced Trace Analysis Alexis Martin , Vania Marangozova-Martin RESEARCH REPORT N° 8889 March 23, 2016 Project-Team Polaris ISSN 0249-6399 ISRN INRIA/RR--8889--FR+ENG Automatic Benchmark Profiling through Advanced Trace Analysis Alexis Martin ∗ † ‡, Vania Marangozova-Martin ∗ † ‡ Project-Team Polaris Research Report n° 8889 — March 23, 2016 — 15 pages Abstract: Benchmarking has proven to be crucial for the investigation of the behavior and performances of a system. However, the choice of relevant benchmarks still remains a challenge. To help the process of comparing and choosing among benchmarks, we propose a solution for automatic benchmark profiling. It computes unified benchmark profiles reflecting benchmarks’ duration, function repartition, stability, CPU efficiency, parallelization and memory usage.
    [Show full text]
  • Metadefender Core V4.12.2
    MetaDefender Core v4.12.2 © 2018 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of Metadefender Core 14 1. Quick Start with Metadefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Scan Files with Metadefender Core 21 2. Installing or Upgrading Metadefender Core 22 2.1. Recommended System Requirements 22 System Requirements For Server 22 Browser Requirements for the Metadefender Core Management Console 24 2.2. Installing Metadefender 25 Installation 25 Installation notes 25 2.2.1. Installing Metadefender Core using command line 26 2.2.2. Installing Metadefender Core using the Install Wizard 27 2.3. Upgrading MetaDefender Core 27 Upgrading from MetaDefender Core 3.x 27 Upgrading from MetaDefender Core 4.x 28 2.4. Metadefender Core Licensing 28 2.4.1. Activating Metadefender Licenses 28 2.4.2. Checking Your Metadefender Core License 35 2.5. Performance and Load Estimation 36 What to know before reading the results: Some factors that affect performance 36 How test results are calculated 37 Test Reports 37 Performance Report - Multi-Scanning On Linux 37 Performance Report - Multi-Scanning On Windows 41 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3. Configuring Metadefender Core 50 3.1. Management Console 50 3.2.
    [Show full text]
  • Musical Notation Codes Index
    Music Notation - www.music-notation.info - Copyright 1997-2019, Gerd Castan Musical notation codes Index xml ascii binary 1. MidiXML 1. PDF used as music notation 1. General information format 2. Apple GarageBand Format 2. MIDI (.band) 2. DARMS 3. QuickScore Elite file format 3. SMDL 3. GUIDO Music Notation (.qsd) Language 4. MPEG4-SMR 4. WAV audio file format (.wav) 4. abc 5. MNML - The Musical Notation 5. MP3 audio file format (.mp3) Markup Language 5. MusiXTeX, MusicTeX, MuTeX... 6. WMA audio file format (.wma) 6. MusicML 6. **kern (.krn) 7. MusicWrite file format (.mwk) 7. MHTML 7. **Hildegard 8. Overture file format (.ove) 8. MML: Music Markup Language 8. **koto 9. ScoreWriter file format (.scw) 9. Theta: Tonal Harmony 9. **bol Exploration and Tutorial Assistent 10. Copyist file format (.CP6 and 10. Musedata format (.md) .CP4) 10. ScoreML 11. LilyPond 11. Rich MIDI Tablature format - 11. JScoreML RMTF 12. Philip's Music Writer (PMW) 12. eXtensible Score Language 12. Creative Music File Format (XScore) 13. TexTab 13. Sibelius Plugin Interface 13. MusiXML: My own format 14. Mup music publication program 14. Finale Plugin Interface 14. MusicXML (.mxl, .xml) 15. NoteEdit 15. Internal format of Finale (.mus) 15. MusiqueXML 16. Liszt: The SharpEye OMR 16. XMF - eXtensible Music 16. GUIDO XML engine output file format Format 17. WEDELMUSIC 17. Drum Tab 17. NIFF 18. ChordML 18. Enigma Transportable Format 18. Internal format of Capella (ETF) (.cap) 19. ChordQL 19. CMN: Common Music 19. SASL: Simple Audio Score 20. NeumesXML Notation Language 21. MEI 20. OMNL: Open Music Notation 20.
    [Show full text]
  • Notensatz Mit Freier Software
    Notensatz mit Freier Software Edgar ’Fast Edi’ Hoffmann Community FreieSoftwareOG [email protected] 30. Juli 2017 Notensatz bezeichnet (analog zum Textsatz im Buchdruck) die Aufbereitung von Noten in veröffentlichungs- und vervielfältigungsfähiger Form. Der handwerkliche Notensatz durch ausgebildete Notenstecher bzw. Notensetzer wird seit dem Ende des 20. Jahrhunderts vom Computernotensatz verdrängt, der sowohl bei der Druckvorlagenherstellung als auch zur Verbreitung von Musik über elektronische Medien Verwendung findet. Bis in die zweite Hälfte des 15. Jahrhunderts konnten Noten ausschließlich handschriftlich vervielfältigt und verbreitet werden. Notensatz Was bedeutet das eigentlich? 2 / 20 Der handwerkliche Notensatz durch ausgebildete Notenstecher bzw. Notensetzer wird seit dem Ende des 20. Jahrhunderts vom Computernotensatz verdrängt, der sowohl bei der Druckvorlagenherstellung als auch zur Verbreitung von Musik über elektronische Medien Verwendung findet. Bis in die zweite Hälfte des 15. Jahrhunderts konnten Noten ausschließlich handschriftlich vervielfältigt und verbreitet werden. Notensatz Was bedeutet das eigentlich? Notensatz bezeichnet (analog zum Textsatz im Buchdruck) die Aufbereitung von Noten in veröffentlichungs- und vervielfältigungsfähiger Form. 2 / 20 Bis in die zweite Hälfte des 15. Jahrhunderts konnten Noten ausschließlich handschriftlich vervielfältigt und verbreitet werden. Notensatz Was bedeutet das eigentlich? Notensatz bezeichnet (analog zum Textsatz im Buchdruck) die Aufbereitung von Noten in veröffentlichungs-
    [Show full text]
  • Deployment of XML for Office Documents in Organizations
    JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen DeployPent of XML for OfÀFe DoFXPents in Organizations JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen Deployment of XML for Office Documents in Organizations UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2014 Deployment of XML for Office Documents in Organizations JYVÄSKYLÄ LICENTIATE THESES IN COMPUTING 16 Eliisa Jauhiainen Deployment of XML for Office Documents in Organizations UNIVERSITY OF JYVÄSKYLÄ JYVÄSKYLÄ 2014 Editor Mauri Leppänen Department of Computer Science and Information Systems, University of Jyväskylä URN:ISBN:978-951-39-5600-4 ISBN 978-951-39-5600-4 (PDF) ISBN 978-951-39-5599-1 (nid.) ISSN 1795-9713 Copyright © 2014, by University of Jyväskylä Jyväskylä University Printing House, Jyväskylä 2014 ABSTRACT Jauhiainen, Eliisa Deployment of XML for office documents in organizations Jyväskylä: University of Jyväskylä, 201, 63 p. (+ four included articles) (-\YlVN\Ol/LFHQWLDWH7KHVHVLQ&RPSXWLQJ ISSN) ,6%1 (nid.), 978-951-39-5600-4 (PDF) Licentiate Thesis Majority of the content in organizations is stored as documents. Structured documents, like XML documents, allow the structure definitions, document instances, and layout specifications to be handled as separate entities. This is an important feature to realize from a document management point of view. A class of similar documents with the same structure constitutes a document type. The documents are built from components that are logical units of information within the context of the document type. Office documents are typically authored using word-processing software, they are relatively short in length, and intended for human consumption. The development of open office standards brought XML to organizations’ office en- vironments and changed the capabilities of using document content in ways that were previously impossible or difficult.
    [Show full text]
  • Improvisatory Music and Painting Interface
    Improvisatory Music and Painting Interface Hugo Solís García Licenciado en Piano Universidad Nacional Autónoma de México November 2001 Submitted to the Program in Media Arts and Sciences, School of Architecture and Planning, in partial fulfillment of the requirements for the degree of Master of Science in Media Arts and Science at the Massachusetts Institute of Technology September 2004 © 2004 Massachusetts Institute of Technology All rights reserved Author: Hugo Solís García Program in Media Arts and Sciences August 16, 2004 Certified by: Tod Machover Professor of Music and Media Thesis Supervisor, MIT Program in Media Arts and Sciences Accepted by: Dr. Andrew B. Lippman Chair, Departmental Committee on Graduate Students Program in Media Arts and Sciences Title Improvisatory Music and Painting Interface Hugo Solís García Submitted to the Program in Media Arts and Sciences, School of Architecture and Planning on August 16, 2004. in partial fulfillment of the requirements for the degree of Master Of Science in Media Arts and Sciences Massachusetts Institute of Technology Abstract Shaping collective free improvisations in order to obtain solid and succinct works with surprising and synchronized events is not an easy task. This thesis is a proposal towards that goal. It presents the theoretical, philosophical and technical framework of the Improvisatory Music and Painting Interface (IMPI) system: a new computer program for the creation of audiovisual improvisations performed in real time by ensembles of acoustic musicians. The coordination of these improvisations is obtained using a graphical language. This language is employed by one “conductor” in order to generate musical scores and abstract visual animations in real time.
    [Show full text]
  • Looking to the Future by JOHN BALDWIN
    1 of 3 Looking to the Future BY JOHN BALDWIN FreeBSD’s 13.0 release delivers new features to users and refines the workflow for new contri- butions. FreeBSD contributors have been busy fixing bugs and adding new features since 12.0’s release in December of 2018. In addition, FreeBSD developers have refined their vision to focus on FreeBSD’s future users. An abbreviated list of some of the changes in 13.0 is given below. A more detailed list can be found in the release notes. Shifting Tools Not all of the changes in the FreeBSD Project over the last two years have taken the form of patches. Some of the largest changes have been made in the tools used to contribute to FreeBSD. The first major change is that FreeBSD has switched from Subversion to Git for storing source code, documentation, and ports. Git is widely used in the software industry and is more familiar to new contribu- tors than Subversion. Git’s distributed nature also more easily facilitates contributions from individuals who are Not all of the changes in the not committers. FreeBSD had been providing Git mir- rors of the Subversion repositories for several years, and FreeBSD Project over the last many developers had used Git to manage in-progress patches. The Git mirrors have now become the offi- two years have taken the form cial repositories and changes are now pushed directly of patches. to Git instead of Subversion. FreeBSD 13.0 is the first release whose sources are only available via Git rather than Subversion.
    [Show full text]
  • Dorico Features in Depth
    Dorico features in depth Revised December 2017 Input and editing Note input tools § Caret for note input, allowing you to freely move the input position between bars and staves with the arrow keys § Rhythmic grid ruler to determine the distance by which the caret moves with the arrow keys § Chord input mode, allowing quick building of chords from the bottom up (shortcut Q) § Grace note input mode, allowing quick input of grace notes (shortcut /) § Copy music to another instrument, then quickly change the pitches of those notes while retaining the rhythms with lock durations mode (shortcut L) § Override Dorico’s automatic notation of rhythms according to the prevailing meter using the force durations mode (shortcut O) † § Quickly repeat the last note or chord during input (shortcut R) § Cut or split existing notes to remove ties using scissors tool (shortcut U) § No need to input rests – Dorico automatically creates appropriate rests based on the meter and rhythmic position of notes† § Unlimited voices (or layers) for each instrument, with comprehensive automatic collision avoidance for notes and rests† § Swap voice contents, and move notes between voices § Specialized input method for unpitched percussion instruments, including automatic voice assignment for drum set (e.g. kick drum and snare drum in a down-stem voice, hi-hat and cymbal in an up-stem voice)‡ § Quickly build chords by adding intervals of any quality (diatonic, major, minor, augmented, diminished, etc.) above or below existing notes with the Shift+I popover‡ Features marked with † are unique to Dorico and not found in any other commercial desktop scoring software.
    [Show full text]