I’ve been exploring some ways to provide online teaching/learning aids for Carnatic music via the Patantara site. It is about time I captured some of the principles that we would like to stand by in a recognizable logo. While the finesse of the logo hasn’t been executed yet, here is a shape that has stuck with me for some time now.
Let me know what you think in the comments.
Patantara supports a notion of “collections” to help teachers maintain access permissions for a set of documents they give access to their students. This post describes how to use them.
For most compositions, the “svarasthana” notation which uses the letter
SrRgGmMPdDnN for the 12 svara sthanas serves pretty well. For ragas which
R as “ga”, for example, this doesn’t work as it creates a difference
between how the svara is written and how it is sung. This also creates
difficulties with typing out svaras where you know the raga isn’t going to
The “substitutions” feature in the Patantara editor helps with these situations and this post is about how to use it.
The ability to have audio tracks integrated with music notation would be of great use to students of Carnatic music. Towards that, we’ve now added support for anyone adding documents to Patantara to also attach audio recordings to the notation lines. We’ve also added a couple of commonly used and requested tools to aid learning and practice that’s integrated right into the notation documents published on Patantara.
In this post we first show you how to use a document which has audio tracks associated with notation lines. In the next post, we will describe for authors how to create such documents.
Earlier, we wrote about the preamble, using which you can change the file name of a document by which it is catalogued. We’d mentioned that the document preamble is intended for more controls on the document being available in a versioned manner. In this post, we introduce how you can control who can view/edit your document.
So far, the names of patantara documents were fixed at creation time. This has proved to be disadvantageous especially given that when a new document is needed, many users are using the “copy” function to copy an existing starter document, which ends up having the same name as the original.
As of this post, patantara supports changing the catalog name of a document for the convenience of users.
Many music notation publication sites provide notation in the form of Microsoft Word “doc” or “docx” files. There are many reasons to avoid using MSWord for notation of Indian classical music. I will try to list down a few here and while on the topic argue why the approach taken by Patantara is much more enduring.
Patantara had thus far used Mozilla Persona for signing in users for editing documents. Since Mozilla retired the Persona service this month, a new email-based signin mechanism is now in place. Our hope is that this will be easier to use for our less technically inclined users.
The Patantara notation viewer used to use combining unicode characters to display sthayi - i.e. octave - markers. These appear as either single dot above or below a svara letter or a double dot above or below. The single dot indicates one octave shift and the double dot indicates two octave shift. These markers displayed correctly only in Safari on MacOSX and failed on the more commonly used Chrome browser due to a series of bugs in Chrome. We’ve now “fixed” these by rendering the dots separately and not relying on the browser’s ability to handle unicode combining characters correctly.