Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
Repository
https://github.com/to-the-sun/amanuensis
Details
A little while back the "octave" parameter saved for each device by singingstream.maxpat was removed, which allowed for easier access of the hotkeys in octave -2. The downside of this was that in initializing a new controller, the pitches randomly assigned to its buttons will lie all over the spectrum and may actually be fairly incongruous to play together. So it would be ideal if, for their random initialization only, the original functionality was reinstated, assigning pitches only within a single octave, thereby creating a specific modality or scale for the player to operate in.
Components
Pitch is chosen in the
initialize_pitchsubpatcher of singingstream.maxpat.Basically, the functionality to initialize an octave at random for each device will need to be integrated back in to it. The
randomand+objects replaced with a quick check of the device's octave and arandom 12(12 pitches in an octave). The old code for initializing the octave is the right-hand portion of the now defunctp initialize_devices:It must be noted that octaves are chosen per device whereas pitches are chosen per control on each device, so you will need to use a
sprintf symout %s==|>deviceto get the device name fromdict ---specsbefore checking for the octave with the above code.Also, there are 11 octaves to choose from (hence the
random 11) but the lowest one should actually be excluded because that is where the hotkeys lie. Don't want to go in circles making the same mistakes here, so therandom 11will need to be altered as well.Deadline
This request should take no more than five days to complete.
Communication
Reply to this post or contact me through Github for more details.
Proof of Work Done
https://github.com/to-the-sun