Weekly Status Reports

08Apr 2023 by parthmah No Comments

Rachana’s Status Report for April 8

Rachana, Weekly Status Reports
Tests I have been running my signal processing params module on a song that can be located on spotify and shazam to see whether those API calls are robust. Moreover, I have run them on pitch modulated files of 15 seconds, and amplitude modulated files of the same length. I have also been able to specify the resolution of the values i.e do i want to get 5 second averages or 3 second averages or just stick to my 1 second averages. They are currently all working fine. I want to be able to run some tests on voiced and unvoiced components, and also run beat detection on an unplugged file and make sure it is not sensing the percussive elements.  Personal Accomplishments Alot of this week went into working…
Read More
08Apr 2023 by parthmah No Comments

Parth’s Status Report for April 8

Parth, Weekly Status Reports
Personal Accomplishments Over the last week, I spent my time working on implementing the logic for converting signal processing to lighting attributes. Parts of the functionality were shown during the interim demo, where we were able to change the intensity and the saturation of the colors. After that, I worked on modularizing the code and implementing other parameters such as rotation, strobe, UV, etc. To accomplish this, I analyzed different signal processing outputs and cleaned the data using running averages, outlier detection, and normalization. I also helped with refining and debugging the lighting engine and the signal processing subsystems. On Track? We were able to make up for lost time from the previous week, and overall progress was on track. We were able to test each function independently and in…
Read More
02Apr 2023 by aagarwa4 No Comments

Abhishek’s Status Report for April 1

Abhishek, Weekly Status Reports
Personal Accomplishments This week, I was working on the Expressive Lighting Engine and I was able to get the lights tested with a lot of different functionality. I designed the lighting system to function like a tree. They have functions such as Select Color, Fade, Rotate, and Color Change. All of these functions have respective implementations for different lights. Right now we are using pars, derbys, strobes, and lasers. Each of these lights can only do some of the functionality but they can not all perform the same function. However I have programmed them to use the best approximation of each function. For example derbys cannot use all colors but they will approximate with the color range that they have. This means that we can control the Gigbar as a…
Read More
02Apr 2023 by rmuralin No Comments

Team Status Report for April 1st, 2023

Weekly Status Reports
April 1, 2023 Team Status Report for April 1 Summary  Our team continued to make significant progress towards our project goals. Last week, we were able to narrow down our subset of features in the signal processing subsystem and test some of these features. Throughout our testing, we realized that some features such as the MFCC and the liveness were not adding much more new information to our analysis, so we decided to shelf them for the meantime. This allowed us to focus on the impact of features such as frequency, amplitudes, and beat detection, which we were able to use to make decisions about the colors, intensity, and timing of the lights respectively. These decisions proved beneficial while determining the lighting logic, and we were able to make significant…
Read More
02Apr 2023 by rmuralin No Comments

Parth’s Status Report for April 1

Parth, Weekly Status Reports
Personal Accomplishments Most of my time this week went towards working on integrating the signal processing subsystem with the lighting engine. I worked extensively on defining the logic which we will be using to convert signal processing attributes to lighting calls. I collaborated with my teammates on the necessary adjustments and refinements to the lighting logic, and we were able to finalize the lighting effects for our show. I also spent time coming up with metrics to test smaller chunks of the functionality, and helped develop audio tracks for the interim demo. Additionally, I worked on creating documentation for my subsystem, making sure it was well-documented and easy to understand for any future developers who may work on the project.  On Track? While I was able to meet all my…
Read More
02Apr 2023 by rmuralin No Comments

Rachana’s Status Report for April 1st, 2023

Rachana, Weekly Status Reports
Personal accomplishments  After a lot of deliberation,we decided to remove certain features that were not affecting our audio signals as much. I thought alot about the use of MFCC as well, and I don't think that was adding as much value as isolating frequencies. So, the newer approach to chunk these dataframes is to use peak frequencies, beat detection, and amplitudes. We also thought about isolating parts of the chorus, but quickly realized that amplitudes are reflective of  While combining these with global parameters, we can see that this gives us quite a bit of information to work off of. This was a necessary reduction in the number of features because we were getting a bit of relevant information. We also increased the resolution of the graphs to incorporate values…
Read More
26Mar 2023 by rmuralin No Comments

Team Status Report for March 25th, 2023

Weekly Status Reports
Summary  We made substantial progress in our individual subsystems. Leading up to the interim demo, we want to finalize some parts of our integration with respect to the signal processing class connected with the lighting engine, UI subsystem’s with feature query subsystems, and UI subsystem’s interaction with the lighting engine. Currently, the feature query subsystem is connected to the signal processing subsystem. We narrowed our subset of features in the signal processing subsystem, and tested some features strobe, fade, blackout, colour cycle, colour, and modifying its interaction with the lights, and we have a working UI as well.  Risk  The primary risk still comes from the latency of the signal processing, and how fast we will be able to generate metrics for the lighting calls to be made. We are…
Read More
26Mar 2023 by rmuralin No Comments

Parth’s Status Report for March 25

Parth, Weekly Status Reports
Personal Accomplishments This week, I focused on polishing up the features of the UI subsystem. I was waiting on my teammates to finish their subsystems so we could start the integration process ahead of our interim demo. I helped them brainstorm, fix bugs, and make design modifications to their subsystems. Further, I started the process of integration by setting up the communication with the signal processor and the lighting engine, and tested the functionality of my subsystem in conjunction with the others. I also worked with the team to plan out the lighting logic that will convert the inputs from the signal processor to the desired light outputs, taking into account the randomness of the GigBar. On Track? I am on track with my work and feel confident in our…
Read More
26Mar 2023 by rmuralin No Comments

Abhishek’s Status Report for March 25th

Abhishek, Weekly Status Reports
Personal Accomplishments This week we spent working on integration and advancing my individual part in the Expressive Lighting Engine. The work on the lighting engine involved taking care of bugs and building out certain functionality. I implemented strobe, fade, blackout, and color cycle and color hold ended up working after some significant bug fixes. The fade is especially hard because an input to the fade function was how long the fade should take to reach from one color to the next. The way that I have been writing these fades is to increment and decrement the light color intensities until the desired color is reached. This is tough if the fade is over a long period of time because then the change in color will be very granular and less…
Read More
26Mar 2023 by rmuralin No Comments

Rachana’s Status Report for March 25th, 2023

Rachana, Weekly Status Reports
Personal Accomplishments I am able to split the song into chunks, and I run song detection on each of the chunks. Currently chunks are split by the 10000 frames. The documentation for Librosa is confusing, and I spent alot of time understanding what the library was helping accomplish. I am able to get MFCC coefficients for a few chunks of 5 second intervals, and relative beat differences for those 5 second intervals.    This allows us to win back more time as we dont need to extract features in every chunk iteration. We also want split signal processing into another thread as this does not depend on song selection and spotify audio features. We are able to process each individual chunk effectively, and notice beat differences. I used asyncio functions…
Read More