Music is a part of every culture around the world and throughout history. Musicology is the study of that music from a structural and sociological perspective. Traditionally this research has been done in a manual and painstaking manner, but the advent of the computer age has enabled an increase of many orders of magnitude in the scope and scale of analysis that we can perform. The music21 project is a Python library for computer aided musicology that is written and used by MIT professor Michael Scott Cuthbert. In this episode he explains how the project was started, how he is using it personally, professionally, and in his lectures, as well as how you can use it for your own exploration of musical analysis.
Do you want to try out some of the tools and applications that you heard about on Podcast.__init__? Do you have a side project that you want to share with the world? Check out Linode at linode.com/podcastinit or use the code podcastinit2019 and get a $20 credit to try out their fast and reliable Linux virtual servers. They’ve got lightning fast networking and SSD servers with plenty of power and storage to run whatever you want to experiment on.
This episode of Podcast.__init__ is brought to you by Clubhouse, the first project management platform for software development that brings everyone together so that teams can focus on what matters – creating products their customers love. Clubhouse provides the perfect balance of simplicity and structure for better cross-functional collaboration. Its fast, intuitive interface makes it easy for people on any team to focus-in on their work on a specific task or project, while also being able to “zoom out” to see how that work is contributing towards the bigger picture. With a simple API and robust set of integrations, Clubhouse also seamlessly integrates with the tools you use everyday, getting out of your way so that you can deliver quality software on time.
Listeners of Podcast.__init__ can sign up for two free months of Clubhouse by visiting pythonpodcast.com/clubhouse.
- Hello and welcome to Podcast.__init__, the podcast about Python and the people who make it great.
- When you’re ready to launch your next app or want to try a project you hear about on the show, you’ll need somewhere to deploy it, so take a look at our friends over at Linode. With 200 Gbit/s private networking, scalable shared block storage, node balancers, and a 40 Gbit/s public network, all controlled by a brand new API you’ve got everything you need to scale up. Go to pythonpodcast.com/linode to get a $20 credit and launch a new server in under a minute. And don’t forget to thank them for their continued support of this show!
- And to keep track of how your team is progressing on building new features and squashing bugs, you need a project management system designed by software engineers, for software engineers. Clubhouse lets you craft a workflow that fits your style, including per-team tasks, cross-project epics, a large suite of pre-built integrations, and a simple API for crafting your own. Podcast.__init__ listeners get 2 months free on any plan by going to pythonpodcast.com/clubhouse today and signing up for a trial.
- Visit the site to subscribe to the show, sign up for the newsletter, and read the show notes. And if you have any questions, comments, or suggestions I would love to hear them. You can reach me on Twitter at @Podcast__init__ or email [email protected])
- To help other people find the show please leave a review on iTunes, or Google Play Music, tell your friends and co-workers, and share it on social media.
- Join the community in the new Zulip chat workspace at pythonpodcast.com/chat
- Your host as usual is Tobias Macey and today I’m interviewing Michael Cuthbert about music21, a toolkit for computer aided musicology
- How did you get introduced to Python?
- Can you start by explaining what computational musicology is?
- What is music21 and what motivated you to create it?
- What are some of the use cases that music21 supports, and what are some common requests that you purposefully don’t support?
- How much knowledge of musical notation, structure, and theory is necessary to be able to work with music21?
- Can you talk through a typical workflow for doing analysis of one or more pieces of existing music?
- What are some of the common challenges that users encounter when working with it (either on the side of Python or musicology/musical theory)?
- What about for doing exploration of new musical works?
- As a professor at MIT, what are some of the ways that music21 has been incorporated into your classroom?
- What have they enjoyed most about it?
- How is music21 implemented, and how has its structure evolved since you first started it?
- What have been the most challenging aspects of building and maintaining the music21 project and community?
- What are some of the most interesting, unusual, or unexpected ways that you have seen music21 used?
- What are some analyses that you have performed which yielded unexpected results?
- What do you have planned for the future of music21?
- Beyond computational analysis of musical theory, what are some of the other ways that you are using Python in your academic and professional pursuits?
Keep In Touch
- Mozart’s Requiem performed by Berlin Philharmonik and conducted by Claudio Abbado
- Studies in Western Music History: Quantitative and Computational Approaches to Music History on MIT Open Courseware
- National Bureau of Economic Research
- Zen of Python
- Abjad Python Package
- Levenshtein Distance
- AVL Tree
- Subversion (SVN)
- Bach Chorales
- Artusi.xyz Interactive Music Theory
- MIT Digital Humanities