Skip to main content

My Tool - Songs Renamer

We all have downloaded songs from the internet or ripped songs from CD/DVD and stored on our PC or music player. Whenever we do that, the songs are named as xxx01.mp3, xxx02.mp3 and so on, where 'xxx' stands for the album name. The song's actual name is hidden away in its Advanced Properties -> Title. This is really frustrating because we cannot identify the song. The tool 'Songs Renamer' which I have created helps you solve this problem. It automates the process of renaming of songs by picking up the text available in Title property and applying it in the file name.

Download Songs Renamer


Creative Commons License
Songs Renamer by Mayank Kumar is licensed under a Creative Commons Attribution-No Derivative Works 2.5 India License.

Features

1. Creates a tree structure based on the folder selected for processing. It can process upto n-level of nested folders. However, it may take some time if the nesting is too deep.
2. Allows user to choose a single file or entire folder. User can alter his choice at any point of time.
3. Single click renaming of files from the application interface itself.
4. 'Open' and 'Open containing folder' options available from the right-click context menu from the application interface.

Usage


1. Install and launch the application.


2. Click om 'Browse' button and select the folder where the songs you want to be renamed are kept.



3. Choose the songs you want to rename by selecting the adjacent check box.


4. Click on 'Rename' button. The renaming progress bar is displayed and finally a 'Rename Complete' message is displayed.



5. You are done!!

Installation


Supported Operating Systems -

1. Windows XP
2. Windows Server 2003
3. Windows Vista
4. Windows 7 (Not fully tested yet)

Pre-requisites -

1. Microsoft .NET Framework 2.0
2. Disk Space - 5 MB
3. Memory - 128 MB of RAM


Bug Reporting


In case you encounter any bug, please mail me at mayankthebest[at]gmail[dot]com along with the generated error log file.

Comments

Popular posts from this blog

Integrating React with SonarQube using Azure DevOps Pipelines

In the world of automation, code quality is of paramount importance. SonarQube and Azure DevOps are two tools which solve this problem in a continuous and automated way. They play well for a majority of languages and frameworks. However, to make the integration work for React applications still remains a challenge. In this post we will explore how we can integrate a React application to SonarQube using Azure DevOps pipelines to continuously build and assess code quality. Creating the React Application Let's start at the beginning. We will use npx to create a Typescript based React app. Why Typescript? I find it easier to work and more maintainable owing to its strongly-typed behavior. You can very well follow this guide for jsx based applications too. We will use the fantastic Create-React-App (CRA) tool to create a React application called ' sonar-azuredevops-app '. > npx create-react-app sonar-azuredevops-app --template typescript Once the project creation is done, we ...

Centralized Configuration for .NET Core using Azure Cosmos DB and Narad

We are living in a micro services world. All these services are generally hosted in Docker container which are ephemeral. Moreover these service need to start themselves up, talk to each other, etc. All this needs configuration and there are many commercially available configuration providers like Spring Cloud Config Server, Consul etc. These are excellent tools which provide a lot more functionality than just storing configuration data. However all these have a weakness - they have a single point of failure - their storage mechanism be it a file system, database etc. There are ways to work around those but if you want a really simple place to store configuration values and at the same time make it highly available, with guaranteed global availability and millisecond reads, what can be a better tool than Azure Cosmos DB! So I set forth on this journey for ASP.NET Core projects to talk to Cosmos DB to retrieve their configuration data. For inspiration I looked at Steeltoe Con...

Add Git Commit Hash and Build Number to a Static React Website using Azure DevOps

While working on a React based static website recently, there was a need to see exactly what was deployed in the Dev/Test environments to reduce confusion amongst teams. I wanted to show something like this: A quick look at the site's footer should show the Git Commit Hash and Build Number which was deployed and click through to actual commits and build results. Let's see how we achieved this using Azure DevOps. Git Commit Hash Azure DevOps exposes a variable called  $(Build.SourceVersion) which contains the hash of the commit. So I defined a variable in the Build Pipeline using it. Build Id and Build Number Azure DevOps also exposes two release time variables  $(Build.BuildId) and  $(Build.BuildNumber) which can be used to define custom variables in the pipeline. So we have a total of 3 variables defined: Next we use these variables in our React App. I created 3 global variables in index.html and assigned a token value to them. < script   type = "text/JavaScri...