sickbeard_mp4_automator VS Sentry

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:

First, sign up for a free account at https://sentry.io. Create a new project and make note of your DSN (Data Source Name).

Using APM tools like NewRelic, Sentry, Datadog, etc to monitor the performance of your application and while you're on it, they can help you identify N+1 queries.

However, ensuring the reliability and performance of your Next.js app is equally crucial. That’s where Sentry comes into play. Combined with Sentry, an industry-leading error monitoring platform, Next.js empowers developers to proactively identify and resolve issues that may arise in their applications. In this article, we’ll explore how to integrate Sentry into your Next.js project for effective error monitoring and performance optimization.

Sentry: Error monitoring for applications, including APIs. Also offers application performance monitoring (APM).

Indeed, webapps are not immune to distribution problems. Wayward and invasive browser extensions are a clear threat, as are 3rd-party dependencies (and their dependencies) loaded at runtime. Which is why companies like https://sentry.io exist. I think the difference is that webapps are "distributable by default" and it takes real work to break this. Versus having local desktop apps which require work to distribute. A potent example of the power of defaults.

Sentry produces nothing of value? You don't value an open source error tracking and performance monitoring platform? https://github.com/getsentry/sentry

> You invent something, and then immediately turn it into a cheap commodity by releasing it for free.

Exactly. A 71-line python script https://github.com/getsentry/sentry/commit/3c2e87573d3bd16f6... was groundbreaking when it came out and the fact that it springboarded into a startup is commendable.

sentry.io: 5

Sentry - Open Source Alternative For Error Tracking

11. Sentry