New Release | Karaoke File Name Fixer v1 Is Ready For Download

Karaoke File Name Fixer V1 Launched

The official V1 release of Karaoke File Name Fixer has arrived!

The Windows-based karaoke software utility that allows KJs to easily batch rename karaoke files to one standard naming convention just got better. The official V1 release of Karaoke File Name Fixer can be downloaded below.

Karaoke File Name Fixer was birthed after customer support kept responding to the same ‘problem’ time and time again; karaoke hosts and karaoke enthusiasts regularly had karaoke songs in MP3+G and Zipped MP3+G from various sources and various file name structures. While PCDJ Karaoki, the top karaoke show hosting software, allows users to apply extraction methods for their various naming conventions on import (so you can make sure title populates the title column and artist in the artist column), it can be a slow and tedious process. We recognized a need for a simpler solution…

Through a guided step-by-step process, Karaoke File Name Fixer allows you to batch conform all your karaoke song titles to one standard naming convention. The result is a karaoke library that’s cleaner in appearance and a one-step process to import into Karaoki (or other karaoke software title).

Stop wasting time with the overly tedious task of manually correcting karaoke file names and give Karaoke File Name Fixer ($19.99) for Windows a try!

New And Improved In Karaoke File Name Fixer V1

  • Improved installation process (fixed ‘db’ error message that sometimes appeared after the first time a user launched KFNF)
  • Various performance improvements and bug fixes
  • Updated User Guide


Have questions about Karaoke File Name Fixer and how you can use it to batch rename karaoke files? Please leave them in the comments section below!

4 replies
  1. Eric Braden
    Eric Braden says:

    I am trying to install the trial version, but I receive the error message:

    “We can’t install the 32-bit version of Office because we found the following 64-bit programs on your PC:

    Office 16 Click-to-Run Extensibility Component 64-bit Registration

    Please uninstall all 64-bit Office programs, then retry installing 32-bit Office. If you want to install 64-bit Office instead, please run the 64-bit setup.”

    I currently have Office 2016 64-bit installed on my PC and do not want to uninstall it. Do you have a 64-bit version of your software or is there a workaround that I can try to use your software?

    BTW: When I finish the installation, KFNF will open but it will not let me select a location. The following error message is displayed:

    “The expression On Load you entered as the event property setting produced the following error: Cannot update. Database or object is read-only.

    * The expression may not result in the name of a macro, the name of a user-defined function, or [Event Procedure].
    * There may have been an error evaluating the function, event, or macro.”

  2. Eric Braden
    Eric Braden says:

    I believe I have resolved this issue on my own. It turns out they are separate issues that I will address below.

    Office 2016 64-bit error message:
    This message is displayed when the installer attempts to install the Office Access 2016 run-time. Since Office is already installed on my machine, it cannot complete the installation. It turns out that Office 2016 installs both the 64-bit and 32-bit extensibility packages so this error message will not prohibit KFNF from running. This is essentially a non-error.

    On Load macro error:
    This error was caused by the installation location that I chose. Since KNFN is actually an Access database with macro functionality, it cannot be installed in secure locations on your PC such as the Program Files folder. This results in the database being opened as read-only. The error message appears to be a result of the macro attempting to write to the database which is in read-only mode. When I re-installed KNFN in My Documents, it runs without error.

    I would recommend adding notes about both of these issues in your installation documentation so other users do not run into these problems.

    Please feel free to delete both of my posts if you feel they do not add to the discussion here.

    Thank you!

    • Ryan Sherr
      Ryan Sherr says:

      This is fantastic information Eric, and we thank you tremendously for sharing it! I will pass this over to development to add to the documentation straight away!

Comments are closed.