rmuralin – Page 2 – Team D4

26Mar 2023 by rmuralin No Comments

Team Status Report for March 25th, 2023

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…

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…

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…

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…

19Mar 2023 by rmuralin No Comments

Rachana’s Status Report for 3/18

Rachana, Weekly Status Reports

Personal Accomplishments I went over the design report that had a lot of feedback for the signal processing section, and I worked on the Ethics assignment that allowed me to examine ethical considerations behind our project a little more. With respect to the design report, there were a few concerns on sampling rate that I had to address. With the default sampling rate being 44.1KHz. Since we are chunking and never really outputting the audio itself, we don't care about the end result of the audio, but we care about the statistics we are able to generate from the audio. Moreover, I realized that in the design report, there were way too many features I wanted to iterate over for a data frame for a singular chunk. I realized that…

19Mar 2023 by rmuralin No Comments

Parth’s Status Report for 3/18

Parth, Weekly Status Reports

Personal Accomplishments This week, I spent my time working on finishing up the UI and completing the Ethics Assignment. I was able to migrate the UI back to a CSS framework from Bootstrap and was able to get the slider functionality working. Further, I was also able to design the functionality for communication with the signal processor and the lighting engine. This will be useful starting next week, when I will begin integrating my subsystem with the others. The GigBar that we had ordered before spring break was also delivered this week. I helped with setting up the GigBar and testing out control with the lighting engine. The GigBar while fundamentally similar to the par lights we were testing with earlier, had some key differences. Majorly, the combination of the…

19Mar 2023 by rmuralin No Comments

Abhishek’s Status Report for March 18th

Abhishek, Weekly Status Reports

Personal Accomplishments This week, the Gigbar 2 light that we ordered came, and I was able to begin properly testing my functionality. I spent the majority of this week figuring out how the lights worked, playing with the inbuilt programming of the lights, and using the DMX input to control the lights. The light set has two pars, two derbys, a laser and a strobe bar. The DMX input allows me to control each individual fixture independently. This is promising because the inbuilt programs are pretty random in their selection of what lights are on at any given moment, so with this fine degree of control we should be able to do much better than any preconfigured program. An example of this lack of inbuilt control is the fact that…

11Mar 2023 by rmuralin No Comments

Parth’s Status Report (3/11 & 3/4)

Parth, Weekly Status Reports

Personal Accomplishments For the week of March 4, I spent a large portion of the week working on the design report. I deliberated with the team in making choices for the design reports, and spent many hours finishing the report. Further, I created the Django models for the UI and was able to establish communication with the USB ports on macs. I also tried switching the front end of our web application to Bootstrap in order to make better sliders, but I realised that it made the web-app marginally slower. Hence, I decided to stick to native CSS. For the week of March 11, I did not do anything as I was out for Spring Break. I travelled with my team to Punta Cana, Dominican Republic, where I got to…

11Mar 2023 by rmuralin No Comments

Team Status Report (3/11 & 3/4)

Weekly Status Reports

Summary Over the last two weeks, the team made some progress in all of the subsystems. For signal processing, we defined the windowing parameters and were able to extract out audio features from a file. As for the lighting engine, we created objects for lights and light sets that are due to be tested when our lights are delivered next week. Finally, for the UI, we created the Django models and established communication with the computer I/O. For the week of March 4th, we spent most of the time working on finishing the design report as a team. We tried to make our design report as thorough as possible, and it required multiple hours of deliberation and work among all of us. For the week of March 11, we did…

11Mar 2023 by rmuralin No Comments

Rachana’s Status Report (3/11 & 3/4)

Rachana, Weekly Status Reports

Personal Accomplishments I do not have any updates on the project from Spring break. I was briefly messing around with the chunks of a song using python asyncio functions. Currently it's able to iterate over multiple chunks, and when it senses a match of song title between two chunks. Once it finds a match it can exit out of the for loop, and doesn't have to iterate over all the chunks for the selected song. I was also looking into accessing the chunks every 30 seconds. This needs to happen over the whole course of the audio because even if we identified the song in the first two chunks, the song might change over the course of the compilation, and we need to account for the song inflections. …