Scordatura Plug-in discussion

• Sep 16, 2020 - 17:49

Forum members have recently suggested the development of plug-in for transposing scordatura playback. I'm certainly open to the idea and would like to focus plug-in discussion here.

I'm suggesting this because I'd like to prevent my recently created a Scoratura topic from being subsumed or derailed by side topics, despite their merit!

I hope this is viewed as a reasonable request.

In the thread just mentioned I myself spurred a side discussion by inquiring about a range selection filter. On seeing the rush of replies I created a forum separate topic on a pitch range selection filter. I did so in an attempt to keep the discussion focused on scordatura, and that worked out well.

I was then able to report back concisely and provide a link to the discussion on pitch-range selection

Thanks for your cooperation on this!

scorster


Comments

It's unclear to me how a MuseScore plug-in could automatically identify candidate notes in scordatura, the notes that need playback transposition. Ultimately it seems that would require mind reading the scordaturist. Nevertheless I'm open to the concept, which is why I created this topic.

I glean that the existing Tempo plug-in requires the user to first add markers throughout their score. This leaves me concerned anyone using a scordatura plug-in would first be required to mark candidate notes and doing so may amount to more work than selecting them manually.

Surely, a range selection filter would assist by doing the bulk of the work, but that feature would have widespread usefulness in MuseScore. So I'd rather see a note-range filter baked into the app itself.

Please add general comments about a range filter here. That way we can stay focused on a scordatura plug-in in this thread.

Much appreciated!

Scorster

In reply to by scorster

The TempoChanges plugin was an example to show that plugins can be interactive if needed. I think this would be vital for a scordatura plugin. Another plugin, the Color Notes plugin, that comes preinstalled in the program is an example of selecting certain notes either score wide or within a selection and changing something about them. Using techniques from both plugins would enable the user to change select notes displayed pitch as needed. The fixed to line problem would need to be fixed somehow though. This isn't out of the question.

In reply to by mike320

I wouldn't assume that at all. I would take it at face value - as I said, a suggestion to start a new forum thread on the "fix to line" feature so we can fully understand what changes might be desired by a broad selection of users. Making a change that happens to make things better for a scordatura plugins but worse for everyone else is not something that I can get behind. Building a consent sus of how the feature could be improved for everyone is. Once there is a good solid design everyone is on board with, we can implement it.

Meanwhile, I haven't really followed the discussion here, but my guess is a plugin could still be developed using the capabilities that are present already. If someone can summarize the expected results - not just of fix to line, but precisely what the plugin should be doing to a given note and why - most likely we can help design it.

To help further this discussion—and clarify my position—I've pasted these comments I express in another thread on scordatura.

===================

A plug-in would need:

a) a means of determining what objects to target
b) a designated impact to perform on those objects

Given the scenario I've outlined I can't conceive of an algorithm that could effectively achieve "a".

At first blush it would appear that a plug-in could simply ask the user to define one (or more) target pitch ranges. But in scordatura a pitch doesn't necessarily indicate a particular string.

For instance, if I have a mandolin (normally GADE) retuned to GDAD, in the Guidian staff the written E above the open A string could be played as:

  • the 7th fret on the A string
  • the open 1st string (the one retuned to D!)

I unable to see how such choices could be automated. That said, I don't need them to be, nor was I recommending it. And if there's not an effective programmatic means of achieving "a" there no reason to think about "b". But perhaps I've overlooked something obvious. I do that all the time!

Scordatura is manual labor—like writing regular notation—and there lots of design decisions made along the way. Naturally I'm comfortable with that because Scordatura itself is easily achieved on the Guidian staff.

Is the believe that, on the fly, a plug-in can transpose of the sound output of scordatura notation? That's all I'm looking for. But again, first one would have to achieve "a" ... exactly as the scordaturist would want. I'd love to be wrong on this, but that possibility seems somewhat far fetched to me.

========

Do you still have an unanswered question? Please log in first to post your question.