Recherche avancée

Sur d’autres sites (11563)

• conflicting of headers between ffmpeg and s3

  2 août 2021, par Juliette

  I have the code below in my server.js file for a web app that uses express for the backend and a built create react app that it serves.

  


  require('rootpath')();
const path = require('path');
const express = require('express');
const app = express();
const bodyParser = require('body-parser');
const cookieParser = require('cookie-parser');
const cors = require('cors');

app.use(bodyParser.urlencoded({ extended: false }));
app.use(bodyParser.json());
app.use(cookieParser());

app.use(cors());


app.use(function(req, res, next) {
  res.header("Cross-Origin-Embedder-Policy", "require-corp");
  res.header("Cross-Origin-Opener-Policy", "same-origin");
  next();
});

// Have Node serve the files for our built React app
app.use(express.static(path.resolve(__dirname, 'build')));

// file api routes
app.use('/accounts', require('./accounts/accounts.controller'));

// file api routes
app.use('/files', require('./files/files.controller'));


// All other GET requests not handled before will return our React app
app.get('*', (req, res) => {
    res.sendFile(path.resolve(__dirname, 'build', 'index.html'));
});

// start server
const port = process.env.PORT || 2002;
app.listen(port, () => console.log('Server listening on port ' + port));


  


  The issue here is that I need this segment of code for my ffmpeg file upload to occur otherwise it throws a SharedArrayBuffer error :

  


     app.use(function(req, res, next) {
      res.header("Cross-Origin-Embedder-Policy", "require-corp");
      res.header("Cross-Origin-Opener-Policy", "same-origin");
      next();
    });


  


  However, when I leave this code in, another part of my program breaks down which gets presigned urls from s3 and plays audio. The issue whenever I play audios from my s3 bucket there is this :

  


  ERR_BLOCKED_BY_RESPONSE.NotSameOriginAfterDefaultedToSameOriginByCoep


  


  The s3 code is this :

  


  function getTemporaryURL({ data }) {

  const customer_id = data['customer-id'];
  const sound_id = data['sound-id'];
  
  return new Promise((resolve, reject) => {
    //get presigned url

    var myBucket = process.env.NODE_APP_BUCKET_NAME;
    var myKey = "sounds/" + customer_id + "/" + sound_id + ".wav"; 
    const signedUrlExpireSeconds = 120;
    try {
      const url = s3.getSignedUrl('getObject', {
        Bucket: myBucket,
        Key: myKey,
        ResponseContentDisposition: 'attachment',
        Expires: signedUrlExpireSeconds
      });
      resolve(url)
    }
    catch {
      console.log('S3 Object does not exist');
      resolve('');
    }
  });
}


  


  How can I modify my server.js to accommodate both of my needs ?

  


• Build ffmpeg2.4.2 with android-ndk-r9b on Winx64 ?

  14 octobre 2014, par luna

  Now, I have got libffmpeg.so on Android, but its size is only 4.96 kB, so obviously something went wrong, but I have no idea...

  Here is my config.sh :

  #!/bin/bash
  
  export TMPDIR="C:/temp"
  
  export NDKROOT="G:/android-ndk-r9b"
  
  PREBUILT=$NDKROOT/toolchains/arm-linux-androideabi-4.6/prebuilt/windows-x86_64
  
  PLATFORM=$NDKROOT/platforms/android-18/arch-arm
  
  ./configure --target-os=linux \
  
  --arch=arm \
  
  --enable-version3 \
  
  --enable-gpl \
  
  --enable-nonfree \
  
  --disable-stripping \
  
  --disable-ffserver \
  
  --enable-decoder=h264 \
  
  --disable-ffprobe \
  
  --disable-encoders \
  
  --disable-muxers \
  
  --disable-devices \
  
  --disable-protocols \
  
  --enable-protocol=file \
  
  --enable-avfilter \
  
  --disable-network \
  
  --disable-avdevice \
  
  --enable-cross-compile \
  
  --cc=$PREBUILT/bin/arm-linux-androideabi-gcc \
  
  --cross-prefix=$PREBUILT/bin/arm-linux-androideabi- \
  
  --nm=$PREBUILT/bin/arm-linux-androideabi-nm \
  
  --extra-cflags="-fPIC -DANDROID" \
  
  --disable-asm \
  
  --enable-neon \
  
  --enable-armv5te \
  
  --extra-ldflags="-Wl,-T,$PREBUILT/arm-linux-androideabi/lib/ldscripts/armelf_linux_eabi.x -Wl,-rpath-link=$PLATFORM/usr/lib
  
   -L$PLATFORM/usr/lib -nostdlib $PREBUILT/lib/gcc/arm-linux-androideabi/4.6/crtbegin.o
  
  
  
  $PREBUILT/lib/gcc/arm-linux-androideabi/4.6/crtend.o -lc -lm -ldl"

  What could the problem be ?

  What I also don’t understand : we already have a makefile - why should we make android.mk once again ?

• Install FFMPEG on android project

  4 octobre 2018, par user3884677

  I try to install FFMPEG on Android project. I follow this tutorial : https://medium.com/@karthikcodes1999/cross-compiling-ffmpeg-4-0-for-android-b988326f16f2

  When I execute the ffmpeg_android.sh file. with this code :

  #!/bin/bash
  
  NDK=$HOME/Library/Android/sdk/ndk-bundle
  
  SYSROOT=$NDK/platforms/android-19/arch-arm/
  
  TOOLCHAIN=$NDK/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64
  
  function build_one
  
  {
  
  ./configure \
  
  --prefix=$PREFIX \
  
  --enable-shared \
  
  --disable-static \
  
  --disable-doc \
  
  --disable-ffplay \
  
  --disable-ffprobe \
  
  --disable-doc \
  
  --disable-symver \
  
  --enable-protocol=concat \
  
  --enable-protocol=file \
  
  --enable-muxer=mp4 \
  
  --enable-demuxer=mpegts \
  
  --cross-prefix=$TOOLCHAIN/bin/arm-linux-androideabi- \
  
  --target-os=linux \
  
  --arch=arm \
  
  --enable-cross-compile \
  
  --sysroot=$SYSROOT \
  
  --extra-cflags="-Os -fpic $ADDI_CFLAGS" \
  
  --extra-ldflags="$ADDI_LDFLAGS" \
  
  $ADDITIONAL_CONFIGURE_FLAG
  
  make clean all
  
  make -j3
  
  make install
  
  }
  
  CPU=arm
  
  PREFIX=$(pwd)/android/$CPU
  
  ADDI_CFLAGS="-marm"
  
  build_one

  I have this error :

  /Users/christophe/Library/Android/sdk/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/darwin-x86_64/bin/arm-linux-androideabi-gcc
  is unable to create an executable file. C compiler test failed.

  If you think configure made a mistake, make sure you are using the
  latest version from Git. If the latest version fails, report the
  problem to the ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on
  irc.freenode.net. Include the log file "ffbuild/config.log" produced
  by configure as this will help solve the problem. Makefile:2 :
  ffbuild/config.mak : No such file or directory Makefile:40 :
  /tools/Makefile : No such file or directory Makefile:41 :
  /ffbuild/common.mak : No such file or directory Makefile:90 :
  /libavutil/Makefile : No such file or directory Makefile:90 :
  /ffbuild/library.mak : No such file or directory Makefile:92 :
  /fftools/Makefile : No such file or directory Makefile:93 :
  /doc/Makefile : No such file or directory Makefile:94 :
  /doc/examples/Makefile : No such file or directory Makefile:159 :
  /tests/Makefile : No such file or directory make : *** No rule to make
  target `/tests/Makefile’. Stop. Makefile:2 : ffbuild/config.mak : No
  such file or directory ...