Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
Both packages are conda install-able and available via conda-forge so hopefully quite uncontroversial and straight-forward.
imagemagick's convert is needed to change the stretch on pre-rendered jpgs, and ffmpeg is needed for making animations of jps/pngs.
The should be added to the base env so that they're available to k8 containers as well as the shared stack and nublado builds.
Attachments
Issue Links
Activity
I'd argue that if people want gifs for a reason, then they should make those gifs, and that we can't know or legistlate every usecase. Clearly mp4s have many advantages over gifs, but sometimes, some people might also need an actual gif.
But anyway, my particular usecase involves imagemagick as part of the moviemaking pipeline, but it doesn't itself make the movies.
Anyway, I have everything I want already - I know how to, and can and do just clone our conda envs and manually install things for myself, and have had what I needed installed into my k8s pods by hand. I just thought that my usecases were common enough (as evidenced by the CLO post, and knowing that I'm not alone in pipelines/commissioning as a movie-maker) that I'd try to spread the love a little and make things easier for others, but I'm happy to just withdraw this as it's clearly a very unpopular proposition with many people.
This will be added to Rubin-extras which will appear with Rubin-env 4.0.
Oops. Should have also added an implementation ticket for adding to shared-stack and RSP.
I'd argue that with the massive compression advantage and clear control over playback speed of mp4 vs. gif, we should discourage using imagemagick for any kind of video making.