OpenSoundControl.org: /pages /contents
/spec/1.0 /spec/1.1 /implementations /publications /about
(contents of
this file: links to each section)
Fix the URLs in implementations.tsv that went into “Jeremy’s Homepage” column 3
Fix broken links from publications into http://cnmat.berkeley.edu/publications
Fix broken URLs of 2004 conference publications
Make an implementations page for the original libOSC from https://github.com/CNMAT/CNMAT-OSC
Get in some more of the known publications
More perspectives:
https://www.music.mcgill.ca/~gary/306/week9/osc.html / https://www.music.mcgill.ca/~gary/306/index.html#Outline
https://www.researchgate.net/publication/228777611_Open_Sound_Control_Constraints_and_Limitations
Within TouchDesigner: https://www.lynda.com/course-tutorials/OSC-Open-Sound-Control-overview/513599/589292-4.html
Make an actual “publications” page framing what this collection is and providing several views:
Make an actual “implementations” page saying we aspire to point to all known implementations. Provide several views:
Make OSC Conference 2004 publications link back to the page
Find easily findable implementations:
Add lighting consoles such as https://www.fullcompass.com/prod/511232-etc-colorsource-20-av-dmx-control-console-for-40-fixtures-with-20-faders-hdmi-and-audio-output
Are these already on github? Yes! https://github.com/CNMAT/CNMAT-OSC
Old web pages:
http://cnmat.org/OpenSoundControl/dumpOSC.html http://cnmat.org/OpenSoundControl/clients/sendOSC.html
binary downloads would be great
Link to the new site page from the 98 OSC Kit publication page’s “context”
support TCP, websockets
Might need to rewrite in C++
Make sure the new site gets archived on archive.org.
Reveal the new site and ask people to contribute fresh info
Prerequisites:
CNMAT home page and email list
CCRMA announcements, facebook
Old Emails scraped from osc_dev
list
linux-audio-user@lists.linuxaudio.org
A guide to OSC libraries, e.g., grouped by programming language and
linking to pages in implementations/*.html
More introductory materials
ongoing OSC publications search
ongoing OSC implementations search
Make sure we have, e.g., github links, for all the implementations.
Link to every top-level page from the prose of the home page:
Make accept-new-implementations handle image downloads
accept-new-publications.sh local download of publications-that-are-downloads
Make the one build script build everything (calling build-implementations etc as needed)
Factor out the rules for converting filenames and section titles into anchor names. Maybe replace all of it with calls to pandoc. (Put the function definition in a file that build.sh and build-index.sh will source)
refactor everything about build?
Let build-implementations.sh take an argument for the last N lines in the TSV instead of always deleting and rebuilding everything
What other kinds of community contributions does the new site solicit? (List in contribute)
Do we want to structure these? If so, for each, need to:
Absorb old “application areas” content into a new introduction to OSC?
Decide whether to serve the legacy site at http://opensoundcontrol.org/legacy/2011-site and if so how to make it visibly obvious that this is legacy content (e.g., big scary red preamble)
link to the old OSC-dev archives (again with a scary preamble)
What to do with files like legacy/2011-site/clean/files/Everything-About-OSC.mov
Which of the “clean” scraped files should be kept for the new site? What needs to be updated or discarded?
Here’s what we have from the top-level folder of the legacy site that’s not yet on the new site:
cnmat-software-library-downloads.md
guide-osc-libraries.md
implementations.md
introduction-osc.md
liblo.md
mailing-list-archives.md
mapping-nonmusical-data-sound.md
multiple-user-shared-musical-control.md
networked-lan-musical-performance.md
osc-application-areas.md
osc-kit-0.md
osc.md
oscpack.md
references.md
resources.md
sensor-gesture-based-electronic-musical-instruments.md
virtual-reality.md
wan-performance-and-telepresence.md
web-interfaces.md
wosclib.md
wrapping-other-protocols-inside-osc.md
re-implement the Drupal “book” structure of the legacy “developer resources”? https://web.archive.org/web/20200706171742/http://opensoundcontrol.org/resources
This page of OpenSoundControl website updated Mon Jul 25 10:33:07 PDT 2022 by matt (license: CC BY).