sickbeard_mp4_automator VS neovim

I have been using MP4 automator for over 5 years; https://github.com/mdhiggins/sickbeard_mp4_automator . I choose MP4 as it works on preety much any device i have ever tryied, H264, AAC stereo and AC3 5.1. Have also used Tdarr for H265 conversion; it really uses 35-50% less space for same quality (4k and I wasnt able to see difference).

They do extended versions of some existing containers that add extra stuff. I use sabnzbd-extended for the SMA support.

SMA, Automatically converts media files to a standardized format, and tags them with the appropriate metadata from TMDB if the container supports tagging. Made to integrate with Radarr, Sonarr, etc. but can be run stand alone. Python required (3+, although 2.7 was still supported, last I knew). Free. https://github.com/mdhiggins/sickbeard_mp4_automator

Sickbeard mp4 Automator for media conversation and metadata matching. Combined with mediaelch for bulk renaming and poster downloads, they’re essential for plex hosting. Also use subler for quick metadata/language code fixes.

You can use something like the following to automate the transcoding: https://github.com/mdhiggins/sickbeard_mp4_automator

Going back to https://github.com/mdhiggins/sickbeard_mp4_automator, I was following the steps for sonarr/radarr and went to add a connection (custom script). Browsed to /usr/local/sma/postSonarr.py and clicked the test button, and I got an error that the script exited with -1. I am wondering if it has something to do with this weird instruction from the github page:

As a software engineer, choosing and understanding your text editor is important part of your work, as it impacts your productivity and workflow efficiency. It's like choosing the perfect tool for any trade - you need to know what tool to use and how to use it effectively if you want to excel. For me, I use Neovim as my editor and I have been using it for a little over a year now.

This got me thinking about my recent pivot, my switch to Neovim by way of LazyVim to write most of my code, and using tmux to keep terminal states alive after closing a session.

Neovim: Make sure you have Neovim installed on your system. You can check the official website for installation instructions: https://neovim.io/ Git: We'll be using Git to clone the LazyVim starter pack. If you don't have Git, you can download it from https://git-scm.com/downloads

There are several ways to install Neovim. This wiki provides several guidelines on how to install Neovim.

All these thoughts I've shared, I would have them on occasion - but ever since I switched to Linux and Neovim, my curiosity has been through the roof. Switching over to Neovim and Linux was a not so fun weekend of configuration and spending half a day getting my work's local dev environment running on my new OS (which no one has tested development on). But I now have a deeper understanding of the tools I use, and have a text editor configured to be the most optimal for the way I want to use it.