Recherche avancée

Sur d’autres sites (13929)

• Why is this ffmpeg conversion turning up trash ?

  12 octobre 2015, par DigitalJedi805

  So, the company I work for still archives some of our data in Windows Media format.

  I’ve written a C# application that loops through all of our WMVs, and in the event that a corresponding MP4 doesn’t exist, it fires off ffmpeg to convert the file.

  What I’m running into, is a combination of problems.

  When I run the following into ffmpeg ( rough C# ) :

  "-i " + File.FullName + " -vf scale=720:480 -b:v 512k -bufsize 512k -vcodec libx264 -acodec aac -strict experimental " + OutputPath

  I end up with a file that cannot play in our browser based player ( JWPlayer ), and cannot play on my local system in Windows Media Player.

  Additionally, the file is larger than my WMV, and is larger than the file I output with [roughly] the same parameters in AVS Video Converter.

  Furthermore, the file details don’t show any values for the video properties - as in, when I right click and go to properties->details, under ’video’, there is a list of length, height, width, frame rate, and bitrate - they are all empty - when I would very much expect some data normally.

  Does anyone have any idea how I can make the conversion more straightforward, or what might be creating the problem in the first place ?

  I’ve tried running this without scaling or bitrate parameters, and added them as an attempt to resolve the more core problem - obviously to no avail.

  For everyone’s appeasement...

  FFMPEG Output :

  video:537604kB audio:158748kB subtitle:0kB other streams:0kB global headers:0kB
  
  muxing overhead: 1.159483%
  
  [libx264 @ 0453d000] frame I:1234  Avg QP:19.98  size: 33645
  
  [libx264 @ 0453d000] frame P:94430 Avg QP:22.92  size:  3984
  
  [libx264 @ 0453d000] frame B:208152 Avg QP:30.67  size:   638
  
  [libx264 @ 0453d000] consecutive B-frames:  7.6%  1.8%  4.0% 86.6%
  
  [libx264 @ 0453d000] mb I  I16..4: 10.5% 61.2% 28.2%
  
  [libx264 @ 0453d000] mb P  I16..4:  0.4%  1.4%  0.3%  P16..4: 26.8%  9.3%  4.8%
  
   0.0%  0.0%    skip:57.0%
  
  [libx264 @ 0453d000] mb B  I16..4:  0.0%  0.0%  0.0%  B16..8: 21.6%  1.1%  0.2%
  
   direct: 0.4%  skip:76.6%  L0:42.6% L1:55.1% BI: 2.3%
  
  [libx264 @ 0453d000] 8x8 transform intra:65.1% inter:71.9%
  
  [libx264 @ 0453d000] coded y,uvDC,uvAC intra: 61.6% 59.3% 30.9% inter: 6.0% 6.7%
  
   1.7%
  
  [libx264 @ 0453d000] i16 v,h,dc,p: 34% 52%  7%  7%
  
  [libx264 @ 0453d000] i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 23% 27% 24%  3%  4%  4%  5%
  
   4%  7%
  
  [libx264 @ 0453d000] i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 27% 38% 10%  3%  5%  4%  6%
  
   3%  5%
  
  [libx264 @ 0453d000] i8c dc,h,v,p: 47% 35% 14%  4%
  
  [libx264 @ 0453d000] Weighted P-Frames: Y:0.2% UV:0.1%
  
  [libx264 @ 0453d000] ref P L0: 67.8% 12.3% 14.3%  5.6%  0.0%
  
  [libx264 @ 0453d000] ref B L0: 88.7%  9.7%  1.6%
  
  [libx264 @ 0453d000] ref B L1: 92.6%  7.4%
  
  [libx264 @ 0453d000] kb/s:434.44

  I’ll make the video files available shortly.

• YUV8_420P - AVFrame conversion hazard (only Y plan)

  4 mai 2017, par Flow

  I’m working on a FFMPEG application. The goal is to convert a picture (YUV input format) to an AVFrame to be able to process it (by applying a specific filter) and then realize the invert conversion to redirect it to the output.

  Although some filters as drawgrid or noise are perfectly working, filters which apply some "space transformation" (as a "crop" or a "hflip") seem to affect only over the Y component. The colors of the output pictures aren’t filtered which leads to an unsatisfying result.

  I’m asking myself why I have such a result but I didn’t reach to find the problem origin.

  Here is the part of cod which convert the YUV picture to an AVFrame :

  unsigned int i = 0;
  
  int number_common_channels = MIN(IMAGEFORMAT_COMPONENTS, AV_NUM_DATA_POINTERS);
  
  
  
  // Transfer the image informations (width, height, pitch and data)
  
  if ((av_im->width = yuv_im->width[0]) <= 0)
  
  {
  
      cu_printf(ERROR, "Width of destination picture null or negative");
  
      return -1;
  
  }
  
  if((av_im->height = yuv_im->height[0]) <= 0)
  
  {
  
      cu_printf(ERROR, "Height of destination picture null or negative");
  
      return -1;
  
  }
  
  for (i=0; i < number_common_channels; i++)
  
  {
  
      av_im->linesize[i] = yuv_im->pitch[i];
  
      av_im->data[i] = yuv_im->data[i];
  
  }

  If necessary, I can transmit you other parts of the cod where the problem could be. Thanks for your cooperation.

  Flow.

  EDIT 1 : After some researches, it would be possible the problem came from my function which initializes the filter graph. Actually, I used the FFMPEG example given on their website to make it and I deleted the options to the pixel format list because I thought it was useless. It’s possible this function and more precisely the av_opt_set_int_list could be the key, but I don’t reach to find a good example using it. Also, another function, av_opt_set_pixel_fmt was created in the last FFMPEG versions and this could be well to try using it, but I don’t know how to do. So please if someone has a good example with that, I’ll took it with hapiness.

  EDIT 2 : The problem came from the way I copied my data back after the filter was applied. Closed.

• What google cloud service can be used to process files stored in Firebase Cloud Storage with FFmpeg ? [closed]

  1er mai 2021, par uponly

  I am building a ReactJs app and I am trying to figure out a way to process files (images, videos, and audio of any type) that are stored in my Firebase storage bucket using FFmpeg. Currently, I have set up the functionality for allowing the user to upload files to my storage bucket, and a corresponding URL link is stored in a document in Firestore.

  


  Ideally, I'd love to do this with Cloud Functions HTTP triggers because I have all of that setup already. It would be nice to just call an HTTP trigger to process the file after it has been uploaded. However, after a bit of research, my current understanding is to somehow deploy my app using a flexible Google App Engine environment because apparently, it is the only way to set a manual timeout in case I have to process a long, high-quality video, for example. Thus I wouldn't be able to use Cloud Functions because there is a very short timeout period which may lead to the files not being fully processed.

  


  Here is the user flow I am trying to achieve, which may help make things more clear :

  


  

  1. [Done] The user uploads a file (image, audio, or video) to Firebase cloud storage. A URL is also stored in their corresponding user document in Firestore.

  


  2. [Here and the steps onward are what I am trying to achieve] After the file has been stored, I'd like to kick off some sort of function that grabs the newly stored file and begin to process it in the cloud.

  


  3. Store the newly processed file back into the Cloud Storage bucket

  


  4. Allow the user to preview the processed file (by streaming it ideally, if possible).

  


  


  In steps 2 and onward, I am just generally confused about what Google service I should be using to process my file in the cloud with FFmpeg. As well as how I can connect it to my React app, client-side. If I have to go the Google App Engine route, how do I go about connecting app engine to my React App such that I don't have to build my app and deploy it, as my app is still in development ?

  


  This is not a coding question so I apologize if this is the wrong place to post in. I am new to all this, any and all help is greatly appreciated. Thank you.