Summer of Code/2018/Music Blocks Widget Improvements: Difference between revisions
para2.1 Tag: visualeditor |
part2.2 Tag: visualeditor |
||
| Line 4: | Line 4: | ||
'''What is your name?''' | '''What is your name?''' | ||
My name is Ritwik Abhishek. I am | My name is Ritwik Abhishek. I am 3rd year undergraduate student at Indian Institute of | ||
Technology Guwahati. | Technology Guwahati. | ||
| Line 62: | Line 62: | ||
My project involves 3 separate parts | My project involves 3 separate parts | ||
1) '''Fix widget bugs''' - There are several widgets in Music Blocks. As reported on github | |||
repository <nowiki>https://github.com/walterbender/musicblocks/labels/widget</nowiki> , there are around | |||
20 bugs reported currently. I think there would be another 10 bugs related to widgets which | |||
would be reported during summers. I am planning to remove 2-3 bugs per day. Most of thebugs involve pitch-time matrix, tempo, timbre, filters, rhythm ruler. Most of bugs are easy | |||
and they would be fixed in around 10 days. Other bug reports involve adding some | |||
functionality and are actually enhancements. | |||
2) '''Pitch tracker -''' It involves making a widget which would record sound, process it to find | |||
fundamental frequency for every small segment, and then choose blocks (whose frequency | |||
is closest to fundamental frequency of each segment), and then use these blocks to code | |||
the recorded sound in Music Blocks language. | |||
I chose to use fundamental frequency because it can be calculated in real time and is easy to | |||
calculate as well. For calculating fundamental frequency I will be using autocorrelation as | |||
feature vector. Autocorrelation is correlation of a signal with its delayed copy. | |||