Recherche avancée

Sur d’autres sites (5232)

• ffmpeg do stream copy together with draw text

  8 mars 2016, par Haris

  I need to record an RTSP stream, before storing it I need draw some text on the video.

  And the below command works fine for recording stream only(no text write).

  openRTSP -D 10 -v -t -c -b 800000 rtsp://video_link.mov | ./ffmpeg -r 15 -i - -codec copy -hls_list_size 65535 -hls_time 2 "./video/live.m3u8"

  But I also need to draw some text on the video before recording. So I re-write the above command like

  openRTSP -D 10 -v -t -c -b 800000 rtsp://video_link.mov | ./ffmpeg -r 15 -i - -vf drawtext="fontfile=/usr/share/fonts/truetype/freefont/FreeMonoBold.ttf: text='Stack Overflow': fontcolor=white: fontsize=24: box=1: boxcolor=black: x=(w-text_w)/2: y=(h-text_h-line_h)/2" -codec copy -hls_list_size 65535 -hls_time 2 "./video/live.m3u8"

  But giving the error like,

  input #0, h264, from 'pipe:':
  
    Duration: N/A, bitrate: N/A
  
      Stream #0:0: Video: h264 (High), yuv420p, 704x480, 25 fps, 25 tbr, 1200k tbn, 50 tbc
  
  Filtergraph 'drawtext=fontfile=/usr/share/fonts/truetype/freefont/FreeMonoBold.ttf: text='Stack Overflow': fontcolor=white: fontsize=24: box=1: boxcolor=black: x=(w-text_w)/2: y=(h-text_h-line_h)/2' was defined for video output stream 0:0 but codec copy was selected.
  
  Filtering and streamcopy cannot be used together.

  I understand that both recording and drawing cannot perform together.
  Any method exist similar, to solve the above problem ?.

• avcodec/mpeg12dec : extract only one type of CC substream

  12 mars 2024, par Marth64

  avcodec/mpeg12dec : extract only one type of CC substream
  In MPEG-2 user data, there can be different types of Closed Captions
  
  formats embedded (A53, SCTE-20, or DVD). The current behavior of the
  
  CC extraction code in the MPEG-2 decoder is to not be aware of
  
  multiple formats if multiple exist, therefore allowing one format
  
  to overwrite the other during the extraction process since the CC
  
  extraction shares one output buffer for the normalized bytes.
  This causes sources that have two CC formats to produce flawed output.
  
  There exist real-world samples which contain both A53 and SCTE-20 captions
  
  in the same MPEG-2 stream, and that manifest this problem. Example of symptom :
  
  THANK YOU (expected) —> THTHANANK K YOYOUU (actual)
  The solution is to pick only the first CC substream observed with valid bytes,
  
  and ignore the other types. Additionally, provide an option for users
  
  to manually "force" a type in the event that this matters for a particular
  
  source.
  Signed-off-by : Marth64 <marth64@proxyid.net>
  

  • [DH] libavcodec/mpeg12dec.c

• Back on the Salty Track

  12 juin 2011, par Multimedia Mike — General

  After I posted about my initial encounter and frustration with Google’s Native Client (NaCl) SDK and took a deep breath, I realized that I achieved an important proof of concept— I successfully played music using the NaCl SDK audio output interface. Then I started taking a closer read through the (C-based set of) header files and realized I might be able to make a go of it after all. I had much better luck this time and managed to create a proper Native Client interface that allows for controlling playback, presenting metadata, and toggling individual voices (a fascinating tool for studying classic game music).

  I haven’t bothered to post the actual plugin because, really, what’s the point ? I started with NaCl SDK 0.3 which requires Chrome 12, which means terribly limited reach, even among Chrome users. At least, that was true when I restarted this little project. Chrome 12 was formally released this past week. Chrome development really does move at breakneck pace.

  Anyway, here is a static screenshot of what the plugin currently looks like :

  
  
  

  Not pretty, but it does the job.

  Dev Journal
  Various notes based on this outing :

  • Portability : I tested my plugin using Chrome 12 on 64-bit Windows, Mac, and Linux. Mac and Linux both work ; Windows does not.
  • Build System : SDK 0.3 is still lacking in its ability to compile .cpp files (instead of .cc files) ; necessary because libgme is C++ using .cpp files. This requires some build system modification.
  • Getting the interfaces : This is where I got tripped up the first time around. get_browser_interface() from their example actually refers to a parameter passed in through the PPP_InitializeModule() function. The SDK’s template generator renames this to get_browser().
  • Debugging : I feel unstoppable once I have a printf() mechanism available to me during development. To that end, console.log() from JavaScript outputs to Chrome’s built-in JavaScript console log while putting printf() statements in the actual NaCl plugin causes the messages to show up in /.xsession-errors on Linux/X.
  • Size Matters : The binaries generated with the NaCl 0.3 SDK are ridiculously huge. The basic "Hello World" example in C compiles to binaries that are 6.7 MB and 7.8 MB for the 32- and 64-bit builds, respectively. This made me apprehensive to build a full version of SaltyGME that contains all the bells and whistles offered by the library. However, all of the GME code compiled into the binary adds very little size. Curiously, the C++ version of "Hello World" only ranges from 1.8-2.0 MB for 32- and 64-bit. Is there some kind of C tax happening here ? Note that running ’strip’ on the resulting .nexe files (they’re ELF files, after all) brings the sizes down into the C++ range, but at the cost of causing them to not work (more specifically, not even load).
  • No Messaging : The NaCl SDK is supposed to have a messaging interface which allows the NaCl plugin to send asynchronous messages up to the hosting page. When I try to instantiate it, I get a NULL. I’m stuck with the alternative of polling from the JavaScript side to, e.g., determine when a song has finished loading via the network.

  That’s all I can think of for now. I may work on this a little more (I’d like to at least see some audio visualization). Maybe Google will enable NaCl per default sometime around Chrome 21 and this program will be ready for prime time by then.

  See Also :

  • My first attempt at this same project