Recherche avancée

Sur d’autres sites (4842)

• avformat/hls : ignore http_persistent for segments requring crypto

  30 décembre 2017, par Aman Gupta

  avformat/hls : ignore http_persistent for segments requring crypto
  Encrypted HLS segments have regular http:// urls, but open_input()
  
  actually prefixes them with crypto+ before calling open_url(), so
  
  they end up using the crypto protocol and not the http protocol.
  This means invoking ff_http_do_new_request will fail, so we avoid
  
  calling it in the first place. After the earlier http.c commit,
  
  the failure results in a warning printed to the user. In earlier
  
  versions, the failure would cause a segfault.
  Signed-off-by : Aman Gupta <aman@tmm1.net>
  

  • [DH] libavformat/hls.c

• FFmpeg adds green hue to video when using multiply blend mode

  19 octobre 2023, par dev_12092

  When using the multiply blendmode with a jpg overlay image I get a green hue being applied to the video :

  


  FFMPEG adds green hue when using multiply blendmode

  


  Command :
ffmpeg -i gen_video/output_vid.mp4 -i "D:\Downloads\Video_bot\forced_alignment_test\subtitles\audio.mp3" -i background.mp3 -i gen_video/input.jpg -filter_complex "fade=t=out:st=200:d=1,format=rgba[vid];[vid][3:v]overlay=(main_w-overlay_w)/2:(main_h-overlay_h)/2:format=gbrp[outv],[0:v][3:v]blend=all_mode='multiply':all_opacity=1,[1:a][2:a]amerge=inputs=2[outa]" -t 10 -map "[outv]" -map "[outa]" -ac 1 final_output.mp4

  


  What I've tried :

  


  

  • using : format=gbrp and format=rgba as mentioned in other posts
It sadly didn't fix the issue.

  


  


  I tried to use an overlay effect along with the multiply blendmode with FFMPEG, I was expecting a regular output video, instead it had a green hue.

  


• Efficiently concatenating & crossfading .ts files with FFMPEG

  11 septembre 2019, par dooman

  I would like to efficiently crossfade multiple transport files together into an m4a file. This means segmenting files, crossfading the 3 seconds at the beginning/end of consecutive transport files, then concatenating the subsets & newly crossfaded overlaps together, to minimize the decoding/re-encoding.

  Gyan provides a solution that correctly crossfades a list of audio files. I was able to modify this program to produce the correct output m4a file for my purposes. However, this requires re-encoding the entirety of each audio file. To crossfade 10 audio files (between 3-5 minutes in length each), this solution runs for 8-12 seconds, which does not meet the criteria for serving this audio for my real time/live stream use case.

  To avoid this decoding/recoding bottleneck, I’ve written a program to segment each transport file, crossfade the overlaps, then concatenate all of the relevant components. This program runs within 1-2 seconds for the 10 audio file case above, which does meet my real time use case.

  Below is an abbreviated version that concatenates two 10 second transport files (a.ts, b.ts). These files are AAC encoded, in mono, and just contain sine saves at different frequencies.

  ffmpeg -i a.ts -map 0 -f segment -segment_times 7 -c:a copy a_%d.ts
  
  ffmpeg -i b.ts -map 0 -f segment -segment_times 3 -c:a copy b_%d.ts
  
  
  
  ffmpeg -i a_1.ts -i b_0.ts -filter_complex acrossfade=d=3:c1=qua:c2=qua xfade.m4a
  
  ffmpeg -i xfade.m4a -c:a copy xfade.ts
  
  
  
  ffmpeg -i "concat:a_0.ts|xfade.ts|b_1.ts" -c:a copy out.m4a

  Note that crossfading the two overlapping 3 second files (a_1.ts and b_0.ts) requires writing to .m4a, then converting back to .ts. Attempting to crossfade -> .ts, or concatenate .ts and .m4a files resulted in unplayable audio or missing audio within the out.m4a file.

  This program produces an audio file that is almost correct (17 seconds of audio, 3 second crossfade between the two files). Below is an image of the wave form. The top is the waveform produced by regular crossfade, with encoding of the entire files (Gyan’s solution) for comparison. The bottom is produced by my program.

  
  Note that are ’artifacts’ introduced at the boundaries of the crossfade. These little gaps cause the audio file to "dip" in volume at the beginning of the crossfade, and there is a click at the end of the crossfade. These artifacts are NOT present for the regular, inefficient crossfade.

  My questions are :

  • What is causing these artifacts to be introduced ?
  • Examining the xfade.m4a waveform reveals that there is a slight ramp up added to the beginning, but the ffmpeg documentation doesn’t reference this. Is this a consequence of muxing/demuxing when converting between .ts / .m4a ?
  • This extra ramp up doesn’t account for the clip at the end. Does that concatenation is also introducing artifacts to these .ts files ?

  Thanks to anyone who reads this.

  EDIT : I should add that these artifacts are present no matter what segment times / audio files are used as input. The artifacts also appear to be deterministic ; they also appear at the exact same times for the exact same inputs.