Processing
Knowledge Base 

 Search

Here you can search and view our site Knowledge Base.
To find a specific article, use KB-article number format (ex. KB-1)

Article number: Article number: kb-85
Q. My jamroom cluster ffmpeg and lame encoder stopped working after upgrading to 4.2 or newer

A. The latest jamroom (4.2 and newer) features moved things around and changed things. The fix should be relatively simple.

To fix lame for jamroom 4.2 or newer;
Login to FTP on your master, go to your jamroom directory, drag and drop the "lame" file in to the tools folder. Problem solved for lame.

To fix ffmpeg for jamroom 4.2 or newer;
Login to jamroom, create a new advanced key for "jr_cluster_ffmpeg_binary". Set the path to /usr/local/bin/ffmpeg and save.

Users running versions prior to 4.2 can safely ignore the above, things will remain in working order without issue.
This page has been viewed 1481 times


Return to Search