| | 10 | In this talk I'll describe how I transfer audio from LP onto digital |
|---|
| | 11 | media, fixing the worst problems of the old LP on the way. I'll |
|---|
| | 12 | mention tools such as gramofile, gwc, lame, and cdrecord. I'll also |
|---|
| | 13 | discuss what to look for at the input end --- the turntable, tone arm |
|---|
| | 14 | and preamplifier; and ask for help with sound card technology. |
|---|
| | 15 | </p> |
|---|
| | 16 | |
|---|
| | 17 | <h3 id="SimonBurton">Simon Burton: SuperCollider and HyperSense</h3> |
|---|
| | 18 | <p> |
|---|
| | 19 | <ul> |
|---|
| | 20 | <li><a href="http://www.audiosynth.com/">SuperCollider3</a> on linux: how to setup and configure with jack output on kernel+2.6</li> |
|---|
| | 21 | |
|---|
| | 22 | <li>Sending code to the SC server</li> |
|---|
| | 23 | |
|---|
| | 24 | <li>A brief introduction to programming SC</li> |
|---|
| | 25 | |
|---|
| | 26 | <li>Sending OSC commands to SC from python</li> |
|---|
| | 27 | |
|---|
| | 28 | <li>a demo of the <a href="http://arrowtheory.com/hypersense/">hypersense</a> |
|---|
| | 29 | technology. This is a trio formed in 2003.</li> |
|---|
| | 30 | </ul> |
|---|
| | 31 | <p> |
|---|
| | 32 | We use custom built USB sensor devices to control SC synthdefs over an |
|---|
| | 33 | ethernet connection. The demo would show one (or more) of these devices |
|---|
| | 34 | working and generating audio events in real time. |
|---|
| | 35 | (<a href="http://arrowtheory.com/hypersense/index.html">Pictures</a>). |
|---|
| | 36 | For this demo we may need to host the USB devices on a Mac, but SC would be |
|---|
| | 37 | +running on a linux box. |
|---|
| | 38 | </p> |
|---|
| | 39 | |
|---|
| | 40 | <p> |
|---|
| | 41 | <i>Simon will be assisted by Alistair Riddell (ANU Centre for New+Media Arts).</i> |
|---|
| | 42 | </p> |
|---|
| | 43 | |
|---|
| | 44 | <h3 id="DaveRobillard">Dave Robillard: Om</h3> |
|---|
| | 45 | |
|---|
| | 46 | <p> |
|---|
| | 47 | <a href="http://www.nongnu.org/om-synth/">Om</a> is a modular synthesizer. |
|---|
| | 48 | It is built around a core philosophy that |
|---|
| | 49 | distinguishes it from currently available modular synthesizers; most |
|---|
| | 50 | importantly the full process level separation of the engine and front end |
|---|
| | 51 | and the lack of an internal plugin format, using standards such as LADSPA |
|---|
| | 52 | to avoid the duplication of effort of its peers. Other noteworthy features |
|---|
| | 53 | include: |
|---|
| | 54 | </p> |
|---|
| | 55 | |
|---|
| | 56 | <ul> |
|---|
| | 57 | <li>Subpatching</li> |
|---|
| | 58 | <li>Polyphony</li> |
|---|
| | 59 | <li>Multiple simultaneous patches, arbitrary Jack port creation</li> |
|---|
| | 60 | <li>All engine/client communication done through Open Sound Control</li> |
|---|
| | 61 | <li>Built from the ground up to be a proper realtime-safe Jack client</li> |
|---|
| | 62 | <li>Full MIDI binding support</li> |
|---|
| | 63 | </ul> |
|---|
| | 64 | |
|---|
| | 65 | <p> |
|---|
| | 66 | Om has been designed to be more than just another modular synth. It's OSC |
|---|
| | 67 | controlled engine design means it can be used in many different configurations, |
|---|
| | 68 | with or without a UI. Possible uses: |
|---|
| | 69 | </p> |
|---|
| | 70 | |
|---|
| | 71 | <ul> |
|---|
| | 72 | <li>Using OSC bindings in languages such as Python to allow algorithmic patch |
|---|
| | 73 | creation and tweaking, and other similar experimentation.</li> |
|---|
| | 74 | |
|---|
| | 75 | <li>Building patches with GUI clients running on seperate computers over the |
|---|
| | 76 | network, allowing one user to see the changes made by the other in realtime, |
|---|
| | 77 | and vice-versa</li> |
|---|
| | 78 | |
|---|
| | 79 | <li>Building simple effects processing patches and running the engine without |
|---|
| | 80 | a UI to accomplish background signal processing tasks (perhaps reverb and |
|---|
| | 81 | compression)</li> |
|---|
| | 82 | |
|---|
| | 83 | <li>Syncing effects parameters to jack transport, allowing tempo-synced effects |
|---|
| | 84 | and/or synthesis with applications such as SooperLooper</li> |
|---|
| | 85 | |
|---|
| | 86 | <li>The code has been built to be as extensible as possible, so more potential |
|---|
| | 87 | should open up as time goes on. The talk will focus on these future |
|---|
| | 88 | directions, what is possible now (with demos) as well as internal design |
|---|
| | 89 | decisions and rationale, short-term future plans, and interaction with other |
|---|
| | 90 | software and a GNU/Linux audio system as a whole.</li> |
|---|
| | 91 | </ul> |
|---|
