Recherche avancée

Sur d’autres sites (3566)

• Google Cloud Platform Storage JSON API upload breaks audio files..?! How to fix ?

  13 octobre 2017, par Zolai

  I did manage to upload files to Google storage with GCP resumable upload (json api) :
  https://cloud.google.com/storage/docs/json_api/v1/how-tos/resumable-upload

  Using jQuery and Plupload http://www.plupload.com

  But now it seems that audio files loses their codecs in upload and those won’t play or ffmpeg can’t probe those. More testing showed that actually .flac files are ok to ffmpeg, but for example .m4a files are not.

  I need to get most of the audio files uploaded to google storage and be able to probe those with ffmpeg. And must be able upload big files over 100Mb. That’s why I believe JSON API is best or only possible way.

  I think I have metadata also added correctly, but now I’m confused how to continue..
  Any ideas what could be the problem here ?

  EDIT (more info) :

  I had working software :

  • Using regular POST > /temp > Google Cloud Storage Client (php).
  • GCP Storage Client uploaded files with perfection.
  • Even that I named uploaded files with random unique name like "woeiwehf.tmp", those did work and ffmpeg could probe them fine.

  THEN something happened, I guess uploading like this was limited (or something) :

  • What meant that my solution couldn’t upload anymore big files, over 32Mb.

  • Well that wasn’t best solution anyway, so that’s okey, that this changed.

  NOW :

  • I have changed software so it uses GCP JSON API upload resumable, and this mainly works
  • But I had to change files to look like "woeiwehf.flac" or what ever type is. ".tmp" didn’t work anymore.
  • For example .flac files work nicely, but .m4a will not.
  • I’ve tested uploading many different ways, and it seems that JSON API upload loses at least codecs and bit rate.

  —

  I would be very grateful if I could get help how to resolve this.
  I guess one solution may could be to fork ffmpeg client and manually set audio codec, but I’m saving that for the last solution.

• Undefined reference to av_log

  12 novembre 2017, par Dana Prakoso

  I am cross-compiling FFMPEG source in Linux for Windows using i686-w64-mingw32 using this script :

  ../ffmpeg/configure --disable-ffmpeg --disable-ffprobe --disable-ffplay --disable-shared --enable-static --arch=x86 --target-os=mingw32 --cross-prefix=i686-w64-mingw32- --enable-cross-compile

  And it generates all static library files with extension *.a inside "lib" folder. Then I try to link those libraries with my own source, with this script :

  i686-w64-mingw32-gcc -m32 -c videoplayer.c -o videoplayer.o -w $(INCLUDEDIR) -Wl,--add-stdcall-alias
  
  i686-w64-mingw32-gcc -static -m32 -o libvideoplayer.dll videoplayer.o -Wl,--out-implib,libvideoplayer_dll.lib -Wl,--add-stdcall-alias -L../../ffmpeg/lib -lavdevice -lavformat -lavcodec -lavutil -lwsock32 -lswresample ../../ffmpeg/lib/libWs2_32.lib

  And I got this bunch of error messages :

  ../../ffmpeg/lib/libavformat.a(rtpproto.o): In function `rtp_resolve_host':
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/rtpproto.c:140: undefined reference to `_imp__getaddrinfo@16'
  
  ../../ffmpeg/lib/libavformat.a(rtpproto.o): In function `rtp_parse_addr_list':
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/rtpproto.c:282: undefined reference to `_imp__freeaddrinfo@4'
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/rtpproto.c:277: undefined reference to `_imp__freeaddrinfo@4'
  
  ../../ffmpeg/lib/libavformat.a(tcp.o): In function `tcp_open':
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/tcp.c:112: undefined reference to `_imp__getaddrinfo@16'
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/tcp.c:114: undefined reference to `_imp__getaddrinfo@16'
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/tcp.c:177: undefined reference to `_imp__freeaddrinfo@4'
  
  /home/dana/Sources/build-ffmpeg/src/libavformat/tcp.c:192: undefined reference to `_imp__freeaddrinfo@4'

  How do I resolve this ? Do I miss something in my script ? Big thanks for someone replying.

• Evolution #3560 : Supprimer l’option expérimentale Google Closure Compiler

  4 mai 2017, par b b

  Super, merci mignon :)