Skip to main content

Convert MP4 videos to MP3 audio files

I wanted to listen to some recordings of foreign language study courses but they were available only as MP4 videos. And when you play them on your phones or tablets, they will be paused if you navigate away from the screen. It's video. You need to be looking at it for it to play.

But I wanted to listen to them during my commute, which means I need to be walking and not staring at the screen the whole time. I looked for ways to workaround the video-gets-paused limitation but I found that converting it to mp3 is fast, and doesn't cost a penny.

First, to share the script. I keep it here.


  1. Copy as zip, or clone the converter script from the link above.
  2. Go to the folder "mp4-mp3-converter and confirm that you have the file convert.bat inside.
  3. For Windows, download FFMPEG here.
  4. Save the ZIP file and unpack it. Let's assume you unpacked it on the desktop.
  5. You will see a folder with a name that looks like :  ffmpeg-2016xxxx-{some-numbers}-win64-static, the folder name may differ. Inside this folder you will find another folder called "bin". Take note of the full path to this "bin" folder. For simplicity, we will call this the {bin} folder from here on.
  6. Assuming you have 2 folders on the desktop, Videos and Music, copy convert.bat into Videos.
  7. Hold down Shift key and right click on the Videos folder.
  8. Choose "Open Command Window Here". A terminal should launch.
  9. From the terminal, run convert.bat {Path-to-Music-folder}. So if the Music folder is on the desktop then, convert.bat C:\Users\{username}\Desktop\Music

That's it. The converted files will be generated in the Music folder with the same name as the videos, only with the mp3 extension.

Enjoy! and let me know if you run into problems.

In the future I plan to make the steps easier by adding a GUI but let's see...

Comments

Post a Comment

Popular posts from this blog

Object detection with Google Colab and Tensorflow

This is just a memo of the challenges I faced when running a model training on Google Colab, while following a great tutorial here . Mind the versions Tensorflow is currently at version 2.2.0 but most tutorials are still using the contrib package, and there is no known easy way to update the code to remove dependency on contrib. So my best bet is to downgrade the tensorflow version to 1.x. Since Google Colab only gives the options of either 1.x or 2.x and we cannot specify the exact version, I ended up with version 1.15.2. Even with the command :  %tensorflow_version  1.15.0 I ended up with : 1.15.2 Another pitfall was the version of numpy. Installing numpy gives us the version 1.18.3 but for some reason this generates the error : TypeError: 'numpy.float64' object cannot be interpreted as an integer Downgrading numpy to version 1.17.4 solved this for me. It seems we don't need ngrok for tensorboard With the command :  %load_ext tensorboard W...
Post a Comment
Read more

Installing a custom ROM on Android (on the GT-N8013)

It's been a while since my last entry and since it is a new start in 2019, I thought I'd write something about "gone with the old and in with the new". I've had my Samsung Galaxy Note 10.1 (pnotewifi) since 2014, and it's one of the early Galaxy Note tablet series. It has served me well all this years but now it just sits there collecting dust. My old Samsung GT-N8013 I've known a long time about custom Android ROMs like CyanogenMod but has never had the motivation to try them out, until now ! Overview of the process For beginners like me, I didn't have an understanding of the installation process and so it looked complicated and it was one of the reasons I was put off in trying the custom ROM. I just want to say, it's not complicated at all!   Basically you will need to Prepare an SD card and install Android SDK (you need adb ). Install a custom boot loader ( TWRP is the de facto tool at the moment). Use adb to copy custom...
15 comments
Read more

Using FCM with the new HTTP v1 API and NodeJS

When trying to send FCM notifications I found out that Google has changed their API specifications. The legacy API still works but if you want to use the latest v1 API you need to make several changes. The list of changes is listed on their site so I won't be repeating them again but I'll just mention some of the things that caused some trial and error on my project. The official guide from Google is here : Official Migration Guide to v1 . The request must have a Body with the JSON containing the message data. Most importantly it needs to have "message" field which must contain the target of the notification. Usually this is a Topic, or Device IDs. Since my previous project was using GAS, my request had a field called "payload" instead of "body". Using the request from my previous project, my request in Node JS was as follows: request ({ url: 'https://fcm.googleapis.com/v1/projects/safe-door-278108/messages:send' , method: ...
Post a Comment
Read more