picard VS FFmpeg

Have you tried https://www.funkwhale.audio/?

It can be used effectively as a "private spotify". Labeling is a solved problem thanks to https://picard.musicbrainz.org/, and the fact that a lot of the music you buy these days comes pre-labeled already.

You then have a web-app (and/or a mobile app, if that's your thing) where you can stream music as you would with Spotify.

You can even build yourself a little music-sharing commune with friends, where you all upload the albums you buy and accumulate a nice collection of diverse tunes.

I use picard for my collection. My work flow is Picard > Lyrics Finder > Foobar for BPM, RealGain and DR > Custom python script to pull genre and mood from Last.FM and spotify> then Advanced Renamer to perform naming clean up of folder names. I lowercase and underscore spaces. Also does files if I happen to need Mp3Tag when Picard doesn't find anything. Once this is done I move files on to may NAS.

Musicbrainz Picard - A great application that I've used in the past to identify and organize my saved music collection. It's not focused on adding semantic tags though: it's used for adding metadata to .mp3 files.

I do the same but run it though Picard[0] before adding to Plex.

[0]https://picard.musicbrainz.org/

feed all of your music to something like 'musicbrainz picard' - it will sort out all the tags and provide the artwork too

Aside from properly ripping and tagging your own physical collection I'd generally refer you to r/piracy but I think they've gone a bit strange since the blackout. I'm fairly sure anything more specific in that direction would not be appropriate for this subreddit.

Downloading MusicBrainz will be a lifesaver for you.

GPL2

Since FFmpeg is GPL2, doesn’t that require CompressX to disclose its source code?

IANAL, apologies if I miss understand license requirements.

https://github.com/FFmpeg/FFmpeg?tab=License-1-ov-file

This turns out to be a lot of assembly macros to help write one x86 assembly. https://github.com/FFmpeg/FFmpeg/blob/master/libavutil/x86/x...

The sibling comment recommending compiler intrinsics is probably the best way to go for writing SIMD code. A mixture of `` style types and intrinsics to specify instructions is a solid 90% solution compared to assembly.

If you want that last 10%, I think macros are putting the emphasis in the wrong place. They're a somewhat easy way to build up a language abstraction which will work if held carefully, but I'm confident the dev experience using this abstraction when you write invalid code will be deeply confusing.

I would suggest to write a parser instead of the macros. That'll tell you clearly when the syntax is invalid (though possibly not with much precision) and it'll give you a place to put semantic analysis for where valid syntax encodes nonsense. Do the equivalent of the macro expansions on the parsed tree instead of on the text. Emit asm as the "back end".

You might have heard of FFMPEG or ImageMagick for image and video edition in a programmatic way. MoviePy is a Python module for video editing (Python wrapper for FFMPEG and ImageMagick). It provides functions for cutting, concatenations, title insertions, video compositing, video processing, and the creation of custom effects. It can read and write common video and audio formats and be run on any platform with Python 2.7 or 3+.

There are many cloud-based tools and websites that can convert your images, but the problem with these tools is that you usually have to upload the files for them to be processed, and some of their services are not free. In this article, I'd like to introduce a piece of software called FFmpeg, which allows you convert the images locally with one simple command.

To run the demo locally, be sure to have Python 3.11 and FFmpeg installed.