Hacking begins at 4pm on Friday, January 31st and ends at 4pm Saturday, February 1st.
The judging panel will award 3 cash prizes for the top three projects: $2,000, $1,500, and $1,000.
An instrument building category will award 1 cash prize of $1,000.
Participants will also get to cast their vote for a participants’ choice award of $500.
Judges may split awards at their discretion.
We encourage teams for this event to include 2-4 people, but solo hackers are welcome. Teams can form ahead of time, among students who already know each other, or at the opening of the event. We encourage teams that include students from multiple campuses or programs. If you’re interested in finding a team, you can list your skills in your project description, and we’ll help you find collaborators during registration on January 31st. See below for ways to get involved in you don’t have previous coding experience.
PeabodyHacks is different from other hackathons because our emphasis is on experimentation, innovation, and learning. We aim to create an inclusive, supportive environment for students who are interested in exploring the intersection between the performing arts and technology, but may not have an academic background in technology. We welcome participants at all levels and have created a rules structure designed to make it easier for busy performing artists to participate while balancing rehearsal and performance schedules.
This hackathon wants to encourage beginners, so we have created a special novice category for this event. Little Bits plug and play components will be provided for users to create a new instrument or sound responsive tool. Beginners will have access to Little Bits kits to create electronic instruments or other performance access projects using plug and play circuits and coding with Google Blockly with and then creating an instrument of their own! One team building a new instrument will be awarded a $1,000 prize – this is a great category for those unsure about how where to get started. You can also make a click-through protoype of the app of your dreams with no coding experience required.
Projects for this hackathon can tackle any problem relating to access in music and the performing arts. Your project can address access by creators to new and innovative tools or access by audiences and students to performances and learning opportunities. Some sample projects to get your inspiration going include:
We have received questions from students who want to use previously developed hardware in this Hackathon. Because of the interdisciplinary nature of this event, we want to encourage planning and collaboration. While projects can include existing open source code or previously developed hardware, any new code or hardware configuration must be developed during the hackathon itself.
We recommend planning on being on site at AFL for the entire 24 hour period. We will have a limited number of blankets and bean bags available, but encourage participants to bring their own pillows or blankets. AFL will lock down at midnight, February 1 and not re-open until 8am that day. Participants who leave after midnight will not be able to return or work until 8am.
Anyone registered before 4pm who can arrive to begin the competition by 8pm is eligible to compete! Anyone who has registered in advance and cannot be onsite to start by 8pm will be ineligible to submit a final project.
We will have a limited amount of hardware available for teams at the event. We can also accommodate a limited number of special requests placed before January 20, 2020 by emailing the team. Hardware and software available will include:
Sumissions for final projects
Final submissions do not need to be fully functioning apps. You may submit a clickable prototype or video of an app on a simulator. If you are submitting an instrument, you must submit a video of your fully functioning instrument. All final projects must be submitted to DevPost. You may register for DevPost at any time between now and 4pm, Friday, January 31.
Additional submission requirements
In addition to your project, please complete the supplementary questions summarizing your project and describing how it meets the judging criteria.
Video links to YouTube, Vimeo or Youku can be submitted. Videos are not required except for instrument submissions. All videos should be no longer than 3 minutes.
Contestants should upload any completed projects files combined into one Zip file.
Information about your Project
Submissions should include a project name, the names of all team members and their contact information, operating systems or devices that can run the app, and any APIs, SDKs, data sets, images, sounds, videos, or code libraries used in developing your project. Proper attribution for all existing APIs, SDKs, data sets, images, sounds, videos or code libraries used is required.
Topic / Categories
Your project should address some aspect of access to the performing arts. We encourage participants to consider institutional barriers to access in addition to geographic, physical, and financial barriers to access.
Using existing work
Projects may build apps on existing hardware or extend existing apps. Extensions to existing apps should be substantial and all submissions should clearly denote all new work and how it builds on the existing app.
Apps do not need to be available in the app store; however, any apps that are available should be linked for judges to review. In lieu of an approved app in the app store, video simulations and click-through protoypes are acceptable submissions.
Each participant or team submission will be given 3 minutes to present your project to the judges and participants. Presentations will be timed and have a hard 3 minute stop. Groups may use their video submissions as their presentation.
Does PeabodyHacks have a code of conduct?
Yes, we do! All attendees must adhere to the MLH code of conduct. For concerns, please contact Kathleen DeLaurenti, firstname.lastname@example.org or Andrea Copland, email@example.com