Recherche avancée

Sur d’autres sites (5987)

• lavc/flacdsp : do not assume maximum R-V VL

  24 mai 2024, par Rémi Denis-Courmont

  lavc/flacdsp : do not assume maximum R-V VL
  This loop correctly assumes that VLMAX=16 (4x128-bit vectors
  
  with 32-bit elements) and 32 >= pred_order > 16. We need to alternate
  
  between VL=16 and VL=t2=pred_order-16 elements to add up to pred_order.
  The current code requests AVL=a2=pred_order elements. In QEMU and on
  
  thte K230 hardware, this sets VL=16 as we need. But the specification
  
  merely guarantees that we get : ceil(AVL / 2) <= VL <= VLMAX. For
  
  instance, if pred_order equals 27, we could end up with VL=14 or VL=15
  
  instead of VL=16. So instead, request literally VLMAX=16.
  

  • [DH] libavcodec/riscv/flacdsp_rvv.S

• How to fix "Cannot find a valid font for the family Sans' while adding text on image using react-native-ffmpeg

  13 mai 2024, par coffee

  I am trying to add text on image using the code below
RNFFmpeg
.execute(`-y -i ${input} -vf "drawtext=text='Hello World':fontcolor=white:fontsize=75:x=0:y=0" ${output}`) ;

  


  I am not using any custom font but still get this error.

  


  Error :

  


  [Parsed_drawtext_0 @ 0x7f87a1ce40] Cannot find a valid font for the family Sans

  


  index.js:115 [AVFilterGraph @ 0x7f6765e760] Error initializing filter 'drawtext'
index.js:115 [AVFilterGraph @ 0x7f6765e760] with args 'text=Hello World:fontcolor=white:fontsize=75:x=0:y=0'
index.js:115 [AVFilterGraph @ 0x7f6765e760]

  


  index.js:115 Error reinitializing filters !

  


  index.js:115 Failed to inject frame into filter network : No such file or directory

  


  index.js:115 Error while processing the decoded data for stream #0:0

  


  Note :

  


  I also tried using a custom font but not able to do it.
When I use RNFFmpegConfig.setFontDirectory('../../assets/fonts') function and with it the following code to add text on image
RNFFmpeg
.execute(`-y -i ${input} -vf "drawtext=text='Hello World':fontfile='../../assets/fonts/MyFont.ttf':fontcolor=white:fontsize=75:x=0:y=0" ${output}`) ;

  


  It gives me the same error.

  


  How can I fix this issue.

  


• FFplay : WASAPI can't initialize audio client (FFmpeg 3.4 binaries)

  9 juillet 2022, par fve

  I am trying to playback a stream that is multicasted over RTP using ffplay on Windows 7 64 bits.
The computer that serves the audio over RTP runs :

  



  ffmpeg -re -f dshow -audio_buffer_size 15 -ac 1 -i audio="Mic in at front Mic-in (Realtek" -ar 8k -acodec pcm_alaw -vn -f rtp rtp://127.0.0.1:5000


  



  The client runs :

  



  ffplay rtp://127.0.0.1:5000


  



  While this was working correctly in release 3.3, release 3.4 fails with this error :

  



  SDL_OpenAudio (1 channels, 8000 Hz): WASAPI can't initialize audio client: CoInitialize has not been called.

No more combinations to try, audio open failed
Failed to open file 'rtp://127.0.0.1:5000' or configure filtergraph


  



  Anyone has an idea of whats going on ?

  



  Thanks

  



  UPDATE #1 :

  



  A workaround is to specify an alternate output driver.
Set SDL_AUDIODRIVER environment variable value to the driver you want to use.
Under windows 7, directsound and winmm both solved my issue.