Recherche avancée

Sur d’autres sites (7649)

• libx264 codex not enabled in ffmpeg ubuntu 18.04

  23 novembre 2022, par Bendemann

  I have some weird codex installation issues with the following docker image.

  


  ARG PYTORCH="1.8.0"
ARG CUDA="11.1"
ARG CUDNN="8"
FROM pytorch/pytorch:${PYTORCH}-cuda${CUDA}-cudnn${CUDNN}-devel

ENV TORCH_CUDA_ARCH_LIST="6.0 6.1 7.0 8.0+PTX"
ENV TORCH_NVCC_FLAGS="-Xfatbin -compress-all"
ENV CMAKE_PREFIX_PATH="$(dirname $(which conda))/../"

# https://github.com/NVIDIA/nvidia-docker/issues/1632
RUN apt-key del 7fa2af80
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/3bf863cc.pub
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu2004/x86_64/7fa2af80.pub

RUN apt-get update && apt-get install -y \
        git nano ninja-build p7zip-full imagemagick wget unzip \
        libglib2.0-0 libsm6 libxrender-dev libxext6 libturbojpeg \
        libxrender1 libfontconfig1 freeglut3-dev llvm-6.0-tools curl \
        amqp-tools ffmpeg libx264-dev \
    && apt --fix-broken install \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* \
    # for visualizing
    && wget https://github.com/mmatl/travis_debs/raw/master/xenial/mesa_18.3.3-0.deb \
    && dpkg -i ./mesa_18.3.3-0.deb || true \
    && apt install -f \
    && git clone https://github.com/mmatl/pyopengl.git \
    && pip install ./pyopengl


  


  First of all, libx264 is supposed to be installed by a simple apt-get install ffmpeg in ubuntu 18.04.5. Indeed I see that it is being installed in the installation instructions but for some reason, it's not enabled. This is confirmed when running ffmpeg -codecs | grep 264, which doesn't show libx264 (only h264, libopenh264 are there).

  


  In addition, I also compiled from source, explicitly enabling libx264 during installation. It didn't make a difference.

  


• libx264 codex not enabled in ffmpeg ubuntu 18.04

  23 novembre 2022, par Bendemann

  I have some weird codex installation issues with the following docker image.

  


  ARG PYTORCH="1.8.0"
ARG CUDA="11.1"
ARG CUDNN="8"
FROM pytorch/pytorch:${PYTORCH}-cuda${CUDA}-cudnn${CUDNN}-devel

ENV TORCH_CUDA_ARCH_LIST="6.0 6.1 7.0 8.0+PTX"
ENV TORCH_NVCC_FLAGS="-Xfatbin -compress-all"
ENV CMAKE_PREFIX_PATH="$(dirname $(which conda))/../"

# https://github.com/NVIDIA/nvidia-docker/issues/1632
RUN apt-key del 7fa2af80
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/cuda/repos/ubuntu2004/x86_64/3bf863cc.pub
RUN apt-key adv --fetch-keys https://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu2004/x86_64/7fa2af80.pub

RUN apt-get update && apt-get install -y \
        git nano ninja-build p7zip-full imagemagick wget unzip \
        libglib2.0-0 libsm6 libxrender-dev libxext6 libturbojpeg \
        libxrender1 libfontconfig1 freeglut3-dev llvm-6.0-tools curl \
        amqp-tools ffmpeg libx264-dev \
    && apt --fix-broken install \
    && apt-get clean \
    && rm -rf /var/lib/apt/lists/* \
    # for visualizing
    && wget https://github.com/mmatl/travis_debs/raw/master/xenial/mesa_18.3.3-0.deb \
    && dpkg -i ./mesa_18.3.3-0.deb || true \
    && apt install -f \
    && git clone https://github.com/mmatl/pyopengl.git \
    && pip install ./pyopengl


  


  First of all, libx264 is supposed to be installed by a simple apt-get install ffmpeg in ubuntu 18.04.5. Indeed I see that it is being installed in the installation instructions but for some reason, it's not enabled. This is confirmed when running ffmpeg -codecs | grep 264, which doesn't show libx264 (only h264, libopenh264 are there).

  


  In addition, I also compiled from source, explicitly enabling libx264 during installation. It didn't make a difference.

  


• Compiling FFMPEG on CentOS DigitalOcean

  29 juillet 2015, par coder_uk

  I set up a DigitalOcean instance running CentOS 6.5 and successfully followed the guide to compile FFMPEG (https://trac.ffmpeg.org/wiki/CompilationGuide/Centos). Hurrah !

  But of course I realised that by default, DigitalOcean creates a root user and so ffmpeg now lives in /root/bin/ffmpeg. Which isn’t ideal because when I want to exec the ffmpeg bin from nginx, I would have to run nginx as root for it to have permission.

  Questions ...

  1) Long-shot, but presumably if I change the owner of the ffmpeg binary to nginx, it still won’t work, because nginx won’t be able to access the /root folder it is in. Correct ?

  2) I could run nginx as root (’user root’). But this seems like a very bad idea. Correct ?

  3) Which leaves me with the option of creating a new user, and then compiling ffmpeg into its home folder. But : which user ? EC2 creates ’ec2-user’, so should I make my own equivalent for DO ? But then won’t I have to run nginx as that user, else I’ll run into the same problem ?

  Or should I compile ffmpeg into the ’nginx’ home folder, if indeed it has one ? Is that how it is supposed to be done ?

  Since compiling ffmpeg takes ages, I don’t want to keep doing it, and the static files all seem very out of date. Thanks