<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[technology is not a fox's skillset!]]></title><description><![CDATA[technology is not a fox's skillset!]]></description><link>https://technologyismyfoe.hashnode.dev</link><generator>RSS for Node</generator><lastBuildDate>Wed, 21 Oct 2026 15:39:19 GMT</lastBuildDate><atom:link href="https://technologyismyfoe.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[How I Merged My Love for Music and Coding in One Project: The Story of Building Raga-Match.]]></title><description><![CDATA[Hindustani Classical Music AI AI Music Recognition Raga Identification Software Deep Learning for Music Spectrogram Analysis Music and AI Fusion Real-Time…]]></description><link>https://technologyismyfoe.hashnode.dev/how-i-merged-my-love-for-music-and-coding-in-one-project-the-story-of-building-raga-match</link><guid isPermaLink="true">https://technologyismyfoe.hashnode.dev/how-i-merged-my-love-for-music-and-coding-in-one-project-the-story-of-building-raga-match</guid><category><![CDATA[Artificial Intelligence]]></category><category><![CDATA[Deep Learning]]></category><category><![CDATA[ai music generator]]></category><category><![CDATA[SoundEngineering ]]></category><dc:creator><![CDATA[Rittika]]></dc:creator><pubDate>Fri, 21 Mar 2025 14:35:31 GMT</pubDate><content:encoded><![CDATA[<p>Music has always been an integral part of life for me. The intricate melodies of Hindustani classical music have intrigued me since childhood, and over the years, my enjoyment of the subtle nuances of raagas, and the way that they can elicit certain feelings and emotions, flourished. However, my life took a turn after I began coding. I ultimately fell in love with programming, AI, and machine learning, but somewhere in my brain, I always wanted to combine the two interests.  </p>
<p>That’s when I had an idea: <strong>What if I could build an AI-powered tool that could recognize Hindustani classical ragas from any given audio?</strong> Something like Shazam, but for classical Indian music.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1742567418388/32fde313-aff2-4d82-91b1-d66736123b46.webp" alt class="image--center mx-auto" /></p>
<h2 id="heading-the-spark-that-led-to-raga-match">The Spark That Led to Raga-Match</h2>
<p>I started researching how music recognition works, digging into the underlying technology behind apps like Shazam. The key to their success was something called spectrogram-based audio fingerprinting, where an audio file is broken down into its frequency components over time, creating a visual representation of sound.</p>
<p>But Hindustani classical music is very different from mainstream Western music. <strong>Unlike fixed-scale compositions, raagas are fluid, with intricate ornamentations (meend, gamak) and variations in tempo (layakari).</strong> This made the challenge even more exciting: I couldn’t just replicate Shazam’s algorithm; <strong>I had to tailor it specifically for classical music.</strong></p>
<h2 id="heading-the-data-problem-no-dataset-no-problem"><strong>The Data Problem: No Dataset, No Problem?</strong></h2>
<p>Unlike Western music, which has well-documented datasets, Hindustani classical music doesn’t have a structured, <strong>easily accessible dataset</strong> for raga recognition. This was my first major roadblock. I had to <strong>manually collect audio samples</strong>, look up recording snippets, and organize them all into a <strong>single dataset</strong>.</p>
<p>At first, it seemed like a simple task—until I started encountering <strong>audio encoding errors</strong> while processing the files. Different recording formats, metadata issues, and even missing audio links forced me to <strong>update file paths multiple times</strong>. But after weeks of trial and error, I finally compiled a working dataset, which I later uploaded to <strong>Kaggle</strong>. You can check it by following the link below:<br />🎵<a target="_blank" href="https://www.kaggle.com/datasets/r4otxrhs/hindustaniclassicalmusic-raaga?select=ragamatch.csv"><strong>Hindustani Classical Music Raga Dataset</strong></a></p>
<h2 id="heading-the-first-roadblock-dealing-with-noisy-audio">The First Roadblock: Dealing with Noisy Audio</h2>
<p>One of the first problems I encountered was the quality of audio recordings. Unlike studio-produced songs, many Hindustani classical performances are recorded live, sometimes with background noise or accompanying instruments overpowering the vocals.</p>
<p>To tackle this, I integrated noise reduction techniques using Librosa and SciPy. I applied:</p>
<p>✔ Preprocessing filters to remove background noise</p>
<p>✔ Normalization techniques to balance volume levels</p>
<p>✔ Spectrogram generation to highlight important frequency patterns</p>
<h2 id="heading-building-the-model-cnn-lstms-for-raga-identification"><strong>Building the Model: CNN + LSTMs for Raga Identification</strong></h2>
<p>Once I had the dataset, it was time to <strong>train the AI model</strong>. Hindustani classical music is vastly different from Western music because:<br /><strong>Ragas evolve over time</strong>, unlike pop songs with fixed chord progressions.<br /><strong>Ornamentations like meend, gamak, and tanpura drones</strong> make feature extraction difficult.<br /><strong>There are no "exact" labels for ragas</strong>, as performances often mix elements of multiple ragas.</p>
<p>Instead of using traditional <strong>audio fingerprinting</strong>, I decided to build a deep learning model that could analyze <strong>Mel-Spectrograms and MFCCs</strong> (Mel-Frequency Cepstral Coefficients). These are <strong>visual representations of sound</strong>, making them perfect for a <strong>Convolutional Neural Network (CNN) + LSTM (Long Short-Term Memory) model</strong>.</p>
<ul>
<li><p><strong>CNN layers</strong> helped extract <strong>spatial features</strong> from the spectrograms.</p>
</li>
<li><p><strong>LSTMs</strong> captured <strong>temporal dependencies</strong> in how a raga unfolds over time.</p>
</li>
</ul>
<p>After multiple training iterations, the model performed <em>shockingly well</em>! The .pth file containing the trained model gave <strong>results that were too good to be true</strong>. But, AI models performing well in theory doesn’t mean they’ll work perfectly in real-world applications—<strong>the real challenge was yet to come.</strong></p>
<h2 id="heading-real-time-identification-the-web-app-challenge"><strong>Real-Time Identification: The Web App Challenge</strong></h2>
<p>Once the model started making decent predictions, the next step was to build an interactive system. I envisioned a <strong>web app with two features</strong>:<br />🎵 <strong>Upload an audio file</strong> → The app processes it and returns the raga name.<br />🎙 <strong>Record live singing</strong> → The app analyzes the real-time input and classifies the raga.</p>
<p>To achieve this, I built the backend using <strong>FastAPI</strong>, a high-performance web framework that supports <strong>Web Sockets for real-time updates</strong>. The biggest challenge? <strong>Live audio streaming and processing</strong>. Unlike static files, a live recording had to be broken into chunks, processed on the go, and classified in real time without delays. This required fine-tuning buffer sizes and optimizing the <strong>Fast Fourier Transform (FFT) calculations</strong>.</p>
<h2 id="heading-the-flask-api-nightmare-and-websockets-struggles"><strong>The Flask API Nightmare and WebSockets Struggles</strong></h2>
<p>The next step was to integrate the model into a <strong>Flask API</strong> so it could be accessed via a web application. I planned a <strong>Next.js frontend</strong> where users could:<br />✅ <strong>Upload an audio file</strong> to get the <strong>raga name</strong>.<br />✅ <strong>Record live singing</strong>, and the AI would <strong>identify the raga in real time</strong>.</p>
<p>I expected this to be straightforward, but I underestimated the difficulties of handling <strong>real-time audio processing with WebSockets</strong>. Flask wasn’t cooperating, and setting up <strong>WebSockets for live audio streaming</strong> became a major headache.</p>
<p><strong>Real-time latency issues</strong> made it hard to analyze continuous audio input.<br /><strong>Buffering problems</strong> caused unexpected <strong>delays in raga identification</strong>.<br /><strong>Deployment challenges</strong> meant Flask and Next.js weren’t communicating properly.</p>
<p><img src="https://cdn.hashnode.com/res/hashnode/image/upload/v1742567485908/5afcef36-14ab-48a9-8848-a0c63062e9c9.png" alt="First look of the web-app" class="image--center mx-auto" /></p>
<h2 id="heading-still-a-work-in-progress-but-closer-than-ever"><strong>Still a Work in Progress... But Closer Than Ever!</strong></h2>
<p>Even though I faced several roadblocks, Raga-Match is finally taking shape. The AI model works well, and I’ve successfully <strong>preprocessed the dataset, trained the CNN-LSTM model, and integrated the API</strong>—but <strong>live audio analysis is still a work in progress</strong>.</p>
<p>I’m currently experimenting with <strong>FastAPI instead of Flask</strong>, optimizing WebSockets, and fine-tuning real-time inference. The ultimate goal is to deploy this as a <strong>fully functional AI-powered web app</strong>, making <strong>Hindustani classical music recognition accessible to everyone</strong>.</p>
<h2 id="heading-final-thoughts-the-beauty-of-music-and-ai"><strong>Final Thoughts: The Beauty of Music and AI</strong></h2>
<p>Building <strong>Raga-Match</strong> has been an incredible experience. It started as a simple idea—combining my love for music and coding—but turned into <strong>a massive learning journey in AI, data collection, and web app deployment</strong>.</p>
<p>Despite all the struggles, seeing the model correctly classify ragas <strong>feels like magic</strong>. I still have a long way to go, but one thing’s for sure: <strong>Music and AI belong together, and this is just the beginning!</strong></p>
]]></content:encoded></item><item><title><![CDATA[How my self-diagnosis spree led to cool discoveries in computational psychiatry]]></title><description><![CDATA[I never imagined that my journey in computational neuroscience would lead me to one of the most complex and enigmatic conditions in psychiatry—Dissociative…]]></description><link>https://technologyismyfoe.hashnode.dev/how-my-self-diagnosis-spree-led-to-cool-discoveries-in-computational-psychiatry</link><guid isPermaLink="true">https://technologyismyfoe.hashnode.dev/how-my-self-diagnosis-spree-led-to-cool-discoveries-in-computational-psychiatry</guid><dc:creator><![CDATA[Rittika]]></dc:creator><pubDate>Mon, 02 Dec 2024 18:30:00 GMT</pubDate><content:encoded><![CDATA[<p>I never imagined that my journey in computational neuroscience would lead me to one of the most complex and enigmatic conditions in psychiatry—<strong>Dissociative Identity Disorder (DID)</strong>. My fascination with neural circuitry and its role in shaping cognition and identity drove me to explore how disruptions in brain networks contribute to the fragmented sense of self experienced by individuals with DID.</p>
<p>When I first delved into the neuroscience of DID, I was struck by how little we understood about its underlying mechanisms. DID is often dismissed as purely psychological, yet mounting evidence suggests that <strong>abnormal neural connectivity and plasticity</strong> play a crucial role. This realization pushed me to explore the disorder from a <strong>computational and neurobiological</strong> perspective, integrating machine learning with functional neuroimaging to uncover patterns that traditional approaches might overlook.</p>
<h2 id="heading-mapping-the-neural-circuit-dysfunction-in-did"><strong>Mapping the Neural Circuit Dysfunction in DID</strong></h2>
<p>One of the most challenging aspects of studying DID is the heterogeneity in how it manifests. Individuals with the disorder experience <strong>disruptions in memory, sense of self, and identity switching</strong>, which are thought to arise from dysregulated interactions between key brain regions. My research focused on analyzing <strong>resting-state functional MRI (rs-fMRI) data</strong> using <strong>Convolutional Neural Networks (CNNs) with attention mechanisms and saliency maps</strong> to identify the most affected brain regions.</p>
<h3 id="heading-key-brain-regions-implicated-in-did"><strong>Key Brain Regions Implicated in DID</strong></h3>
<p>Through deep learning models, I examined the connectivity between:</p>
<ul>
<li><p><strong>Ventromedial prefrontal cortex (VmPFC)</strong> – Crucial for self-referential processing and identity integration. Reduced connectivity here is associated with <strong>self-fragmentation and altered self-awareness</strong> in DID.</p>
</li>
<li><p><strong>Amygdala</strong> – Governs emotional regulation, often <strong>hyperactive</strong> in trauma-related disorders, contributing to <strong>fear responses and dissociation triggers</strong>.</p>
</li>
<li><p><strong>Hippocampus</strong> – Essential for memory formation, frequently impaired in DID, leading to memory gaps and disrupted autobiographical recall.</p>
</li>
<li><p><strong>Insular Cortex</strong> – Plays a role in <strong>interoception (awareness of bodily states)</strong>, with abnormalities linked to <strong>dissociative symptoms</strong>.</p>
</li>
<li><p><strong>Posterior Parietal Cortex (PPC)</strong> – Involved in <strong>spatial and sensory integration</strong>, often showing reduced connectivity in DID, contributing to <strong>feelings of detachment and depersonalization</strong>.</p>
</li>
</ul>
<p>To enhance interpretability, I incorporated <strong>attention mechanisms with CNNs</strong> and <strong>saliency maps</strong> to pinpoint which brain regions exhibited the most abnormal connectivity patterns in resting-state fMRI. The attention mechanisms helped the model prioritize <strong>clinically relevant neural signals</strong>, ensuring that the most diagnostically significant regions were highlighted. Saliency maps provided a <strong>visual explanation of neural disruptions</strong>, allowing us to see precisely where DID-related abnormalities occurred. This approach not only improved classification accuracy but also offered valuable insights into the functional deficits underlying DID.</p>
<p>By leveraging these techniques, I was able to observe distinct patterns of <strong>hypo- and hyperconnectivity</strong> across these regions, supporting the hypothesis that DID arises from <strong>impaired communication between self-referential and emotion-processing networks</strong>. These findings suggest that clinicians might detect DID in patients by focusing on <strong>abnormalities in identity processing, emotional regulation, and interoception</strong>, as governed by these affected regions. Future advancements in this field could lead to the development of <strong>personalized diagnostic tools</strong> based on neural biomarkers, paving the way for targeted interventions tailored to each individual’s unique neural profile.</p>
<h2 id="heading-bridging-computational-neuroscience-with-clinical-insights"><strong>Bridging Computational Neuroscience with Clinical Insights</strong></h2>
<p>One of the most rewarding aspects of this work has been its potential <strong>clinical applications</strong>. Many DID patients struggle with misdiagnosis and inadequate treatment due to the subjective nature of psychiatric evaluations. By leveraging <strong>functional connectivity biomarkers</strong>, we can move toward more <strong>objective diagnostic tools</strong>, ensuring that individuals receive the care they need.</p>
<p>Beyond diagnosis, my work has also explored <strong>predictive modeling for therapeutic interventions</strong>. By studying <strong>long-term potentiation (LTP) and long-term depression (LTD) in synaptic plasticity</strong>, I aimed to uncover whether targeted neuroplasticity-based treatments—such as <strong>non-invasive brain stimulation or AI-personalized cognitive therapy</strong>—could help reintegrate fragmented neural networks in DID.</p>
<h2 id="heading-the-future-of-did-research-and-my-next-steps"><strong>The Future of DID Research and My Next Steps</strong></h2>
<p>While my findings have contributed a small piece to the larger puzzle of DID, there is still much to explore. Moving forward, I aim to integrate <strong>calcium-dependent synaptic plasticity modeling</strong> to better understand how neural circuits in DID patients adapt (or fail to adapt) over time. <strong>Computational psychiatry offers a revolutionary approach to mental health</strong>, and I believe that <strong>merging neuroscience with AI and deep learning</strong> will be instrumental in unraveling the complexities of DID.</p>
<p>This journey has reinforced my belief that <strong>identity is not just a psychological construct but a deeply biological phenomenon</strong>. The brain’s ability to fragment and reorganize in response to trauma is both awe-inspiring and deeply tragic. As I continue my research, my ultimate goal is to bridge the gap between neuroscience and psychiatry, using computational models to illuminate the hidden architecture of the mind—and, hopefully, to offer new paths toward healing.</p>
]]></content:encoded></item></channel></rss>