Dear Soumya Kushwaha

I hope this message finds you well. I wanted to address an issue regarding the responsiveness of the GUI in our spectrogram application. Currently, users are experiencing delays and freezes in the interface, particularly during audio processing tasks. To enhance user experience and ensure smooth operation of the application, I propose implementing the following strategies:

1.Multithreading: Execute the audio processing and plotting tasks in separate threads to prevent blocking the main GUI thread. This will ensure that the GUI remains responsive even during heavy audio processing.

2.Optimized Plotting: Optimize the plotting code to minimize the time taken to update the plot. This may involve reducing unnecessary computations or using more efficient plotting methods.

3.Buffering: Implement buffering of audio data to smooth out the processing load and avoid sudden spikes in CPU usage. Buffering will provide more consistent performance and prevent the GUI from freezing.
By implementing these strategies, we can significantly improve the responsiveness and usability of the spectrogram application, thereby enhancing user satisfaction.

Dear Soumya Kushwaha,

I hope this message finds you well. I wanted to update you on the latest enhancements I've made to our audio recording and visualization application. Below is a summary of the new features:

Save Recording Functionality: Users can now save their recordings directly from the application. Upon clicking the "Save Recording" button, the recorded audio is saved as a WAV file named "recording.wav".

Pause and Resume Buttons: I've added functionality for users to pause and resume recording sessions. This gives users more control over their recording sessions, allowing them to pause and resume whenever needed.

These features enhance the usability and flexibility of our application, providing users with more options and control over their recording experiences.

Please assign make this issue I work on it
Thank You

In GSSoC'24, GitHub Topics will help the discoverability of your project.

I see that you already have great topics on your repository!
I would recommend adding the name of the company like the software you use to build like "vs-code, ghdesktop" to improve your discoverability.

If you are happy with the topics you have, feel free to close this issue. 👍

Is your feature request related to a problem? Please describe.
The current method of accessing GUI elements, such as the "graph" element from the "window" dictionary stored in the "_VARS" dictionary, is not very intuitive or readable.

Describe the solution you'd like
I propose the following changes to improve the readability and user experience of the application:

1. Change the AppFont variable from "Any 16" to "Helvetica" for better readability.
2. Add tooltips to the sg.Graph and all sg.Button elements in the layout to provide better user guidance.
3. Add a sg.Text element before the progress bar to label it as "Progress:" to make it clear what this bar represents.
   Screenshots:
   Before
   
   After
   

Describe alternatives you've considered
Not applicable. The changes suggested do not have direct alternatives as they are specific improvements to the user interface. They are based on standard UI/UX principles and are generally applicable across different GUI libraries or frameworks.

It is important that we add how one can contribute in this project and some important features about this project will also help.

We need to create a Streamlit application that visualizes real-time audio input through a microphone. The app should provide two types of visualizations: waveform and spectrogram. Once the app is developed, it should be deployed to a free hosting service for easy access and use.

I am participating in GSSOC'24

Many users face limitations in manipulating and enhancing audio recordings obtained through microphones. Traditional methods may lack precision or require extensive manual effort.
So as a solution I suggest Integrating Generative AI techniques to empower users to manipulate and enhance audio recordings with unprecedented flexibility and efficiency. This could include tasks such as noise reduction, voice separation, audio synthesis, and more.

Alternative methods for audio enhancement exist, including manual editing with software tools or applying conventional signal processing algorithms. However, these methods often lack the sophistication and automation provided by Generative AI.

Generative AI has demonstrated remarkable capabilities in various domains, from image generation to natural language processing. By harnessing its power, we can revolutionize the way users interact with and manipulate audio recordings, opening up new possibilities for creativity and productivity.

Additionaly if you like to work on this idea the assign me as a GSSoC'24 Contributor as it will help me also.

Describe the feature

This app uses a specific version of python. So, it may not work on everybody's device. Containerizing the application using docker would make it easier and more developer friendly.
Please assign me this issue under GSSOC'24

Add ScreenShots

Description

Create a visualizer that detects and displays the beats in the audio input for music analysis and rhythm visualization.

Requirements

• Detect beats in real time and visualize them with indicators.
• Customize the visualizer with different beat detection methods.

Tasks

• Design the user interface for the visualizer.
• Implement the visualizer using PyAudio and PySimpleGUI.
• Test the visualizer for accuracy and responsiveness.
• Document how to use the visualizer.

Error handling can be added to check PyAudio is correctly initialized or not in https://github.com/Soumya-Kushwaha/SoundScape/blob/main/Spectogram.py

Hello there! 👋 I've been really impressed by the idea of the project. I'm particularly keen on enhancing the UI to ensure it's not just visually appealing but also user-friendly for both end-users and fellow contributors.

I propose to work on refining UI elements, providing intuitive widgets aligned with the project's theme, and adding more aesthetically pleasing features for graph plotting. My experience in similar projects equips me well for this task.

Also the PySimpleGUI used for the project is proprietary and ask for payment after free trial. So to avoid this i suggest to use CustomTkinter for the same purpose, and i can help you with that

I'd be thrilled to take on this issue and contribute to making our project even better. Looking forward to your feedback and the opportunity to collaborate on this! 😊

Here are some images of the UI of the projects i worked on: (You can see them in my profile)

Describe the bug
Upon attempting to close the application after initiating a recording session and subsequently closing the window, an error occurs related to progress bar update, preventing the application from terminating gracefully. The error persists regardless of how many times the application is closed via the window close button.
To Reproduce
Steps to reproduce the behavior:

1. run python waveform.py or python amplitude-frequency-visualizer.py or python spectogram.py
2. Click on listen and speak
3. Now close the application thorugh window
4. Now this shows error in progressbar update no matter how many times you close from there it wont terminate gracefully.

Expected behavior
It should close the application gracefully but it's not doing that it asks to terminate the application.

Screenshots

Additional context
I would like to contribute these changes to the main project. Could you please assign me .I would like to request that this issue be labeled as part of GSSoC'24 and marked as Level 2.

Description:

Create a visualizer that displays the root mean square (RMS) amplitude of the audio signal over time, providing insight into the perceived loudness of the audio input.

Requirements:

• Display the RMS amplitude in real time as a plot.
• Include customization options for different color schemes and thresholds for amplitude levels.

Tasks:

• Design the user interface for the visualizer.
• Implement the visualizer using PyAudio and PySimpleGUI.
• Test the visualizer for accuracy and responsiveness.
• Document how to use the visualizer.

Is your feature request related to a problem? Please describe.

Yes, the current version of the project lacks support for custom visualizers, limiting users to predefined visualization techniques. This restricts users' ability to customize the visualization experience according to their specific needs and preferences.

Describe the solution you'd like

I would like to have the ability to add custom visualizers to the SoundScape project. This would allow users to create and use their own visualization techniques for analyzing real-time audio. Users should be able to define custom visualization methods and seamlessly integrate them into the SoundScape interface.

Describe alternatives you've considered

One alternative solution would be to rely solely on the predefined visualizers provided by the project. However, this would limit users' ability to customize the visualization experience and may not meet the diverse needs of all users. Another alternative would be to use external visualization libraries, but this could complicate the integration process and reduce the cohesiveness of the project.

Additional context

The ability to add custom visualizers would greatly enhance the versatility and utility of the SoundScape project, empowering users to tailor the visualization experience to their specific requirements. This feature would open up new possibilities for analyzing real-time audio data and contribute to a more immersive and personalized user experience.

Hi @Soumya-Kushwaha , can you please assign this to me under GSSOC" 24 ?

We recommend that every repo has a code of conduct. If you don’t feel comfortable creating your own Code of Conduct from scratch we highly recommend using one of the templates provided by GitHub. If you do use a template, please read through the template and ensure that you can and will abide by the Code of Conduct.

Please follow these instructions on how to add a Code of Conduct.

Sample: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/CODE_OF_CONDUCT.md

1. Another way to create sound waves could be to add an audio file and generate plot, besides uploading and recording from a microphone in the moment.
2. Display the note corresponding to the audio signal, for example, A# or C, this could be an important feature for musicians.
3. Audio-based color generation: Depending on the audio signal, have a color corresponding to the signal amplitude in the background. This would improve visual appearance.

Can you assign me to these 3 issues? @Soumya-Kushwaha

The requirements.txt file needs to be updated because the previous PR #39 utilized the soundfile library in Amplitude-Frequency-Visualizer.py.

Add the above mentioned function to Intensity-vs-Frequency-and-time.py file

I would like to contribute to your project by adding a Code of Conduct file to your project. Please assign this issue to me.

Learn repos should have a LEARN.md file to teach student how to build your project step by step. You can explain how to build your project with text, code snippets, images, or even short (5 minute) long video lessons. As the maintainer of a Learn repo, the LEARN.md file requires you to think critically about how to explain the building of your project and how to also make it engaging. We don't expect you to be an expert teacher, but we would like you to reflect on how difficult it was to get to your level of knowledge, and then provide friendly guidance to help other students to learn.

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/blob/main/Learn.md

Create PR templates for the SoundScape project to guide contributors when submitting pull requests. PR templates will help maintain consistency in contributions and facilitate the review process by providing a clear structure for contributors to follow.

Requirements

1. Template Structure:

• The PR template should include sections for:
• PR title and description.
• Changes and additions made in the pull request.
• Testing and validation done for the changes.
• Any additional context or information relevant to the PR.
• Checklists for contributors to ensure all necessary tasks are completed.

2. Instructions: Provide clear instructions for contributors on how to complete each section of the template.

3. Quality Assurance: Include a checklist to ensure the contributor has completed necessary checks, such as running tests, reviewing their code, and following project guidelines.

4. References: If applicable, provide references to project documentation such as Contributing.md and other related documents.

5. Additional Notes: The PR template should be clear and concise to ensure that contributors can easily follow it.

Implementation Steps

1. Research: Research best practices for PR templates and review other successful open-source projects for reference.
2. Draft Template: Create a draft template with the sections mentioned in the requirements.
3. Feedback: Gather feedback from the project maintainers and potential contributors to refine the draft template.
4. Finalization: Finalize the PR template and add it to the project repository.
5. Documentation: Add a section in the Contributing.md file explaining how to use the PR template.
6. Testing: Test the PR template with a dummy pull request to ensure it works as expected.

Expected Outcome

Once implemented, the PR template should streamline the pull request process, making it easier for contributors to submit their changes and for maintainers to review them. This will help maintain a consistent and organized contribution workflow for the SoundScape project.

As the maintainer of a Collaborate repo, keeping Issues up-to-date will help the student community understand what they can do to contribute. Issues should vary by the easy (update documentation) to the difficult (add a new feature). The more involved you are, the more opportunities there are to collaborate.

Recommendations:

Add issues of varying difficulty to the repo often. you must add the tag GSSoC'24, Level 1, Level2, Level 3 good first issue etc.
How we cacluclate the Scores on Leaderboard: Every PR one point
Level 1: 10 points
Level 2: 25 points
Level 3: 45 points
Try to add some documentation issues as well it would be easy for beginner contributor to explore opensource through your repo.
Generate issues even if you plan on solving them, so the repository appears as active.
Contribute/commit often to the repo so it does not go stale.
Reference https://github.com/Recode-Hive/Stackoverflow-Analysis/issues

Is your feature request related to a problem? Please describe.
The project lacks proper code structure and there is a lot of code redundancy.

Describe the solution you'd like
I would like to create a design for the code such that functions like draw() are reused which will allow users to use these functions and build up on it. Also adding a file structure will help users to navigate easily.

Proposed file structure
a) src:
--->1) main.py - which calls the 3 audio visualizers based on user input
--->2) util - containing draw.py and other utils
--->3) visualizers - which contain the main code (importing the utils required)
b) documentation
c) guidelines

Additional context
I would like to contribute these changes to the main project. Please assign me this issue @Soumya-Kushwaha

Depending on the amplitude of the sound wave, the background visuals will get updated with the colour corresponding to wave-form. Kindly @Soumya-Kushwaha share your views on this and assign me this issue if it is good!

Description:
The current description of SoundScape provides a comprehensive overview of the project, detailing its functionality, visualizers, usage, contribution guidelines, and references. However, there are a couple of minor corrections and improvements that could enhance its clarity and consistency.

Spectogram Spelling: The term "Spectogram" should be corrected to "Spectrogram" for accuracy.

Visualizer Title Clarification: The title "Frequency v/s Amplitude" could be clarified for better understanding and consistency. It can be rephrased as "Frequency vs. Amplitude" or "Frequency versus Amplitude."

**You can refer the mistake here **

Is your feature request related to a problem? Please describe.
Currently, there is no mechanism in place to track the decibel level of audio in real-time within the project. This makes it challenging for users to monitor the amplitude of the audio signal, hindering their ability to analyze and understand the audio data effectively.

Describe the solution you'd like
I propose creating a new Python file within the project that implements functionality to track the decibel level of audio in real-time. This new file will provide users with a tool to monitor the amplitude of the audio signal as it is being processed, enabling them to gain valuable insights into the audio data and make more informed decisions based on the amplitude levels.

Describe alternatives you've considered
N/A. These features are additions to the existing functionality and do not replace any current features.

Additional context
I would like to contribute these changes to the main project. Could you please assign me to an issue where I can submit these updates as a pull request? Given the complexity of these changes, I would like to request that this issue be labeled as part of GSSoC'24 and marked as Level 3.

Thank you for considering my contributions. I look forward to your feedback.

I wish to add the code of conduct which needs to be followed for contributing in this project

@Soumya-Kushwaha Please share the references that helped you complete this project. Even if you have used ChatGPT you must provide details on the source of this work.

We need to create a main landing page for the SoundScape application that serves as an entry point for users to navigate to different visualizers. The landing page should be user-friendly and provide a clear introduction to the application.
The main landing page will serve as the central hub for users to select and navigate to these visualizers. It will provide a brief introduction to SoundScape and offer quick access to visualizers and an exit button.

Objective:
Design and develop a main landing page that:

1. Introduces the application.
2. Provides navigation options to various visualizers.
3. Add an Exit Button

Please assign me this task.

Hello @Soumya-Kushwaha, please assign me the task of adding precise comments in between the lines of code under GSSOC'24 so that even a beginner can understand the code hence improving its readability.

Thank you!!

👋 Hi @Soumya-Kushwaha,

I am Prince,web developer(Core Team) Girlscript Summer of Code. I'll be collaborating with you on preparing your repo for GSSoC'24 Program

Why are these changes required?
After Analysing last year's contributions and feedback it would be great for students to have a couple of standard readme files on the repo to understand what the project is all about and some issues detailing what they can contribute. This will help you to see increased engagement in your repository as well.

As mentioned students get a chance to learn step by step, how to build this project as well as invite mentors to collaborate and add features to this repo. I will generate issues, which will provide guidance on how to prepare your repo for Girlscript summer of code 2024 on 10th May.

This issue will serve as a tracking issue to track all issues related to GSSoC'24. I recommend creating a new branch for every issue and opening a pull request to track changes so we can effectively collaborate with each other and merge changes when you and I feel like those changes are ready to be merged on your primary branch.

If you have any questions or concerns, please feel free to leave a comment on this issue or any of the other issues that are generated.

I look forward to working with you

• #19
• #20
• #21
• #22
• #23

Is your feature request related to a problem? Please describe.
No, this feature request is not related to a problem. It is an enhancement to the existing functionality of the Amplitude-Frequency-Visualizer.py script in the "Amplitude-Frequency-Visualizer" project.

Describe the solution you'd like
I have implemented several new features that I believe would enhance the functionality and user experience of the project:

1. Added the ability to pause and resume the audio stream through pause and resume functions. These are tied to "Pause" and "Resume" buttons in the GUI.

2. Implemented a save function that allows users to save the audio data to a .wav file and the frequency plot to a .png file. This is tied to a "Save" button in the GUI.

3. Introduced an audio buffer (_VARS["audioBuffer"]) to store all the audio data for saving purposes.

4. Enhanced the frequency plot with gridlines and a legend.

5. Imported the soundfile library to facilitate saving of audio data to a .wav file.

6. Adjusted the canvas size of the graph from (500, 500) to (600, 600) for better visibility.

7. Updated the GUI layout to accommodate the new "Pause", "Resume", and "Save" buttons.

Describe alternatives you've considered
N/A. These features are additions to the existing functionality and do not replace any current features.

Additional context
I would like to contribute these changes to the main project. Could you please assign me to an issue where I can submit these updates as a pull request? Given the complexity of these changes, I would like to request that this issue be labeled as part of GSSoC'24 and marked as Level 3.

Thank you for considering my contributions. I look forward to your feedback.

This feature aims to solve the problem of inconsistent and delayed communication following the merging of PRs. By automating the commenting process, it ensures that contributors receive timely feedback and acknowledgments. It also reduces the administrative burden on maintainers, allowing them to focus more on code reviews and other critical tasks.

Could you please assign me this issue under GSSOC'24.

I would like to LEARN.md file in main. Please assign this task to me under GSSOC'24.
@Soumya-Kushwaha

@Soumya-Kushwaha Can you please confirm if all the modules listed in requirements.txt are required for this project? I had to install a lot of large AI/ML & Intel acceleration modules which might not be required for the project. Please also confirm if you created this file from the project itself or if you used a requirement.txt from one of your other projects.

If all these libraries are actually required for the project then please provide a dependency graph and a disclaimer for users.

We go through a variety of sound levels and zones in our daily life, even when we are sleeping. This may not look like a big deal to us but it can surely create problems with ongoing age and development of our surroundings. This problem can be reduced tho,not by letting others help you with their actions but analyzing the noise levels and acting accordingly.

The solution can initially deal with the noise level analyzation ,which can source out the frequencies(highs and lows) and filter them out. Using time frequency channels next ,we can have non linear compression which can compress out sections where it needs the most accurately which is super useful for acoustic events. We can have different visualizations via different spectrums to see the frequency distribution which we are dealing with.

There are some methods which I can think of but not sure if all would be possible to work with. As for now ,I can implement the primary method which is straight forward and not very tacky for users who might not have extensive knowledge in this field.

Additional context
I would definitely like to try out the other methods for this issue, so should I create a new issue if I am able to successfully do it after this task is done?

I would like to add Python code that could plot Frequency vs Energy for a particular sound.

Describe the feature

The repository contains code in python, it does not have workflow for code scanning.

Describe the solution you'd like

I aim to implement the CodeQL workflow to automate security checks. CodeQL, GitHub's code analysis engine, will identify vulnerabilities in the code and present the findings as code scanning alerts. This workflow will be activated for every push, commit, and pull request through GitHub Actions.

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSoC'24 contributor
• I want to work on this issue

Description:
Create a visualizer that displays a heatmap of sound intensity over time.

Requirements:

The visualizer should show the intensity of sound across a range of frequencies and time.
Customize the heatmap with different color scales and intensity thresholds.
The visualizer should efficiently handle real-time data processing.

https://docs.docker.com/reference/dockerfile/

I am interested in contributing to the project by adding detailed instructions on how to contribute using GitHub Desktop.

I believe that by providing clear and comprehensive guidance, we can encourage more contributors to participate in the project, especially those who prefer using GitHub Desktop for their contributions.

Could you please assign me the issue related to adding GitHub Desktop contribution instructions under gssoc24? I am excited about the opportunity to contribute to the project and help streamline the contribution process for others.

Describe the feature

As the contributor count rises on the repo, it becomes increasingly challenging for maintainers to personally greet and encourage each contributor for their valuable input. Equally important is the reminder for them to review the project's contribution guidelines.

Add ScreenShots

PR greeting message ⬇️

ISSUE greeting message ⬇️

Record

• I agree to follow this project's Code of Conduct
• I'm a GSSoC'24 contributor
• I want to work on this issue

A GUI which can be used to open the graphs.
I want this issue to be assigned to me.

Issue templates are very helpful for a collaboration repo. When users identify a bug or want to add a new feature, you can provide templates so you can collect all the pertinent information you need to fix a bug or add a new feature.

We recommend creating a “Report Bug” and “Feature Request” issue template.
you can refer this: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

Some suggested prompts/questions you can add to a “Report Bug” template are:

Briefly describe the bug
What is the expected behavior?
Please provide step by step instructions on how to reproduce the bug
Some suggested prompts/questions you can add to a “Feature Request” issue template are:

Briefly describe your feature request
What problem is this feature trying to solve?
How do we know when the feature is complete?

Reference: https://github.com/Recode-Hive/Stackoverflow-Analysis/issues/new/choose
Click on Get Started button and copy the template to your

I propose adding a menu bar to the top of the application window to enhance the usability and accessibility of the project. This menu bar will include options to run the spectrogram, Frequency v/s Amplitude and waveform visualizers with a simple click.

Currently, users must manually start the visualizations, which can be cumbersome and not intuitive, especially for those unfamiliar with the underlying code.

I want this issue to be assigned to me

Solution
This feature will detect sound events, like clapping, car horns, footsteps and highlighting them in the visualization to provide information about the sound. This feature would enable the system to automatically detect specific sound events in real-time and provide visual indications or triggers based on the detected events.

I propose implementing a Sound Event Detection feature in the SoundScape project in GSSoC'24.

Why Implement Sound Event Detection?

Enhanced User Experience: Sound event detection adds interactivity and engagement to the SoundScape project, allowing users to interact with the system based on detected sound events.

Security monitoring: It can be used in security systems to monitor suspicious sounds such as glass breaking or trigger alerts.

Research and Development: Implementing sound event detection provides an opportunity for experimentation and research in audio processing and machine learning techniques.

Implementation

1. Research and select appropriate sound event detection algorithms or techniques based on project requirements.

2. Provide options for users to configure detection parameters, such as sensitivity thresholds or target sound event types.

3. Implement visual indicators or triggers to notify users of detected sound events, such as highlighting relevant portions of the visualization or triggering external actions.

Create an issue template for the SoundScape project to guide contributors when creating new issues. The template will help maintain consistency in contributions and facilitate the review process by providing a clear structure for contributors to follow.

Requirements

1. Template Structure:
   The issue template should include sections for:

• The description about the visualizer.
• How shall the visualizer be used?
• Any additional context or information relevant to the issue.
• Checklists for contributors to ensure all necessary tasks are completed.

2. Instructions: Provide clear instructions for contributors on how to complete each section of the template.

3. Quality Assurance: Include a checklist to ensure the contributor has completed necessary checks, such as running tests, reviewing their code, and following project guidelines.

4. References: If applicable, provide references to project documentation such as Contributing.md and other related documents.

5. Additional Notes: The PR template should be clear and concise to ensure that contributors can easily follow it.

Implementation Steps

1. Research: Research best practices for issue templates and review other successful open-source projects for reference.
2. Draft Template: Create a draft template with the sections mentioned in the requirements.
3. Feedback: Gather feedback from the project maintainers and potential contributors to refine the draft template.
4. Finalization: Finalize the issue template and add it to the project repository.
5. Documentation: Add a section in the Contributing.md file explaining how to use the issue template.
6. Testing: Test the issue template with a dummy issue to ensure it works as expected.

Expected Outcome

Once implemented, the issue template should streamline the issue creation process, making it easier for contributors to raise their issues and for maintainers to review them. This will help maintain a consistent and organized contribution workflow for the SoundScape project.

The current requirements.txt file lists the necessary dependencies that are needed for the SoundScape project but lacks version numbers. I want the users to have a smoother installation process, especially the users unfamiliar with Python package management .It is something I have faced problem with in the past it's important to provide the version details in requirement file.

The Current requirements.txt Content includes:
numpy
matplotlib
scipy
PyAudio
PySimpleGUI
sounddevice
soundfile
I would like to add the versions along with them for smoother installation so can you assign this an issue to me