DOCSLIB.ORG

Embedded Sound Synthesis

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Embedded Sound Synthesis Victor LAZZARINI, Joseph TIMONEY and Shane BYRNE Sound and Digital Music Technology Group Maynooth University Maynooth, Co.Kildare Ireland, fVictor.Lazzarini, Joseph.Timoney, [email protected] Abstract ity of Csound, which has been shown to run This article introduces the use of the Intel Galileo on a great variety of platforms, from super- development board as a platform for sound synthe- computers2 to mobile[Lazzarini et al., 2012][Yi sis and processing, in conjunction with the Csound and Lazzarini, 2012] and web[Lazzarini et al., sound and music computing system. The board in- 2014], and now on embedded systems such as cludes an Arduino-compatible electronics interface, the Galileo. The hardware and software combi- and runs an embedded systems version of the Linux nation discussed in this paper has the potential operating system. The paper describes the relevant of opening up a variety of new applications for hardware and software environment. It introduces a port of Csound, which includes custom frontends electronic music composers and performers. that take some advantage of the board capabilities. As a case study, we have developed a com- As a case study, a MIDI synthesizer is explored as plete software image for the system, which al- one of the many potential applications of the system. lows it to be booted up as an outboard MIDI Further possibilities of the technology for Ubiquitous synthesizer. This paper is organised as follows: Music are also discussed, which use the various in- we first describe the hardware and software en- terfacing facilities present on the Galileo. vironment that is available to Galileo develop- Keywords ers. We then discuss the details of the port of the Csound system, and its custom frontend Embedded systems, sound synthesis and processing, that takes advantage of the board's Arduino- music programming, Ubiquitous Music like capabilities. This is followed by a report 1 Introduction on our case study, the MIDI synthesizer. Fi- nally, we propose some further applications of The Intel Galileo board1 (fig.1) is an embed- the technology. ded systems development board based on the Quark System-on-Chip (SoC), which includes an Arduino-like functionality (and compatibil- 2 Galileo hardware and software ity with some existing extension shields and software). The board can be used as a straight Galileo boards have been produced under replacement for the Arduino Uno boards, with two slightly different hardware configurations, a customised Arduino Integrated Development namely, original (GEN1, pictured in fig.1), Environment (IDE) that allows programming of and a revised specification (GEN2, pictured 3 applications (sketches) using the Wiring library. in fig.2) . They generally run under custom, The Galileo, however, runs under a Linux-based specially-designed, Linux for embedded systems operating system, and thus allows other modes images, created and supported by the Yocto 4 of application that are not restricted to Arduino Project . The board can be booted up from the IDE sketches, and which can take more com- flash memory (containing a minimal/small linux plete advantage of the board capabilities. image), or from the SD card, which can contain In this article, we examine the use of more complete operating system images. the Galileo board for sound synthesis and processing, with the Csound[ffitch et al., 2Csound was used as part of two class C projects 2014][Boulanger, 2000] sound and music com- at the Irish Centre for High-Performance Computing puting system. We demonstrate the scalabil- (ICHEC) exploring parallel processing for audio 3http://www.intel.ie/content/www/ie/en/ 1http://arduino.cc/en/ArduinoCertified/ do-it-yourself/galileo-maker-quark-board.html IntelGalileo 4https://www.yoctoproject.org Figure 1: The Intel Galileo (GEN1) with ethernet and USB connections 2.1 Hardware specifications put/output functions). The Quark GPIOs allow The two share some basic attributes that in- faster switching performance, through a dedi- clude a Quark processor, which has the same cated software interface. Analog IOs are imple- instruction set to the Pentium, or i586, CPU, mented in GEN1 via an Analog Devices AD7298 and contains a single core running at 400 ADC IC, providing 12 bits of resolution, and MHz (also known as `Clanton')5, 10/100Mbit in GEN2 via a Texas Instruments ADS108S102 ethernet, PCI Express, USB 2.0 device and IIO-ADC, which is 10-bit (scaled to a 12-bit host interfaces, and microSD card reader. range for compatibility purposes). Pulse-width GEN1 boards have a 3.5 mm RS-232 connec- modulation (PWM) is also implemented differ- tor, whereas GEN2 replaces this with a 6-pin ently on the GEN2 board, providing higher res- Transistor-Transistor Logic (TTL) Universal olution. Asynchronous Receiver-Transmitter (UART) header that is compatible with standard adap- 2.2 Software systems tors. The board is generally run under a specially- The Galileo uses the standard Arduino pin built Linux OS image, although a Debian-based layout, which includes 20 General-Purpose In- system has also recently been tested, and Mi- put/Output (GPIO) pins (6 multiplexed as ana- crosoft has also provided a cut-down version of log inputs), plus power and Serial Peripheral Windows 8 for it. We will discuss here the orig- Interface (SPI) headers. The hardware imple- inal Linux software that has been designed for mentation of these is different in GEN1 and the board. There are two types of Linux im- GEN2. In the former, an external GPIO ex- ages that are used in the Galileo, based on dif- pander chip (Cypress CY8C9540A) is used to ferent versions of the standard C library. The control most of the pins in the shield, with only smaller image, mostly meant to be run from two Quark GPIOs connected directly (accessi- the limited space in the board flash memory, ble via a multiplexer switch). The latter has is built with uClibc. This library was originally 12 Quark GPIOs fully accessible to the head- designed for embedded Linux systems not us- ers, and uses a different GPIO expander chip ing memory management units, but also runs layout (3 NXP PCAL9535A), mostly to con- on standard Linux. The other type of image is trol multiplexing (leaving eight available for in- based on eglibc, which was designed for embed- 5http://ark.intel.com/products/79084/ ded systems but is generally compatible with Intel-Quark-SoC-X1000-16K-Cache-400-MHz the standard glibc. This library is more suit- Figure 2: The Intel Galileo (GEN2) with ethernet, USB audio and a potentiometer connected to analog input 1 (pin A1) able for SD card-based installations with no size USB or PCI Express interfaces. constraints, as it is more fully-featured and pro- vides better performance than uClibc. Software built with the Arduino IDE normally depends 3 Csound for the Galileo on uClibc, and therefore will not run on an eglibc image (although the Arduino IDE can be A fully-functional port of Csound was built for rebuilt from source to target this). the Galileo board using the cross-compilation 2.2.1 Development environment environment described above. The only two ba- Although it is possible to include all the devel- sic dependencies for Csound are libsndfile (for opment tools and use the board itself to build soundfile access) and the ALSA library (for re- software, it is more advisable to set up a cross- altime audio and MIDI). Although the image compiling toolchain on a host computer. This built with the provided BSP contains both, is done by building an image and the toolchain there are still a few issues to be resolved be- from the sources, through a Linux Board Sup- fore we can build the system. Firstly, the cross- port Package (BSP) provided by Intel for the compilation environment installation does not Clanton platform. The BSP is a collection of appear to include the ALSA headers, so these scripts (shell scripts, python scripts, recipes, need to be copied manually from the sysroot in etc) built with the resources provided by the the Yocto build to the installed toolchain sys- Yocto Project, that allows us to build full Linux- root. based operating systems for specific embedded Secondly, the libsndfile originally provided platforms. It uses the bitbake tool to collect all by the Yocto build is broken, as it depends on the information in the various scripts, download large file offset support that is not provided from sources, patch, build, and install the oper- as standard by the system. So we have to ating system software. The Galileo Yocto BSP modify the bitbake build recipe (provided in can be used to build a fully-functional eglibc- ./poky/meta/recipes-multimedia/libsndfi based Linux standard base distribution, and a le/libsndfile1 1.0.25.bb) to configure Software Developer Kit (SDK) containing a gc- the build with -D FILE OFFSET BITS=64, and c/g++ toolchain. Most importantly for us, this rebuild the image and SDK. With this in place, Linux image contains the alsa library, and with we can proceed to build Csound in the usual it, we can access soundcards connected via the manner, using the CMake tools. 3.1 Custom frontends 3.3 Digital input and output In order to access the basic Arduino-like func- The remaining 14 pins can be used for general- tionality of the Galileo, specific frontends were purpose digital input or output. Access is developed: gcsound (GEN1) and gcsound2 provided as requested, through blocking read- (GEN2). This functionality can be divided ing/writing operations. This functionality is into two groups: access to analog inputs, and implemented as new opcodes in the system: access to the GPIO digital input and output.
Recommended publications
  • RZ/G Verified Linux Package for 64Bit Kernel V1.0.5-RT Release Note For

    RZ/G Verified Linux Package for 64Bit Kernel V1.0.5-RT Release Note For

    Release Note RZ/G Verified Linux Package for 64bit kernel Version 1.0.5-RT R01TU0311EJ0102 Rev. 1.02 Release Note for HTML5 Sep 7, 2020 Introduction This release note describes the contents, building procedures for HTML5 (Gecko) and important points of the RZ/G Verified Linux Package for 64bit kernel (hereinafter referred to as “VLP64”). In this release, Linux packages for HTML5 is preliminary and provided AS IS with no warranty. If you need information to build Linux BSPs without a GUI Framework of HTML5, please refer to “RZ/G Verified Linux Package for 64bit kernel Version 1.0.5-RT Release Note”. Contents 1. Release Items ................................................................................................................. 2 2. Build environment .......................................................................................................... 4 3. Building Instructions ...................................................................................................... 6 3.1 Setup the Linux Host PC to build images ................................................................................. 6 3.2 Building images to run on the board ........................................................................................ 8 3.3 Building SDK ............................................................................................................................. 12 4. Components ................................................................................................................. 13 5. Restrictions
  • Embedded Linux Systems with the Yocto Project™

    Embedded Linux Systems with the Yocto Project™

    OPEN SOURCE SOFTWARE DEVELOPMENT SERIES Embedded Linux Systems with the Yocto Project" FREE SAMPLE CHAPTER SHARE WITH OTHERS �f, � � � � Embedded Linux Systems with the Yocto ProjectTM This page intentionally left blank Embedded Linux Systems with the Yocto ProjectTM Rudolf J. Streif Boston • Columbus • Indianapolis • New York • San Francisco • Amsterdam • Cape Town Dubai • London • Madrid • Milan • Munich • Paris • Montreal • Toronto • Delhi • Mexico City São Paulo • Sidney • Hong Kong • Seoul • Singapore • Taipei • Tokyo Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. For information about buying this title in bulk quantities, or for special sales opportunities (which may include electronic versions; custom cover designs; and content particular to your business, training goals, marketing focus, or branding interests), please contact our corporate sales depart- ment at [email protected] or (800) 382-3419. For government sales inquiries, please contact [email protected]. For questions about sales outside the U.S., please contact [email protected]. Visit us on the Web: informit.com Cataloging-in-Publication Data is on file with the Library of Congress.
  • Riscv-Software-Stack-Tutorial-Hpca2015

    Riscv-Software-Stack-Tutorial-Hpca2015

    Software Tools Bootcamp RISC-V ISA Tutorial — HPCA-21 08 February 2015 Albert Ou UC Berkeley [email protected] Preliminaries To follow along, download these slides at http://riscv.org/tutorial-hpca2015.html 2 Preliminaries . Shell commands are prefixed by a “$” prompt. Due to time constraints, we will not be building everything from source in real-time. - Binaries have been prepared for you in the VM image. - Detailed build steps are documented here for completeness but are not necessary if using the VM. Interactive portions of this tutorial are denoted with: $ echo 'Hello world' . Also as a reminder, these slides are marked with an icon in the upper-right corner: 3 Software Stack . Many possible combinations (and growing) . But here we will focus on the most common workflows for RISC-V software development 4 Agenda 1. riscv-tools infrastructure 2. First Steps 3. Spike + Proxy Kernel 4. QEMU + Linux 5. Advanced Cross-Compiling 6. Yocto/OpenEmbedded 5 riscv-tools — Overview “Meta-repository” with Git submodules for every stable component of the RISC-V software toolchain Submodule Contents riscv-fesvr RISC-V Frontend Server riscv-isa-sim Functional ISA simulator (“Spike”) riscv-qemu Higher-performance ISA simulator riscv-gnu-toolchain binutils, gcc, newlib, glibc, Linux UAPI headers riscv-llvm LLVM, riscv-clang submodule riscv-pk RISC-V Proxy Kernel (riscv-linux) Linux/RISC-V kernel port riscv-tests ISA assembly tests, benchmark suite All listed submodules are hosted under the riscv GitHub organization: https://github.com/riscv 6 riscv-tools — Installation . Build riscv-gnu-toolchain (riscv*-*-elf / newlib target), riscv-fesvr, riscv-isa-sim, and riscv-pk: (pre-installed in VM) $ git clone https://github.com/riscv/riscv-tools $ cd riscv-tools $ git submodule update --init --recursive $ export RISCV=<installation path> $ export PATH=${PATH}:${RISCV}/bin $ ./build.sh .
  • Continuous Integration and Testing of a Yocto Project Based Automotive Head Unit

    Continuous Integration and Testing of a Yocto Project Based Automotive Head Unit

    CONTINUOUS INTEGRATION AND TESTING OF A YOCTO PROJECT BASED AUTOMOTIVE HEAD UNIT MARIO DOMENECH GOULART MIKKO RAPELI Embedded Linux Conference Europe 2016 ABOUT BMW CAR IT GMBH Founded in 2001 as a wholly owned subsidiary of the BMW AG Strengthen BMW's software competence View vehicles as software systems Develop innovative software for future BMW Group vehicles Prototype solutions for early and reliable project decisions Participate in several open-source communities and research projects Embedded Linux Conference Europe 2016 Page 2 CARS AND HEAD UNITS Embedded Linux Conference Europe 2016 Page 3 PROJECT SETUP Development of a head unit for BMW cars A connected multimedia computer with navigation and telephony Several companies, physically distributed Hundreds of developers, on various levels Complex infrastructure Technical and political obstacles to set up technical solutions Embedded Linux Conference Europe 2016 Page 4 CI SYSTEM REQUIREMENTS Provide fast feedback for developers, integrators, project organization Automatic multi-stage CI Software components change-verification in an SDK environment Build components Execute unit tests Software integration change-verification in the system build Build the full system, for all targets, all images Quality assurance checks after build Build Acceptance Testing (BAT) on real target environments (hardware, SDK) Embedded Linux Conference Europe 2016 Page 5 QUICK OVERVIEW OF YOCTO PROJECT Linux-based cross-compilation framework Set of metadata and a task scheduler which,
  • Yocto-Slides.Pdf

    Yocto-Slides.Pdf

    Yocto Project and OpenEmbedded Training Yocto Project and OpenEmbedded Training © Copyright 2004-2021, Bootlin. Creative Commons BY-SA 3.0 license. Latest update: October 6, 2021. Document updates and sources: https://bootlin.com/doc/training/yocto Corrections, suggestions, contributions and translations are welcome! embedded Linux and kernel engineering Send them to [email protected] - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 1/296 Rights to copy © Copyright 2004-2021, Bootlin License: Creative Commons Attribution - Share Alike 3.0 https://creativecommons.org/licenses/by-sa/3.0/legalcode You are free: I to copy, distribute, display, and perform the work I to make derivative works I to make commercial use of the work Under the following conditions: I Attribution. You must give the original author credit. I Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license identical to this one. I For any reuse or distribution, you must make clear to others the license terms of this work. I Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. Document sources: https://github.com/bootlin/training-materials/ - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 2/296 Hyperlinks in the document There are many hyperlinks in the document I Regular hyperlinks: https://kernel.org/ I Kernel documentation links: dev-tools/kasan I Links to kernel source files and directories: drivers/input/ include/linux/fb.h I Links to the declarations, definitions and instances of kernel symbols (functions, types, data, structures): platform_get_irq() GFP_KERNEL struct file_operations - Kernel, drivers and embedded Linux - Development, consulting, training and support - https://bootlin.com 3/296 Company at a glance I Engineering company created in 2004, named ”Free Electrons” until Feb.
  • With Yocto/Openembedded

    With Yocto/Openembedded

    PORTING NEW CODE TO RISC-V WITH YOCTO/OPENEMBEDDED Martin Maas ([email protected]) 1st RISC-V Workshop, January 15, 2015 Monterey, CA WHY WE NEED A LINUX DISTRIBUTION • To build an application for RISC-V, you need to: – Download and build the RISC-V toolchain + Linux – Download, patch and build application + dependencies – Create an image and run it in QEMU or on hardware • Problems with this approach: – Error-prone: Easy to corrupt FS or get a step wrong – Reproducibility: Others can’t easily reuse your work – Rigidity: If a dependency changes, need to do it all over • We need a Linux distribution! – Automatic build process with dependency tracking – Ability to distribute binary packages and SDKs 2 RISCV-POKY: A PORT OF THE YOCTO PROJECT • We ported the Yocto Project – Official Linux Foundation Workgroup, supported by a large number of industry partners – Part I: Collection of hundreds of recipes (scripts that describe how to build packages for different platforms), shared with OpenEmbedded project – Part II: Bitbake, a parallel build system that takes recipes and fetches, patches, cross-compiles and produces packages (RPM/DEB), images, SDKs, etc. • Focus on build process and customizability 3 GETTING STARTED WITH RISCV-POKY • Let’s build a full Linux system including the GCC toolchain, Linux, QEMU + a large set of packages (including bash, ssh, python, perl, apt, wget,…) • Step I: Clone riscv-poky: git clone [email protected]:ucb-bar/riscv-poky.git • Step II: Set up the build system: source oe-init-build-env • Step III: Build an image (may
  • 62 Years and Counting: MUSIC N and the Modular Revolution

    62 Years and Counting: MUSIC N and the Modular Revolution

    62 Years and Counting: MUSIC N and the Modular Revolution By Brian Lindgren MUSC 7660X - History of Electronic and Computer Music Fall 2019 24 December 2019 © Copyright 2020 Brian Lindgren Abstract. MUSIC N by Max Mathews had two profound impacts in the world of music ​ synthesis. The first was the implementation of modularity to ensure a flexibility as a tool for the user; with the introduction of the unit generator, the instrument and the compiler, composers had the building blocks to create an unlimited range of sounds. The second was the impact of this implementation in the modular analog synthesizers developed a few years later. While Jean-Claude Risset, a well known Mathews associate, asserts this, Mathews actually denies it. They both are correct in their perspectives. Introduction Over 76 years have passed since the invention of the first electronic general purpose computer,1 the ENIAC. Today, we carry computers in our pockets that can perform millions of times more calculations per second.2 With the amazing rate of change in computer technology, it's hard to imagine that any development of yesteryear could maintain a semblance of relevance today. However, in the world of music synthesis, the foundations that were laid six decades ago not only spawned a breadth of multifaceted innovation but continue to function as the bedrock of important digital applications used around the world today. Not only did a new modular approach implemented by its creator, Max Mathews, ensure that the MUSIC N lineage would continue to be useful in today’s world (in one of its descendents, Csound) but this approach also likely inspired the analog synthesizer engineers of the day, impacting their designs.
  • The Computational Attitude in Music Theory

    The Computational Attitude in Music Theory

    The Computational Attitude in Music Theory Eamonn Bell Submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy in the Graduate School of Arts and Sciences COLUMBIA UNIVERSITY 2019 © 2019 Eamonn Bell All rights reserved ABSTRACT The Computational Attitude in Music Theory Eamonn Bell Music studies’s turn to computation during the twentieth century has engendered particular habits of thought about music, habits that remain in operation long after the music scholar has stepped away from the computer. The computational attitude is a way of thinking about music that is learned at the computer but can be applied away from it. It may be manifest in actual computer use, or in invocations of computationalism, a theory of mind whose influence on twentieth-century music theory is palpable. It may also be manifest in more informal discussions about music, which make liberal use of computational metaphors. In Chapter 1, I describe this attitude, the stakes for considering the computer as one of its instruments, and the kinds of historical sources and methodologies we might draw on to chart its ascendance. The remainder of this dissertation considers distinct and varied cases from the mid-twentieth century in which computers or computationalist musical ideas were used to pursue new musical objects, to quantify and classify musical scores as data, and to instantiate a generally music-structuralist mode of analysis. I present an account of the decades-long effort to prepare an exhaustive and accurate catalog of the all-interval twelve-tone series (Chapter 2). This problem was first posed in the 1920s but was not solved until 1959, when the composer Hanns Jelinek collaborated with the computer engineer Heinz Zemanek to jointly develop and run a computer program.
  • A Smart Way to Manage OSS Compliance with Yocto+SPDX

    A Smart Way to Manage OSS Compliance with Yocto+SPDX

    A Smart Way to Manage OSS Compliance with Yocto+SPDX Zheng Ruoqin, Fujitsu [email protected] Lei Maohui, Fujitsu Copyright 2017 FUJITSU COMPUTER TECHNOLOGIES LIMITED Fujitsu’s contributions to Yocto community Data comes from yocto (2015 ~) Contribution in yocto Layers Changesets commits 1 oe-core 90 meta-openembedded 258 2 258 3 meta-cloud-services 80 4 meta-virtualization 21 90 80 5 meta-cgl 11 21 11 6 2 meta-qt5 2 1 Copyright 2017 FUJITSU COMPUTER TECHNOLOGIES LIMITED Fujitsu’s contributions to Yocto community Data comes from meta-openembedded.git (2015 ~) Developers with the most changesets Top changeset contributors by Developer Changesets employer 1 Andreas Müller 440 (11.2%) commits 2 Derek Straka 421 (10.7%) 3 Martin Jansa 312 (7.9%) 1407 4 Khem Raj 300 (7.6%) 5 Jackie Huang 141 (3.1%) 6 Armin Kuster 121 (3.1%) 7 Li xin (Fujitsu) 100 (2.5%) 8 Yi Zhao 86 (2.2%) 742 9 Roy Li 85 (2.1%) 10 Kai Kang 84 (2.1%) 11 Alexander Kanavin 81 (2.1%) 258 230 12 Fabio Berton 62 (1.6%) 94 78 30 13 Andre McCurdy 60 (1.5%) 14 Chen Qi 50 (1.3%) 15 Robert Yang 46 (1.2%) 16 Pascal Bach 44 (1.1%) 17 Bian Naimeng(Fujitsu) 38 (1.0%) 2 Copyright 2017 FUJITSU COMPUTER TECHNOLOGIES LIMITED Agenda Introduction of SPDX • Background of SPDX • What is SPDX • Who are working for SPDX • The status of SPDX specification • SPDX file Yocto+SPDX • What is Yocto • Why we use SPDX in Yocto • Current state about Yocto+SPDX • What we have done for Yocto+SPDX • Future work Manage SPDX files by smart • What is smart • What we have done • How to Manage SPDX files by smart • Future work 3 Copyright 2017 FUJITSU COMPUTER TECHNOLOGIES LIMITED Introduction of SPDX Background of SPDX What is SPDX Who are working for SPDX The status of SPDX specification SPDX file 4 Copyright 2017 FUJITSU COMPUTER TECHNOLOGIES LIMITED Background of SPDX(1/2) meta-ivi meta-agl OSS B OSS C (GPLv3) OSS A No GPLv3! OSS C (GPLv3) License problem will be met in your company.
  • Yocto Project and Embedded OS

    Yocto Project and Embedded OS

    Yocto Project and Jeffrey Osier-Mixon Embedded OS •What is the Yocto Project and why is it important? •Working with an open source collaborative project & community Kevin McGrath •Yocto Project concepts in a nutshell: environment, metadata, tools • Using Yocto cross-compiler • Running kernel via qemu th • Module installation, virtio, etc. July 28 2015 • Lessons learned, capabilities 11:00 PDT (GMT -7) 1 Yocto Project and Embedded OS Our guests Jeffrey Osier-Mixon: Jeff "Jefro" Osier-Mixon works for Intel Corporation in Intel's Open Source Technology Center, where his current role is community manager for the Yocto Project.. Jefro also works as a community architect and consultant for a number of open source projects and speaks regularly at open source conferences worldwide. He has been deeply involved with open source since the early 1990s. Kevin McGrath : Instructor at Oregon State University. I primarily teach the operating systems sequence and the senior capstone project sequence, but have taught architecture, assembly programming, introductory programming classes, and just about anything else that needs someone to teach it. While my background is in network security and high performance computing (computational physics), today I mostly live in the embedded space, leading to the “ECE wannabe” title in my department. Oleg Verge (Moderator): Technical Program Manager Intel Higher Education, System Engineer MCSE,CCNA, VCP Intel® IoT Developer Kit v1.0 Hardware components = + + Helpful Linux* tools (GCC tool chain, perf, oProfile, Software image + etc.), required drivers (Wi-Fi*, Bluetooth®, etc.), useful = API libraries, and daemons like LighttPD and Node.js. + Intel XDK Support for various IDEs = + + + For C/C++ For java, For Arduino* For Visual + node.js.,html5 sketches Programming Cloud services = Intel IoT Analytics includes capabilities for data collection, + storage, visualization, and analysis of sensor data.
  • LAC-07 Proceedings

    LAC-07 Proceedings

    LINUX AUDIO CONFERENCE BERLIN Lectures/Demos/Workshops Concerts/LinuxSoundnight P roceedin G S TU-Berlin 22.-25.03.07 www.lac.tu-berlin.de5 Published by: Technische Universität Berlin, Germany March 2007 All copyrights remain with the authors www.lac.tu-berlin.de Credits: Cover design and logos: Alexander Grüner Layout: Marije Baalman Typesetting: LaTeX Thanks to: Vincent Verfaille for creating and sharing the DAFX’06 “How to make your own Proceedings” examples. Printed in Berlin by TU Haus-Druckerei — March 2007 Proc. of the 5th Int. Linux Audio Conference (LAC07), Berlin, Germany, March 22-25, 2007 LAC07-iv Preface The International Linux Audio Conference 2007, the fifth of its kind, is taking place at the Technis- che Universität Berlin. We are very glad to have been given the opportunity to organise this event, and we hope to have been able to put together an interesting conference program, both for developers and users, thanks to many submissions of our participants, as well as the support from our cooperation partners. The DAAD - Berliner Künstlerprogramm has supported us by printing the flyers and inviting some of the composers. The Cervantes Institute has given us support for involving composers from Latin America and Spain. Tesla has been a generous host for two concert evenings. Furthermore, Maerz- Musik and the C-Base have given us a place for the lounge and club concerts. The Seminar für Medienwissenschaften of the Humboldt Universität zu Berlin have contributed their Signallabor, a computer pool with 6 Linux audio workstations and a multichannel setup, in which the Hands On Demos are being held.
  • International Computer Music Conference (ICMC/SMC)

    International Computer Music Conference (ICMC/SMC)

    Conference Program 40th International Computer Music Conference joint with the 11th Sound and Music Computing conference Music Technology Meets Philosophy: From digital echos to virtual ethos ICMC | SMC |2014 14-20 September 2014, Athens, Greece ICMC|SMC|2014 14-20 September 2014, Athens, Greece Programme of the ICMC | SMC | 2014 Conference 40th International Computer Music Conference joint with the 11th Sound and Music Computing conference Editor: Kostas Moschos PuBlished By: x The National anD KapoDistrian University of Athens Music Department anD Department of Informatics & Telecommunications Panepistimioupolis, Ilissia, GR-15784, Athens, Greece x The Institute for Research on Music & Acoustics http://www.iema.gr/ ADrianou 105, GR-10558, Athens, Greece IEMA ISBN: 978-960-7313-25-6 UOA ISBN: 978-960-466-133-6 Ξ^ĞƉƚĞŵďĞƌϮϬϭϰʹ All copyrights reserved 2 ICMC|SMC|2014 14-20 September 2014, Athens, Greece Contents Contents ..................................................................................................................................................... 3 Sponsors ..................................................................................................................................................... 4 Preface ....................................................................................................................................................... 5 Summer School .......................................................................................................................................