[Mscore-developer] GSoC project idea "Accessibility"

Hi all, I have already introduced myself, and I am interested in the GSoC project idea, Accessibility. In this project, I am planning to implement a keyboard based interface on top of the museScore system. I thought of having a one-to-one mapping of required events to key combinations without

Re: [Mscore-developer] GSoC project idea "Accessibility"

On Sat, Mar 19, 2016 at 1:51 AM Samadhi Poornima < samadhipoornima...@cse.mrt.ac.lk> wrote: > 2). Enable the use of keyboard to navigate to a text element or an > articulation or a crescendo marking. > I think there is probably a pretty straightforward model for how this could work, based on

Re: [Mscore-developer] GSoC 2016 - automatic sheet creation - Music/Voice recognition

I will first try to address the technical aspects of your questions, from my personal perspective as one of the developers: I think you'll find this is a far more complex topic than you might realize. Just doing the translation from audio to pitches is hard enough, then on top of that you need

[Mscore-developer] GSoC Introduction and Project Idea

Hi All! My name is Kathryn, currently a second year student studying at University of Toronto Engineering Science. Alto in choir, amateur piano player. I have years of experience programming in C and python, and I've been working on my C++ skills for a few months. I've been using MuseScore to

[Mscore-developer] GSoC 2016 - automatic sheet creation - Music/Voice recognition

Hi My name is Igor Konyakhin. I am 4th-year student at the department of Computer Science of Moscow State University I have an experience using many programming languages (especially C++, C#, JavaScript). My knowledge of algorithms is quite good and the code I write is easy to understand. I am a

Re: [Mscore-developer] GSoC project idea "Accessibility"

Thanks for your interest in this project. Do you have ideas on how this system you mention might work? The main thing thst is not currently keybaord-acciessible now are the palettes. One idea lasconic had was to make these searchable much liek the Symbols dialog (press "Z" to display) or the

Re: [Mscore-developer] Tablature question - how to determine if in a 5 staff line banjo tab or not

Hi, You are working on this one right https://musescore.org/en/node/102186 There is no way to know if a staff is for a banjo or not. Checking the number of staff lines or the midi program are not safe ways. I believe you need to come up with a more global approach about this problem. Maybe it

Re: [Mscore-developer] Tablature question - how to determine if in a 5 staff line banjo tab or not

FWIW, as the one who coded most of the tab feature, I second lasconic in his opposition to anything tied to a specific instrument; for instance, the piano Ped. feature is there, but it is not specifically tied to a staff being a piano staff, for it being used or usable (the user is ultimately

Re: [Mscore-developer] GSoC project idea "Accessibility"

Let me add that even sighted mouse addicts will appreciate a palette that can be filtered. The advanced palette has several 100 symbols and even in the basic palette, there are over 100 symbols. A lot of users have hard time to locate specific symbols. lasconic 2016-03-17 19:07 GMT+04:00 Marc

Re: [Mscore-developer] (GSOC 2016) Regarding the Virtual Singer project idea...

Non-developer jumping in again. *Sinsy* supports English, and can be accessed via a web service. Send a MusicXML file in, and get a .wav file back. For implementation details, see: https://pypi.python.org/pypi/sinsy-cli/ Since Sinsy says it works well with MuseScore's MusicXML (it says so on

Re: [Mscore-developer] Tablature question - how to determine if in a 5 staff line banjo tab or not

fwiw, I would say that Change String Tuning is the appropriate way to handle a partial or non-standard capo (e.g. a capo that frets only some strings, or one that spans differing frets). Each string has an "open

Re: [Mscore-developer] Hello, and: Chord Playback GSoC idea

Hi, I'm also very interested in this topic. I just wonder if it shouldn't be too complicated to just have a priority for extensions (like root has lowest priority, fifth next lowest - third has very high priority and tensions are higher than root and fifth but maybe the 7th is more important than

Re: [Mscore-developer] Hello, and: Chord Playback GSoC idea

FWIW, I think the algorithm to come up with a voicing is the least important part of this project. Deciding on on overall idesign for how the feature would work in general is much more important. So hopefully rhe forum thread generates some good ideas there. On Wed, Mar 16, 2016 at 7:50 AM

Re: [Mscore-developer] GSoC project idea "Accessibility"

Hello, Marc, Lasconic, Samadhi! The code that Marc is talking about for traversing palettes and also for providing screen reader feedback for it's elements can be found in this branch: https://github.com/andreituicu/MuseScore/tree/accessible_palettes As Marc said, the code is pretty old, so if

Re: [Mscore-developer] GSoC project idea "Accessibility"

By considering the suggestions mentioned and the notes from Andrei here are the requirements of the project as I feel. 1/ Make the palettes keyboard accessible · Make the palettes searchable by implementing a filter- A shortcut (something like ctrl+F9) to summon the

Re: [Mscore-developer] GSoC project idea "Accessibility"

Sorry about the previous message. It has some formatting errors. So here I attach the formatted message. By considering the suggestions mentioned and the notes from Andrei here are the requirements of the project as I feel. 1). Make the palettes keyboard accessible - Make the palettes