Recherche avancée

Médias (0)

Mot : - Tags -/xmp

Aucun média correspondant à vos critères n’est disponible sur le site.

Autres articles (99)

  • MediaSPIP 0.1 Beta version

    25 avril 2011, par

    MediaSPIP 0.1 beta is the first version of MediaSPIP proclaimed as "usable".
    The zip file provided here only contains the sources of MediaSPIP in its standalone version.
    To get a working installation, you must manually install all-software dependencies on the server.
    If you want to use this archive for an installation in "farm mode", you will also need to proceed to other manual (...)

  • HTML5 audio and video support

    13 avril 2011, par

    MediaSPIP uses HTML5 video and audio tags to play multimedia files, taking advantage of the latest W3C innovations supported by modern browsers.
    The MediaSPIP player used has been created specifically for MediaSPIP and can be easily adapted to fit in with a specific theme.
    For older browsers the Flowplayer flash fallback is used.
    MediaSPIP allows for media playback on major mobile platforms with the above (...)

  • ANNEXE : Les plugins utilisés spécifiquement pour la ferme

    5 mars 2010, par

    Le site central/maître de la ferme a besoin d’utiliser plusieurs plugins supplémentaires vis à vis des canaux pour son bon fonctionnement. le plugin Gestion de la mutualisation ; le plugin inscription3 pour gérer les inscriptions et les demandes de création d’instance de mutualisation dès l’inscription des utilisateurs ; le plugin verifier qui fournit une API de vérification des champs (utilisé par inscription3) ; le plugin champs extras v2 nécessité par inscription3 (...)

Sur d’autres sites (7302)

  • ffmpeg built on mac 10.13 fails when ran on other computer (dyld : Library not loaded libmp3lame.0.dylib)

    15 mars 2023, par Martin

    I have a shell script called buildffmpeg.sh which I call with the command $ sh buildffmpeg.sh on my mac os high sierra 10.13 machine :

    


    #!/bin/bash

# If you get error `c compiler failed` run `sudo apt install libglfw3-dev libglew-dev`
# apt-get install build-essential
# apt-get build-dep ffmpeg
# when running this on mac, you need to install some libraries such as 'brew install opus'

set -e

CWD=$(pwd)
PACKAGES="$CWD/packages"
WORKSPACE="$CWD/workspace"
ADDITIONAL_CONFIGURE_OPTIONS=""


mkdir -p "$PACKAGES"
mkdir -p "$WORKSPACE"

FFMPEG_TAG="$1"
FFMPEG_URL="http://git.ffmpeg.org/gitweb/ffmpeg.git/snapshot/74c4c539538e36d8df02de2484b045010d292f2c.tar.gz"

FFMPEG_ARCHIVE="$PACKAGES/ffmpeg.tar.gz"

if [ ! -f "$FFMPEG_ARCHIVE" ]; then
    echo "Downloading tag ${FFMPEG_TAG}..."
    curl -L -o "$FFMPEG_ARCHIVE" "$FFMPEG_URL"
fi

EXTRACTED_DIR="$PACKAGES/extracted"

mkdir -p "$EXTRACTED_DIR"

echo "Extracting..."
tar -xf "$FFMPEG_ARCHIVE" --strip-components=1 -C "$EXTRACTED_DIR"

cd "$EXTRACTED_DIR"

echo "Building..."

# Min electron supported version
MACOS_MIN="10.10"

./configure $ADDITIONAL_CONFIGURE_OPTIONS \
    --pkgconfigdir="$WORKSPACE/lib/pkgconfig" \
    --prefix=${WORKSPACE} \
    --pkg-config-flags="--static" \
    --extra-cflags="-I$WORKSPACE/include -mmacosx-version-min=${MACOS_MIN}" \
    --extra-ldflags="-L$WORKSPACE/lib -mmacosx-version-min=${MACOS_MIN} -L/usr/local/opt/lame/lib -Wl,-rpath,/usr/local/opt/lame/lib" \
    --extra-libs="-lpthread -lm" \
    --enable-static \
    --disable-securetransport \
    --disable-debug \
    --disable-shared \
    --disable-ffplay \
    --disable-lzma \
    --disable-doc \
    --enable-version3 \
    --enable-pthreads \
    --enable-runtime-cpudetect \
    --enable-avfilter \
    --enable-filters \
    --disable-libxcb \
    --enable-gpl \
    --disable-libass \
    --enable-libmp3lame \
    --enable-libx264 \
    --enable-libopus

make -j 4
make install

otool -L "$WORKSPACE/bin/ffmpeg"
otool -L "$WORKSPACE/bin/ffprobe"

echo "Building done. The binaries can be found here: $WORKSPACE/bin/ffmpeg $WORKSPACE/bin/ffprobe"

mkdir ffmpeg-mac/ 
cp -r "$WORKSPACE/bin/" "$CWD/ffmpeg-mac/"

rm -rf "$PACKAGES"
rm -rf "$WORKSPACE"

exit 0



    


    When it finishes, I have a folder ffmpeg-mac/ which contains two built executables ffmpeg and ffprobe.

    


    but if I try to move the ffmpeg-mac folder onto my other macbook, running 11.2.3 big sur, and if i try to call my built ffmpeg file with ./ffmpeg-mac/ffmpeg, it fails with this error :

    


    $ ./ffmpeg-mac/ffmpeg 
dyld: Library not loaded: /usr/local/opt/lame/lib/libmp3lame.0.dylib
  Referenced from: /Users/martinbarker/Documents/projects/rendertunev1.1.2/./ffmpeg-mac/ffmpeg
  Reason: image not found
Abort trap: 6



    


    So I think when I run the script to build ffmpeg on my mac 10.13 high sierra machine, it for some reason is not including the file libmp3lame.0.dylib. I've tried using brew to uninstall, install, unlink, and link lame, but no luck. I've tried manually editing my shell script to include the file but no luck.

    


    Can anyone help me fix my build script so that when I build ffmpeg on high sierra, I can use the finished built file on other mac computers ?

    


  • how to get 120fps encoded video to play at "normal" speed instead of slow mo

    1er mars 2023, par Patrick Vellia

    I used my GoPro Hero10 to record at 4k 120fps on a green screen. This original video plays slo-mo in QuickTime but "normal" speed in the browser. I want it playing normal speed, and if end user wants to slow it down they have the extra frames for that to maintain clarity, which is why I record at 120.

    


    I then used FFMPEG to create an image sequence of the video.

    


    Then I ran Image Magic to create the transparent frames.

    


    Then I put it back together with the following command for a HEVC mov file :

    


    ffmpeg -r 120 -f image2 -i transparent/image_transparent_%08d.png -vcodec hevc_videotoolbox -crf 28 -alpha_quality 1  -tag:v hvc1 output.mov


    


    I am still on an Intel MacBook Pro running FFMPEG 4.6 (as I've found 5+ was buggy with one of my commands a few months ago but can't remember which one, I think it was the videotoolbox).

    


    The GoPro video has the following stream data as input to the FFMPEG :

    


    Duration: 00:00:08.15, start: 0.000000, bitrate: 60160 kb/s
  Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro H.265
      vendor_id       : [0][0][0][0]
      encoder         : GoPro H.265 encoder
      timecode        : 19:05:32:105
  Stream #0:1(eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 189 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro AAC  
      vendor_id       : [0][0][0][0]
      timecode        : 19:05:32:105
  Stream #0:2(eng): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro TCD  
      timecode        : 19:05:32:105
  Stream #0:3(eng): Data: bin_data (gpmd / 0x646D7067), 76 kb/s (default)
    Metadata:
      creation_time   : 2023-02-28T19:06:41.000000Z
      handler_name    : GoPro MET  


    


    Whereas the re-constructed video has the following data :

    


    Duration: 00:00:08.13, start: 0.000000, bitrate: 763650 kb/s
  Stream #0:0: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 763696 kb/s, 120 fps, 120 tbr, 15360 tbn, 15360 tbc (default)
    Metadata:
      handler_name    : VideoHandler
      vendor_id       : FFMP
      encoder         : Lavc58.134.100 hevc_videotoolbo


    


    When this re-constructed video plays in the browser, it is in slow-mo and I need to set the playbackRate to 4.0 for it to play "normally".

    


    Is there something I need to add to the video for the browser to play it at "normal" speed ?

    


    EDIT

    


    I just compared the two video streams :

    


    original:
Stream #0:0(eng): Video: hevc (Main) (hvc1 / 0x31637668), yuvj420p(pc, bt709), 3840x2160 [SAR 1:1 DAR 16:9], 59891 kb/s, 119.88 fps, 119.88 tbr, 120k tbn, 119.88 tbc (default)

Reconstructed:
 Stream #0:0: Video: hevc (Main) (hvc1 / 0x31637668), yuv420p(tv, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 763696 kb/s, 120 fps, 120 tbr, 15360 tbn, 15360 tbc (default)


    


    I don't quit understand all of this though. so here's what I notice :

    


    original.         reconstructed
--------------------------------
bt709             progressive
89871 kb/s.       763696 kb/s
119.88 fps.       120 fps
119.88 tbr.       120 tbr
120k tbr.         15360 tbr
11960 tbr.        15360 tbc


    


    Hmm. I suspect it has something to do with tbr and tbc whatever those are, or perhaps the progressive vs the bt709 ? the pirates are also vastly different.

    


  • how can I assign unique AVFoundation camera device names ?

    28 avril 2023, par mcgregor94086

    Short summary :
I have a USB multi-camera array device. According to system_profiler, each of these webcams share the same name : "USB Camera". I have no unique name I can use with FFMPEG AVFoundation and get images from that specific camera. How can I tell FFMPEG the specific camera that I want (each has a unique USB path that I normally use to identify a specific camera.

    


    I can solve this problem on Linux, but I can't figure out how to do it on macOS.

    


    How I might do this on Linux
I know the unique USB Path to each camera, and I would like to use this to assign a unique Name that I can address using FFMPEG when taking images. On Linux I can use the udev system to make those assignments,

    


    In Linux, I can reassign a new unique camera name using /etc/udev/rules.d/60-v4l.rules. with something like this :

    


    SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_1, ENVID_V4L_PRODUCT="Cam_00"
SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_3, ENVID_V4L_PRODUCT="Cam_01"
...

    


    More details :
Of course macOS doesn't work this way, as it uses AVFoundation to address video devices.

    


    When I attach the device I see that 16 new cameras now appear when I type query system_profiler SPCameraDataType, it prints the output shown further below

    


    You may notice that there are 16 cameras all named "USB Camera :" but system_profiler is reporting that each has a "Unique ID :" that is different for each camera. This Unique ID is composed of a unique USB Path (e.g. '0x1441311') concatenated with the "Vendor ID" ('00bda') and product ID ('5829') all expressed in hexadecimal.

    


    Unfortunately, this means every camera has the same generic name in iPhoto, and when specifying the input camera in FFMPEG with AVFoundation syntax, I can't seem to indicate which specific camera I want.

    


    I want to take 1 photo from each camera in a specific order. I have a table that maps each camera's USB Path to a desired name that would make it easy for me to trigger the camera captures in the sequence I desire.

    


    In Linux, I can reassign a new unique camera name using /etc/udev/rules.d/60-v4l.rules.

    


    SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_1, ENVID_V4L_PRODUCT="Cam_00"
SUBSYSTEMS=="usb", ENVID_VENDOR_ID=="0bda", ENVID_MODEL_ID=="5829", ENVID_PATH_TAG==platform-fd500000_pcie-0000_01_00_0-usb_1_4_5_1_3_1_3, ENVID_V4L_PRODUCT="Cam_01"
...

    


    % system_profiler SPCameraDataType

    


    Camera :

    


    USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144131100bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144200000bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144141400bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144131300bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144141300bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144121200bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144121400bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144133000bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144131200bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144141100bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144143000bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144121300bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144110000bda5829

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144141200bda5829

FaceTime HD Camera (Built-in):

  Model ID: UVC Camera VendorID_1452 ProductID_34068
  Unique ID: 0x8020000005ac8514

USB Camera:

  Model ID: UVC Camera VendorID_3034 ProductID_22569
  Unique ID: 0x144300000bda5829


    


    MacBook Pro, OS X 10.11
Posted on Apr 27, 2023 10:49 PM
Reply

    


    Page content loaded
There are no replies.
how can I assign unique AVFoundation camera device names ?
Reply