Recherche avancée

Sur d’autres sites (5911)

• 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.

• Merge commit '421c10ed4fb0475a2cb055dd130ba12a6adb9f70'

  11 novembre 2017, par James Almer

  Merge commit '421c10ed4fb0475a2cb055dd130ba12a6adb9f70'
  * commit '421c10ed4fb0475a2cb055dd130ba12a6adb9f70' :
  
    configure : Drop test for fork()
  We keep the check as it's needed by the http_multiclient example.
  Merged-by : James Almer <jamrial@gmail.com>
  

  • [DH] configure

• FFmpeg vs Libav vs libVLC as of 2018

  25 avril 2018, par Dharma

  I am trying to do some video processing on real time. I was beginning to try the FFmpeg, but I saw this question :

  Why would I choose Libav over FFmpeg, or is there even a difference ?

  Which further links to this question :

  What are the differences and similarities between ffmpeg, libav, and avconv ?

  and this blog post :

  http://blog.pkh.me/p/13-the-ffmpeg-libav-situation.html

  After reading this I came to know that Libav is a fork from FFmpeg and is being developed separately. I am need of developing C++ application using either Libav or FFmpeg or libVLC. I think there has been a lot of changes after these questions are answered. It would be great to have some benchmark on these tools.

  Do you guys have any preference of one over another, any benchmark results for video and audio processing ? I need to process frames fast and stream a video to multiple C++ applications, what would be the best way to solve this problem and what will be the best tool to choose ?

  So as of 2018 what is the current status of these tools on video processing.
  It would be nice to know some results from the people working on video processing who are familiar with these tools.