81–89 of 89 posts
Earlier quoted context omitted.
Same for me: Running on Firefox 31.0 (Windows 7) and i can crash it every time ...
Do you guys happen to be using Intel graphics?
Earlier quoted context omitted.
I have been thinking a lot on how to implement this feature. Showing it easy enough, but creating strumming patterns is a bit of a challenge... This is my favorite feature though.
Don't implement strumming patterns! I've watched my wife trying to learn guitar pursing her lips saying up-down-up-up-down to herself and it just sounds robotic. Once you can play the chords smoothly enough strumming just happens. Even better, everyone seems to strum their own way (i cant sing so i strum a lot to compensate, whereas i have a friend with a beautiful voice who barely touches the strings)
I couldn't get this to work, after selecting a song it appears to work for ~30 seconds and replies with "This song cannot be analyzed because it is not set as public on YouTube." or "This song cannot be analyzed because it is not set as public on SoundCloud."
What songs? I'll check
Earlier quoted context omitted.
You're right. The idea is that each note of the scale should fall on a successive line or space on the staff, and the "convention" of having keys be only sharps or flats falls out from that (hm, why? I've never thought about that). So for diatonic chords we spell them with those same notes of the scale as well, of course. Some scales even have double flats or sharps!
> The idea is that each note of the scale should fall on a successive line or space on the staff, and the "convention" of having keys be only sharps or flats falls out from that (hm, why? I've never thought about that). The second part is really the same as the first. You want to be able to spell each diatonic alphabetically in order without skipping any letters of the alphabet. The B major scale is B C# D# E F# G# A…
Yup, that's true, though the choice of enharmonic keys will depend on context: e.g. the V7/V in a sharp key will be spelled in another sharp key even if more awkward, with double-sharps etc. Also, to get pedantic there are no "accidentals in the key signature" by definition.
Earlier quoted context omitted.
> The idea is that each note of the scale should fall on a successive line or space on the staff, and the "convention" of having keys be only sharps or flats falls out from that (hm, why? I've never thought about that). The second part is really the same as the first. You want to be able to spell each diatonic alphabetically in order without skipping any letters of the alphabet. The B major scale is B C# D# E F# G# A…
> As for diatonic scales that start on an accidental, as far as I know you can use either the flat or the sharp notation. They are enharmonic equivalents. I know there are often traditional preferences, simply to choose the spelling that leaves fewer accidentals in the key signature. For instance, I think that Db major is more common than the equivalent C# major because the former has 5 flats while the latter has 7 s…
Yeah, I tried to figure out a better term for that, but I'm not aware of one. Of course, I meant notes that are accidentals in C major, i.e. the black keys on a piano.
A question about your plans: you describe annotating as 'contributing to the community' but your terms of service say that only you, not the community, have a license to my copyright on the annotations. You also say that you may one day charge fees.
There have been cases (notably http://en.wikipedia.org/wiki/Gracenote_licensing_controversy) where users have built a database that a company has then claimed as its own and profited from, to the exclusion of the users. So, the question: are the user-contributed annotations open source and licensed as such? And, if not, why would I contribute annotations to a wiki that I may later no longer be allowed to access?
Earlier quoted context omitted.
It tries to figure out the artist by itself and as with all automatic things like this it missed sometimes.
You have an editor to fix the chords. Is there a way to fix the metadata? Can it understand the difference between a composer and a performer?