Recherche avancée

Sur d’autres sites (6261)

• AVPlayer won't play audio files from FFMPEG

  18 janvier 2021, par Marcus

  Before requesting audio data AVPlayer requests byte range 0-1 from FFMPEG.

  


  FFMPEG gives a 200 response, but AVPlayer requires a 206 response.

  


  This results in the request failing and audio can't be played.

  


  Expected behavior :
Play tracks when streaming through ffmpeg

  


  Current behavior : When trying to stream with ffmpeg we get "Operation Stopped"

  


  Sample FFMPEG command :

  


  ffmpeg -i "/path/to/audio/track.mp3" -vn -strict -2 -acodec pcm_u8 -f wav -listen 1 -seekable 1 http://localhost:8090/restream.wav


  


  Player Log :

  


  Error Domain=AVFoundationErrorDomain Code=-11850 "Operation Stopped" UserInfo={NSLocalizedFailureReason=The server is not correctly configured., NSLocalizedDescription=Operation Stopped, NSUnderlyingError=0x600003bcc4b0 {Error Domain=NSOSStatusErrorDomain Code=-12939 "(null)"}}
!av_interleaved_write_frame(): Broken pipe

!Connection to tcp://localhost:8090 failed: Connection refused

!Connection to tcp://localhost:8090 failed: Connection refused

!Connection to tcp://localhost:8090 failed: Connection refused

!Error writing trailer of http://localhost:8090/restream.wav: Broken pipe


  


  This error is defined by Apple as :

  


  +"The HTTP server sending the media resource is not configured as expected. This might mean that the server does not support byte range requests."


  


  And summarised nicely in this StackOverflow post :

  


  when AVPlayerItem receive a video URL , it do the following task:

    Send a bytes request HTTP Request, and range = 0 -1
    If the response code is 206 and return 1 bytes data, It do the 3th task, if not, AVErrorServerIncorrectlyConfigured error occurred.
    continue send other HTTP Request, to download segment of All duration. and the response of VideoData code must be 206

In my situation , when send range[0-1] HTTP request, the server side give me a 200 OK response, So error occurred.


  


  Network Log :

  


  GET /file.wav HTTP/1.1
Host: localhost:1234
X-Playback-Session-Id: F72F1139-6F4C-4A22-B334-407672045A86
Range: bytes=0-1
Accept: */*
User-Agent: AppleCoreMedia/1.0.0.18C61 (iPhone; U; CPU OS 14_3 like Mac OS X; en_us)
Accept-Language: en-us
Accept-Encoding: identity
Connection: keep-alive

HTTP/1.1 200 OK
Content-Type: application/octet-stream
Transfer-Encoding: chunked


  


  Reproduce using this sample app :

  


  This can also be reproduced using standard ffmpeg and adding URL to local or remote ffmpeg URL

  


  Can we solve this by making changes to FFMPEG or AVPlayer ?

  


• avformat/flacenc : Fix memleak when writing attached pictures fails

  20 novembre 2020, par Andreas Rheinhardt

  avformat/flacenc : Fix memleak when writing attached pictures fails
  The FLAC muxer currently stores an attached picture corresponding to an
  
  AVStream in AVStream.priv_data. The AVPacket contained therein is
  
  unreferenced after it has been written. The AVPacket structure itself is
  
  then freed generically as AVStream.priv_data.
  And this can lead to memleaks if an attached picture is not written :
  
  It might be because the trailer is never written or because writing
  
  a previous attached picture failed in case error_recognition is set
  
  to explode.
  Therefore free the packets properly (i.e. with av_packet_free())
  
  in the muxer's deinit function.
  Signed-off-by : Andreas Rheinhardt <andreas.rheinhardt@gmail.com>
  

  • [DH] libavformat/flacenc.c

• FFMPEG when live streaming sends a message and exits after some frames were sent

  30 octobre 2020, par jstuardo

  when doing an streaming with FFMPEG all works perfectly until I get these messages and then, ffmpeg.exe exits :

  


  av_interleaved_write_frame(): Unknown error

frame= 1224 fps=3.4 q=13.0 size=    2758kB time=00:01:21.94 bitrate= 275.8kbits/s speed=0.226x    

av_interleaved_write_frame(): Unknown error

[flv @ 000001e310e8a1c0] Failed to update header with correct duration.

[flv @ 000001e310e8a1c0] Failed to update header with correct filesize.

Error writing trailer of rtmp://example.com/s/2b32abdc-130c-43e5-997e-079e69d1fd7f: Error number -10053 occurred

frame= 1224 fps=3.4 q=13.0 Lsize=    2758kB time=00:01:21.98 bitrate= 275.6kbits/s speed=0.226x    

video:2481kB audio:221kB subtitle:0kB other streams:0kB global headers:0kB muxing overhead: 2.084671%

[libx264 @ 000001e310ad6080] frame I:41    Avg QP:10.29  size: 57664

[libx264 @ 000001e310ad6080] frame P:1183  Avg QP:13.52  size:   148

[libx264 @ 000001e310ad6080] mb I  I16..4: 100.0%  0.0%  0.0%

[libx264 @ 000001e310ad6080] mb P  I16..4:  0.1%  0.0%  0.0%  P16..4:  0.2%  0.0%  0.0%  0.0%  0.0%    skip:99.7%

[libx264 @ 000001e310ad6080] coded y,uvDC,uvAC intra: 10.9% 7.1% 5.4% inter: 0.0% 0.1% 0.0%

[libx264 @ 000001e310ad6080] i16 v,h,dc,p: 84%  6%  6%  4%

[libx264 @ 000001e310ad6080] i8c dc,h,v,p: 91%  6%  3%  1%

[libx264 @ 000001e310ad6080] kb/s:248.98

[aac @ 000001e310a46d40] Qavg: 108.454

Conversion failed!


  


  Normally, the messages I received are similar to this :

  


  frame= 1196 fps=3.4 q=13.0 size=    2692kB time=00:01:20.08 bitrate= 275.4kbits/s speed=0.227x    


  


  Which are the expected messages. Sometimes, I received this message, but this does not cause ffmpeg.exe to exit :

  


  Input #0, matroska,webm, from 'pipe:':

  Metadata:

    encoder         : Chrome

  Duration: N/A, start: 0.000000, bitrate: N/A

    Stream #0:0(eng): Audio: opus, 48000 Hz, mono, fltp (default)

    Stream #0:1(eng): Video: h264 (Constrained Baseline), yuv420p(progressive), 1920x1080, SAR 1:1 DAR 16:9, 30.30 fps, 14.99 tbr, 1k tbn, 60 tbc (default)


  


  What may be happening ? maybe it is a problem of the RTMP server ? or something is wrong with FFMPEG ?

  


  This version of FFMPEG.EXE is for windows. The programming language is C# from where I am launching FFMPEG.EXE process.

  


  As I told, this happens after several frames sent to the server. Only once, this problem occured after a few frames sent. That is why I suspect that the RTMP server is the problem.

  


  EDIT : This is the command :

  


  FFMPEG -i - -c:v libx264 -preset ultrafast -tune zerolatency -max_muxing_queue_size 1000 -bufsize 5000 -r 15 -g 30 -keyint_min 30 -x264opts keyint=30 -crf 25 -pix_fmt yuv420p -profile:v baseline -level 3 -c:a aac -b:a 22k -ar 22050 -f flv rtmp://rtmp.xxxx.yyyy


  


  Regards
Jaime